Skip to content

How TabShed works

Your files are processed by your browser, not by our servers. Here is how, and how to check.

Updated November 19, 2026

The work happens in your browser

Most online converters upload your file to a server, process it there and send the result back. TabShed does it the other way around: the page sends your browser the program, and your browser runs it on your file. The file is read from your disk into the tab's memory and the result is written back as a download. Our server only sends the page itself.

The programs are well-known open-source libraries compiled to run in a browser, mostly as WebAssembly:

  • ffmpeg (ffmpeg.wasm) for video and audio: compressing, extracting sound, converting formats.
  • pdf-lib and PDF.js for PDF files: PDF.js draws pages, pdf-lib merges, splits, rotates and edits them.
  • Potrace for tracing a PNG or JPG into an SVG outline.
  • Tesseract.js for reading text from scanned pages (OCR).
  • ONNX Runtime Web for the few small models, such as background removal and face detection. We only ship models small enough to download quickly, and they run on your device too.
  • The browser's own Canvas, Web Audio and file APIs for cropping, resizing, color and audio effects.

What is kept, and where

A tool forgets your file when you close the tab. A few tools keep things on purpose, such as the PDF editor's documents, saved signatures and your theme. They are stored in IndexedDB and localStorage inside your browser, never on a server. The Local storage page lists everything stored and lets you delete it. Clearing the site data in your browser removes it too.

Send to phone

Send to phone and the file transfer tool connect two of your own devices with WebRTC. You scan a QR code, the two browsers agree on a connection and then the file travels directly from one device to the other, encrypted. Our server only passes the short setup message and deletes it within minutes. If a direct route is blocked, for example by a strict company network, the connection can fail instead of falling back to a server relay.

How to check it yourself

  1. Open a tool, for example Delete PDF pages.
  2. Open your browser's DevTools (F12, or Cmd+Option+I on a Mac) and choose the Network tab.
  3. Click the clear button, then choose a file and run the tool.
  4. Look at the requests. You will see the program files loading and, on some pages, ad requests, but no request that carries your file. Sort by size: nothing as large as your file leaves your computer.

You can go further: turn on airplane mode after the page has loaded, and most tools keep working, because nothing needs the network.

Limits to expect

  • Your device sets the limit. A tab can use only part of your memory. On a computer, files of a few hundred megabytes are usually fine; on a phone, large videos (a long 4K clip, for example) may run out of memory and fail. Try a shorter clip or a computer.
  • Speed depends on your processor. Video compression in a browser is slower than a desktop app on the same machine. Keep the tab open and in front while it works, because phones pause background tabs.
  • Browsers differ. We test in current Chrome, Safari and Firefox. Older browsers may lack features such as WebAssembly threads or some audio formats.
  • The first run downloads the tool. Big programs such as ffmpeg are fetched once, then cached by your browser.

Hit a limit we did not list? Tell us on the contact page.