Every time you use a "free" online tool to compress an image, convert a PDF, or trim a video, there's a question worth asking: where does your file actually go?

For most web-based tools, the answer is uncomfortable. Your file gets uploaded to a server you know nothing about, processed there, and then (maybe) deleted. You've just handed a stranger your document, photo, or video and trusted them to handle it responsibly.

EazyStudio works differently — not just as a policy, but as a technical architecture. Here's exactly how.

The problem with server-side processing

When you visit ilovepdf.com, smallpdf.com, or dozens of similar tools and drag in a file, what happens next is invisible to you. Your browser sends the file over the network to a remote server. That server runs the conversion or compression, then sends the result back. Your file existed on someone else's machine.

This creates real risks:

  • Data exposure — the server operator, their employees, and potentially their hosting provider can access your file.
  • Breach risk — if that server is compromised, your files could be in the leak.
  • Data retention — many services keep uploaded files for hours, days, or longer, even if they claim to delete them.
  • Regulatory risk — if you're processing confidential documents (contracts, medical records, financial data), uploading to a third-party server may violate GDPR, HIPAA, or NDA agreements.
In 2019, researchers found that several popular "free PDF" tools were storing uploaded documents indefinitely. Some were indexed by search engines. Others were sold as datasets.

How EazyStudio processes files locally

Every tool on EazyStudio runs entirely inside your browser using a combination of modern web APIs. No file data ever leaves your device.

Here's the technical stack that makes this possible:

  • File API — when you select a file, the browser gives JavaScript temporary read-only access to it in memory. Nothing is transmitted.
  • WebAssembly (WASM) — for heavy lifting like audio/video encoding, we use compiled C/C++ libraries (FFmpeg, libvips) that run inside the browser's sandbox at near-native speed.
  • Canvas API — image manipulation (resize, compress, convert) happens entirely on the GPU via Canvas, without any network calls.
  • Web Workers — processing runs on a background thread so your tab stays responsive even during large operations.
  • Blob URLs — the processed output is held in browser memory and offered as a download via a temporary URL that only exists in your tab.

How to verify this yourself

Don't take our word for it. Here's how to confirm no file data leaves your browser when you use EazyStudio:

1
Open DevTools
Press F12 (or Cmd+Option+I on Mac) to open your browser's developer tools.
2
Go to the Network tab
Click the "Network" tab and make sure recording is active (the red circle).
3
Use any tool
Open a file in one of our tools and process it completely.
4
Inspect the requests
Look at every network request. You'll see font and library loads on initial page load — but no outbound request containing your file data. Zero.
Pro tip: Filter the Network tab by "XHR" or "Fetch" requests specifically. These are the only types of requests that could carry file data to a server. With EazyStudio tools open and actively processing a file, you'll see none.

Why more tools don't do this

Running processing in the browser is harder to build than a server-side tool. WebAssembly is complex. Browser APIs have quirks. Performance requires careful optimisation. Server-side processing is simply easier to develop.

But we believe the extra engineering effort is worth it. Your files are private by default — not as a setting, not as a paid feature, but as the only possible outcome of how the software works.

Try it yourself — process a file right now
Every tool works the same way: entirely in your browser, no upload, no account, no limit.
Browse all tools