Why file4edit has no server

file4edit is a website whose 57 image and PDF tools run entirely in the visitor's browser, which is why it has no upload step and no accounts. Your browser downloads some HTML, CSS and JavaScript once and then runs the whole decode, edit and re-encode pipeline on your own machine — browsers have had everything needed for this since about 2020: canvas, typed arrays, Web Workers and WebAssembly. The design has costs and they are stated plainly: very large files are limited by your machine rather than by a datacentre, AVIF encoding works only in Chromium browsers, and nothing is remembered between visits.

How it works

  1. Open the network panel Open your browser's developer tools and switch to the network panel before you process anything.
  2. Process a file Convert, resize or compress an image as you normally would. No request appears, because the work happens in the tab rather than on a server.
  3. Disconnect and keep working Turn the network off entirely. file4edit installs a service worker on first load and keeps running with no connection, which a service that uploaded could not do.
  4. Check the format table on the front page The table on the landing page is measured in your own browser as the page loads rather than looked up. Reload it in a different browser and the row changes — on Safari, AVIF flips from writable to read-only while you watch.

Questions

Can anyone at file4edit see the images I convert?
No, because there is no server that receives them. file4edit is a static site: the tools are JavaScript running in your browser, the image is read from disk into that tab's memory, and it is released when you close the tab. Nothing is written to disk unless you download it, and there is no database anywhere that could hold a copy.
Why is file4edit free?
It costs almost nothing to run. file4edit is a set of static files on a CDN, and the actual processing happens on the visitor's own computer rather than on hardware someone has to rent, so there is no per-conversion cost to recover. There is no paid tier and no account.
What are the downsides of doing this in the browser?
Three real ones. Very large images are limited by your machine's memory rather than by a datacentre — above roughly 100 megapixels a browser starts refusing to allocate. AVIF can only be encoded in Chromium browsers, so Firefox and Safari can display it but not create it. And nothing is remembered between visits beyond a few preferences kept in your own browser's local storage.

Every tool