Safety & transparency
What Framewise touches, and what it never does
A complete list, so you can decide for yourself.
Last updated October 20, 2026
What it reads and changes
- Your Fortnite settings file,
GameUserSettings.ini, the same file the in-game Video menu saves. A backup is made before every change. - Windows power plan, Game Mode, Xbox Game Bar capture and Focus notifications.
- Apps you choose to pause during a match. Nothing is paused unless you add it.
- Windows' DirectX shader cache, only when you press Clear.
What it never does
- Read or write the memory of Fortnite or any other game
- Inject DLLs, overlays or hooks into a game
- Interact with Easy Anti-Cheat or any anti-cheat software
- Modify game files other than your settings file
- Overclock, undervolt or change fan curves
- Install drivers, browser extensions or any third-party software
- Run in the background when you close it
How frame times are measured
Framewise uses Event Tracing for Windows to see when frames are presented, the same approach as Intel's open-source PresentMon. It observes the operating system, not the game.
Undo
Restore shows every change with its original value. Restore all returns your settings file and Windows settings to how they were before Framewise touched them. Your first-launch backup is kept until you uninstall.
Network use
Framewise checks for updates once a day. The connection test sends small packets to your router and to public test servers only when you start it. No telemetry is sent unless you choose to send a crash report.
Relationship with Epic Games
Framewise is independent and is not affiliated with, endorsed by or sponsored by Epic Games. We follow Epic's published guidance on Fortnite performance, such as its help article on low frame rates, and we don't claim any special access to the game.