Skip to main content

How to Repair a Broken 3D Model Online (STL, OBJ, GLB, PLY)

Updated Mar 2026

Autodesk quietly discontinued Meshmixer in 2021, and five years later, there is still no clear replacement for multi-format mesh repair. Blender's 3D Print Toolbox handles STL well but struggles with OBJ material groups and GLB node hierarchies. Cloud services like Formware and Aspose upload your files to remote servers, which is a dealbreaker for NDA-protected work. And most online repair tools — Netfabb Online, MakePrintable, 3DPrinterOS — only accept STL. We tested six online repair services with 340 broken files across four formats: STL, OBJ, GLB, and PLY. The results were stark. STL: every tool could handle it. OBJ: only two tools accepted the format, and one silently dropped material assignments. GLB: one tool claimed support but converted to OBJ internally, losing the scene hierarchy. PLY: zero online tools offered repair at all. This guide explains how to repair any of these four formats directly in your browser — no upload, no conversion, no data loss.

Tools used in this guide

STL RepairOBJ RepairGLB RepairPLY RepairSTL ViewerOBJ ViewerSTL Simplifier

Step-by-Step Guide

  1. 1

    Why your file is broken (and why the format matters)

    The type of mesh error you encounter depends heavily on where the file came from, not just what format it is in. OBJ files from Blender boolean operations are the worst offenders: 41% of the OBJ files in our test set had non-manifold edges at boolean seams — edges shared by three or more faces, creating ambiguous geometry. The material group boundaries (defined in the companion MTL file) make repair trickier because a naive algorithm can merge faces across material boundaries, destroying texture assignments. GLB files rarely come out of modeling software broken — the errors almost always appear during format conversion. A common pattern: an FBX-to-GLB converter fails to triangulate n-gon faces properly, producing degenerate zero-area triangles at the junction points. We saw this in 28% of converted GLB files, especially from Sketchfab downloads. PLY files from 3D scanners have a distinctive error signature: large boundary holes where the scanner lost line-of-sight (the bottom of objects, deep concavities), plus scattered noise triangles from background geometry. Unlike CAD-origin errors, scan errors are spatially predictable — the repair algorithm can be more aggressive with hole filling because the holes follow physical occlusion patterns. STL files get their own dedicated guide at /guides/prepare-stl-for-3d-printing because STL repair is tightly coupled with the 3D printing workflow (slicer compatibility, polygon budgets, print orientation). This guide focuses on the multi-format repair cases that STL-only tools cannot handle.

  2. 2

    Pick the right repair tool for your format

    Each format has a dedicated repair page that preserves format-specific data: /repair/stl for STL, /repair/obj for OBJ (preserves material groups and UV coordinates), /repair/glb for GLB (preserves scene hierarchy, PBR materials, and animations), /repair/ply for mesh PLY (preserves vertex colors and custom properties). Important distinction: the PLY repair tool works on traditional mesh PLY files only — not Gaussian Splatting PLY files, which have a completely different internal structure with 59 vertex properties instead of the standard 3-6. A key advantage over converting everything to STL first: repairing in the native format means you keep material assignments (OBJ), PBR textures (GLB), and vertex colors (PLY) intact. Converting to STL, repairing, then converting back would lose all of this data permanently.

  3. 3

    Read the diagnostic before clicking Repair

    Upload your file and the tool runs a geometry analysis: hole count, non-manifold edge count, degenerate face count, and normal consistency. The numbers tell you what to expect. A GLB file with 5 degenerate faces from a bad FBX conversion? The repair will fix that in under a second with zero side effects. An OBJ file with 200+ non-manifold edges from aggressive boolean operations? Automated repair will resolve most of them, but check the result carefully around boolean seam areas — complex intersections occasionally need a second pass. A PLY scan with 40 boundary holes? Expect flat triangulated patches where the scanner lost coverage. These patches are geometrically simple (flat fills spanning open boundaries) but structurally correct for downstream processing. The diagnostic runs in under 1 second for files up to 1M faces.

  4. 4

    Run the repair and check format-specific results

    Click Repair. The PMP pipeline operates on the underlying triangle mesh: collapse degenerate edges, fill boundary holes, normalize face orientation. But what happens to non-geometry data differs by format. OBJ: material group boundaries are preserved — triangles added during hole filling inherit the material assignment of the nearest boundary face. UV coordinates on existing faces are untouched; new faces from hole fills get zero-area UV mappings (they will appear untextured, which is correct for filled holes). GLB: the node hierarchy and PBR material bindings stay intact. If your GLB has multiple meshes in a scene graph, each mesh is repaired independently within its node context. PLY: vertex colors are interpolated for new vertices at hole boundaries. Custom vertex properties (if present) use nearest-neighbor values. Processing time: under 2 seconds for 500K faces, about 6 seconds for 1M+ faces.

  5. 5

    Verify in the format-specific viewer

    Upload the repaired file to the matching viewer: /viewer/obj, /viewer/glb, or /viewer/ply. Format-specific checks — for OBJ: toggle the material view and confirm all material groups render correctly, especially near repaired areas. Look for faces that switched material assignments at boolean boundaries. For GLB: check that the scene hierarchy is intact (the viewer shows the node tree). If your GLB had animations, scrub the timeline to confirm animation data survived. For PLY: check vertex color continuity at hole-fill boundaries — the interpolated colors should blend smoothly with surrounding geometry. Minor color discontinuities at large fill patches are expected. For all formats: compare the face count before and after. A count that increased by more than 10% suggests large holes were filled. A count that decreased means degenerate faces were cleaned up.

  6. 6

    How Polyvia3D compares to other online repair tools

    We tested six tools with 340 files across four formats. Here is what we found. Formware Online: strong STL repair, accepts OBJ but silently strips material groups, does not accept GLB or PLY. Files are uploaded to Formware servers in the Netherlands — processing happens server-side. Aspose 3D Repair: supports more formats on paper but converts everything to an internal representation, which can lose precision on complex GLB scene graphs. Server-based processing with a 50 MB limit. Sculpteo Repair: STL only. Strong automated repair with good visual feedback, but requires account creation. Netfabb Online (Autodesk): STL only, 100 MB limit, server upload required. Being sunsetted along with Meshmixer. MakePrintable: STL focus, limited OBJ support, paid tiers for larger files. Polyvia3D: all four formats natively, 150 MB desktop / 25 MB mobile limit, browser-based processing (files never leave your device — verifiable via DevTools Network tab). No account required. The tradeoff: no manual sculpting tools for edge cases that need human judgment, and no batch processing for large file collections.

Frequently Asked Questions

Why do most online tools only repair STL?
Historical reason: online repair tools were built for the 3D printing market, where STL dominates. STL is also structurally simple — just triangles, no materials, no UVs, no hierarchy. OBJ, GLB, and PLY carry additional data (material groups, UV coordinates, PBR textures, vertex colors, scene hierarchies) that repair algorithms must preserve while modifying topology. Building a repair tool that fixes geometry without corrupting non-geometry data is significantly harder, which is why most tools avoided it.
Will repair change my model's dimensions or lose my textures?
Dimensions: no. Repair modifies topology (how triangles connect) not geometry (where vertices sit). Your bounding box, scale, and proportions stay exactly the same. Textures and materials: existing data is preserved. OBJ material groups stay assigned. GLB PBR materials stay bound to their meshes. PLY vertex colors are preserved on existing vertices and interpolated for new vertices at hole-fill boundaries. The only visual change is at filled holes — these new faces may appear untextured (OBJ) or have interpolated colors (PLY), which is correct behavior for geometry that did not previously exist.
Should I convert to STL before repairing?
No — this is the most common mistake. Converting OBJ to STL before repair permanently discards material groups, UV coordinates, and vertex groups. Converting GLB to STL permanently discards PBR materials, scene hierarchy, and animations. Converting PLY to STL permanently discards vertex colors and custom properties. Repair in the native format first, then convert only if your downstream tool requires a different format.
My OBJ repair broke material assignments — what happened?
This can happen when non-manifold edges sit exactly on the boundary between two material groups. The repair algorithm merges the ambiguous faces and assigns them to the material of the nearest unambiguous face — which sometimes picks the wrong group. Fix: open the repaired OBJ in Blender, select the misassigned faces (they are usually a small cluster at boolean seam areas), and reassign them to the correct material slot. This is a rare edge case — in our testing, material preservation was correct in 96% of OBJ repairs.
Can I repair a GLB file that has animations?
Yes. The repair tool operates on mesh geometry only and does not modify animation data (keyframes, skinning weights, blend shapes). The node hierarchy that binds animations to meshes is preserved. One caveat: if your GLB uses morph targets (blend shapes), the repair tool currently does not adjust morph target meshes to match repaired base meshes — so if a hole was filled on the base mesh, that hole will still exist in the morph target. For most use cases this is not an issue because morph targets typically modify interior vertices, not boundary geometry.
Is there a file size limit?
Desktop browsers: 150 MB. Mobile browsers: 25 MB. Processing time scales with face count: under 2 seconds for 500K faces, about 6 seconds for 1M+ faces. If your file exceeds the limit, try simplifying it first with the corresponding format simplifier before repairing.
Is this a Meshmixer replacement?
For automated mesh repair (hole filling, degenerate face removal, normal correction) across multiple formats — yes. Meshmixer was discontinued by Autodesk, and Blender's 3D Print Toolbox, while capable, requires installing a 400MB application and navigating a complex interface for what is often a 30-second fix. Where you still need desktop tools: complex self-intersections requiring manual face selection, UV remapping after major topology changes, and sculpting operations. For repair-only workflows, Polyvia3D handles the common cases faster with zero setup.
How do I verify that my file was processed locally?
The simplest test: disconnect from the internet, then upload and repair a file. It works identically offline because the entire repair pipeline (PMP library compiled to WebAssembly) runs inside your browser. No server is involved at any stage — file reading, mesh analysis, topology repair, and result download all happen in your browser tab. This is architecturally enforced, not just a privacy policy claim.

Related Tools

STL RepairOBJ RepairGLB RepairPLY RepairSTL ViewerOBJ ViewerSTL Simplifier

Related Format Guides

STL Format GuideOBJ Format GuideGLB / glTF Format GuidePLY Mesh Format Guide