tool4.dev

Files / LOCAL TOOL

FBX Asset Repairer

Repair broken FBX texture paths across an asset pack and download a portable ZIP locally.

Runs locally — input is never uploaded
Asset packUp to 500 files · 250 MiB total
Texture pools
Repair planReady when you are

Choose FBX files with their texture folders to build a repair plan.

Detailed FBX preview

Drag to orbit · wheel to zoom · selected textures are loaded locally

WHAT IT DOES

Repair the asset pack once instead of reconnecting every material in every editor.

Choose a complete asset folder and the repairer recursively finds its FBX and texture files. Exact paths and filenames are accepted automatically; extension alternatives and nearby filenames are proposed visibly for review, with deterministic alphabetical tie-breaking. The download contains repaired copies, the textures they resolve to, and machine-readable and human-readable reports; source files are never overwritten.

Why use it?

Use it to repair broken texture file references in an asset collection without rewriting the original geometry or overwriting source files.

How to use this tool

  1. Choose the asset folder with its FBXs and textures so the repair plan can compare available paths and filenames.
  2. Review exact, approximate, ambiguous, and missing matches. Open a row's preview and explicitly choose the intended texture where naming alone is insufficient.
  3. Prefer Strict export after resolving every review item. Permissive export keeps unresolved references and proposed choices in a bundle with reports; it does not make them correct.
  4. Download the repaired copies and inspect the reports before importing them. This repairs texture references, not missing UVs, skin weights, or incompatible animation rigs.

Details and limitations

  • Bulk selection handles as many as 500 local files and 250 MiB in one pass, deduplicating a resolved texture used by several models in the ZIP.
  • Exact relative paths and filenames are green. Extension alternatives and similar filenames are selected as approximate matches with a yellow warning, using filename similarity and alphabetical order to break a tie; manually choosing the file confirms it.
  • Clicking a repair-plan row opens an orbitable 3D preview in the browser. Texture assignments are routed into that preview from the selected local files, so a mapping can be checked before export.
  • Binary and ASCII FBX 7 documents are parsed as node trees. Only texture filename properties are replaced; node offsets are rebuilt while geometry, rigs, animations, and unrelated encoded properties are preserved.
  • Strict export refuses a bundle with approximate, missing, ambiguous, or invalid items. Permissive export includes every visible proposed match and unchanged unresolved reference alongside both reports so incomplete work is never silent.

COMMON QUESTIONS

FBX Repairer questions

Can it repair a whole folder of FBX files at once?
Yes. Click the asset drop zone to choose a folder, or drop the folder into it. Subfolders are scanned recursively, unrelated file types are ignored, and one shared texture index is used for every FBX before the result is downloaded as one ZIP.
How do I assign a texture when the automatic match is wrong?
Every external texture reference has an assignment picker containing the image files from the selected pack. Choose another file or leave the reference unresolved; selecting its row refreshes the local 3D preview with the current assignments.
Will it choose between similarly named texture variants?
It proposes the closest filename and uses alphabetical order when candidates are equally close. Because that is not an exact match, a yellow warning remains until you review and confirm or replace the assignment.
Does it overwrite the original FBX files?
No. Browser file access is read-only here. Repaired copies are written into the downloaded ZIP, and the selected source files remain untouched.