How it works
The work happens on your device.
Every operation runs in your browser, on your own processor and memory — not on a server queue. Your files and results are kept in your FIXLYIER account so a project survives the tab, and nothing goes to an AI provider unless you approve that separately, for that operation.
What happens to a file
A file opens in your browser
When you choose a file, it opens directly into your browser's memory — the same way a photo opens in a local app — and is saved to your account so you can pick the work up later.
Your device does the work
Processing runs as code on your own processor and memory, inside the browser's sandbox. FIXLYIER's job is to bring the code to your file rather than send your file away to be processed. Saving the result to your account is a separate step, and that step does transmit.
The result is saved from memory
The output is assembled in your browser and downloaded straight to your disk. Your original is never modified — it is kept as the first version, so you can always go back to it.
Where your work lives
What you open is saved to your FIXLYIER account, so you can leave and come back to it — on the same machine or another one. Every version you commit is kept, and the original is never overwritten.
Saving something to your account is not the same as showing it to an AI model. When a capability genuinely needs to look at a file, FIXLYIER asks — for that operation, that file and that provider.
What that means in practice
No AI for ordinary edits
Compressing, resizing, cropping, rotating and converting are arithmetic. They run in the editor, need no AI model, and cost nothing from your daily allowance.
The work happens in the editor
Once a page has loaded, the processing itself runs in your browser — an image never makes a round trip to be resized. The network is used to save the result to your account.
One destination
The tool pages ship a Content-Security-Policy header with
connect-src 'self', so the browser will not let this page talk to anywhere other than FIXLYIER. Sending a file onward to an AI provider is a separate decision, made per operation, and FIXLYIER asks first.
What FIXLYIER ships
FIXLYIER only publishes tools that already work. What you see on this site is what it can do — no previews, no betas, no coming-soon pages.
Built with React and React Router · Type set in Archivo & IBM Plex Mono · Served as prerendered static HTML from FIXLYIER's own server