System Requirements & Performance Tips
Check if your Windows PC is ready for QGIS and learn easy ways to keep maps fast and responsive.
At a glance
- Windows 10/11 (64‑bit)
- 4 GB RAM minimum (8–16 GB recommended)
- SSD strongly recommended
- Updated graphics drivers
Minimum vs Recommended specs
Minimum
- OS: Windows 10/11 (64‑bit)
- CPU: 2 cores
- RAM: 4 GB
- Storage: 2–4 GB free (app), more for data
- GPU: Integrated/Discrete with current drivers
- Display: 1366×768
- Network: Internet for OSGeo4W install
- Permissions: Administrator for install
Recommended
- CPU: 4+ cores
- RAM: 8–16 GB (or more for large rasters)
- Storage: SSD for app and projects
- Display: Full HD (1920×1080) or higher
- GPU: Current drivers; enable hardware acceleration if supported
- Backups: External or cloud for projects/data
Performance tips
Use efficient formats
Prefer GeoPackage (GPKG) or GeoTIFF over many small Shapefiles. Keep attribute indexes for fields you filter or join.
Optimize styles & labels
Reduce complex symbol layers, simplify geometry while editing, and avoid heavy label rules on very large datasets.
Cache tiles & data
Enable tile caching for web basemaps and store working data on an SSD rather than a network drive.
Keep drivers current
Update your GPU drivers. Out‑of‑date drivers can slow rendering or cause glitches.
Project housekeeping
Turn off layers you don't need, use scale‑based rendering, and keep CRS definitions consistent across layers.
Avoid bottlenecks
Large network shares, real‑time antivirus scans on project folders, and huge unindexed tables will slow you down.
FAQ
Will QGIS run on older 64‑bit hardware?
Yes, but performance may be limited. Ensure enough RAM and consider lighter datasets. SSDs help a lot on older systems.
Does QGIS need a dedicated GPU?
No, but a dedicated GPU with current drivers improves rendering. Integrated GPUs work for most 2D maps.
Why is map rendering slow?
Common reasons: huge unindexed layers, complex symbology/labels, slow network drives, or antivirus scanning. See tips above or visit Troubleshooting.