A .vox file is a compact chunked voxel model, best known as MagicaVoxel's native format. Instead of arbitrary triangle surfaces it stores occupied integer grid cells and palette indices, which a renderer turns into visible cube faces.
Private for supported formats — processed in your browser
Convert supported files
Runs on your device
+
Drop VOX files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.
MagicaVoxel made VOX popular by providing a small, approachable voxel editor and a stable file format for pixel-art-like 3D scenes. The format spread into games, procedural tools and asset libraries because it is easy to generate and preserves the discrete voxel structure that a triangle export would erase.
How VOX works
VOX begins with the four-byte VOX signature and a little-endian version number.
MAIN contains child chunks such as SIZE, XYZI and RGBA.
XYZI records one byte each for x, y, z and palette index, imposing bounded grid coordinates in the classic form.
Converting to a mesh creates cube surfaces, so vertex and triangle counts grow beyond the number of occupied voxels.
When to use VOX
Opening MagicaVoxel assets in a conventional 3D workflow
Publishing a voxel model in GLB or USDZ
Preparing block geometry for printing
Inspecting a small procedural voxel fixture
Strengths and limitations
Strengths
Very compact for sparse block models
Preserves discrete voxel and palette identity
Simple chunk structure and deterministic coordinates
Limitations
Not a general polygon scene format
Meshing can multiply geometry size
Palette and per-voxel meaning may be flattened in ordinary mesh targets
Compatibility
MagicaVoxel and many voxel editors read VOX, while general DCC tools usually need an importer. Novus Convert decodes bounded chunks locally, builds surface geometry and exports STL, OBJ, 3MF, GLB, glTF, PLY or USDZ. The release fixture checks occupied extents and then independently reopens every generated output.
Occupied geometry is preserved; palette colours and scene-layer metadata are flattened or omitted by geometry-only targets.