What is AutoFPS in Microsoft Flight Simulator, and should you use it?
Learn what AutoFPS changes in Microsoft Flight Simulator, who benefits, its limits, and when fixed graphics settings are the better choice.
AutoFPS is an unofficial, PC-only companion utility that adjusts selected Microsoft Flight Simulator graphics settings while you fly, usually to hold a chosen frame-rate target. It is useful when performance swings between dense airports and cruise, but it is unnecessary if your sim already maintains smooth, consistent frame times.
How does AutoFPS work?
AutoFPS monitors simulator performance and changes supported settings in response to the workload. At a detailed airport it can reduce scenery complexity; once airborne, it can restore visual detail when more performance headroom becomes available.
- Terrain level of detail (TLOD) controls the distance and detail of terrain, buildings and streamed scenery. Lowering it can relieve a main-thread bottleneck around large airports and cities.
- Object level of detail (OLOD) changes how far away detailed three-dimensional objects remain visible.
- Cloud quality and other supported controls may be adjusted by some utility versions or profiles, helping when the graphics card rather than the processor is limiting performance.
The available controls differ between AutoFPS releases and between Microsoft Flight Simulator 2020 and 2024. AutoFPS is not installed in the Community folder: it is a separate Windows program that runs alongside the simulator.
It does not create performance from nothing. The utility exchanges visual detail for steadier frame rates, then raises that detail again when the computer has spare capacity.
Should you use AutoFPS?
AutoFPS is most useful on PCs that run smoothly in cruise but lose substantial performance at detailed airports, particularly when the simulator is limited by its main thread.
| Situation | Recommendation | Reason |
|---|---|---|
| Large FPS changes between airports and cruise | Try AutoFPS | Dynamic LOD can adapt to the changing scenery workload. |
| Stable capped frame rate with acceptable visuals | Skip it | Another background utility adds complexity without solving a problem. |
| GPU usage is saturated almost everywhere | Fix the baseline first | Resolution, render scaling, clouds and anti-aliasing usually need attention before dynamic LOD. |
| VR with reprojection | Test cautiously | Stable frame timing matters more than peak FPS, and changing detail can be conspicuous in a headset. |
| Xbox Series X|S, PS5 or PS5 Pro | Cannot be used | Consoles cannot run the required Windows companion utility. |
Before adding AutoFPS, choose a sound fixed-settings baseline for MSFS. A system running excessive render scaling, clouds or traffic will not be rescued simply by changing terrain LOD.
What can AutoFPS fix, and what can it not fix?
AutoFPS can improve frame-rate consistency when scenery complexity changes during a flight. It is particularly effective when reducing LOD moves Microsoft Flight Simulator out of a CPU or main-thread limit.
It cannot repair a faulty add-on, unstable overclock, shader-compilation pause, scenery-streaming delay, memory pressure or network interruption. If performance is poor throughout MSFS 2024 rather than only in complex areas, start by identifying whether the CPU or GPU is actually limiting the simulator.
Low average FPS and stuttering are not the same fault. If the image still pauses when LOD is already low, use our guidance to separate streaming and frame-pacing stutters from ordinary low FPS.
Frame generation also needs care. A performance overlay may report generated frames rather than the simulator's underlying render rate, so do not choose an AutoFPS target solely from the larger displayed number. In VR, base the target on the headset's reprojection cadence and frame timing rather than a desktop FPS counter.
What AutoFPS mistakes make performance worse?
Most poor AutoFPS results come from an unrealistic target or overly broad adjustment limits rather than from the basic idea behind the utility.
- Setting an impossible target: AutoFPS can drive detail to its permitted minimum and still miss the requested rate. The result is unattractive scenery without smoother performance.
- Allowing excessive LOD changes: Wide minimum and maximum values can produce visible object pop-in or repeated quality shifts during approach.
- Running two automatic controllers: Where a simulator build offers its own Dynamic Settings, do not let that feature and AutoFPS control the same performance target during testing.
- Watching only average FPS: An apparently higher average can conceal uneven frame times. Judge taxiing, camera movement and final approach for visible judder.
- Ignoring simulator updates: An AutoFPS release intended for a different MSFS version may stop working or change the wrong values. Confirm compatibility after major simulator updates rather than forcing an outdated build to run.
How should you test AutoFPS?
A controlled comparison shows whether AutoFPS helps your particular aircraft, route and hardware.
- Record your baseline. Save or photograph the relevant graphics settings, then fly a demanding airport scenario with AutoFPS closed.
- Choose a realistic target. Use a frame rate the PC can approach without destroying visual quality, not simply the refresh rate printed on the monitor.
- Start with conservative limits. Prevent the utility from reducing LOD below a level you consider acceptable or raising it so far that performance repeatedly collapses.
- Repeat the same scenario. Keep the aircraft, airport, weather, traffic and camera position unchanged so the comparison means something.
- Check a complete flight phase. Test a busy gate, taxi, take-off, cruise and arrival. A setting that looks good in cruise may fail during an approach over dense scenery.
For the controls and adjustment order, follow our detailed AutoFPS configuration procedure rather than copying another simmer's target and LOD limits. Those values depend heavily on processor performance, resolution, aircraft complexity and traffic.
Is AutoFPS safe, and does it work on console?
AutoFPS is a third-party Windows executable, not an official Microsoft Flight Simulator feature. Use a release explicitly compatible with your simulator edition, scan downloaded files normally and keep a record of the settings it may alter; an antivirus warning alone proves neither that a file is safe nor that it is malicious.
It is unavailable on every console edition, including MSFS 2020 and 2024 on Xbox Series X|S and MSFS 2024 on PS5 or PS5 Pro. Console players must use the simulator's own graphics and performance controls.
Our verdict
We recommend trying AutoFPS when a well-configured PC suffers predictable performance drops at dense airports but has unused headroom in less demanding phases. Keep it only if repeated flights show steadier frame times without distracting LOD changes. If MSFS is already smooth, fixed settings remain simpler and more reliable.