Fix BlenderGIS DEM Import Freeze: Why Blender Hangs and How to Import Large Terrain Files

You hit “import terrain” in BlenderGIS, the progress bar stalls, and Blender stops responding. The window says “Not Responding,” the mouse spins, and you can’t tell whether the import is working or dead. This guide explains why BlenderGIS freezes on large DEM imports and gives you the fixes that actually work.

Why BlenderGIS Freezes on Large DEM Imports

When you import elevation data — through GIS > Web geodata > Basemap > Elevation (SRTM) or the GDAL raster import — BlenderGIS builds a real 3D mesh from the elevation grid. Every pixel in the raster becomes multiple vertices in the mesh, so the geometry grows far faster than the file size suggests.

The math gets brutal fast. A 3,600 × 3,600 pixel tile (about 1° × 1° of SRTM data) holds roughly 13 million pixels, which becomes tens of millions of vertices. Blender keeps the entire mesh in memory, so once the system starts swapping to disk, the interface stops responding. The import may technically still be grinding along — but for all practical purposes, it’s frozen.

The two classic triggers are requesting too large an area in the Web geodata viewport and importing a high-resolution DEM (like 1-meter LiDAR-derived rasters) without downsampling. Both are avoidable.

How to Fix the Freeze

Fix 1 — Preprocess the DEM in QGIS before importing

This is the most reliable fix and should be your default workflow for any terrain work. QGIS is free and open source, and these three operations take minutes:

1. Clip to your area of interest. Open the DEM in QGIS and use Raster > Extraction > Clip Raster by Mask Layer. Cutting the pixel count is the single biggest performance win.
2. Downsample the resolution. Use Raster > Projections > Warp and set a coarser output — 5–10 meter pixels are plenty for site-scale models. Halving each dimension cuts the vertex count by 4×.
3. Reproject to a meter-based CRS. In the same Warp dialog, set the target to your local UTM zone. This also prevents the scale problems covered in our scale troubleshooting guide.

Then import the processed GeoTIFF with GIS > Import > Import georeferenced raster. The QGIS-to-Blender workflow guide covers this handoff, and the DEM terrain tutorial covers the Blender-side settings.

Fix 2 — Shrink the query area in Web geodata

If you’re pulling elevation from the web SRTM service, the area you zoom to is the import size. Zoom the viewport to cover only the site you need — a few square kilometers at most — before running GIS > Web geodata > Basemap > Elevation (SRTM). Need a bigger region? Import several small tiles and let georeferencing align them; small meshes are far safer than one giant one.

Fix 3 — Mind these import settings

• Don’t use “separate objects” on large data. Object splitting multiplies bookkeeping overhead (outliner, depsgraph, per-object data) and commonly locks the interface on heavy imports. Leave it off — separate regions manually later with P in Edit mode.
• Keep the native raster data type. uint16 (typical for SRTM) and float32/float64 (LiDAR products) both import cleanly. Never convert elevation to an 8-bit image first — the steps become visible terraces.
• Use any subsampling option your version offers. A 2× subsample is the difference between a frozen machine and a workable mesh.

Blender is frozen right now — what to do

1. Don’t kill it immediately. If the disk light is blinking hard, the import may still be progressing through swap. Give it 5–10 minutes.
2. Check Task Manager / System Monitor. RAM pinned at the limit with near-zero disk I/O means it’s genuinely stuck — kill the process.
3. Recover, then shrink. Restart Blender, apply Fix 1 or Fix 2, and re-import the smaller file.
4. Save before big imports. Ctrl+S before clicking import costs two seconds and saves your scene if things go sideways.

Frequently Asked Questions