Browser-based GLB Compressor — demo reduced from 3.14 MB to 489.58 KB

Hi everyone,

I’m the creator of Toolkit360. I built a free browser-based GLB compressor and would love feedback from developers working with glTF/GLB assets.

In a recent test using the built-in demo model:

  • Original size: 3.14 MB

  • Compressed size: 489.58 KB

  • Reduction: approximately 85%

This result is specific to the demo model; compression and visual quality will vary with the asset and settings.

Features include:

  • Draco and Meshopt geometry compression

  • WebP texture optimization

  • Smart target-size mode and manual controls

  • Original/compressed model preview

  • Local processing without uploading your model

  • No sign-up required

Try it here:

I’d appreciate feedback from anyone trying the exported models in Babylon.js, especially on materials, animations and loading compatibility. If you encounter an issue, please share the settings and error details so I can investigate.

What would make this tool more useful in your asset workflow?

7 Likes

That’d be an awesome improvement over this babylonjs extension I wrote years ago. It’d be a nice touch to be able to optimize these files in-place in your project.

1 Like

This would be an awesome addition to the sandbox and inspector. cc @ryantrem

Awesome work @AkashGuptaEmk_AkEmk !

1 Like

Can’t agree more!!

1 Like

Thank you so much, everyone! Really appreciate the positive feedback and suggestions! :raising_hands:

Integrating GLB compression directly into the Babylon.js Sandbox and Inspector would be an amazing improvement for developers.

I’d love to explore this possibility and collaborate with the Babylon.js team to make it happen.

The goal behind Toolkit360’s GLB Compressor is to make 3D model optimization simple, fast, and accessible directly in the browser.

@ComicSans @ComicSans Thanks again for the encouragement!

I’d be happy to discuss the technical requirements and explore how we could bring this functionality into the Babylon.js ecosystem. :rocket:

1 Like

@labris This is very similar to what you did, but with more statistical elements added.

2 Likes

Hi @brightMoon,

thanks for sharing! The extra statistics are great for comparing before and after compression. Which metrics do you find most helpful? I’d love to learn from your approach.

Hi, the file size and the number of vertices have been very helpful to me. The most important one is the file size. This is the most intuitive way to judge. If it seems to meet my expectations, I will directly download the file.

1 Like