AssetRipper export mode comparison
Do not use the phrase export as FBX as if it describes every AssetRipper build. The available model output depends on the current project capabilities and the input. If FBX is the final format required by your pipeline, treat AssetRipper as the authorized extraction step and use a separate, appropriate converter only after you have a valid intermediate result.
| Output | Use it when | Check afterward |
|---|---|---|
| Unity Project | You want a project-shaped directory for Unity investigation | Editor version, packages, scripts, shaders, references |
| Primary Content | You need selected recognized assets | Missing dependencies, converted formats, naming |
| GLB or supported model output | You need geometry in a portable viewer | Materials, textures, rigs, animation tracks |
| Texture, audio, scene, prefab, or animation selection | You are investigating one content type | Whether the asset depends on a shared file |
A reliable AssetRipper export sequence
Make a working copy
Keep the original input untouched. Copy or select a separate output directory with enough room for generated assets.
Load the smallest useful input
Use one bundle, scene, serialized file, or folder first. Smaller inputs make warnings and missing dependencies easier to interpret.
Filter the content
Select the content types or assets that match your goal instead of exporting every object by default.
Choose the output mode
Pick Unity Project for editor work, Primary Content for focused inspection, or a model-oriented output for portable viewing.
Validate in the target tool
Open the result in Unity, a model viewer, an image editor, or an audio tool and check whether dependencies survived.
GLB, FBX, and model workflows
A model export is more than a mesh. A useful result may need a transform hierarchy, materials, texture files, skin weights, animation clips, and a coordinate-system adjustment. If a GLB opens with geometry but no textures, inspect the output folder for referenced images and confirm that the viewer can resolve their paths.
If the end goal is FBX, export a supported model representation first and convert it in a tool that understands the resulting geometry. Keep a copy of the intermediate export so you can compare whether a missing material or animation was lost in AssetRipper or in the second conversion step.
Why a GLB or Unity export can be empty
- The selected file is a container or reference, not the actual mesh or texture data.
- The model depends on a shared asset, material, shader, or texture that was not loaded with it.
- The input uses a Unity version, compression method, or custom format that the current build cannot reconstruct fully.
- The output was written to a different folder than expected, or the viewer is not resolving external resources.
- The source content is encrypted, stripped, or intentionally incomplete before AssetRipper sees it.
AssetRipper Export validation after the files are written
An AssetRipper Export is only the middle of the workflow. After the files are written, open the result in the target application and check the parts that matter for your goal. For a Unity Project, inspect the project structure, package requirements, scenes, prefabs, scripts, materials, and console warnings. For a model result, check geometry, transforms, textures, materials, skin weights, and animation tracks rather than judging it from one thumbnail.
Keep the output folder unchanged for the first review. If you immediately rename files, move textures, or repair references, it becomes difficult to tell whether a problem came from the parser or from the cleanup step. Copy the export before making edits, and note every conversion or import setting that changes the appearance. This is especially important when you need an FBX deliverable and use a separate converter after a supported intermediate model export.
A focused export is often easier to validate than a full reconstruction. Export one scene, one prefab, one texture group, or one model with its likely dependencies, then compare the result with the source file list. If the small test works, expand the input in controlled groups. If it fails, the smaller reproduction gives you a clearer explanation and a better report than a multi-gigabyte export with hundreds of warnings.
Think of AssetRipper Export as a handoff between parsing and inspection. The exported folder should preserve enough evidence for the next tool to open it, but it may still need package fixes, shader replacement, path repair, or format conversion. Keep the original export beside any edited copy so you can return to the parser result when a later cleanup step introduces a new problem.
Before calling an AssetRipper Export complete, compare the requested output with the actual result. If you wanted one animation clip, confirm that the clip and its references exist; if you wanted a scene, check its prefabs and resources; if you wanted a texture, confirm its dimensions and format. This small acceptance check keeps a technically successful write from being mistaken for a complete recovery.
Before an AssetRipper export, define the smallest result that answers your question. A Unity Project is useful for editor-oriented investigation, Primary Content is useful for a focused selection, and a model or GLB result is useful for portable viewing. Keeping these goals separate reduces memory pressure and makes it clearer whether a missing texture, material, animation, or reference came from the input or the chosen output mode.
After opening the exported files, validate them in the application that will use them. Check project structure and packages in Unity, geometry and materials in a model viewer, dimensions in an image editor, and tracks in an animation tool. Preserve the untouched export beside any repaired copy. That comparison protects the original evidence when a later conversion, shader replacement, or path edit changes the visible result.
Check the expected files
Confirm that the output contains the content type you selected and that the destination is the folder you intended to inspect.
Open the result independently
Use a compatible Unity editor, model viewer, image editor, or audio player instead of assuming the export is valid because no error appeared.
Trace missing dependencies
Look for shared resources, textures, materials, shaders, rigs, and references that were not included in the first input.
Record the boundary
Write down what worked and what did not, then preserve the version and warning details before trying another build.
AssetRipper export questions
Can AssetRipper export one content type?
Use the content filters and selection workflow when available in the current build. A focused export is usually easier to validate than a full project export.
Can AssetRipper export FBX directly?
Do not assume that every build provides direct FBX output. Use the supported model or project export and then an authorized conversion workflow if your pipeline requires FBX.
Why are my exported models empty?
Check whether the source contains the mesh data, whether dependencies were loaded, whether the export finished, and whether your viewer can resolve external textures or materials.
Where are AssetRipper exports saved?
The destination is chosen during the export workflow. Use a separate writable folder and verify the generated directory after the operation completes.