Give Fortnite gamer tags a clean OCR path.
Fortnite names appear in several places, but they do not all have the same size, contrast, or motion. Use the preset as a starting point, then tune each scan zone around the exact window and HUD layout on your computer.
1. Open the source you will actually scan
PC players can scan the Fortnite window. Console players need a visible capture-card preview, OBS preview, PS Remote Play window, or Xbox Remote Play window on the computer running GGSight. The scanner does not install on a console.
2. Keep the source readable
Use a sharp 1080p or higher image when possible. Avoid shrinking a full game frame into a small browser or preview window. Low bitrate streams, heavy compression, and motion blur can turn short gamer tags into unstable text.
3. Select the Fortnite preset
The preset starts with name-bearing areas such as the bus-driver feed, elimination feed, and match results. Presets are guides, not universal coordinates. Resolution, aspect ratio, HUD scale, language, and window borders can move the real text.
4. Tighten each scan zone
Draw around the gamer-tag text itself. Exclude the minimap, player count, damage values, rank columns, weapon labels, and scrolling chat. A narrow zone is faster and less likely to interpret a number or interface label as a name.
5. Run the screenshot test
Pause on a frame with a readable name and use the screenshot test before live play. Check that the candidate preserves letters, numbers, underscores, periods, and creator markers such as TTV or YT. Adjust the zone if nearby words enter the result.
6. Review source-labeled results
During scanning, raw OCR does not equal a verified profile. A result should identify the supported public source that returned it. Use Wrong profile or Unsure when a public account does not appear connected to the player visible in the game.
Bus-driver feed
Useful early in a match when names are readable and the background is stable. Keep the zone away from player counts and other nearby HUD numbers.
Elimination feed
Names may move quickly and appear beside verbs, icons, or weapon text. Use a tight name area and let multiple frames agree before lookup.
Match results
A stable post-match screen can provide larger text and more review time. Keep direct profile decisions in the post-match workflow when extra context is available.
Live streams and recorded video
The scanner can read visible text from a video window, but compression and overlays may reduce accuracy. Only use content you are allowed to view, and follow the GGSight Stream Sniping Policy.
When names do not look right.
Only numbers appear
Move the zone away from counters, ranks, scores, and damage columns. A gamer-tag zone should contain at least one plausible name character sequence.
Characters keep changing
Increase the source window size, wait for a steadier frame, and reduce the zone to the text baseline. Motion and transparency often cause unstable reads.
No public profile appears
The visible gamer tag may not be used on a supported source, the provider may be unavailable, or the account name may differ too much for a responsible match.
An unrelated profile appears
Mark it Wrong profile. Matching text is evidence, not proof of ownership, and correction feedback should remove the association from future alerts.
Continue with the complete setup guide, learn how gamer tag OCR works, or review the Stream Sniping Policy.