Tiny Online Tools
One camera, one light rig, every model
The difference between an asset library that looks professional and one that looks thrown together is almost never the models. It is the thumbnails. When every preview is shot from a slightly different angle, at a slightly different size, on a slightly different background, the grid looks noisy and nothing is comparable. When they all agree, the grid reads instantly.
This tool sets the camera once and then never touches it. Load ten, fifty or two hundred models, press Generate, and get back a ZIP of PNGs that were all rendered under identical conditions.
Two kinds of consistency
Fit each model scales every model to fill its frame. A screw and a shipping container end up equally legible. This is what you want for an icon grid, a file browser or a search-results page.
Uniform scale computes the camera distance once, from the largest model in the batch, and reuses it for every shot. Relative sizes are preserved, so the screw really does look tiny next to the container. This is what you want when scale is part of the information — a parts catalogue, a print-farm queue, a furniture range.
Everything else stays fixed in both modes: azimuth, elevation, light intensity, shading mode, backdrop and output resolution.
Transparent by default
Thumbnails have to work on a light page and a dark page, in a modal and in a sidebar. A baked-in background colour eventually clashes with something. PNG output carries a real alpha channel, so the same file works everywhere. Solid colours and a studio gradient are available when you want them, and JPG output is there for bandwidth-sensitive grids.
Formats it reads
GLB, GLTF, OBJ, STL, PLY, FBX, COLLADA, 3MF, 3DS, USDZ, OFF, AMF, VRML and Draco. Mixed batches are fine — a folder containing STLs from a slicer and GLBs from a marketplace is rendered into one coherent set.
What comes out
A ZIP containing one image per model, named after the source file, plus a thumbnails.json manifest listing the source name, the output name, the triangle count and the exact render settings used. That makes the ZIP a build input, not just a pile of pictures — you can regenerate the batch later with the same numbers.
Files that fail to parse are reported individually with the reason, and the rest of the batch still completes. One corrupt FBX should not cost you thirty-nine good thumbnails.
Privacy
Every file is parsed and rendered on your own machine, by your own GPU. Nothing is uploaded.