About Piqav

Piqav is a set of free PDF and image tools that do their work inside your browser. Your files are never uploaded, because the work is done by your browser rather than our server - and you can confirm that yourself in about thirty seconds.

Our Engineering Mission

Most online PDF tools work by uploading your file to their server, processing it there and sending the result back. That is convenient, but it means a copy of your payslip, medical scan or contract sits, for a while at least, on a computer you do not control - and how long it stays there is a promise you cannot check.

Piqav does the same jobs inside your browser instead, so the file stays on your device. It uses WebAssembly (Wasm), the browser's Canvas API and Web Workers to do work that used to need a server.

What Happens to Your File

The Open-Source Code That Does the Work

We did not write PDF or image engines from scratch. The tools are built on open-source libraries that anyone can inspect:

Verify It Yourself

You should not have to take our word for any of this. Unlike a cloud service, where "we delete your files after an hour" is a promise you cannot check, a local-processing claim is observable from your own machine in about thirty seconds:

What We Collect, and What We Never Will

Being precise about this matters more than claiming to collect nothing at all:

• Your file contents: never. Documents and images are never serialized into a network request. There is no server-side copy to leak, subpoena, or forget to delete, because one is never created.
• Page analytics: yes. We use Google Analytics to see which tools get used and where pages are slow. It records page visits and device information, not file contents, and in our network tests none of its requests carried any file data.
• Advertising: yes. Google AdSense serves the ads that keep these tools free, and it sets cookies to do so. The specifics, including how to opt out, are in our Privacy Policy.

The distinction is the whole point: we measure how the site is used, and we never see what you use it on.

How Piqav Stays Free

There are no accounts, no subscriptions and no watermarks, and the site is funded entirely by advertising. The only limits are practical ones, such as the 100 MB per file that Compress PDF accepts. That is possible precisely because the processing is local: our running costs are serving static files and WebAssembly binaries, not renting CPU time to compress somebody else's PDF. A cloud tool pays for every file it touches and eventually has to charge you for it, or find another way to make your documents pay. We do not have that cost, so we do not have that incentive.

The Limits of Working In-Browser

This architecture involves real trade-offs, and you should know them before trusting it with something important:

• Your device does the work. Very large or image-heavy documents are bound by the memory your browser can allocate. A desktop will handle files that make a phone struggle.
• The first run downloads an engine. The WebAssembly binaries behind PDF rendering and OCR are downloaded once and then cached, so the first use of a tool is slower than later ones.
• Modern browsers only. The tools depend on WebAssembly, Web Workers, and Canvas APIs. Current versions of Chrome, Edge, Firefox, and Safari are supported; older browsers are not.

We think that is the right trade for confidential work. A tool that occasionally takes longer on a large file, but never uploads it, is a better deal than the reverse.

Who Runs Piqav, and How We Write

Piqav is built and run by Rajashekara, a developer in India, who also writes and tests the guides on the blog. It is a small independent operation, not backed by a company or investors, and there is no support department - email reaches the person who builds the tools. Contact details and the jurisdiction we operate under are on the contact page.

The site pays for itself through advertising. That is the whole business model: there is no paid tier, no account to create, and no data to sell, because the files never reach us in the first place. Ads and analytics are third-party scripts that see your visit - they are entirely separate from file handling, and the privacy policy sets out exactly what each one collects.

The guides in our blog are written from building and testing these tools rather than from research alone, which means they occasionally contradict what a tool's marketing would prefer to say. When we find that a page claims more than the software actually does, we change the page. Our Redact PDF tool used to draw black boxes over text without removing it, and its page said so; since 27 September 2026 it removes the covered content, and the page records the change. If you find something on this site that is wrong, tell us and we will correct it.

Pages are drafted with the help of AI writing tools. Every number and claim on them comes from running the tools ourselves, and we check each one before publishing.