Spider-Man: Miles Morales PC stuttering, low FPS, and crashing usually come from four pressure points: ray tracing, shader compilation, crowded-city asset streaming, and unstable overlays or drivers. Start with the latest GPU driver, disable ray tracing, use DLSS 2 or FSR 2, cap the frame rate below your monitor's refresh rate, and let the game finish its shader work before judging performance. Those changes solve the biggest problems without turning Manhattan into a blurry mess.
This guide targets the Steam and Epic PC versions, including the PC release's demanding traversal sequences. The game is built on Insomniac's engine, so a scene that looks smooth in a rooftop fight can hitch badly when Miles crosses several blocks at high speed. For official updates, check the Steam page for Marvel's Spider-Man: Miles Morales, the Nixxes support portal, and the official PlayStation game page.
Use the right performance profile first
Before changing obscure Windows settings, pick a sensible baseline. The PC version supports DLSS, AMD FSR 2, Intel XeSS, dynamic resolution, an unlocked frame rate, and optional ray-traced reflections. On an RTX 3060-class card, 1080p High with DLSS Quality and ray tracing disabled is a far better starting point than native 1440p with every slider maxed.
| Target hardware | Resolution and preset | Upscaling | Expected target |
|---|---|---|---|
| GTX 1060 6GB / RX 580 | 1080p Low to Medium | FSR 2 Balanced | 30-45 FPS |
| RTX 2060 / RX 5700 | 1080p High | DLSS Quality or FSR 2 Quality | 55-75 FPS |
| RTX 3060 Ti / RX 6700 XT | 1440p High | DLSS Quality or FSR 2 Quality | 60 FPS class |
| RTX 4070 / RX 7800 XT | 1440p Very High | DLSS Quality or FSR 2 Quality | 80-120 FPS |
| RTX 4080 or faster | 4K Very High | DLSS Quality | 60 FPS class |
Those are practical targets, not guarantees. CPU speed, RAM capacity, background applications, and the exact density of the city all matter. The game officially lists 16GB of RAM as the recommended memory target, and that is the sensible floor for a smooth experience. If your system is close to the minimum requirements, a locked 30 FPS profile will feel substantially better than an unstable 45-60 FPS.
Stop stuttering during fast web-swinging
The most recognizable hitch happens when Miles swings quickly across Manhattan. The engine is loading buildings, traffic, pedestrians, shadows, and mission assets while the camera moves at extreme speed. That workload can create traversal stutter even when your average frame rate looks healthy.
Change these settings in this order
- Ray-traced reflections: Off. If you want to keep them, use Low and reduce the ray-traced geometry detail. Reflections are much more expensive during wide city views than during indoor combat.
- Traffic and crowd density: Medium. This reduces CPU-side simulation and helps prevent frame-time spikes in busy streets.
- Hair quality: Medium. It mostly affects character hair and can be lowered with little impact during movement.
- Level of detail: High rather than Very High. The visual difference while swinging is minor, but the streaming budget is easier to manage.
- Texture quality: Match it to VRAM. Use High on 8GB cards and Medium on 6GB cards if you see sudden hitching or texture pop-in.
- Motion blur: Personal preference. Turning it off improves clarity, but it will not fix a genuine frame-time problem.
Use a frame cap rather than chasing an unstable maximum. Set 58 FPS for a 60Hz display, 72 or 90 FPS for a 75Hz or 100Hz display, and 117 FPS for 120Hz. A cap gives the CPU and GPU breathing room for asset streaming. If your game still has short hitches, compare it with our broader Elex PC crash and FPS fixes; the same overlay and driver checks apply.
Best graphics settings for stable FPS
Do not lower every option blindly. Spider-Man: Miles Morales responds more strongly to a handful of settings, while texture filtering and many small quality toggles have a relatively modest performance cost. The goal is consistent frame time, not a screenshot benchmark.
| Setting | Recommended value | FPS impact | Visual trade-off |
|---|---|---|---|
| Ray-traced reflections | Off or Low | Very high | Less realistic glass and puddle reflections |
| Upscaling method | DLSS Quality / FSR 2 Quality | Very high gain | Slight softness compared with native resolution |
| Texture quality | High with 8GB VRAM | Low to medium | Lower values reduce surface detail |
| Shadow quality | High | Medium | Less precise distant shadows at lower settings |
| Ambient occlusion | SSAO or HBAO+ | Low to medium | Reduced contact shading when lowered |
| Traffic and crowd density | Medium | Medium to high on CPUs | Fewer cars and pedestrians |
| Level of detail | High | Medium | Shorter detail distance during traversal |
| Depth of field | Low or Medium | Low | Less cinematic background blur |
DLSS Quality is the best option on supported Nvidia cards because it preserves thin web lines and building detail better than aggressive modes. FSR 2 Quality is a strong alternative on AMD and older Nvidia hardware. Avoid Performance mode at 1080p unless you have no other choice; its internal resolution can make Miles' suit and distant signage look noticeably smeared.
Fix crashes, black screens, and launch failures
Crashes that happen before the main menu usually point to a corrupted installation, bad shader data, incompatible overlays, or a driver problem. Crashes during play can also come from a VRAM spike, unstable overclock, or a damaged configuration file.
Run this crash-fix sequence
- Verify the game files. In Steam, open Properties, Installed Files, then Verify integrity of game files. Epic users can select Manage and Verify. Wait for the process to replace missing or damaged files.
- Update or clean-install the GPU driver. Use the current Game Ready driver for Nvidia or Adrenalin package for AMD. If the problem began immediately after an update, test the previous stable driver instead.
- Disable overlays. Turn off Steam Overlay, Discord Overlay, GeForce Experience overlay, AMD metrics, Xbox Game Bar, and MSI Afterburner or RivaTuner temporarily. Overlays hook into the renderer and are frequent crash suspects.
- Remove overclocks. Return the GPU, CPU, and RAM to stock settings, including aggressive XMP or EXPO profiles. A game that appears stable elsewhere can expose marginal memory instability.
- Reset the configuration. Back up your save files, then rename the game's settings folder in your user Documents directory so the game creates a fresh configuration. Do not delete saves without making a backup.
- Check Windows security software. Add the game's executable to your antivirus exclusions only if you trust the installation, and make sure Controlled Folder Access is not blocking file writes.
If the game crashes after enabling ray tracing, turn it off before relaunching. Ray tracing does not merely lower average FPS; it can push a card over its available VRAM budget, especially at 1440p or 4K with High textures. Our EscapeVR crash troubleshooting guide also covers the same clean-boot and overlay isolation approach.
Reduce VRAM pressure and shader compilation hitches
Texture quality, resolution, ray tracing, and upscaling interact. A card with 6GB of VRAM may run a quiet scene smoothly, then hitch when the game streams a new district. That is not always a raw GPU power problem; it can be memory exhaustion followed by asset eviction.
Start by keeping textures at High or Medium, not Very High, and turn ray tracing off. Close browsers with video tabs, hardware monitoring dashboards, and launchers you do not need. Windows' page file should remain system-managed on an SSD with free space. Do not disable it to chase a tiny benchmark gain.
After a driver update or settings reset, allow the game to build shaders. The first launch and the first visit to busy areas can be less consistent than later sessions. Avoid repeatedly force-closing the game during this process. If stutter appears only for a few seconds after entering a location and then settles, that is likely compilation or streaming rather than a permanent performance failure.
Install the game on an SSD whenever possible. A hard drive can still launch the title, but rapid traversal asks it to deliver a large amount of data quickly. That is exactly where a mechanical drive tends to produce pauses, texture pop-in, and delayed detail.
Windows and driver tweaks that actually help
Windows tweaks should come after in-game settings, not before them. Set the game's executable to High performance in Windows Graphics settings if you have both integrated and dedicated graphics. On laptops, connect AC power and select a performance profile from the manufacturer's control software. Battery modes can hard-limit CPU and GPU clocks.
- Enable Game Mode and test Hardware-accelerated GPU scheduling. HAGS helps some systems and hurts others, so keep whichever produces better frame-time consistency.
- Use exclusive fullscreen or borderless mode based on your setup. Borderless is convenient for multitasking, while exclusive fullscreen can reduce desktop interference on some systems.
- Set Nvidia Power management mode to Prefer maximum performance for the game profile. AMD users should avoid aggressive Radeon Chill limits that conflict with the in-game cap.
- Do not force sharpening, frame generation, or driver-level anti-aliasing on top of the game's own renderer.
- Keep at least 15-20 percent free space on the SSD containing the game and Windows page file.
For a clean diagnosis, change one variable at a time and record average FPS plus the feel of the 1% lows. A profile that reports 90 FPS but repeatedly drops to 35 during traversal will feel worse than a locked 60. If you want another example of tuning around demanding open-world streaming, see our Far Cry 6 settings guide and the Filament performance guide.
Test the fix without fooling yourself
Use the same repeatable route after every change: load a save near a busy Manhattan street, swing for several minutes toward a dense intersection, enter a combat encounter, and then fast-travel if available. Check crowded streets, snow effects, indoor missions, and a fight with multiple enemies. Miles' Venom abilities, particle effects, and rapid camera movement can stress the system differently from simple rooftop traversal.
| Symptom | Most likely cause | First fix | Next step |
|---|---|---|---|
| Brief hitches while swinging | Asset streaming or shader compilation | Use SSD and cap FPS | Lower crowd density and LOD |
| Low FPS everywhere | GPU settings too high | Disable ray tracing and enable upscaling | Lower resolution or shadows |
| Sudden pauses with texture pop-in | VRAM pressure | Lower textures and RT | Close background GPU apps |
| Crash at startup | Driver, overlay, or damaged files | Verify files and disable overlays | Clean-install or roll back driver |
| Crash after several minutes | Overclock, heat, or memory exhaustion | Return hardware to stock | Monitor temperatures and VRAM |
The strongest all-purpose setup is 1080p or 1440p, High preset, ray tracing off, DLSS or FSR 2 Quality, Medium crowd density, High textures matched to VRAM, and a stable 60 FPS cap. Once that profile is clean, raise one setting at a time. If the game still crashes after file verification, stock hardware, driver changes, and overlay removal, send the crash details through Nixxes' official support request form rather than guessing at registry edits.