Look inside a Blender file without Blender

What it shows

• The Blender version that saved it. Read from the first 12 bytes (BLENDER-v293 means 64-bit, little-endian, Blender 2.93) or, for Blender 5.0 and later, the 17-byte header BLENDER17-01v0501. Inside, the file’s global block adds the subversion, the exact build (a 12-character commit hash and its date) and the oldest Blender the file says can read it completely, which answers “will this open in my 3.6?” before you install anything.
• The thumbnail. Blender stores a small preview, usually 128 × 128 pixels, when it saves from its window. It is shown and can be saved as a PNG. It is the picture a file browser shows, not a render.
• Scenes, objects and data. Each scene with its render engine (Cycles, EEVEE, Workbench), output resolution and percentage, frame range, frame rate and active camera. Each object with its type (mesh, camera, light, empty, curve, text, armature, grease pencil and the rest), the data it uses and its parent. Collections and what is in them, meshes with their vertex, face and edge counts, materials, cameras with focal length, lights with type and power.
• Every texture, and where it is. Each image datablock with its file path, marked packed inside (the picture is stored in the .blend), external (only a path such as //textures/wood_diff_2k.jpg is stored, so on any other computer it is missing and Blender shows it pink), generated in Blender, or coming from a linked library.
• Packed files out. Packed images, fonts and sounds are listed with their size and can be saved one by one under their original file names, or all at once in one ZIP. They come out byte for byte as they were packed: a packed JPEG is the original JPEG.
• The other .blend files it needs. A file that links objects or materials from other .blend files (File › Link) is incomplete without them. Each library is listed with its path and the datablocks taken from it, as a warning at the top.

How the file is read

The layout

A .blend file is Blender’s memory written to disk: a header, then thousands of blocks, each with a four-letter code (OB for an object, ME a mesh, IM an image, DATA for everything they point to), its length and the memory address it had when saved. One block, DNA1, describes every struct in the file: its fields, their types and sizes. This page reads that description first and finds every value by its field name, so it does not depend on a fixed layout, and it reads 32-bit, big-endian and 64-bit files alike.

Compressed files

Blender’s “Compress” option wraps the whole file: in gzip up to 2.93 (the file starts 1F 8B) and in Zstandard from 3.0 (it starts 28 B5 2F FD). The Poly Haven wet-floor-sign model this page is tested on is 124,582 bytes as saved by Blender 2.93 and 774,324 bytes unpacked. The file is unpacked in the tab first; for a big scene that needs memory for both copies.

Paths starting with //

Blender writes paths relative to the .blend file’s own folder with a leading //. //textures/brick.png means a textures folder beside the .blend. Absolute paths such as C:\Users\… show the folder layout of the computer that saved it.

What this cannot do

• Render the scene or show the 3D model. There is no viewport and no renderer here: meshes are counted, not drawn, and materials are named, not shaded. To see the model, someone with Blender has to export it (File › Export › glTF 2.0, OBJ or STL), and the 3D model viewer opens that.
• Edit, repack or fix the file. It only reads. It cannot relink missing textures, pack them in or save a .blend.
• Show what modifiers, geometry nodes or simulations make. Counts are the base mesh as saved. A cube with a Subdivision Surface modifier at level 3 is listed with 8 vertices, though it renders with thousands. Node trees, animation, shape keys, particles, add-on data and Python text blocks are counted under “Everything in the file”, not shown.
• Show textures it does not have. An external image is only a path in the file; its pixels were never in the .blend, so nothing can show them. Only packed images can be saved.
• Read very old files completely. It was tested on files saved by Blender 2.93, 4.5 and 5.1. Files from before 2.50 (2009) use the same block layout, so the version, names and counts are read, but some fields had other names then and may show as “—”, and those files usually carry no thumbnail.
• Read a damaged file. A file cut short, for example by a crash while saving, is read up to the break and the page says so. Blender keeps the previous save as .blend1 beside it, which often opens whole.

Useful to know about .blend files

Pink textures after opening a file from someone else

The textures were external and did not travel with the .blend. Drop the file here to see exactly which file names it expects and where. The sender can fix it with File › External Data › Pack Resources and save again, or send the texture folder with the same layout.

“File written by newer Blender binary”

Blender warns when a file was saved by a newer version than yours. The version and “Opens in” line here tell you which Blender to get before you download it. Newer files usually open in older versions with features missing; files from Blender 5.0 and later use a new header that Blender 4.4 and earlier cannot read at all.

What .blend1 files are

Each time Blender saves, it renames the previous version to .blend1 (and, with more save versions set, .blend2 and on). They are complete .blend files and open here the same way.

Why nothing runs

A .blend can hold Python scripts that Blender runs on open when “Auto Run Python Scripts” is on. This page never runs anything from the file; it only reads names and numbers.