Batch Model Compression

Up to 20 models per batch. If you exceed that limit, only the first 20 are processed and the rest are skipped with a notice, so keep each batch under the limit or split the work.

Yes. ZIP archives are extracted automatically, and each model inside becomes its own job. You can mix individual model files and ZIPs freely within the same batch.

Yes. One set of simplification, texture, and Meshopt/Draco settings is applied to every model in the batch, so bulk optimization results stay consistent. If individual files need different settings, process them in separate batches.

Upload them alongside the model files or include them inside a ZIP. The tool reads each model's internal file references and matches auxiliary files automatically; unmatched files are flagged with a warning so you can correct the upload.

Each model is processed independently, so one failure does not affect the others. Failed jobs are marked in the file list, while successful models remain available for individual download or as part of the ZIP.

Mesh simplification (Meshopt library) removes faces and vertices: higher strength means fewer polygons, smaller files, but visible quality loss. Meshopt and Draco are glTF container encodings that compress existing geometry without changing the face count; Meshopt decodes faster, and Draco can achieve smaller sizes, so the two are mutually exclusive. Use both strategies together: simplify first, then add one encoding. STL, OBJ, and FBX skip the container encoding and only receive simplification, plus texture compression when applicable.

Results vary widely: simple models may shrink by 30-50%, while complex textured models can reach 70-90% when all options are enabled. Each job keeps its own format, so the savings apply within that file's native format.

For web deployment, enabling everything (simplify, texture compress, and Meshopt/Draco) produces the smallest files. For archival use, you might skip simplification to preserve full detail. The batch applies the same choice to every file.

WebP offers the best compression ratio, about 30% smaller than JPEG at similar quality, and is supported by all modern browsers. Choose JPEG for maximum compatibility if needed. KTX2 is an option for GPU-ready delivery in supporting engines.

Each job keeps its original format: STL to STL, OBJ to OBJ, FBX to FBX, PLY to PLY. GLB/GLTF inputs export an optimized GLB, which is the only case where the container changes. Mixed batches produce mixed extensions inside the result ZIP.

KTX2 is a GPU-optimized texture format with hardware-accelerated decoding. Note that most image viewers and standard 3D software cannot open KTX2 textures. You need compatible tools such as Three.js (KTX2Loader), Babylon.js, or dedicated GPU texture utilities to view and use them.

Yes, Any3D's core features are free to use forever. We provide format conversion, model optimization, and online preview at no cost, with no registration required.

No. Files you select are processed only in your browser on this device, so they never leave your device and are never sent to our servers. We don't store any user files; after processing, related data in browser memory is released.

No installation required. Any3D is entirely browser-based; just open the webpage to use all features. It works on Windows, Mac, Linux, and other major operating systems.

The processing capacity depends on your device performance and the model's vertex count and texture complexity, rather than file size alone. We impose no file size limit, but when a model exceeds what your device can handle, the page may lag or even crash.