How it works.
Every tool on fwip runs on your device. When you drop a file in, it stays on your machine. It's not uploaded. It's not sent to a cloud. It's not transmitted anywhere. The work happens locally, in your browser, using your own hardware.
What runs on your device
PDF tools
Compression, merging, splitting, signing, redaction, OCR, form filling, watermarking. All run in your browser. Your PDF never leaves your computer.
Image tools
Resize, compress, convert between formats (JPG, PNG, WebP, and more), crop, batch process. On-device. Format conversions happen in your browser's memory and never touch a server.
Video tools
Convert between MOV, MP4, MKV, AVI, WebM and more. Compress, trim, rotate, resize, merge, extract audio. Your video stays on your machine.
Audio tools
Convert between MP3, WAV, FLAC, OGG, AAC, M4A. Trim, merge, clean background noise. All local.
AI tools
Background removal, image upscaling, OCR, speech-to-text. The AI models run in your browser, not on a server. The model itself has no internet connection to your data. It literally cannot phone home.
Privacy tools
File encryption and decryption happen entirely in the browser using strong, modern cryptography. Your password never leaves your device. The encrypted output is the only thing that touches your disk.
Data tools
JSON, CSV, XML, YAML, TOML. Processed in memory, never transmitted. Format, validate, convert, deduplicate. Your data stays in your browser tab and nowhere else.
What never leaves your device
- Your files. No file is ever uploaded, transmitted, or sent to a server. Not temporarily. Not "encrypted in transit." Not at all.
- Your data. No file content is read, logged, stored, or analysed by fwip. There's nowhere for it to go. There's no server-side processing infrastructure to send it to.
- Your identity. No account is required to use the free browser tools. No personal data is collected. No cookies. No fingerprinting. No tracking pixels.
What fwip does collect
- Anonymous page view analytics via a privacy-focused, cookie-free, EU-hosted service. fwip knows how many people visited the Compress PDF page. fwip does not know who they are or what they compressed.
- Email address if you join the waitlist or download the desktop trial. Used only for launch notification and trial nurture emails. Not sold. Not shared. Not added to any third-party list.
What happens offline
- Desktop app. Works fully offline after installation. No internet connection required for any tool. The only network request is a license key check on first launch. After that, it works offline indefinitely.
- Browser tools. Need an initial page load to download the tool code. After that, processing is local. Load a tool, disconnect from the internet, and the tool still works.
Limitations
We'd rather tell you the edges than pretend they don't exist.
Large files (500MB+) can be slow or run into browser memory limits. The desktop app handles larger files more reliably.
AI tools need to download a small model on first use. After that, it's cached. First run is slow. Every run after is fast.
Processing speed depends on your hardware. Modern laptops handle most jobs in seconds. Older devices may be slower.
Prove it yourself
You don't need to trust us. Try this:
- Open any fwip tool. Compress PDF works.
- Wait for the page to fully load.
- Turn off your internet. Airplane mode. Pull the ethernet. Whatever.
- Open DevTools if you want. Check the Network tab.
- Drop a file in. Run the tool. Watch nothing happen on the network.
- Save the result.
- Close the browser tab.
The tool worked. Offline. No request went out. The file you dropped never existed anywhere except your machine. Now it's gone from this tab too.
That's the whole product. Other tools want you to send them your files. We send you the tools. You do the work. Close the browser. fwip forgets it.
Privacy by architecture. Not policy.
Why this matters
Most "free" file tools upload your document to their server, process it remotely, and send the result back. Some delete it after an hour. Some keep it for model training. Some don't say.
fwip can't see your files. Not because of a policy. Because of architecture. The file never leaves your machine. There is nothing for us to see.