zlim
Docs
// format optimizer

Any 3D format in,
optimized model out.
One API.

Stop juggling Blender, Pixyz, gltfpack, and a zoo of plugins. Zlim ingests the dirty formats — STEP, CATIA, FBX, USD, and more — and returns one clean, optimized GLB. Deterministic. Measurable.

70–80%
file size reduction
11
input formats
1
clean output (GLB)
Read the docs See pricing

The format gauntlet — any format in, one GLB out

CAD
STEPIGES · soonCreoCATIASolidWorks · soon3MFDXF · soon
DCC & Mesh
FBXOBJColladaUSD / USDZ3DS · soonglTFVRML / X3D · soonSTLPLY
GLBoptimized · compressed · web-ready

The 3D format tax

Format chaos

Every tool exports its own thing — STEP from CAD, FBX from your DCC, USD from the pipeline. Nothing speaks to everything.

Bloat

Raw exports ship 5–10× heavier than they need to be: uncompressed geometry, full-res textures, thousands of stray draw calls.

Broken files

Dirty CAD, FBX, and USD exports arrive with missing materials, inverted normals, or geometry no viewer will open.

Won’t load on web or AR

Authoring formats aren’t real-time formats. Browsers, AR, and game engines need GLB — and they need it small.

Why Zlim

Dirty-format breadth is the moat

Only Zlim ingests the formats nobody else tames — STEP, CATIA, Creo, FBX, USD, 3MF — and returns one clean, optimized GLB in a single pass. No Blender round-trips, no plugin zoo.

Deterministic quality

70–80% smaller. Not approximately smaller. Measured per job via mesh quantization, Draco compression, and texture mipmap generation.

REST API

Integrate from any backend or build pipeline. A CLI and MCP server are coming soon.

Starts free, scales with you

Start free with 25 optimizations a month. Upgrade to Pro at $29/mo for more volume, every format, and larger files. Simple plans, no per-seat pricing.

What Zlim optimizes — the whole budget

−70–80%

Faces

Tolerance-bounded decimation and vertex quantization remove redundant geometry without changing the silhouette.

Fewer

Draw calls

Merging meshes that share a material cuts the number of GPU binds — the lever that actually moves frame rate on the web and in AR.

KTX2

Texture memory

Textures transcoded to KTX2/Basis stay GPU-compressed in VRAM — the hidden half of the budget that crashes mobile and AR.

Poly count is one lever of three. Zlim optimizes all of them — and reports each, measured, on every job.

Before / after — one measured job

A representative product model on the default profile. Every number is reported per job — deterministic and reproducible.

MetricBeforeAfterReduction
Faces1,240,000286,000−77%
Draw calls34012−96%
Texture memory96 MB18 MB−81%
File size45 MB9.2 MB−80%

Same look, every lever down. Results depend on the source model; the reduction is always measured and returned with the job.

How it works

1

Upload your model

Create a job on the hosted API and upload your file. Any supported format.

bash
curl -X POST https://zlim.ai/api/v1/jobs \
  -H "Authorization: Bearer $ZLIM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "filename": "model.fbx", "options": { "preset": "balanced" } }'
2

Zlim optimizes

The engine runs mesh decimation, quantization, Draco compression, and texture optimization. Typically completes in seconds.

3

Download the GLB

Poll the job status, then fetch the result URL. A signed download link returns the optimized GLB — 70–80% smaller.

bash
curl https://zlim.ai/api/v1/jobs/$JOB_ID/result-url \
  -H "Authorization: Bearer $ZLIM_API_KEY"
# → signed URL for model.glb  (73% smaller)

Ready to shrink your pipeline?

Any 3D format in, optimized model out. See exactly how it works.

Read the docs See pricing