GGSight works by reading visible screen text only. It does not read game memory, inspect network packets, inject overlays, or reveal hidden player data. Use this guide to configure it for the screen area where gamer tags are actually visible.
Go to the download page and choose the Windows bundle for the best current experience. The macOS and Linux bundles are available for testing, OCR validation, and future desktop support.
After downloading, extract the zip before running any install script. Do not run GGSight from inside the compressed zip window.
Open PowerShell in the extracted folder and run the installer script shown in the download instructions. The installer copies the desktop app into the GGSight runtime folder, creates the desktop/start-menu shortcut when allowed, and uses the GGSight icon for the app.
If Windows warns about an unsigned beta build, only continue if you downloaded it from the official GGSight download link and you understand this is an MVP beta. Signed installers are the safer packaging step for public release.
On first launch, read and accept the legal and safety agreement. The app is for personal screen-only gamer-tag detection and public profile lookup. Do not use it to harass players, bypass privacy settings, cheat, or violate game/platform rules.
Choose the game you are testing from the Game menu. GGSight changes the default scan-zone list based on the game. Fortnite and Call of Duty need different scan areas because their names appear in different places.
For Fortnite, place the scan zone over the visible kill feed and bus-driver feed area. The Fortnite kill-feed parser is tuned to read the left-side actor name, such as MattTheo_ in MattTheo_ eliminated SexyNutella_. It does not save the red/right-side target unless that player later appears on the left side in a new line.
Bus-driver lines such as TTV_BlazeKing thanked the bus driver are still captured because the player name appears before the action phrase.
For Call of Duty, names often appear on the right side while finding a match. Use the Right lobby roster or Lobby activity scan zone over the player list, not the left side of the screen.
The roster parser handles rows with levels, clan tags, and spaced names, such as 36 [LAZY] vilemutt, 5 [LAZY] Ghostfridge19, and 55 [666] Lana Del Thick. It ignores labels such as LOBBY and SEARCHING FOR PLAYERS.
For PS5 and Xbox, run the game on the console and show the gameplay on the PC through a capture card preview, OBS preview, PS Remote Play, or Xbox Remote Play. GGSight runs on the PC and scans the visible preview window.
GGSight does not install on the console and does not access console system data. It only reads the visible screen pixels displayed on the PC.
Use the Test button with a screenshot first. Confirm the Last OCR Read area contains player names and not only random HUD labels. If it reads the wrong text, reset the game zone or draw a smaller scan box around the exact list/feed.
Click Start Scan after the zone is correct. GGSight waits for repeated OCR evidence across multiple frames before saving a player. This reduces false reads from blur, motion, and UI effects.
Once a name is saved in the current match/session, GGSight skips duplicate saves and duplicate lookups for that same normalized gamer tag.
A detected name is not automatically a verified identity. GGSight should only notify when there is meaningful signal, such as a verified GGSight profile, supported public tracker match, creator-source match, repeat encounter, marked player, or confidence threshold.
If lookup providers are not configured, the app can still detect and record visible names locally, but it should not claim a real creator or public identity match without evidence.
Use popup settings to choose dashboard/native alerts, color, position, duration, compact mode, and confidence display. Raising confidence thresholds reduces popup noise during crowded lobbies.
Use local-only mode, lookup disable, username blocklist, player deletion, match deletion, and full history deletion if you do not want local encounter records kept. Avoid sharing screenshots or player data outside your own lawful and platform-compliant use.
If no names are detected, make the scan box smaller, increase text size in the game if possible, avoid blurry motion, test with a screenshot, and confirm the selected game matches the scan zone. For COD finding-match screens, use the right-side lobby roster. For Fortnite feeds, use the left-side kill-feed/bus-driver area.