Drop a folder or ZIP of messy model files (FBX with loose textures, GLTF split into .bin + images, OBJ missing its MTL) and get a cleanly organized ZIP with every file in its place.
or click to browse, paste supported
The packer scans your upload for model files, then resolves each model's external dependencies: FBX texture paths, GLTF .bin buffers and images, and OBJ .mtl material files with their map_* textures. Every model gets its own folder in the output ZIP; files that could not be matched to any model go into _unmatched.
| Option | What it does | Default / range |
|---|---|---|
Embed resources into GLTF | Separate .bin and texture files are embedded into a single self-contained GLTF. | off |
Embed textures into FBX | FBX models with separate textures are merged into a single FBX with textures embedded. | off |
Include unmatched files | Unmatched files are copied into the _unmatched folder of the ZIP. Disable to drop them from the output. | off |
| Option | What it does | Default / range |
|---|---|---|
Model packs | Each model file becomes a pack folder in the output ZIP, with its detected dependencies grouped alongside. |
| Option | What it does | Default / range |
|---|---|---|
Unmatched files | Files that no model references. Enable "Include unmatched files" to copy them into the _unmatched folder of the ZIP. |
About this tool
Usually not. FBX stores material and texture references, but the actual texture images are separate files. If those files are missing or scattered, the model renders without textures. This tool bundles the referenced textures with the FBX so the asset stays complete.
No. Model files are copied into the ZIP exactly as they are. The only transformation is optional: GLTF models can be embedded into a single self-contained GLTF file with textures and binary data inlined.
Unmatched files are collected in the _unmatched folder of the output ZIP, so nothing is silently dropped.
When a model references a .bin buffer, texture, or .mtl material file that isn't present in your upload, it counts as a missing reference. The pack results flag the missing count so you can add the files and pack again.
Any format the site can read is recognized as a model file: FBX, GLTF, GLB, OBJ, STL, 3MF, PLY and more. Dependency resolution is automatic for FBX, GLTF and OBJ; other formats are packed as self-contained files.
Up to 50 main model files. Models beyond the limit are skipped and flagged in the results. For more models, pack them in batches.
When a reference path in the model can't be found in the upload, the tool falls back to matching by file name; for example, texture.jpg matches a texture file with the same name. For more reliable resolution, keep textures in the same folder as the model and keep file names consistent.
General questions
Core features are free forever. Format conversion, model optimization, and online preview do not require an account. Some advanced features are paid.
No. Files you select are processed only in your browser on this device, so they never leave your device and are never sent to our servers. We don't store any user files; after processing, related data in browser memory is released.
No installation required. Any3D is entirely browser-based; just open the webpage to use all features. It works on Windows, Mac, Linux, and other major operating systems.
There is no cap on file size or polygon count. How large a model you can open depends on your device's memory and graphics card, and very heavy models may make the page lag or crash. Some tools do limit how many files go in at once, such as 50 models per batch or single images up to 50 MB in texture compression. See Limits for the full list.
