Prepar3D v4, v5 and v6 PC requirements: CPU, GPU, RAM, VRAM, Windows and SSD targets, plus upgrade, laptop and add-on guidance.
For Prepar3D v5 or v6, we recommend a supported 64-bit edition of Windows 10 or 11, a modern six- to eight-core CPU with strong single-core performance, 16 GB RAM for light use or 32 GB with add-ons, a DirectX 12 graphics card with at least 8 GB VRAM, and an SSD with at least 100 GB free.
These are practical planning specifications, not the bare minimum needed to reach the menu. Complex aircraft, detailed airports, AI traffic, weather, VR and high resolutions can make Prepar3D far more demanding than a default flight over rural scenery.
Practical Prepar3D v5 and v6 system requirements
A balanced computer provides better results than one expensive component paired with several weak ones.
| Use case | CPU | System RAM | Graphics card | Storage |
|---|---|---|---|---|
| Default or light use at 1080p | Modern four- to six-core CPU with good per-core speed | 16 GB | Dedicated compatible GPU with 6–8 GB VRAM | SSD with at least 100 GB free |
| Add-ons at 1080p or 1440p | Fast six- to eight-core CPU | 32 GB | 8–12 GB VRAM | 250 GB to 1 TB of SSD capacity |
| Complex hubs, 4K, VR or extensive scenery | High-performance eight-core or better CPU | 32–64 GB | 12–16 GB VRAM or more | 1–2 TB NVMe SSD |
No specification guarantees the same frame rate everywhere. A detailed airliner at a large add-on airport with heavy traffic may run much more slowly than a default aircraft on the same computer.
Common hardware-buying mistakes
- Buying by core count alone: Prepar3D often becomes limited by its main rendering thread. Compare per-core performance, and do not compare clock speeds directly across unrelated processor generations.
- Choosing integrated graphics: some integrated GPUs can start the simulator, but shared memory and limited sustained performance make them a poor choice for a dedicated Prepar3D computer.
- Confusing RAM with VRAM: additional system memory does not cure graphics-memory exhaustion. VRAM capacity also does not measure GPU speed; a slow 12 GB card is not automatically better than a faster 8 GB model.
- Buying only for default content: detailed airports, photographic scenery, complex aircraft, traffic and external utilities can change the requirement substantially.
Does Prepar3D need a better CPU or GPU?
Prepar3D needs both, but the CPU is commonly the first limit at busy airports, while resolution, lighting and image-quality settings place more pressure on the GPU.
- CPU-heavy workloads: AI traffic, autogen, scenery density, draw distance and complex aircraft systems.
- GPU-heavy settings: resolution, anti-aliasing, shadows, reflections, dynamic lighting, clouds and VR rendering.
- VRAM-heavy content: high-resolution textures, detailed airports, photographic scenery and multiple high-resolution displays.
Overall CPU utilisation can appear low when one logical core is saturated. Our guide to identifying whether Prepar3D is CPU- or GPU-bound explains how to read that behaviour, while the recommended Prepar3D graphics settings show which options to reduce before replacing hardware.
Is 16 GB of RAM enough for Prepar3D?
Sixteen gigabytes is enough for a base or moderately modified installation, but 32 GB is the better target for detailed aircraft, large airports, AI traffic, weather software and browser-based charts. Sixty-four gigabytes becomes useful when extensive scenery and several external programs run alongside the simulator.
Keep the Windows page file enabled, preferably under system management. Disabling it does not make Prepar3D faster and can turn a temporary memory spike into an application or system failure.
How much space does an installed copy of Prepar3D need?
Reserve at least 100 GB for Prepar3D and installation headroom, around 250 GB for moderate add-on use, and 500 GB or more for a scenery-heavy installation. The exact installed size depends on the version, optional components and content library.
The aircraft, airports and utilities in our Prepar3D add-on library illustrate why storage grows quickly. A single 5.96 GB photoreal Hawaii package, for example, uses more space than many aircraft collections.
An SSD reduces loading times and delayed scenery or texture access. NVMe is preferable when price and capacity are similar, but moving from a mechanical hard drive to any competent SSD matters more than moving from SATA SSD storage to NVMe; storage speed rarely fixes a main-thread frame-rate limit.
How do Prepar3D v4, v5 and v6 requirements differ?
The major differences are the move from 32-bit to 64-bit in Prepar3D v4 and the adoption of DirectX 12 in v5 and v6.
| Prepar3D version | Hardware implication |
|---|---|
| v1–v3 | These are 32-bit applications. More physical RAM helps Windows and supporting programs, but it cannot remove the simulator's restricted address space or prevent every out-of-memory error. |
| v4 | This release is 64-bit and uses DirectX 11. A capable DX11 card and 16 GB RAM are workable, with 32 GB preferable for substantial add-on use. |
| v5–v6 | These are 64-bit DirectX 12 simulators. We would target 32 GB RAM, at least 8 GB VRAM and modern graphics drivers. |
Check the supported Windows release, graphics API and add-ons for the exact version you plan to run; our Prepar3D download and installation guidance covers that pre-installation check. Faster hardware cannot make an incompatible legacy gauge or aircraft module work.
Our explanation of how Prepar3D's architecture changed from 32-bit to 64-bit covers the broader differences between generations. If an older aircraft loads without working instruments, see the guide to blank gauges and 64-bit add-on compatibility.
Which PC upgrade improves Prepar3D most?
The best upgrade is the component limiting the aircraft, airport and settings you actually use.
- Replace a mechanical drive first if Prepar3D, its scenery or the Windows page file resides on one. This improves loading and asset delivery, though not necessarily steady frame rates.
- Prioritise the CPU when one or two logical cores repeatedly reach their limit while the GPU has spare capacity.
- Prioritise the GPU when graphics utilisation remains near its limit. If VRAM is exhausted, severe stuttering, texture problems or device errors can follow.
- Add RAM when committed memory approaches capacity and Windows pages heavily during complex flights. Moving from 16 GB to 32 GB helps here, but not with a CPU-limited frame rate.
A crash does not automatically mean the computer is underpowered. Faulty scenery, damaged or incompatible add-ons, overheating, unstable overclocks and page-file changes can cause similar symptoms; our guide to scenery and memory causes behind Terrain.dll errors covers that diagnosis separately.
Can a laptop run Prepar3D?
A gaming laptop can run Prepar3D if it has dedicated graphics, sufficient VRAM and cooling capable of sustaining CPU and GPU performance. Laptop parts sharing a name with desktop components may operate at lower power, so product names alone are unreliable comparisons.
Use mains power and the laptop's performance mode while flying. A desktop usually offers better cooling, easier storage expansion and a clearer upgrade path for a computer intended mainly for Prepar3D.
Do I need a joystick or other flight controls?
Prepar3D works with a keyboard and mouse, but a joystick or yoke is the most useful additional hardware. A twist-axis joystick can replace separate rudder pedals; throttles, head tracking and VR are optional. Allow enough powered USB capacity, and check Windows drivers for older specialist controllers and headset compatibility for the exact Prepar3D release.