Free tool
Are your 3D files ready for a configurator?
Drop a file in and find out in seconds. You get the same read our 3D team would give it: geometry, dimensions, pivot, materials, textures and compression, checked against the spec we actually build against. The file never leaves your machine - everything runs in your browser, and we never see the file or its name.
What the check looks at
Nothing here is a pass or fail. Every finding is either fine as it is, something we sort out in setup, or something worth changing at your end - and we will tell you which.
Geometry weight
Vertices per model and in total. Our limit is 10K per model, and under 1K is where a large range stays fast on a phone.
Dimensions and units
The bounding box in millimetres, so you can hold it against the measurements on your spec sheet. A model exported in millimetres instead of metres shows up immediately.
Pivot and level
Modules rotate and snap around their pivot. An off-centre pivot makes them drift apart as the customer builds, and a model that is not level hovers or sinks into the floor.
Materials and textures
Missing materials, missing textures, resolution and whether textures are square. A material with no texture renders as untextured white next to the ones that are right.
Compression
Draco, meshopt and KTX2. Draco is the important one: a Draco file looks perfect in every other viewer and will not load on our platform.
File size
Two megabytes is the ceiling and under one is the target. If textures are the reason, the report says so - that is usually a compression job, not a modelling job.
What it costs to get files ready
We cannot quote from a web page, but the shape of it is simple, and it has three steps.
Files that already meet the spec go straight to setup. There is no preparation line on the quote at all - this is the cheapest way to start, and it is why the check is worth running before you scope.
Files that need optimisation - too large, textures too big, the wrong texture format - we run through our own pipeline. You do nothing, and it adds a modest, predictable amount to setup because it is a batch job rather than craft work.
Files that need remodelling - geometry too heavy to decimate cleanly, no usable source, or CAD that has to be rebuilt for real-time - is the step that carries real cost, because someone models each part by hand. It is also the step most often avoidable: send us a representative file early and we will tell you which of the three you are in before you commit to anything.
What counts as one module
This comes up every time a modular range gets scoped, and getting it wrong in either direction distorts the estimate.
A module is a unique component we prepare once: origin calibrated, materials assigned, snap behaviour defined. Once it is in, it can be placed any number of times at no extra cost. So a single bench, a double bench and one leg design is three modules - not four, even though the double bench uses that leg twice.
The rule is simple: count unique parts, not placements. A different leg design would add a module. Using the same one more often would not.
Questions people ask
Does my file get uploaded anywhere?
No. The check runs entirely in your browser using your own machine. There is no upload, no server call, and no log of the file name or its contents. You can confirm it yourself: open your browser network tab, drop a file in, and you will see no request carrying it. That matters if you are sitting on files for a range that has not been announced yet.
Our files failed the check. Is that a no?
No. There is no pass or fail here, and that is deliberate. Everything the tool flags is fixable - some of it we fix in setup without you doing anything, some of it is a change at your end, and some of it we would remodel. A file that needs work tells us what the work is, which is a much better starting point than an empty inbox.
We only have STEP or CAD files. Can you use those?
Yes. STEP, SketchUp, Solidworks, PYTHA and most CAD exports are all things we work with - we convert them ourselves as part of preparing the range. The browser cannot read them, which is why this tool asks for GLB or glTF, but that is a limit of the tool and not of the platform. Send the file and you will get a concrete answer back the same day.
Why does Draco compression get flagged?
Because our platform does not support it. A Draco-compressed file loads perfectly in almost every other viewer you would test it in, so it is exactly the kind of thing that survives your own review and then fails at ours. Re-exporting without Draco is usually a single checkbox, and if it is not, we can decompress it.
What if we do not have 3D files at all?
Then we model them. It is a normal way for a project to start, and a lot of ranges we run began exactly there. Send drawings, dimensions and product photography and we will tell you what the modelling work looks like.
Can the tool tell us everything?
No, and it says so in the report. Whether a texture tiles without a visible seam is a judgement made with the eye, not something a browser can measure - we check that when we look at the files. The same goes for how cleanly the faces that snap together line up. The tool covers what can be measured; a person covers the rest.