For the best Miles Morales PC performance, start with the High preset, disable ray-traced reflections, use DLSS or FSR 2.1 at Quality, set crowd and traffic density to Medium, and cap the frame rate to a number your GPU can hold consistently. That combination usually delivers the sweet spot: sharp snow, clean neon reflections, responsive Venom attacks, and far fewer traversal stutters than the Ultra or ray-tracing-heavy presets.
Marvel’s Spider-Man: Miles Morales is not a brutally demanding game by modern PC standards, but its fastest moments are unusually good at exposing weak frame-time consistency. Swinging across Manhattan streams in buildings, traffic, pedestrians, particles, and reflections while combat throws extra effects on top. A 90 fps counter means very little if the game repeatedly dives to 55 fps during a high-speed turn. The goal here is stable delivery, not a pretty benchmark number that collapses the moment Miles lands in Times Square.
Before changing anything, check the official Steam page for the current system requirements and patches. If another PC game is also stuttering, our guide to stopping crashes and rescuing FPS has useful Windows-side checks that apply here too.
Start With the Right Miles Morales PC Preset
Insomniac’s PC port gives you a broad range of options, but your target resolution should decide the starting point. At 1080p, the recommended hardware is roughly an Intel Core i5-4670 or AMD Ryzen 5 1600, 16GB of RAM, and a GeForce GTX 1060 6GB or Radeon RX 580 8GB for a 60 fps-oriented Medium experience. The minimum specification—Core i3-4160, 8GB RAM, and GTX 960 4GB—targets 720p at 30 fps on Low, not smooth 1080p gaming.
For 1440p at 60 fps, the official recommendation moves to hardware around an RTX 3070 or Radeon RX 6800, paired with a Core i5-11400 or Ryzen 5 3600. A 4K/60 target is a different class of workload: the published guidance points toward an RTX 3080 or RX 6950 XT and a Core i7-12700K or Ryzen 7 5800X. Those figures make sense because resolution, reflections, and texture memory all climb together in Manhattan’s busiest scenes.
| Target | Starting Profile | Hardware Guidance | Expected Result |
|---|---|---|---|
| 1080p/60 | High, no ray tracing, Quality upscaling | GTX 1060 6GB / RX 580 8GB or better | Strong 60 fps with sensible compromises |
| 1440p/60 | High, DLSS or FSR 2.1 Quality | RTX 3070 / RX 6800 or better | Good detail and stable traversal |
| 1440p/90+ | Medium-High, upscaling Balanced | RTX 4070 / RX 7800 XT class | High refresh play without maxed ray tracing |
| 4K/60 | High, upscaling Quality, RT off | RTX 3080 / RX 6950 XT or better | Excellent image quality, occasional heavy dips |
The best baseline profile
Set Texture Quality to High if your graphics card has 8GB or more VRAM; use Medium on 4GB cards to avoid texture streaming pauses. Set Texture Filtering to 8x or 16x. Its performance cost is tiny, while roads, rooftops, and brickwork remain much clearer at oblique angles. Keep Level of Detail on High unless your processor is older, because it controls how quickly distant geometry and city detail simplify.
For a balanced 1080p or 1440p setup, choose High preset, then set Shadows to Medium, Ambient Occlusion to High, Screen Space Reflections to High, Hair Quality to Medium, Weather Particle Quality to Medium, Crowd Density to Medium, and Traffic Density to Medium. Leave Depth of Field, Vignette, and Film Grain off unless you specifically like the cinematic look. Those effects do not rescue performance, but removing them makes motion cleaner and the image easier to read.
The official PlayStation game page is useful for checking the PC edition’s feature set, while the PC port’s official support resources should be your first stop after a patch changes behavior.
🎮 FORM
Looking to experience this game? Grab your digital key directly on our store for $14.99.
View on Steammoz Store →Settings With the Biggest FPS Impact
Not every slider deserves equal attention. The big performance hitters are ray-traced reflections, shadow quality, volumetric weather effects, crowd density, traffic density, and output resolution. Texture quality mostly affects VRAM capacity rather than raw frame rate. Dropping it from High to Low on a strong GPU can make the game look worse without solving a GPU bottleneck.
| Setting | Recommended Value | FPS Impact | Visual Trade-Off |
|---|---|---|---|
| Ray-Traced Reflections | Off for high FPS; Medium for 60 fps | Very high | Fewer accurate window, puddle, and car reflections |
| Resolution | Native or DLSS/FSR Quality | Very high | Lower output resolution reduces fine detail |
| Shadow Quality | Medium or High | High | Less contact detail and softer distant shadows |
| Volumetric Effects | Medium | Medium-high | Less dense snow, fog, and atmospheric lighting |
| Crowd Density | Medium | Medium CPU impact | Fewer pedestrians and simpler street activity |
| Traffic Density | Medium | Medium CPU impact | Fewer cars during fast traversal |
| Hair Quality | Medium | Medium | Less detailed hair simulation in close-ups |
| Ambient Occlusion | High | Low-medium | Lower values flatten corners and contact shadows |
| Texture Quality | High with 8GB+ VRAM | Low-medium | Lower-resolution surfaces and more visible streaming |
Ray tracing is the luxury setting
Ray-Traced Reflections are gorgeous in rainy Manhattan, especially around Roxxon facilities, glass towers, puddles, and nighttime streets. They are also the easiest way to turn a comfortable 90 fps into a choppy 50–60 fps. Medium ray tracing can already be expensive because reflections are calculated across a huge open city, not just inside a small room. High and Very High increase reflection quality and range, but the visual return is much smaller than the performance bill.
If you have an RTX 3060 Ti, RTX 3070, RX 6800, or weaker card, leave RT off for a high-refresh target. If you own an RTX 4070-class GPU or better, try RT Medium at 1440p with DLSS Quality. Test it during a nighttime swing through Midtown, then in a busy combat encounter. If those two scenes stay above your cap, RT is safe to keep. AMD users should be especially conservative because ray tracing generally costs more on equivalent Radeon hardware.
CPU-bound problems look different
When GPU usage falls below roughly 90 percent while the frame rate dips, lower Crowd Density and Traffic Density before touching textures. These settings affect how many pedestrians, vehicles, and simulation tasks the processor handles. They matter most during rapid traversal and street-level combat. A powerful GPU paired with an older four-core processor may still stutter with both options on High.
Shadow Quality is a better first cut when GPU usage is pinned at 99 percent. Medium retains attractive lighting while removing a surprising amount of rendering work. Weather Particle Quality also matters during snowstorms and heavy effects. Medium keeps the atmosphere intact; Low can make the city feel noticeably emptier.
DLSS, FSR, IGTI, and Frame Generation Explained
Upscaling is the cleanest way to gain performance without simply making Miles Morales look blurry. On Nvidia cards, DLSS Quality is the preferred 1440p starting point, while DLSS Balanced is a useful fallback if you need another 10–15 percent of GPU headroom. At 1080p, native resolution can look cleaner because the reconstruction has fewer pixels to work with; use DLSS Quality only when your GPU is struggling.
AMD and Nvidia users can use FSR 2.1 Quality. It provides a meaningful uplift and holds detail better than old spatial upscalers, but fine wires, snow, and distant building edges may shimmer more than with DLSS. IGTI is another available reconstruction option. It can perform well, but its image usually looks softer than DLSS or FSR at the same nominal mode. Start with Quality, not Performance, unless you are targeting 4K on midrange hardware.
| Upscaler Mode | Best Use | Image Quality | Performance Expectation |
|---|---|---|---|
| Native | 1080p with a strong GPU | Sharpest raw image | Baseline |
| DLSS Quality | Nvidia GPUs at 1440p or 4K | Excellent reconstruction | Roughly 15–30% uplift |
| FSR 2.1 Quality | AMD or mixed GPU systems | Very good, occasional shimmer | Roughly 15–30% uplift |
| DLSS/FSR Balanced | GPU-limited 1440p and 4K | Good, softer in motion | Roughly 25–40% uplift |
| Performance | 4K on hardware below target | Clearly softer | Largest uplift, use only if needed |
DLSS 3 Frame Generation is available on compatible RTX 40-series cards. It can make the counter jump dramatically, but generated frames do not replace the responsiveness of genuinely rendered frames. Keep the base frame rate around 60 fps or higher, enable Nvidia Reflex if the game exposes it, and avoid using frame generation to disguise a 35 fps baseline. Swinging may look smooth while aiming, dodging, and reacting to Underground Brutes still feel delayed.
For a 120Hz display, cap the game at 90 or 100 fps if that is the stable range. For a 60Hz screen, a locked 60 fps is preferable to an unlocked 72–95 fps that repeatedly plunges during traversal. Use the in-game limiter first; if frame pacing still feels uneven, try your GPU driver’s limiter or RTSS. Turn V-Sync on when you see tearing, then test G-SYNC or FreeSync with V-Sync enabled in the driver and disabled in-game if your display setup recommends that combination.
How to Eliminate Stutter During Swinging
Traversal stutter is the issue that makes an otherwise excellent port feel rough. The game is constantly pulling in Manhattan geometry, NPCs, vehicles, animation data, and effects as Miles moves. A fast NVMe SSD helps, but it cannot fix a CPU limit or unstable settings by itself. Install the game on an SSD with at least 15–20 percent free space, close browser tabs and recording tools, and let shader compilation finish after driver updates or major patches.
Use the benchmark only as a starting point. The real test is a repeatable route: begin near the Financial District, swing north through Midtown, dive toward street level, then fight a group of Roxxon or Underground enemies. This route stresses streaming, crowds, traffic, reflections, and combat particles. Watch the one-percent lows and frame-time graph, not just the average FPS. A flat 16.7 ms graph means reliable 60 fps; spikes to 30 ms or 40 ms are the hitch you feel as a pause.
A practical troubleshooting order
- Update the GPU driver, then reboot. Avoid changing five driver features at once; you want to know what actually helped.
- Disable overlays from Steam, Discord, GeForce Experience, Radeon Software, and Xbox Game Bar for one test run.
- Verify game files through Steam and allow the game to rebuild shaders if prompted.
- Lower Crowd Density and Traffic Density if dips happen during street-level movement with low GPU utilization.
- Disable ray tracing if GPU utilization is maxed or frame times spike around glass buildings and puddles.
- Set a stable frame cap five to ten frames below your normal average instead of chasing the highest peak.
Windows 11 users should also test Hardware-Accelerated GPU Scheduling both on and off, because results vary by driver and GPU generation. Do not expect every tweak to help every system. If your issue is broad rather than game-specific, our crashing and low-FPS checklist covers clean driver installation, background processes, and storage checks. For older cards, the broader max-FPS settings guide also explains why consistent frame pacing beats an inflated average.
Three Profiles Worth Copying
Here are three profiles that make sense in real play rather than just in a screenshot. Apply one, run the same swinging route for five minutes, and adjust only one setting at a time. Miles Morales has enough moving parts that random slider changes make it hard to identify the real bottleneck.
| Profile | Core Settings | Best Hardware | What It Feels Like |
|---|---|---|---|
| Competitive Smooth | 1080p, Medium-High, RT Off, DLSS/FSR Quality, 90–144 fps cap | RTX 3060 Ti / RX 6700 XT or better | Fast controls and clean traversal |
| Cinematic 60 | 1440p, High, RT Medium, DLSS/FSR Quality, 60 fps cap | RTX 4070 / RX 7800 XT or better | Rich reflections without constant hitching |
| Ultra 4K | 4K, Very High, RT High, DLSS Quality, 60 fps cap | RTX 4080-class hardware | Best image, but demanding in heavy scenes |
My recommended all-round setup
For most players, I’d use 1440p, High preset, DLSS Quality on Nvidia or FSR 2.1 Quality on Radeon, RT Off, Shadows High, Ambient Occlusion High, Screen Space Reflections High, Weather Particle Quality Medium, Hair Quality Medium, and Crowd and Traffic Density Medium. Turn Motion Blur down to 0 or 2, disable Film Grain and Chromatic Aberration, and cap the game at 60, 72, or 90 fps depending on what your system holds in Manhattan’s worst moments.
If you have an RTX 4070 Super or faster, test RT Medium after the baseline is stable. If you have 8GB of VRAM, keep textures High but watch for memory warnings at 4K. If you have 4GB, use Medium textures and avoid stacking ray tracing with Performance-quality reconstruction. The goal is not to make every setting say Very High; it’s to keep Miles’ venom punches, wall runs, and last-second dodges feeling immediate from Harlem to the Financial District.
For more PC optimization reading, see our higher-FPS settings breakdown. In Miles Morales, the winning formula remains simple: prioritize frame-time stability, use upscaling intelligently, and treat ray tracing as an optional visual extra rather than a requirement for a great-looking game.