BlenderGIS Workflow Guide

How to Import GeoTIFF into Blender with BlenderGIS (2026)

A GeoTIFF is an ordinary TIFF image with geographic coordinates embedded inside it. Blender on its own ignores that georeferencing — but BlenderGIS reads it, so your raster lands in the scene at the correct real-world location and scale. Here is the full import workflow, including the CRS check that prevents 90% of problems and memory tips for large files.

People reach for GeoTIFF import for two main reasons: they already have an elevation model (a DEM) they want to turn into 3D terrain, or they have an orthophoto or satellite image they want placed accurately in a georeferenced scene. Both work the same way in BlenderGIS: GIS > Import > GeoTIFF. The critical detail is the coordinate reference system (CRS) — the import only behaves if the file’s CRS matches your scene’s CRS.

If you have not installed the add-on yet, start with downloading BlenderGIS and our installation guide. If you would rather download elevation data directly instead of importing a file, see how to create 3D terrain from DEM data.

Before You Import: The CRS Must Match

Every GeoTIFF carries a declared CRS — most commonly Web Mercator (EPSG:3857) for web-sourced imagery, or a UTM zone for survey data. BlenderGIS scenes also have a working CRS (Web Mercator, EPSG:3857, is the usual default). When the two match, the raster drops into the scene exactly where it belongs. When they do not match, the file lands in the wrong place, at the wrong scale, or the import fails outright.

So before importing, find out your file’s CRS. The BlenderGIS import dialog reports the CRS it detects in the file — compare it with your scene CRS in the add-on’s GIS preferences. If they differ, reproject the file first: open it in QGIS and export it again in EPSG:3857 (or in whatever CRS your scene uses). Two minutes in QGIS saves an hour of confused troubleshooting later. Mixing a UTM GeoTIFF into a Web Mercator scene is the single most common cause of “my import is in the wrong place.”

Step-by-Step: Import a GeoTIFF with BlenderGIS

1. Confirm the CRS. Check the file’s CRS (the import dialog shows it, or inspect it in QGIS) and make sure it matches your BlenderGIS scene CRS — usually EPSG:3857. Reproject first if it does not.
2. Open the importer. In the 3D Viewport, go to GIS > Import > GeoTIFF and select your .tif / .tiff file. BlenderGIS reads both the pixels and the embedded georeferencing.
3. Choose the import mode. For imagery and orthophotos, import as a textured plane: you get a correctly placed, correctly scaled image in the scene. For a DEM (elevation GeoTIFF), import it as a raster — the height values come in as data, ready for the next step.
4. Verify placement against a basemap. Load a BlenderGIS basemap of the same area (GIS > Web geodata > Basemap) and confirm your import lines up with real-world features — coastlines, roads, field boundaries. If it is offset or scaled wrong, you have a CRS mismatch: stop and reproject rather than nudging it by hand.
5. Next step for DEMs: build the mesh. An imported elevation raster is still flat data. Select it and run GIS > Mesh > Delaunay triangulation to convert it into true 3D terrain, then optionally drape imagery over it. The complete workflow is covered in Create 3D Terrain from DEM Data in Blender with BlenderGIS — join it at the triangulation step.

Large GeoTIFF Files: Memory Tips

GeoTIFFs get big fast: a single 10,000 × 10,000 pixel raster is 100 million pixels, and triangulation turns a large share of those into mesh vertices. Practical rules:

• Clip a subset first. If you only need a valley, do not import the whole country. Clip the area of interest in QGIS before importing — this one step prevents most crashes.
• Use 16 GB of RAM or more for serious rasters. Below that, keep imports modest (a few thousand pixels per side) and close other applications while Blender works.
• Downsample when detail allows. A regional overview does not need full-resolution source data; exporting a reduced-resolution copy for the first pass lets you verify the whole pipeline cheaply.
• If Blender still crashes or freezes on import, work through the troubleshooting hub before retrying with the same file — repeating an oversized import changes nothing.

What to do next. An imported GeoTIFF is the starting point, not the finish. Elevation rasters become 3D terrain via Delaunay triangulation (see the DEM-to-terrain guide); imagery rasters become texture sources you can drape over that terrain. Vector context — buildings, roads, boundaries — comes in through Shapefile import or the Overpass API. And if your end goal is a physical object, the finished mesh exports to STL or OBJ like any other Blender model. If anything in this chain misbehaves, the troubleshooting hub is the fastest route to a fix.

Frequently Asked Questions