Memory and FPS in Rust: how to remove freezes and adjust graphics
Low FPS and short stutters in Rust require different solutions. Here we will figure out what limits your PC, what settings to change, and how to check the results.
Updated on October 6, 2026. Guide for Windows PC; menu item names may change with game updates.
| Issue | Where to Start |
|---|---|
| Low FPS almost everywhere | Graphics and Resolution → then CPU/GPU Load Comparison |
| Short stutters while moving | RAM, Page File, and SSD |
| Drops near bases and players | Measurement on the same server → PC Limitations Check |
| Players stutter, but camera is smooth | Ping and Network: lowering graphics may not help |
1. Measuring FPS and Finding the Cause
Open the console with the F1 key and type perf 3: FPS, frame time, and memory usage will appear on the screen. For ping, use perf 4. Simultaneously check GPU load, RAM usage, and disk activity in Task Manager.
Let the game load, then walk the same route 2-3 times. Compare settings on the same server, in a similar scene. Change one setting at a time: otherwise, it's unclear what helped.
- Reduced resolution, noticeable FPS increase? Likely, a significant part of the load is on the GPU.
- Resolution change has little effect? Check FPS limit, V-Sync, and CPU load. CPU load below 100% does not exclude a limitation on a single thread.
- Memory almost full, disk busy during freeze? Check RAM and page file. This is a hint, not a definitive diagnosis.
- Stable FPS, but actions delayed? Compare ping and behavior on another server. The issue may be with the connection or server.
Important: perf 1 shows FPS, not 1% low. To measure rare drops, you need a separate tool to record frame times. For regular settings, tracking FPS, frame time, and repeatable stutters is sufficient.
2. Adjusting Graphics Without Sacrifices
Save screenshots of your settings. Low preset is convenient for testing, but it's not necessary to keep it forever: after measurement, return the quality of options that have little impact on the result.
Start with shadows and reflections. Lower resolution and render scale if limited by GPU. When limited by CPU, the image quality will degrade, and FPS may hardly change.
| Setting | What to Try |
|---|---|
| Shadows and Reflections | Reduce shadow distance and quality, reflection quality. Check the same scene. |
| Object Distance and Quality | Gradually decrease; stop when visibility remains comfortable. |
| Textures | Decrease when low on VRAM. With sufficient VRAM, FPS increase may be minimal. |
| Water | Check lower quality near shore: effect depends on the scene. |
| Motion Blur / Depth of Field | Disable if affecting sharpness. Significant FPS increase not guaranteed. |
| DLSS / Render Scale | On compatible RTX, compare DLSS Quality and Balanced. Without DLSS, try reducing Render Scale; evaluate distant sharpness. |
Choose an FPS limit that your computer can more consistently maintain. For example, a steady 90 frames may feel smoother than constant jumps between 90 and 150. Limit does not eliminate the cause of deep drops.
On NVIDIA, try Reflex On in-game if available. It reduces input delay; it's not a setting for guaranteed FPS increase. Reflex takes precedence over Low Latency mode in the NVIDIA panel. NVIDIA explanation.
DLSS and Render Scale are described in the Facepunch update. More examples are available in our guide on FPS settings without losing visibility.
3. Checking RAM, Page File, and Disk
RAM and VRAM are different memory types. RAM is used by the game and Windows, VRAM by the graphics card. Insufficient RAM makes the system access the disk more actively; insufficient VRAM may manifest during texture loading and scene changes.
- Close heavy browser tabs and unnecessary applications. Compare memory usage before launching Rust and after connecting to a server.
- Install the game on an SSD and leave free space for updates and paging. Switching from HDD can help with loading and resource streaming, but does not guarantee an increase in average FPS.
- Leave the page file under Windows control. System additional settings → Performance → Settings → Advanced → Virtual memory → Change → "Automatically manage paging file size for all drives." After changing, restart the PC.
Facepunch recommends automatic paging management and sufficient free space on SSD. Paging helps avoid memory shortages but does not replace physical RAM. Developers' guide.
Do not set a large gc.buffer based on someone else's advice and do not bind constant "memory clearing" to a button. gc.collect triggers garbage collection and may cause a pause. It's not a fix for memory leaks or a way to constantly boost FPS.












Latest comments