Slicer import fixes

OrcaSlicer STL import error? Find the file problem locally

OrcaSlicer inherits parts of the Bambu Studio and PrusaSlicer workflow, but it still cannot open a file that is structurally broken. A failed import, a model that lands at the wrong scale or a repair that leaves the plate empty is usually a file or geometry problem that can be identified before changing profiles. This page runs those checks locally in your browser.

OrcaSlicerNo uploadSlicers · Windows / macOS / Linux

Typical symptoms

  • The import fails or the object never appears on the plate.
  • A 3MF project opens with missing parts or an empty object list.
  • The model is scaled by a familiar factor such as 10, 25.4 or 1000.
File import check

File import check

No upload

OrcaSlicer

The detected signature, bounds and topology are reported locally. These are triage signals, not a slicer validation.

File checks

The detected signature, bounds and topology are reported locally. These are triage signals, not a slicer validation.

Detected file signatureBoundary edges · Non-manifold edgesTypical symptoms

Drop the file that won't open

STL, OBJ, PLY, 3MF, GLB, glTF, or a .gltf with its .bin companions. The file is read locally.

Choose a file

Max file size: 500 MB · No upload

No upload · Worker

Typical symptoms

  • The import fails or the object never appears on the plate.
  • A 3MF project opens with missing parts or an empty object list.
  • The model is scaled by a familiar factor such as 10, 25.4 or 1000.
  • Automatic repair completes but the preview still shows gaps, flipped faces or non-manifold edges.

Common causes

The file is incomplete or mislabeled

A browser error page saved as .3mf, a partial download or a renamed mesh can look valid in the file picker while failing the format check inside OrcaSlicer.

The mesh is open or self-intersecting

OrcaSlicer may repair simple defects, but a heavily open surface or overlapping shells can produce missing layers and unstable slicing. The topology report separates these cases.

The 3MF project metadata is incompatible

A 3MF created by a different slicer may contain settings or object structure OrcaSlicer does not expect. Exporting a standard model file is often more reliable than importing another slicer's project.

The export uses the wrong units

STL and OBJ do not carry reliable print units. Metres, inches and millimetres can all produce a valid file at the wrong physical size; the bounds check makes the mismatch visible.

Export checklist

  1. 1

    Export a binary STL or a standard 3MF in millimetres and check the file after downloading it.

  2. 2

    Keep one object per file unless the slicer project needs a deliberate multi-part arrangement.

  3. 3

    Apply transforms and place the object near the origin before export.

  4. 4

    If a 3MF project fails, try exporting the geometry as STL to separate a project issue from a mesh issue.

How it works

  1. 1

    Drop the file and confirm the detected signature and triangle count.

  2. 2

    Check for empty geometry or a scale error using the reported bounds.

  3. 3

    Review boundary, non-manifold and self-intersection findings before slicing.

  4. 4

    Use the repair links to create a new cleaned mesh, or re-export from CAD if the file is unreadable.

Questions

References

Specs verified: 2026-11-01

Each page checks the file header, triangle count, bounds and topology in this tab. No account, upload or slicer integration.

Other slicer checks