This Starfield Low-End PC Guide focuses on Crowd Density and FSR 2 first, because those two changes together recover more FPS than everything else combined on weak hardware. Starfield on a low-end PC is a different challenge than Cyberpunk or Warzone on the same hardware, because the constraint is often the CPU single thread rather than the GPU. This means you can have a GTX 1660 Super and still hit reasonable performance with the right settings — because in space and less populated environments, that card is not the limit. The challenge is cities, and cities have a specific fix.
📋 Table of Contents
TL;DR: Set Crowd Density to Low, enable FSR 2 at Quality or Balanced mode, lower Shadow Quality to Low, and disable Motion Blur and Depth of Field. On a GTX 1060 or similar, these four changes make Starfield playable at 30 to 45 FPS in cities and 50 to 65 FPS in space and on planets.
Quick wins if you are in a hurry
- Crowd Density → Low. The most effective single setting change in Starfield for CPU-limited systems. Directly reduces the AI simulation load on the single thread that limits performance in cities.
- Enable FSR 2 in Display settings → Resolution Scaling. Set to Balanced or Performance mode on very weak GPUs. FSR works on all GPU brands.
- Shadow Quality → Low. Recovers 10 to 18 FPS in planetary surface environments with outdoor lighting.
- Disable Motion Blur, Depth of Field, and Lens Flare in Display settings. Free FPS, pure cosmetic removal.
What low-end means for Starfield
Starfield’s official minimum spec is an NVIDIA GTX 1070 Ti or AMD Radeon RX 5700. In practice, a GTX 1060 6 GB is borderline playable with optimized settings. The challenge on low-end hardware is twofold: GPU workload in graphically complex environments, and VRAM requirements for the game’s high-resolution planet textures.
Starfield uses approximately 6 to 8 GB of VRAM at medium settings at 1080p. On a 6 GB GPU, VRAM overflow causes stuttering during texture streaming, particularly when transitioning between interiors and planetary surfaces. Low texture settings bring this below 5 GB.
Settings ranked by FPS impact on weak hardware
1. Crowd Density → Low
This is mandatory on weak hardware. New Atlantis at High Crowd Density can cause a modern GPU to sit at 40 to 50 percent utilization while the CPU thread is maxed — the GPU is waiting, not working. On a weak CPU paired with a weak GPU, the combined effect of Crowd Density High plus GPU limitation creates some of the worst performance on any low-end combination.
At Low Crowd Density, cities are still populated but the simulation load is cut dramatically. On a Ryzen 5 3600 + GTX 1660, New Atlantis at Low Crowd Density compared to High shows approximately 18 to 25 FPS improvement in community testing.
2. FSR 2 at Balanced or Performance mode
On very weak GPUs (GTX 1060, RX 580), FSR 2 Quality mode may not provide enough GPU relief for stable performance in demanding areas. Use Balanced or Performance mode instead. FSR 2 Performance mode renders at approximately 50 percent of output resolution — the image is noticeably softer but the FPS gain is 50 to 60 percent, which is the difference between unplayable and stable on a GTX 1060.
Note: Starfield’s art style — rocky planetary surfaces, industrial space stations — masks FSR upscaling softness better than Night City’s neon detail work. Performance mode in Starfield looks more acceptable than Performance mode in Cyberpunk 2077 at equivalent resolution.
3. Shadow Quality → Low
Starfield’s planetary surfaces with outdoor lighting use shadow rendering extensively. High and Medium Shadow Quality in sunny planet environments costs 10 to 18 FPS on weak GPUs. Low is noticeably different visually — shadow edges are lower resolution and static shadows reduce — but the performance recovery on a sub-$200 GPU makes this non-optional.
4. Indirect Lighting → Low
Indirect Lighting controls how light bounces between surfaces in interiors and on planet surfaces. Medium versus Low shows approximately 8 to 12 FPS difference in complex lighting environments with minimal visual impact at normal play distances.
5. Disable purely cosmetic effects
Motion Blur, Depth of Field, Lens Flare, and Film Grain are all cosmetic post-processing with no gameplay impact. Disable all of them. On a GTX 1060, removing these effects recovers 8 to 12 FPS total.
6. Texture Quality → Medium (6 GB VRAM) or Low (4 GB VRAM)
Starfield’s planetary textures are large. On a 6 GB VRAM GPU, High textures will occasionally overflow into system RAM during texture streaming when landing on a new planet. Medium textures at 1080p use approximately 5 GB of VRAM on a 6 GB card, staying within the limit most of the time. Low textures use approximately 3.5 to 4 GB, providing reliable margin. On 4 GB GPUs (GTX 1650 level), Low textures are required.
FPS expectations by hardware tier at 1080p
| GPU | CPU | Cities (Low settings + FSR Balanced) | Space/Planets |
|---|---|---|---|
| GTX 1060 6GB | Ryzen 5 3600 | 28-38 FPS | 45-60 FPS |
| GTX 1660 Super | Ryzen 5 3600 | 38-52 FPS | 60-80 FPS |
| RTX 2060 / RX 5700 | Ryzen 5 5600 | 48-65 FPS | 75-95 FPS |
| RTX 3060 / RX 6600 XT | Ryzen 5 5600X | 55-75 FPS | 90-120 FPS |
Based on community benchmarks at equivalent configurations. City numbers represent New Atlantis at Crowd Density Low. Space numbers represent open-space environments. Performance varies significantly by specific area.
SSD requirement
Starfield requires an SSD — Bethesda lists it as a hard requirement, not a recommendation. The game’s constant texture and world streaming will not function stably on an HDD. If you are running on an HDD, you will see loading issues and severe streaming stutter regardless of other settings. Move Starfield to an SSD before troubleshooting any other performance issue.
System-level tweaks for weak PCs
Enable HAGS in Windows Display settings. Unlike Warzone where HAGS can be problematic, HAGS consistently helps Starfield by reducing CPU overhead in GPU memory management. On weak hardware where every CPU cycle matters for the single simulation thread, this is meaningful.
Set Windows Power Plan to High Performance. Starfield’s single-thread bottleneck means the CPU needs to sustain its maximum clock constantly in city environments. Balanced plan downclocking during brief lulls means the thread cannot ramp back fast enough when load returns.
Enable XMP or EXPO in BIOS. Starfield on Ryzen systems shows 10 to 20 FPS improvement from running RAM at 3600 MHz versus 2133 MHz default. This is a free change with significant impact.
Common issues and fixes
Issue: Stuttering when landing on a new planet for the first time.
Fix: Normal streaming behavior as Starfield loads the new planet’s asset set. The first landing is always slower. Subsequent visits to the same planet are significantly smoother as assets are cached.
Issue: FPS drops to unplayable levels specifically in New Atlantis despite other areas being fine.
Fix: New Atlantis is the single most demanding area in Starfield for CPU simulation load. Crowd Density Low is mandatory here. Also confirm HAGS and XMP are enabled, as both have their largest impact in high-simulation-load city environments.
Issue: Game crashes after a few minutes on a 4 GB VRAM GPU.
Fix: VRAM overflow causing instability. Set Texture Quality to Low and confirm FSR 2 is enabled (it slightly reduces VRAM usage compared to native resolution). On 4 GB VRAM, Starfield is at the absolute edge of playability and requires the most aggressive low settings.
Frequently asked questions
Is Starfield playable on a GTX 1060?
Barely, with all optimizations applied. In space and on most planets, expect 45 to 60 FPS at Low-Medium settings with FSR 2 Balanced. In New Atlantis at Crowd Density Low, expect 30 to 40 FPS. At a locked 30 FPS with consistent frame times, the game is playable for story exploration. Demanding combat in cities may drop below 30 FPS on this hardware.
Does FSR 2 help Starfield on weak hardware?
Yes significantly. FSR 2 Performance mode on a GTX 1060 at 1080p effectively brings the GPU workload below what a GTX 1070 Ti would face at native. The image quality tradeoff at Performance mode is real but Starfield’s rocky terrain textures and industrial interiors are more forgiving than Night City’s fine detail.
What is the minimum PC to play Starfield reasonably?
A Ryzen 5 3600 or Core i5-10400F CPU combined with a GTX 1660 Super or RX 5700 and 16 GB of RAM provides 45 to 65 FPS in most environments at optimized Low-Medium settings with FSR 2. Below this, performance is increasingly inconsistent in cities. An SSD is non-negotiable.
Starfield Low-End PC Guide: Quick Checklist
- Crowd Density: Low
- FSR 2: enabled at Balanced or Performance mode (not Quality on very weak GPUs)
- Shadow Quality: Low
- Indirect Lighting: Low
- Motion Blur, Depth of Field, Lens Flare, Film Grain: all Off
- Texture Quality: Medium (6 GB VRAM) or Low (4 GB VRAM)
- HAGS: enabled in Windows
- Power Plan: High Performance
- XMP/EXPO: enabled in BIOS
- Game installed on SSD
Starfield on weak hardware is harder than most recent open-world games due to its engine architecture, but it is achievable at 30 to 60 FPS with the right configuration. Accept the city performance ceiling and optimize around it. For understanding which hardware component matters most for raising that ceiling, our Starfield PC specs guide explains the CPU-first upgrade priority for this specific engine.
Bethesda’s official Starfield system requirements show minimum and recommended specs. GamersNexus’s Starfield optimization guide includes benchmark comparisons on lower-tier hardware configurations.
Tested by Anir | FPSFlow.com
Hardware: RTX 4070 + Ryzen 7 5800X as reference. Low-end estimates based on community benchmarks from Ryzen 5 3600 + GTX 1660 Super and equivalent configurations.
Last updated: July 2026
Method: Each setting change isolated in New Atlantis and on a desolate planet environment to separate CPU from GPU bottleneck effects.


