About
Who builds ilove3d
ilove3d is a personal project. Here's who writes it, how it works underneath, and why it costs nothing.
Author
Luca Cuello
Developer. I write and maintain ilove3d, launched in July 2026.
What it is
A set of 3D tools that run inside the browser: open a model and measure it, convert between formats, repair a broken mesh, lighten it, and build printable pieces from scratch: vases, lamps, boxes, hose adapters, star maps. All free, none of them ask you to sign up. It started as a dental STL and PLY viewer, and that tool is still the specialized vertical of the set. It can also be installed as an app straight from the browser, with no download and no app store.
Why your files never leave your machine
Because there is no server to upload them to. Every tool runs on WebGL and WebAssembly inside the tab: the file is read from disk into browser memory, processed there, and the result downloads straight back. You can check this yourself by opening the browser's network panel while using any tool: you will not see an upload, because there isn't one. The single exception is stated plainly: the AI features send the text you type, never the model and never the filename.
What we measure
To learn which tools work and whether people return, we record usage events and a random identifier stored in your browser. No account is needed, and you can remove it by clearing this site's local data. We measure opens, loads, previews and downloads; your models and filenames are never sent. Those same events are stored in my own database and in PostHog, the tool I use to analyse them: both receive exactly the same thing. The questions on the site (whether a download worked, which format is missing, which tool you were looking for) only store the answer you pick, with the tool and the format, and nothing about you. They work even if you decline analytics, because you send the answer yourself.
Why it's free
No accounts, no paid tier, no file limits, no watermark. Serving the site is cheap precisely because the processing happens on your machine and not on a server of mine: what gets sent is a page, not your geometry. It is funded as a personal project. If that ever changes, it will be said here before anywhere else.
What it's built with
Three.js for everything 3D, except the DICOM viewer, which uses Cornerstone3D. Next.js sits on top. The generators build watertight geometry by construction, with no boolean operations, and each one has a signed-volume and edge test that runs outside the browser.
If something's broken
Write to me here and I'll read it. A bug, a missing tool, or something that didn't work the way you expected.