How it works
Your files stay on your device. Here is how.
Every MicroPlugins tool runs inside your browser. When you open a file, your own computer or phone does the work. This page explains what happens, what we can and cannot see, and how to check it yourself.
In short
MicroPlugins sends the tool to your browser instead of sending your file to a server. The page loads the code it needs, your browser reads the file locally, JavaScript and WebAssembly process it on your device, and any result downloads straight to your computer or phone. The file’s contents are never transmitted.
Upload-based tools vs MicroPlugins
Most online file tools follow the same pattern: you upload the file, their server processes it, and you download the result. That works, but your file now sits on a computer you do not control.
MicroPlugins reverses the pattern. Modern browsers can run heavy software at near-native speed through WebAssembly, and draw complex 3D scenes with WebGL. So the tool comes to your file, not the other way round.
| Upload-based tool | MicroPlugins | |
|---|---|---|
| Where the work happens | Their server | Your browser |
| Your file crosses the internet | Yes, twice | Never |
| A copy stays on someone else’s computer | Possibly | No |
| Speed depends on | Upload speed and server queue | Your device |
What happens when you open a file
- The page loads the tool Your browser downloads the app’s code from microplugins.app, like any other web page.
- You choose a file Dropping or picking a file lets this browser tab read it. Nothing is sent anywhere.
- Parsers run on your device JavaScript and WebAssembly parsers decode the file inside the tab, often in a background worker. Some formats need an extra parser, such as OpenCascade for STEP or web-ifc for IFC, which your browser downloads once.
- Your graphics chip draws it WebGL 2 renders the model with your device’s GPU, so rotating and zooming stay smooth.
- Results are saved locally Converted or compressed files are created in your device’s memory and downloaded straight to it.
What we can and cannot see
| Data | Sent to MicroPlugins? |
|---|---|
| Your files and their contents | Never |
| File names, sizes and model details | Never |
| Measurements, edits and settings you make in a tool | Never |
| Cookies, analytics or advertising IDs | None are used |
| Standard request data: IP address, browser type, pages requested | Yes, like every website. Our hosting provider logs these requests to deliver pages and block abuse. |
What stays in your browser
A few small things are saved in your own browser’s storage. They never leave your device:
- Your theme. Whether you chose light or dark mode.
- Layout preferences. Panel sizes and the interface mode you picked in the 3D Viewer.
- A short-lived copy of a file you hand over. When you send a result from the converter or compressor to the viewer, it is stored in the browser for that hand-off and deleted once the viewer opens it.
You can clear all of it at any time from your browser’s site data settings.
How to check it yourself
You do not have to trust us. Your browser’s developer tools show every request a page makes.
- Open a tool, such as the 3D Viewer.
- Open developer tools. Press F12 or Ctrl Shift I on Windows and Linux, or ⌘ ⌥ I on a Mac. In Safari, first turn on Show features for web developers in Settings, Advanced.
- Select the Network tab and tick Preserve log.
- Drop a file onto the page.
- Read the list. You will see the page download code, and perhaps a parser for your format. You will not see any request that sends your file.
Tip: sort the Network list by size, or filter it to Fetch/XHR. An upload would appear as a large outgoing request with your file in its payload. There is none.
How the site is secured
- HTTPS everywhere. Every page is served over an encrypted connection, and browsers are told never to use plain HTTP.
- No third-party code. No ads, no analytics, no tracking pixels and no social widgets. Fonts, parsers and decoders are all served from microplugins.app itself, so opening a file contacts no other company.
- A strict Content Security Policy. Pages declare exactly which scripts may run, which blocks injected code.
- Open source where it matters. The 3D engine is MIT-licensed, so anyone can read the code that handles your files.
Where local processing has limits
Doing the work on your device has trade-offs, and you should know them:
- Speed depends on your device. A large CAD assembly opens faster on a desktop than on an older phone.
- Memory is the ceiling. Single files up to 2 GB are supported, but your device needs enough free memory to hold the model.
- Loading from a link is different. If you open a model or an environment image by URL, your browser fetches it directly from that address, and that server sees the request.
Frequently asked questions
Does MicroPlugins upload my files?
No. Your browser reads and processes each file on your own device. The file is never sent to MicroPlugins or to anyone else.
Can MicroPlugins see what I open?
No. We never receive your files, their names or anything about their contents. Our hosting provider only sees the standard request data every website receives, such as which pages were loaded.
Why is the first STEP or IFC file slower to open?
CAD and BIM formats need a large parser, such as OpenCascade for STEP or web-ifc for IFC. Your browser downloads it the first time you open that format, then keeps a copy, so later files open faster.
Do the tools use cookies or analytics?
No. MicroPlugins sets no cookies and runs no analytics or advertising scripts. A few preferences, such as light or dark theme, are saved in your own browser.
Is it safe to open files covered by an NDA?
Local processing means the file never leaves your device, which removes the biggest risk of online tools. As with any software, follow your organisation’s own rules for confidential data.
See it for yourself
Open the 3D Viewer with your developer tools open and drop in a file. Watch what does not happen.