Forem: Pranav Mailarpawar

I Tested Every "Free" PDF Tool Online. Only One Is Actually Free.

Pranav Mailarpawar — Sun, 05 Apr 2026 12:38:28 +0000

It is 10 PM. You have a 40-page contract that needs to be merged with an NDA and compressed to under 5MB before emailing to a client in the morning. You search "merge PDF free online," click the first result, upload your documents — and then you see it.
"Your file is ready! Upgrade to Pro to remove the watermark."
The word WATERMARK stamped diagonally across every page of the document you were about to send to a client.
You close the tab, try the next result. Same story. Third one asks you to create an account. Fourth one says you have used your two free tasks for the day. Forty minutes later, you are still looking.
This experience is not an accident. It is a business model. And once you understand it, you will never fall into that trap again.

The "free" PDF tool trap — what is actually happening
When iLovePDF, Smallpdf, or Adobe offer a "free" tier, they are running what the software industry calls a freemium funnel. The goal is not to give you a useful free tool. The goal is to get you close enough to finishing a task that you feel the friction of the limitation — the watermark, the task cap, the size limit — and convert to a paying customer rather than start over.
Every design decision in the free tier is optimised for that conversion, not for your convenience.
There is one tool that works completely differently. ihatepdf.cv processes every single PDF operation inside your browser tab using WebAssembly — a technology that lets professional-grade libraries like Ghostscript run at near-native speed without a server. Open DevTools while using it. Watch the Network tab. You will see zero upload requests for your PDF file. Nothing leaves your device. No server means no cost to throttle, no mechanism to inject a watermark, and nothing to log in for.
That is the structural difference. Everything else flows from it.
Now, the honest breakdown of every major player.

ihatepdf.cv — the one built differently
ihatepdf.cv launched with one design constraint above all others: files never leave your device. This is not a privacy marketing claim bolted on afterwards. It is a technical consequence of the architecture.
What it means in practice:
No watermarks, ever. There is no server generating output files, so there is no mechanism to inject a watermark. The output is produced by the WebAssembly library running in your browser — it only does what you ask it to do.
No task limits. Limits exist to throttle server usage and push users toward paid tiers. With no server usage, there is nothing to throttle. Merge 50 PDFs, compress them, split them, edit them, and encrypt them all in one afternoon — no limit hit.
Works offline. Once the page has loaded, the WebAssembly libraries are cached via a service worker. Disconnect your WiFi and every tool still works. This is structurally impossible for server-based tools.
No account required. Accounts exist to track usage against a limit and retain users for conversion. With no limits to track and no server-side data to store, there is nothing to log in for.
The trade-off worth being honest about: very heavy processing on old or low-memory devices takes longer than a dedicated server. Compressing a 100MB PDF on an eight-year-old laptop is slower than the same operation on cloud infrastructure. For very large files on constrained devices, server-based tools have a genuine speed advantage. That is a real difference and worth knowing.

iLovePDF — the most popular, with real limitations
iLovePDF is the dominant name in browser-based PDF tools. Ask most people to name an online PDF tool and they will name iLovePDF. The interface is fast and polished, and the range of tools is wide. For occasional light use, the free tier is genuinely functional.
But it breaks down in ways that matter.
The free tier caps file size at 200MB per file — which sounds generous until you are handling scanned document archives or high-resolution design PDFs. Files are uploaded and processed on their servers, which means your document travels through infrastructure you do not control. Their privacy policy states deletion after two hours, but your file exists on their hardware during that window. And the free tier adds watermarks on certain conversion outputs — which tools add them and which do not is not clearly communicated upfront. You find out after processing.
iLovePDF Premium runs at approximately $6.61 per month on an annual plan. It removes limits and watermarks. If you process PDFs professionally every day and cloud convenience outweighs privacy concerns, it is a reasonable value. For anyone else, the free tier limitations are a real friction point.
The honest verdict: Best for casual, non-sensitive use where privacy is not a concern. Not suitable for sensitive documents, offline use, or high-volume workflows without paying.

Smallpdf — the best-designed tool with the worst free tier
Smallpdf has arguably the most polished interface of any online PDF tool. The user experience is smooth, the design is genuinely good, and the brand recognition is massive.
The free tier, however, is the most restrictive of any major tool.
Two tasks per hour. Two tasks per day. This is stated clearly — but the real impact only becomes clear when you hit it mid-workflow. Two tasks means: merge one PDF, compress one PDF. That is your day done on the free tier. Beyond that, output files on the free tier carry a clearly visible Smallpdf watermark placed on document content, not tucked in a margin.
Smallpdf Pro costs $12 per month (monthly billing) or $108 per year. For teams that need a polished, cloud-synced PDF workflow with collaboration features, the Pro pricing is competitive. For individuals who occasionally need to process a PDF without a watermark, paying $12 a month is genuinely hard to justify.
The honest verdict: The 2-tasks-per-day free tier is not a free tier — it is a 24-hour free trial that resets daily. If you will pay for a PDF tool and want cloud-based team collaboration with the best-designed interface in the category, Smallpdf Pro earns its price. For everyone else, there are better options.

Adobe Acrobat online — the brand name with the weakest free offering
Adobe invented the PDF format. Their Acrobat desktop software is the definitive professional tool used by law firms, publishers, and enterprise organisations worldwide. The desktop application is comprehensive and genuinely powerful.
The online free tier is a different story.
Adobe's free web offering is designed as a lead magnet for Acrobat subscriptions, not as a standalone tool. Core editing, form creation, advanced conversion — anything beyond basic viewing requires a subscription. An Adobe ID is required even for the limited free functions. Acrobat Standard costs $12.99 per month (annual commitment). Acrobat Pro costs $23.99 per month. Monthly pricing is significantly higher.
Where Adobe genuinely excels is the paid Acrobat Pro desktop application. Advanced redaction, certified digital signatures that meet legal standards, PDF/A archiving compliance, accessibility tagging, and professional print production features are all best-in-class. For legal, publishing, and enterprise workflows that genuinely require these capabilities, the subscription is justified.
The honest verdict: Not meaningfully competitive as a free tool — the free tier exists primarily to prompt subscription sign-ups. For professional legal, enterprise, or publishing workflows requiring certified e-signatures and advanced compliance features, Acrobat Pro is the industry standard. For everything else, the price is impossible to justify.

Sejda — the most honest free tier of the server-based tools
Sejda is less well-known but deserves a mention for one reason: it is the most transparently communicated free tier of the server-based options. Limits are stated upfront rather than revealed after processing.
Three tasks per hour, with a 200-page or 50MB cap per task. More generous than Smallpdf's two-per-day, but still a real constraint for anything beyond occasional use. The key differentiator: Sejda does not watermark free tier output. That separates it from Smallpdf cleanly. No account is required for most tools. Files go to their servers with a stated two-hour deletion window.
Sejda Premium is $7.50 per month on an annual plan — the most affordable premium option among server-based tools.
The honest verdict: The most user-respectful server-based free option. No watermarks, clear limits stated upfront, no account required. For non-sensitive documents where server processing is acceptable and you run into device memory limits on ihatepdf.cv, Sejda is the best fallback.

The privacy question nobody explains clearly
This is the most consequential difference between the tools, and the least clearly communicated.
When you upload a file to any server-based PDF tool — regardless of what their privacy policy says — the following happens: your file travels over the internet to their data centre, it lands on a server and is written to disk, it is processed by their software, the output is written and made available for download, and at some point within the stated retention window it is deleted, assuming their systems work correctly.
For most documents — a recipe PDF, a product manual, a publicly available report — none of this matters. For contracts, medical records, financial statements, personal ID documents, legal filings, or CVs with personal data, this chain of custody has real implications. GDPR, HIPAA, and most professional codes of conduct for legal and financial work have specific requirements about where and how client data may be processed.
ihatepdf.cv's approach is not "we delete your files promptly." It is "we never receive your files at all." That is a categorically different guarantee, not a stronger version of the same thing.

The honest comparison in plain language
Here is the actual state of each tool on the dimensions that matter:
ihatepdf.cv — No watermark. No limits. No upload. No sign-up. Works offline. Free.
iLovePDF (free tier) — Watermark on some tools. File size cap at 200MB. Server upload required. Occasional queue times. No offline use. Free, or $6.61/month for Pro.
Smallpdf (free tier) — Watermark on output. 2 tasks per day. Server upload required. Sign-up pushed throughout. No offline use. Free, or $12/month for Pro.
Adobe Acrobat online — Very limited free functionality. Account required. Server upload required. No offline use. $12.99–$23.99/month for meaningful access.
Sejda (free tier) — No watermark. 3 tasks per hour. Server upload required. No account required. No offline use. Free, or $7.50/month for Pro.

When to actually use each one
Use ihatepdf.cv when privacy matters, you want genuinely unlimited free use, you might be offline, or you need a tool that works without hitting unexpected limits mid-workflow. Also the right choice for sensitive documents — contracts, CVs, medical records — where you would not be comfortable uploading to a third-party server.
Use iLovePDF when you are processing large files on an older device and speed outweighs privacy concerns, or you are already on iLovePDF Premium and the cloud sync is part of your workflow.
Use Smallpdf Pro when you are paying for it, need team collaboration features, and want the best-designed interface in the category. On the free tier: genuinely do not bother.
Use Adobe Acrobat Pro when you work in legal, publishing, or enterprise contexts requiring certified digital signatures, PDF/A compliance, or advanced accessibility features. It is a professional tool at a professional price — that match is either right for your context or it is not.
Use Sejda free when you need a server-based tool for speed on a constrained device and privacy is acceptable. The most user-respectful server-based free option available.

The bottom line
The free PDF tool space is mostly a collection of freemium funnels dressed up as utilities. Watermarks, task limits, and forced sign-ups are not limitations of the technology — they are deliberate friction designed to drive conversions to paid tiers.
ihatepdf.cv is genuinely different because the architecture that makes it private is the same architecture that makes it free. No server means no cost to throttle, no mechanism to watermark, and nothing to log in for. It is free because there is no server infrastructure to pay for — not because they are running a generous limited-time offer.
If you process PDFs that contain anything you would not casually email to a stranger, the choice is straightforward.
👉 Try it for free at ihatepdf.cv

Tested all tools in mid-2025. Pricing and free tier terms are accurate as of the time of writing and subject to change.

Tags: PDF tools, ihatepdf, free PDF editor, iLovePDF, Smallpdf, Adobe Acrobat, online PDF editor, PDF compressor, free PDF tools, privacy, no watermark PDF

ihatepdf.cv is a free online PDF toolkit — merge, split, compress, edit, convert, and transform PDF files without watermarks, without sign-ups, and without sending your files to a server.

How to Invert PDF Colours Online for Free — The Easiest Tool You Haven't Tried Yet

Pranav Mailarpawar — Sun, 05 Apr 2026 11:59:59 +0000

If you've ever opened a PDF late at night and been blasted by a blinding white background, you already know the problem. Or maybe you're printing a document and want to save toner by flipping colours. Whatever the reason, inverting PDF colours sounds like it should be simple — but most tools make it surprisingly complicated.
That's exactly why ihatepdf.cv built its Invert PDF Colours tool. It does one thing, it does it well, and it costs you nothing.

What Does "Invert PDF Colours" Actually Mean?
When you invert a PDF's colours, every colour in the document flips to its opposite on the colour wheel. White becomes black. Black becomes white. Dark navy turns bright yellow. It's essentially the same as toggling "Dark Mode" — but for any PDF file, regardless of how it was created.
This is especially useful for:

Night reading — A white-background PDF can feel like staring into a flashlight at 11 PM. Inverted colours are dramatically easier on the eyes in low-light environments.
Accessibility — For people with light sensitivity, migraines, or certain visual impairments, dark-background documents significantly reduce eye strain.
Printing efficiency — Inverting a heavily white document to a dark one (or vice versa) can save a surprising amount of ink and toner, especially for presentations or design-heavy files.
Design and presentations — Sometimes you need a dark-themed version of a document for a specific brand context or slide deck style.

Why Most PDF Tools Make This Harder Than It Needs to Be
Before ihatepdf.cv, inverting PDF colours usually meant:

Downloading bulky desktop software
Paying for a premium subscription
Jumping through export and re-import hoops in Adobe Acrobat
Receiving a watermarked output because you used a "free" tier

That's an absurd amount of friction for what should be a two-second job.

How ihatepdf.cv's Invert PDF Colours Tool Works
Here's the entire process — and yes, it really is this short:
Step 1 — Go to ihatepdf.cv
Open your browser and head to ihatepdf.cv. No account needed, no app to download.
Step 2 — Select the Invert PDF Colours Tool
From the homepage, find the Invert PDF Colours option. It's right there in the tools menu — no hunting through settings or dropdowns.
Step 3 — Upload Your PDF
Drag and drop your file onto the upload area, or click to browse and select it from your device. The tool accepts standard PDF files of all sizes.
Step 4 — Click Invert
Hit the button. The tool processes your document instantly — no waiting, no progress bar spinning for five minutes.
Step 5 — Download Your Inverted PDF
Your colour-inverted PDF is ready. Download it directly. No watermark. No email required. No forced sign-up.
That's it. Five steps, under thirty seconds.

What Makes ihatepdf.cv Different from Other Free PDF Tools?
There are dozens of online PDF tools, so why should you choose ihatepdf.cv? The GSC data tells the story clearly — thousands of users search for it every month, and a significant portion of them specifically come back for the .cv domain, meaning they remember the brand. Here's why:
✅ Completely Free, No Watermarks
The number one complaint with free PDF tools is the watermark problem. You process a clean professional document, download it, and find a giant "Processed by XYZ" stamp across every page. ihatepdf.cv doesn't do that.
✅ No Sign-Up Required
You don't need to create an account, hand over your email address, or start a free trial that auto-charges you in 14 days. Open the site, use the tool, leave. Simple.
✅ Works on Any Device
Whether you're on a Windows desktop, a MacBook, an Android phone, or an iPad — ihatepdf.cv is browser-based and fully responsive. No compatibility issues.
✅ Fast and Lightweight
The tool is built to process PDFs quickly. There's no server queue or slow upload bottleneck. You get your file back fast.
✅ Privacy-Conscious
Your uploaded files are processed and then deleted. You're not contributing your sensitive documents to a permanent database somewhere.

Real-World Use Cases for Inverting PDF Colours
Students Studying at Night
If you're reading lecture notes or research papers after dark, a white PDF on full brightness is brutal. Inverting the colours creates a comfortable dark-on-light reading experience that won't tire your eyes out before your exam tomorrow.
Remote Workers and Freelancers
Working across different time zones often means late-night document reviews. An inverted PDF is much more comfortable during those 2 AM catch-up sessions.
People with Visual Sensitivities
Many people experience headaches or eye discomfort with bright white screens. Inverted PDFs can serve as a quick accessibility workaround when an application doesn't offer a native dark mode.
Architects, Designers, and Engineers
Technical drawings and CAD exports are often presented as dark lines on a white background. Inverting them creates a dramatic dark-background look that can be striking in presentations.
Teachers and Educators
Creating handouts or worksheets? An inverted colour scheme can add visual variety to printed materials and make certain documents stand out in a packet.

ihatepdf.cv — More Than Just One Tool
While the Invert PDF Colours tool is excellent, it's just one part of what ihatepdf.cv offers. The platform is built around the idea that every common PDF task should be fast, free, and frustration-free. Other popular tools on the site include:

Merge PDF — Combine multiple PDFs into a single document
Split PDF — Extract specific pages from a large file
Compress PDF — Reduce file size without losing quality
Edit PDF — Make changes directly to text and images
Convert PDF — Transform PDFs to Word, Excel, JPG, and more
Rotate PDF — Fix the orientation of scanned or incorrectly saved pages

All of these follow the same zero-friction philosophy: no watermarks, no sign-up, no nonsense.

How to Get the Best Results When Inverting PDF Colours
A few quick tips to make the most of the tool:
Check your document type first. Text-heavy PDFs (like research papers or contracts) invert beautifully. Colour photographs embedded in PDFs will also invert, which can look unusual — keep that in mind if your document has full-colour imagery.
Use it for reading, not final publishing. For personal reading and study use, the inverted file is perfect. For professionally shared documents, you may want to stick with the original colour scheme unless the dark version is intentional.
Combine with Compress PDF if needed. After inverting, if your file size has increased, run it through the Compress PDF tool on ihatepdf.cv to bring it back down.

The Bottom Line
If you need to invert the colours of a PDF — for eye comfort, accessibility, printing, or design — ihatepdf.cv is the fastest, cleanest way to do it online. No watermarks. No account. No cost. Just upload, invert, and download.
It's the kind of tool that makes you wonder why you ever struggled with anything else.
👉 Try it now at ihatepdf.cv

Found this useful? Share it with someone who's still squinting at a blinding white PDF at midnight.

Tags: PDF tools, Invert PDF, Dark mode PDF, Free PDF editor, ihatepdf.cv, Online PDF tools, PDF colour invert, Edit PDF online free, PDF accessibility

ihatepdf.cv is a free online PDF toolkit that helps users merge, split, compress, edit, convert, and transform PDF files — without watermarks, without sign-ups, and without the usual headaches.

How to Compress a PDF for Free — Up to 70% Smaller, No Upload, No Watermark

Pranav Mailarpawar — Sat, 04 Apr 2026 18:25:32 +0000

If you've ever hit "Send" on an email only to get a bounce-back saying your attachment is too large — you already know the pain. Gmail blocks files over 25MB. Outlook caps at 20MB. Government portals, HR systems, and university submission forms often set limits as low as 2MB.
And yet, somehow, your PDF is 47MB.
The good news: you can compress a PDF down by up to 70% for free, right in your browser, in under 30 seconds — no account, no watermark, and critically, no uploading your file to someone else's server.
Here's everything you need to know.

Why Most Online PDF Compressors Are a Privacy Risk (And What to Use Instead)
Most popular PDF tools — ilovepdf, smallpdf, Adobe Acrobat Online — work by uploading your file to their servers, compressing it there, and sending it back. That means your CV, your contract, your medical records, or your client documents sit on a third-party server you have no control over.
ihatepdf.cv/compress-pdf takes a different approach entirely.
It uses Ghostscript compiled to WebAssembly, which means the entire compression pipeline runs inside your browser tab. Your file bytes never travel anywhere. Not to ihatepdf.cv's servers. Not anywhere. Once the page loads, it even works fully offline.
This is the only truly private way to compress a PDF online.

How to Compress a PDF Free — Step by Step

Go to ihatepdf.cv/compress-pdf — no sign-up, no email required
Click "Select PDF to Compress" or drag and drop your file onto the page
Choose your compression level (more on this below)
Click "Compress PDF Now" and wait 5–30 seconds
Download your smaller PDF — no watermark added

That's it. Works on Windows, Mac, iPhone, and Android — any modern browser, any device.

Which Compression Level Should You Choose?
This is the question most guides skip, and it's the most important one.
🟢 Light — 20–30% reduction
Images are resampled to 300 DPI. Best for documents where print quality matters: design portfolios, high-resolution presentations, professional photography. The output is visually indistinguishable from the original.
🟡 Medium — 40–50% reduction
Images at 150 DPI. This is the sweet spot for 99% of use cases: CVs, business reports, contracts, slide decks, university submissions. Barely any visible quality difference on screen.
🔴 Heavy — 60–70% reduction
Images at 72 DPI. Maximum compression for archiving, internal records, or any situation where file size is the only priority. Text remains perfectly sharp at every level — only raster images are affected.
Quick rule of thumb: Start with Medium. If the file is still too large, switch to Heavy.

Will Compressing a PDF Make It Blurry?
Short answer: text will never be affected — not even slightly.
Text in PDFs is stored as mathematical vector paths, not pixels. Compression doesn't touch it. What changes is embedded raster images: photos, scanned pages, illustrations. At Light and Medium, this difference is invisible on screen. At Heavy, photos may look slightly softer — but every word stays razor-sharp.
If your PDF is mostly text (a CV, a report, a contract), even Heavy compression will look identical to the original on screen.

How Much Can Your PDF Actually Compress?
Results vary significantly by document type:
Document TypeExpected ReductionScanned documents50–70%Presentations with stock photos40–60%CVs and text-heavy reports10–30%PDFs exported from Word/Excel15–40%
A 15MB scanned report typically compresses to 2–4MB on Heavy. A photo-heavy slide deck at 30MB often drops below 12MB on Medium.

Compressing a PDF for Email: The Fastest Approach
Gmail: 25MB limit
Outlook: 20MB limit
Most HR/university portals: 2–5MB limit
Here's the decision tree:

Try Medium compression first — most PDFs under 50MB will clear the 25MB limit
Still too large? Switch to Heavy compression
Still too large after Heavy? Use ihatepdf.cv/split-pdf to divide the document into sections, send them separately, then merge them back afterwards if needed

How to Compress a PDF to Under 1MB
A 1MB target is achievable for most PDFs with Heavy compression. For image-heavy files that are still over 1MB after compression:

Apply Heavy compression at ihatepdf.cv/compress-pdf
Split the result into smaller sections using ihatepdf.cv/split-pdf
Compress each section individually
Submit sections separately, or merge them back using ihatepdf.cv/merge-pdf

One More Trick: Flatten Before You Compress
PDFs with interactive form fields, annotations, and embedded JavaScript carry significant invisible overhead. If your PDF was originally a fillable form or has tracked changes and comments, flatten it first.
Go to ihatepdf.cv/flatten-pdf → flatten → then compress.
This two-step process often produces smaller files than compression alone, especially for PDFs exported from form-building tools.

What About Password-Protected PDFs?
Password-protected PDFs can't be compressed directly. You'll need to:

Decrypt the file at ihatepdf.cv/remove-password
Compress at ihatepdf.cv/compress-pdf
Re-encrypt if needed at ihatepdf.cv/encrypt-pdf

FAQ
Is there a file size limit?
No artificial limit. The practical ceiling is your device's available RAM — typically 100–150MB on a desktop browser. Close other tabs if you're working with very large files.
Can I compress multiple PDFs at once?
The tool processes one file at a time. For a batch, use ihatepdf.cv/merge-pdf to combine them first, then compress the merged file in a single pass.
Why is my compressed file still large?
If Heavy compression only shrank your file by 10–15%, the PDF is mostly text and vector graphics — not images. There's limited room to compress further. Try splitting the document instead.
Does compression affect links, form fields, or bookmarks?
No. Hyperlinks, form fields, bookmarks, and annotations are all preserved after compression.

The Bottom Line
The fastest, most private way to compress a PDF:
ihatepdf.cv/compress-pdf
No upload. No watermark. No account. Works on every device. Runs entirely in your browser.
Pick Medium compression, click compress, and your file will be ready in under 30 seconds.

Have a PDF that's fighting back? Drop a question in the comments — happy to help figure out the best approach for your specific file.

Also on ihatepdf.cv:

Merge PDFs — Combine files before or after compressing
Split PDF — Divide large files to hit upload limits
Flatten PDF — Lock form fields to reduce size further

How to Merge PDF Files Free Online — No Watermark, No Sign-Up, Works Offline

Pranav Mailarpawar — Thu, 02 Apr 2026 17:21:37 +0000

You've got three PDFs. A contract, an attachment, and a cover letter. You need them as one file before the deadline. So you search for a PDF merger, land on something that looks free, upload your files — and then it tells you the download requires an account, or worse, the output has a watermark stamped across every page.
Sound familiar?
Here's how to actually merge PDFs for free, with no watermark, no sign-up, and no files leaving your device — using ihatepdf.cv.

What You Actually Need to Merge PDFs
Just a browser. That's it.
ihatepdf.cv's PDF merger runs entirely in your browser — no software installation, no account, no watermark on the output. Your files never leave your device. It also works offline once the page has loaded.

How to Merge PDFs in Under 2 Minutes

Go to ihatepdf.cv/merge-pdf — no sign-up required
Upload your PDF files — click Select PDFs or drag and drop. Add as many files as you need, no limit
Drag to reorder — drag the thumbnails into the final page sequence you want
Click Merge PDFs — processing takes a few seconds, locally in your browser
Download — the combined PDF downloads instantly with no watermark

The whole thing takes about 90 seconds for most people.

How to Merge PDFs on Mac
On Mac you can also use Preview: open the first PDF, go to View → Thumbnails, then drag other PDFs into the sidebar. This works for basic merging but requires all files already on your Mac and you must save manually.
For a faster solution that works on any OS without installing anything, ihatepdf.cv's merger is the quickest option — and it doesn't require any application to be open.

How to Merge PDFs on Windows
Windows has no built-in PDF merger. The fastest approach is a browser-based tool — open ihatepdf.cv/merge-pdf in Chrome, Edge, or Firefox, upload your files, and download the merged result. No software installation needed, no account required.

How to Merge PDFs on iPhone or Android
ihatepdf.cv works perfectly on mobile browsers. Open the tool in Safari on iPhone or Chrome on Android, tap to upload from your Files app or Google Drive, reorder the page thumbnails, and tap Download. The merged file saves directly to your phone's Downloads folder. No app installation needed.

What to Do If the Merged PDF Is Too Large to Email
After merging, if the file exceeds your email provider's attachment limit — Gmail caps at 25MB, Outlook at 20MB — run the merged file through ihatepdf.cv's PDF compressor. Medium compression typically reduces a merged PDF by 40–50% with no visible quality loss on screen.
If you still need it smaller, try splitting the merged PDF into logical sections and sending them separately.

Reorder Pages Before Merging for Perfect Results
If individual PDFs have internal page issues — wrong page order, sideways scans, or blank pages to remove — use Organize Pages on each file first to fix the internal order, then merge them all together. This two-step approach gives you full control over the final page sequence.

Why "No Upload" Matters More Than You Think
Most PDF merging services upload your documents to their servers before combining them. For contracts, CVs, financial records, or any confidential document, this is an unnecessary privacy risk.
ihatepdf.cv uses pdf-lib compiled to WebAssembly — the entire merge operation runs inside your browser tab. The bytes of your documents never travel over the network.
Want to verify it? Open DevTools → Network tab → upload your files and hit Merge. Upload column: zero.

Frequently Asked Questions
Is there a limit on how many PDFs I can merge?
No limit. Merge as many files as your device memory allows — typically 20–50 files on a desktop browser.
Will the merged PDF have a watermark?
Never. ihatepdf.cv does not add watermarks to any output file under any circumstances.
Does merging PDFs reduce quality?
No. The merge operation is structural only — it preserves the original quality of every page exactly as-is. No re-encoding occurs.
Can I merge password-protected PDFs?
You need to remove the password first, then merge, then re-encrypt with Encrypt PDF if needed.
Can I merge PDFs with different page sizes?
Yes. PDFs with different page dimensions — A4 mixed with US Letter, portrait mixed with landscape — can be merged. Each page retains its original dimensions in the output. Use Crop & Resize first if you need all pages to be the same size.

Merging PDFs shouldn't require an account, a subscription, or a watermark on your work. ihatepdf.cv just does it — free, private, no nonsense.
Merge your PDFs now →

Scan Any Document to a Searchable PDF For Free, Right in Your Browser

Pranav Mailarpawar — Wed, 01 Apr 2026 19:08:53 +0000

If you've ever had a printed contract, a handwritten note, or a physical receipt that you desperately needed as a PDF — and found yourself wrestling with apps that either upload your files to some random server, slap a watermark on the result, or charge you after three free scans — you know the frustration.
There's a better way. It's called ihatepdf.cv, and it runs entirely in your browser.

What ihatepdf.cv Actually Does
ihatepdf.cv is a free browser-based document scanner. You open it, point your phone or laptop camera at a piece of paper, and it spits out a clean, flat, searchable PDF — with no account required, no file ever leaving your device, and absolutely no watermark.
It's the kind of tool that should have always existed. Here's what happens under the hood when you hit that shutter button.

Step 1: It Detects the Document Edges Automatically
The moment you capture a frame, ihatepdf.cv runs an edge-detection algorithm directly in JavaScript — no computer vision library, no WebAssembly blob to download. It applies a Gaussian blur to reduce noise, then runs a Sobel operator across the image to find where brightness changes sharply (i.e., where your document meets the desk or background).
The four corners of your document are estimated from those edge points and shown as draggable handles on screen. Most of the time the auto-detect is spot on. When it isn't, you just drag the corners yourself — and a little magnifying loupe pops up under your finger so you can place them with pixel-level precision.

Step 2: Perspective Correction (The Magic Part)
This is what separates a real document scanner from just "taking a photo." Even if your paper is at an angle — tilted 20 degrees, shot from the side — ihatepdf.cv mathematically flattens it.
It computes a homography matrix: a transformation that maps your four selected corners to a perfect rectangle. Then it walks every pixel of the output image backwards through that transformation to find where it came from in the original photo. The result is a flat, de-skewed document that looks like it came off a flatbed scanner.
No OpenCV. No server. Eight equations, eight unknowns, solved in JavaScript.

Step 3: Enhancement — Make It Actually Readable
Raw camera images are often too soft or too grey for OCR to work well. ihatepdf.cv gives you five one-tap presets:

Original — untouched, exactly what the camera saw
Document — boosted contrast and brightness, great for printed text
B&W — full greyscale with heavy contrast, sharp black text on white
Whiteboard — aggressive brightness lift for whiteboard photos
Photo — gentle enhancement for mixed-content pages

You can also fine-tune brightness and contrast manually with sliders. Any preset can be applied to all pages in one tap — useful when you're scanning a multi-page document in the same lighting conditions.

Step 4: OCR — Turn Your Scan Into a Searchable PDF
This is the feature that makes the output genuinely useful rather than just a pretty image. After you've captured and adjusted your pages, hitting "Scan & Extract Text" fires up Tesseract.js — an open-source OCR engine that runs locally in your browser.
It supports 17 languages including English, Hindi, French, German, Arabic, Chinese, Japanese, Korean, and more. Set it to Auto and it detects the script automatically from your first page.
Before OCR runs, ihatepdf.cv preprocesses each image:

Normalises the contrast range so faint text becomes visible
Sharpens edges with a Laplacian filter
Upscales small images to the sweet spot for Tesseract accuracy (~1800px)
If confidence is low, automatically retries on a binarised (black and white) version

The extracted words, along with their exact positions on the page, are embedded as an invisible text layer in the final PDF — white text sitting just underneath the image. The document looks exactly like your scan, but you can select text, search with Ctrl+F, and have it indexed by any search engine or document manager.

Step 5: Export Options That Don't Hold You Hostage
Once processed, you get:

Download as PDF — a proper searchable PDF, no watermark, no size limit other than your device's memory
Download as .txt — the raw extracted text, useful for pasting into other documents
Copy text — one tap to clipboard
Share — on mobile, triggers the native share sheet so you can AirDrop, send via WhatsApp, email it, whatever

There's also a merge feature: if you already have an existing PDF, you can load it and choose whether your new scan goes before or after it. Useful when you're adding pages to a report or combining a handwritten note with a typed document.

Multi-Page and Batch Scanning
Single-page scanning is the easy case. ihatepdf.cv handles multi-page documents too.
After each capture, you land back in a review screen where your pages appear as a scrollable thumbnail strip. Tap any thumbnail to preview it full-screen. Drag thumbnails to reorder pages. Long-press for a context menu that lets you rotate, replace, move, or delete individual pages. Swipe left and right on the preview to navigate between pages.
For situations where you need to quickly capture a stack of documents, Batch mode lets you keep the camera open and shoot as many frames as you want. You then review all captures at once, edit corners on any that need it, and add everything to your document in a single step.
A small coloured dot on each thumbnail gives you a blur quality score — green means sharp, amber is borderline, red means you should retake it. It's a small thing, but it saves you from building a 20-page PDF only to find page 7 is unreadable.

Why "No Upload" Actually Matters
Most online PDF tools — even the free ones — route your files through a server. That's fine for a grocery receipt. It's less fine for:

Medical records
Legal contracts
Financial statements
ID documents
Confidential work files

ihatepdf.cv processes everything on your device. The image never leaves. There's no server log of what you scanned, no storage bucket somewhere holding your documents, no terms of service clause about training AI on your uploads.
This isn't a privacy marketing line. It's just what happens when you do image processing in JavaScript on a canvas element. The data literally cannot go anywhere because there's nowhere to send it.

Works Without an Internet Connection
Once the page loads, ihatepdf.cv works offline. The OCR language models are fetched on first use and cached by the browser. After that, you could put your phone in airplane mode and scan a full document to a searchable PDF without any network activity.
This matters more than it sounds. You're scanning in a basement. On a plane. In a client meeting where pulling out your phone to use some cloud service looks unprofessional. ihatepdf.cv doesn't care.

Import From Your Gallery Too
Don't have something in front of you to scan right now? You can import existing photos from your camera roll. ihatepdf.cv runs the same edge detection and perspective correction on imported images, automatically applies the Document filter, and adds them to your page stack just like a live capture.
This is useful for: photos you already took of a whiteboard, photos of receipts sent to you by someone else, or images of documents you photographed earlier without a scanning app.

The Short Version
If you need to turn a physical document into a PDF and you want it to be:

Free
Searchable
Watermark-free
Private (nothing uploaded)
Available offline
Multi-language
Multi-page

— ihatepdf.cv does all of that. In your browser. Right now.
No sign-up. No install. Try ihatepdf.cv now →

Scan Any Document to a Searchable PDF — For Free, Right in Your Browser

Pranav Mailarpawar — Wed, 01 Apr 2026 19:05:23 +0000

What DocScan Actually Does
DocScan is a browser-based document scanner. You open it, point your phone or laptop camera at a piece of paper, and it spits out a clean, flat, searchable PDF — with no account required, no file ever leaving your device, and absolutely no watermark.
It's the kind of tool that should have always existed. Here's what happens under the hood when you hit that shutter button.

Step 1: It Detects the Document Edges Automatically
The moment you capture a frame, DocScan runs an edge-detection algorithm directly in JavaScript — no computer vision library, no WebAssembly blob to download. It applies a Gaussian blur to reduce noise, then runs a Sobel operator across the image to find where brightness changes sharply (i.e., where your document meets the desk or background).
The four corners of your document are estimated from those edge points and shown as draggable handles on screen. Most of the time the auto-detect is spot on. When it isn't, you just drag the corners yourself — and a little magnifying loupe pops up under your finger so you can place them with pixel-level precision.

Step 2: Perspective Correction (The Magic Part)
This is what separates a real document scanner from just "taking a photo." Even if your paper is at an angle — tilted 20 degrees, shot from the side — DocScan mathematically flattens it.
It computes a homography matrix: a transformation that maps your four selected corners to a perfect rectangle. Then it walks every pixel of the output image backwards through that transformation to find where it came from in the original photo. The result is a flat, de-skewed document that looks like it came off a flatbed scanner.
No OpenCV. No server. Eight equations, eight unknowns, solved in JavaScript.

Step 3: Enhancement — Make It Actually Readable
Raw camera images are often too soft or too grey for OCR to work well. DocScan gives you five one-tap presets:

Step 5: Export Options That Don't Hold You Hostage
Once processed, you get:

Multi-Page and Batch Scanning
Single-page scanning is the easy case. DocScan handles multi-page documents too.
After each capture, you land back in a review screen where your pages appear as a scrollable thumbnail strip. Tap any thumbnail to preview it full-screen. Drag thumbnails to reorder pages. Long-press for a context menu that lets you rotate, replace, move, or delete individual pages. Swipe left and right on the preview to navigate between pages.
For situations where you need to quickly capture a stack of documents, Batch mode lets you keep the camera open and shoot as many frames as you want. You then review all captures at once, edit corners on any that need it, and add everything to your document in a single step.
A small coloured dot on each thumbnail gives you a blur quality score — green means sharp, amber is borderline, red means you should retake it. It's a small thing, but it saves you from building a 20-page PDF only to find page 7 is unreadable.

Why "No Upload" Actually Matters
Most online PDF tools — even the free ones — route your files through a server. That's fine for a grocery receipt. It's less fine for:

Medical records
Legal contracts
Financial statements
ID documents
Confidential work files

DocScan processes everything on your device. The image never leaves. There's no server log of what you scanned, no storage bucket somewhere holding your documents, no terms of service clause about training AI on your uploads.
This isn't a privacy marketing line. It's just what happens when you do image processing in JavaScript on a canvas element. The data literally cannot go anywhere because there's nowhere to send it.

Works Without an Internet Connection
Once the page loads, DocScan works offline. The OCR language models are fetched on first use and cached by the browser. After that, you could put your phone in airplane mode and scan a full document to a searchable PDF without any network activity.
This matters more than it sounds. You're scanning in a basement. On a plane. In a client meeting where pulling out your phone to use some cloud service looks unprofessional. DocScan doesn't care.

Import From Your Gallery Too
Don't have something in front of you to scan right now? You can import existing photos from your camera roll. DocScan runs the same edge detection and perspective correction on imported images, automatically applies the Document filter, and adds them to your page stack just like a live capture.
This is useful for: photos you already took of a whiteboard, photos of receipts sent to you by someone else, or images of documents you photographed earlier without a scanning app.

The Short Version
If you need to turn a physical document into a PDF and you want it to be:

Free
Searchable
Watermark-free
Private (nothing uploaded)
Available offline
Multi-language
Multi-page

— DocScan does all of that. In your browser. Right now.
No sign-up. No install. Just open it and scan.

How to Add Page Numbers to a PDF for Free — No Sign Up, No Watermark

Pranav Mailarpawar — Sat, 28 Mar 2026 08:17:15 +0000

If you've ever had to submit a report, share a proposal, or send a multi-page document to someone, you already know the quiet embarrassment of handing over an unnumbered PDF. Readers flip back and forth with no reference point. "Go to page 7" means nothing when there's no page 7 visible. Page numbers aren't decorative — they're functional.
The problem? Most tools that let you add page numbers to a PDF online are either bloated with upsells, shove a watermark on every page, or demand you create an account before you can do anything useful.
That's exactly the problem iHatePDF.cv was built to solve.

Why Adding Page Numbers to a PDF Is Harder Than It Should Be
Let's be honest about the PDF ecosystem for a second. It's dominated by a handful of giants — Adobe Acrobat at the premium end, and a pile of "free" tools in the middle that aren't really free. You go to edit a PDF and you're either paying $20/month or dealing with watermarks, file size limits, forced account registrations, and files being uploaded to servers you've never heard of.
For something as simple as adding a page number to a document, none of that should be necessary.
Searches like "free pdf editor no sign up", "add page numbers to pdf free", and "free online pdf editor without watermark" get tens of thousands of queries every month — and most of the results lead to tools that quietly disappoint. The free tier runs out. The watermark appears. The sign-up wall goes up.

What iHatePDF.cv's Page Numbers Tool Actually Does
The Add Page Numbers to PDF tool on iHatePDF.cv is refreshingly straightforward. You drop in your PDF, configure how you want the numbers to look, and download. That's it. No account. No watermark. No upload to a remote server.
Here's what you can actually configure:

Number Format Not everyone wants plain "1, 2, 3." The tool gives you five formats to choose from:

1, 2, 3 — the standard numeric format
i, ii, iii — Roman numerals, great for front matter in academic documents or legal filings
A, B, C — alphabetical, useful for appendices or exhibit labelling
Page 1 — written-out format, common in formal reports
1 / 10 — shows progress (current page out of total), good for presentations and manuals

Position — Six Placements You can place your page number in any of six spots on the page:

Top left, top center, top right
Bottom left, bottom center, bottom right

An interactive position picker in the UI makes this visual and intuitive — you click the spot on a mini page diagram, not a dropdown.

Color Customization Seven presets (dark grey, black, red, blue, green, purple, orange) plus a full color picker if you want to match your brand or document style exactly.
Font Size and Weight Slider control from 6pt to 48pt, plus a toggle between regular and bold. Small touches, but they matter when the numbers need to blend into a polished document or stand out on a technical one.
Start Number and Skip First Page You can start numbering from any number — useful when your PDF is a chapter in a larger document that starts at page 34, for example. There's also a single checkbox to skip the first page, which is the right behavior for most cover-page documents.

The Privacy Angle: Files Never Leave Your Browser
This is worth spelling out clearly because it's non-obvious and genuinely important.
iHatePDF.cv processes everything locally in your browser using PDF-lib and PDF.js. Your file is never uploaded to any server. The page numbers are added entirely client-side, in memory, and the resulting file is downloaded directly to your device.
For anyone working with confidential documents — legal contracts, financial reports, HR materials — this isn't a minor feature. It's the whole point. Tools that upload your files to process them are making a choice you may not be aware of. iHatePDF.cv made the opposite choice.

Live Preview Before You Commit
One thing that separates this tool from the more barebones free options is the live preview panel. As you adjust the format, position, color, and font size, the first five pages of your PDF update in real time to show you exactly where the numbers will appear and what they'll look like.
This catches problems before they become problems. You can see immediately if "bottom-center" looks awkward on your particular layout, or if the font size you chose is too small to read comfortably.

Who This Is Actually For
The short answer: anyone who works with PDFs regularly and doesn't want to pay Adobe's subscription fee for a one-off formatting task.
More specifically:
Students and researchers — Academic papers, thesis documents, and reports almost universally require page numbers. Roman numerals for the front matter, Arabic numerals for the body is a classic format that this tool handles directly by letting you set a custom start number per section.
Legal and compliance professionals — Legal documents need precise pagination. The ability to choose "Page 1" format or "1 / 10" totals, and to place numbers in a specific corner per organizational style guides, is practical here.
Business users — Proposals, decks exported as PDFs, business reports handed off to clients. Page numbers make these documents look finished and professional.
Developers and technical writers — Documentation and manuals are obvious candidates. The fact that this tool is entirely browser-based also makes it a clean fit for privacy-conscious technical environments.

How It Compares to the Usual Alternatives
ToolFree?Watermark?Upload Required?No Sign-Up?Adobe AcrobatPaidNoYesNoiLovePDFLimitedSometimesYesPartialSmallpdfLimitedSometimesYesPartialiHatePDFYesNoNoYes
The positioning is deliberate. iHatePDF.cv isn't trying to compete on feature breadth with Acrobat. It's competing on the things that actually matter for most common PDF tasks: free, fast, private, no friction.

Step-by-Step: Adding Page Numbers in About 30 Seconds

Go to ihatepdf.cv/page-numbers
Click "Choose PDF" or drag and drop your file
Select your number format (1,2,3 / i,ii,iii / A,B,C / Page 1 / 1/10)
Click your preferred position on the page diagram
Adjust color, font size, and weight if needed
Set your start number, toggle "skip first page" if you have a cover
Click Add Numbers
Your numbered PDF downloads instantly

The live preview updates as you go, so by the time you hit the button, you already know exactly what you're getting.

Final Thought
The best tools get out of your way. They do the one thing they promise, they do it well, and they don't try to upsell you at every step or hold your file hostage behind a paywall.
The iHatePDF.cv page numbers tool is exactly that. It's free, it's private, it works in your browser without an account, and it gives you more formatting control than most tools you'd actually pay for.
If you regularly deal with PDFs — and in 2025, who doesn't — it's worth bookmarking.

Try it at ihatepdf.cv/page-numbers — free, no sign up, no watermark.

I Built a PDF Splitter That Never Touches Your Files — Here's How

Pranav Mailarpawar — Fri, 27 Mar 2026 16:20:50 +0000

Why another PDF tool? Because privacy shouldn't be a premium feature.

We've all been there. You have a 40-page PDF report, your client needs pages 12–18, and the only tools you can find either slap a watermark on the output, cap your file size, or — most troublingly — upload your document to some server you've never heard of before "processing" it.
That last part should bother you more than it does.
I built iHatePDF's Split PDF tool to solve exactly this problem. It's fast, it's free, it has no file size limit, and — most importantly — your files never leave your device. Not a single byte.
Here's the full story.

The Problem with Most Online PDF Tools
Online PDF utilities are everywhere. But most of them share an uncomfortable architecture: you upload your file, it travels to a remote server, gets processed, and then gets sent back to you. Along the way, your document — which might contain contracts, medical records, financial data, or intellectual property — passes through infrastructure you don't control and likely don't understand.
Some tools are upfront about this. Many are not. And even the honest ones that promise to "delete your file after 1 hour" are asking you to take their word for it.
There's a better way.

The Core Idea: Keep Everything in the Browser
Modern browsers are incredibly capable. Thanks to APIs like the File API, Web Workers, and libraries like pdf-lib, you can do serious PDF manipulation entirely on the client side — no server required.
This is exactly what the Split PDF tool does. When you upload a PDF:

It's read into memory using the browser's FileReader API as an ArrayBuffer.
pdf-lib parses the document and counts the pages.
When you hit "Split PDF," the library creates new PDF documents, copies the relevant pages over, and generates downloadable byte arrays.
Those byte arrays are handed directly to your browser's download mechanism.

At no point does the file travel over a network. The "server" is your own CPU.
javascriptconst buffer = await readFileAsArrayBuffer(file);
const { PDFDocument } = window.PDFLib;
const sourcePdf = await PDFDocument.load(buffer);
Three lines. That's the entire "upload" step — and it never left your machine.

Two Ways to Split
The tool offers two splitting modes, designed to cover the most common real-world scenarios.

By Page Ranges This is the power-user mode. You type something like 1-5, 10-15, 20 and the tool produces three separate PDF files — one for each range. It's perfect for:

Breaking a book into chapters
Extracting a specific section of a report to share with stakeholders
Separating a combined invoice document into individual invoices

The range parser handles both ranges (1-5) and single pages (20) in the same input string, separated by commas. Clean and flexible.
javascriptconst parseRanges = (rangeStr) => {
const result = [];
for (const part of rangeStr.split(",").map((s) => s.trim())) {
if (part.includes("-")) {
const [start, end] = part.split("-").map((n) => parseInt(n.trim()));
if (!isNaN(start) && !isNaN(end) && start <= end)
result.push({ start: start - 1, end: end - 1 });
} else {
const num = parseInt(part);
if (!isNaN(num)) result.push({ start: num - 1, end: num - 1 });
}
}
return result;
};
Notice the - 1 offsets — PDF page indices are zero-based internally, but humans count from 1. Small detail, big UX impact.

Individual Pages One click, and every page becomes its own PDF file. A 20-page document turns into 20 separate downloads. This is ideal for distributing slides, archiving scanned documents page by page, or just giving someone exactly the one page they asked for. To avoid overwhelming the browser's download manager, individual page downloads are staggered with a 100ms delay between each one — a tiny but important UX consideration.

Handling Downloads Across Every Browser
Cross-browser file downloads sound trivial until you try to support Safari on iOS. The tool uses a layered download helper that tries progressively more compatible approaches:

A custom window.download function if available
The legacy msSaveOrOpenBlob for old Edge/IE
A programmatically clicked tag (the standard modern approach)
As a last resort, window.open() with a blob URL, with a prompt to allow pop-ups

iOS Safari gets a special callout UI element that reminds users to check their Files app → Downloads folder, since the native Safari download behavior differs from desktop browsers.
javascriptconst isIOSSafari = () => {
const ua = window.navigator.userAgent;
return (
(!!ua.match(/iPad/i) || !!ua.match(/iPhone/i)) &&
!!ua.match(/WebKit/i) &&
!ua.match(/CriOS/i)
);
};
Small touches like this are what separate a tool people actually use from a tool people abandon in frustration.

Local History Without a Backend
The tool tracks your recent splits using a hybrid storage strategy:

Metadata (filename, tool used, timestamp, size) goes into localStorage — lightweight and fast.
The actual PDF bytes go into IndexedDB — the browser's structured data store, capable of handling large binary blobs.

This means you can revisit recent files without re-uploading anything, and it all works offline. No accounts. No sync. No data leaving your device.
javascriptconst addToHistory = async (pdfData) => {
const history = JSON.parse(localStorage.getItem(HISTORY_KEY) || "[]");
const newEntry = { id: Date.now(), name: pdfData.name, tool: pdfData.tool, ... };
if (pdfData.bytes) {
await dbSet(pdf_${newEntry.id}, pdfData.bytes); // IndexedDB
}
history.unshift(newEntry);
localStorage.setItem(HISTORY_KEY, JSON.stringify(history.slice(0, 50)));
};
The history is capped at 50 entries to keep storage usage reasonable. Pragmatic, not precious.

Quality Is Never Compromised
One concern people often have with PDF tools is quality degradation. This tool sidesteps the issue entirely — because there is no re-rendering happening.
pdf-lib doesn't rasterize your pages into images and repack them. It copies the raw PDF page objects from the source document into the new document. The text stays as text. The vector graphics stay as vectors. The embedded fonts stay embedded. You get a byte-perfect extraction, not a screenshot of a page.

The Bigger Picture
This tool is part of a broader philosophy: your files are yours. The browser has become powerful enough that the reflexive "upload to server → process → download" pipeline is often unnecessary, and increasingly, it's irresponsible.
Client-side PDF processing is just one example. The same principle applies to image compression, document conversion, data parsing, and dozens of other utility tasks that millions of people outsource to servers every day when they don't have to.
As developers, we have a responsibility to ask: does this actually need to leave the user's device? More often than the current ecosystem suggests, the answer is no.

Try It
If you've ever needed to split a PDF — and who hasn't — give it a try. Upload a file, split it, and notice what doesn't happen: no spinner while a server "processes" it, no email confirmation, no account wall, no watermark on the output.
Just your PDF, split the way you want it, in seconds, entirely on your machine.
That's what PDF tools should have been all along.

Built with React, pdf-lib, and a deep distrust of unnecessary server round-trips. All processing happens locally in your browser — always.

I Built a PDF to Word Converter That Places Every Word at Its Exact Coordinates

Pranav Mailarpawar — Thu, 26 Mar 2026 16:06:24 +0000

PDF to Word conversion is a solved problem if you don't care about accuracy. Export the text, dump it into paragraphs, call it a docx. The result opens in Word and technically contains the words from the original document, arranged in ways that bear no resemblance to the original layout.

Doing it accurately is a different problem entirely.

The PDF to Word converter inside ihatepdf.cv has two modes. Pixel Perfect — every page becomes a high-resolution JPEG embedded in the docx, visually identical to the original, text not editable. Ultra-Accurate Editable — every word extracted from the PDF's internal structure with its exact X/Y coordinates, font size, font family, bold, and italic state, then placed as an absolutely-positioned text box in the docx at its precise location. Both run entirely in your browser. No upload.

Here's how the accurate mode works.

What a PDF actually stores

A PDF is not a document format in the way Word is. It is closer to a list of drawing instructions. When a PDF renderer encounters text, it executes a series of PostScript-derived commands that describe exactly where to place each glyph on the page.

The key data structure is the text transform matrix. Every text item in a PDF has a 6-element array:

[a, b, c, d, tx, ty]

This is an affine transformation matrix. For horizontal text (which is most text), a and d are the horizontal and vertical scale factors, and tx, ty are the translation — the absolute position of the character on the page in PDF points.

The font size can be extracted directly from the matrix:

const [a, b, c, d, tx, ty] = item.transform;
const fontSize = Math.sqrt(a * a + b * b); // actual rendered size in pts

Math.sqrt(a² + b²) gives the magnitude of the horizontal basis vector — which is exactly the rendered font size accounting for any scaling applied to the text state.

The Y coordinate needs coordinate system conversion. PDFs use a bottom-left origin; HTML, CSS, and Word use top-left. The conversion:

const x = tx;
const y = viewport.height - ty; // flip Y axis

This gives us the top-left corner of the text in the PDF's point coordinate system, which is what we need to place it in Word.

Extracting the full text layer

The extraction function reads every text item from PDF.js's getTextContent() API:

async function extractNativeTextItems(pdfPage) {
  const content = await pdfPage.getTextContent({
    includeMarkedContent: false,
  });
  const vp = pdfPage.getViewport({ scale: 1 });

  const items = [];
  for (const item of content.items) {
    if (!item.str || !item.str.trim()) continue;

    const [a, b, c, d, tx, ty] = item.transform;
    const fontSize = Math.sqrt(a * a + b * b);
    const x = tx;
    const y = vp.height - ty;         // flip Y for top-left origin
    const w = item.width || fontSize * item.str.length * 0.6;
    const h = item.height || fontSize * 1.2;

    items.push({
      str:       item.str,
      x, y, w, h,
      fontSize,
      fontName:  (item.fontName || '').toLowerCase(),
      transform: item.transform,
      hasEOL:    item.hasEOL || false,
    });
  }
  return { items, pageW: vp.width, pageH: vp.height };
}

The item.fontName from PDF.js is the PDF's internal font identifier — typically something like BCDEAA+Arial-BoldItalic or g_d0_f1. The six-character prefix before the + is a PDF subset tag that can be ignored; everything after it is the actual font information.

Font detection from internal names

PDF font names encode style information in their naming patterns. Bold and italic are detected with regex:

function detectFontStyle(fontName = '') {
  const f = fontName.toLowerCase();
  const isBold   = /bold|heavy|black|semibold|demi/i.test(f);
  const isItalic = /italic|oblique|slanted/i.test(f);
  return { isBold, isItalic };
}

The font family name is normalised through a lookup table that maps PDF internal names to Word-compatible font families:

const FONT_MAP = [
  [/times|tmnr|nimbus rom/i,   'Times New Roman'],
  [/arial|helvetica|swiss/i,   'Arial'],
  [/courier/i,                  'Courier New'],
  [/georgia/i,                  'Georgia'],
  [/verdana/i,                  'Verdana'],
  [/calibri/i,                  'Calibri'],
  [/cambria/i,                  'Cambria'],
  [/palatino|palladio/i,        'Palatino Linotype'],
  // ...
];

function normaliseFont(rawName, fallbackFont) {
  if (!rawName) return fallbackFont;
  for (const [re, mapped] of FONT_MAP) {
    if (re.test(rawName)) return mapped;
  }
  // Strip subset prefix, clean up separators
  const clean = rawName.replace(/^[A-Z]{6}\+/, '').replace(/[-_,]/g, ' ');
  return clean || fallbackFont;
}

If the font can't be matched, the user's chosen fallback font (Calibri by default) is used. This handles the common case of PDF fonts with completely opaque internal names.

Line clustering — grouping spans that belong together

PDF.js returns text as individual spans, not lines. A single visual line of text might be 20 separate spans if the PDF uses different fonts, sizes, or colors mid-line. To place them sensibly in Word, they need to be grouped into lines first.

The clustering algorithm compares vertical overlap between consecutive spans:

function groupIntoLines(items) {
  const sorted = [...items].sort((a, b) =>
    a.y !== b.y ? a.y - b.y : a.x - b.x
  );

  const lines = [];
  let current = [sorted[0]];

  for (let i = 1; i < sorted.length; i++) {
    const prev = current[current.length - 1];
    const cur  = sorted[i];
    const prevMid = prev.y + prev.h / 2;
    const curMid  = cur.y  + cur.h / 2;
    const overlap = Math.min(prev.y + prev.h, cur.y + cur.h)
                  - Math.max(prev.y, cur.y);
    const minH    = Math.min(prev.h, cur.h);

    if (Math.abs(prevMid - curMid) < minH * 0.65 || overlap > minH * 0.4) {
      current.push(cur);
    } else {
      lines.push(current.sort((a, b) => a.x - b.x));
      current = [cur];
    }
  }
  if (current.length) lines.push(current.sort((a, b) => a.x - b.x));
  return lines;
}

After grouping, adjacent spans on the same line that have matching font properties are merged with a space if the gap between them warrants one:

function mergeAdjacentSpans(lines, mergeGapThreshold = 2) {
  return lines.map(line => {
    const merged = [{ ...line[0] }];
    for (let i = 1; i < line.length; i++) {
      const prev = merged[merged.length - 1];
      const cur  = line[i];
      const gap  = cur.x - (prev.x + prev.w);
      const sameFontSize = Math.abs(cur.fontSize - prev.fontSize) < 0.8;
      const sameBold     = cur.isBold   === prev.isBold;
      const sameItalic   = cur.isItalic === prev.isItalic;

      if (gap <= mergeGapThreshold && sameFontSize && sameBold && sameItalic) {
        prev.str += (gap > 0.5 ? ' ' : '') + cur.str;
        prev.w    = cur.x + cur.w - prev.x;
      } else {
        merged.push({ ...cur });
      }
    }
    return merged;
  });
}

Converting coordinates to EMU

Word's internal coordinate system uses EMU — English Metric Units. One point equals 12,700 EMU. One inch equals 914,400 EMU. This is the coordinate space that Word uses for absolute positioning of floating elements.

const PT_TO_EMU = 12700;

// For each text item:
const xEmu = Math.round(item.x * PT_TO_EMU);
const yEmu = Math.round(item.y * PT_TO_EMU);
const wEmu = Math.round(item.w * PT_TO_EMU);
const hEmu = Math.round(item.h * PT_TO_EMU);

The page dimensions also need to be converted for the DOCX section properties. PDF uses points for page dimensions; Word uses twips (twentieths of a point):

const PT_TO_TWIPS = 20;

const pgWTwips = Math.round(pageWPt * PT_TO_TWIPS);
const pgHTwips = Math.round(pageHPt * PT_TO_TWIPS);

This ensures the output DOCX has exactly the same page dimensions as the original PDF — no layout shift.

Building the DOCX anchored text boxes

Each text item becomes a <wp:anchor> — an absolutely-positioned floating text box in OOXML (the XML format underlying docx files). The anchor is positioned relative to the page at the exact EMU coordinates extracted from the PDF:

function buildAnchoredTextBox(params, id) {
  const { xEmu, yEmu, wEmu, hEmu, runs, pageWEmu, pageHEmu } = params;

  // Clamp to page bounds — prevents out-of-range crashes in Word
  const safeX = Math.max(0, Math.min(xEmu, pageWEmu - 91440)); // 91440 EMU = min 1pt
  const safeY = Math.max(0, Math.min(yEmu, pageHEmu - 91440));
  const safeW = Math.max(91440, Math.min(wEmu, pageWEmu - safeX));
  const safeH = Math.max(91440, Math.min(hEmu, pageHEmu - safeY));

  return (
    `<wp:anchor relativeFrom="page">` +
    `<wp:positionH relativeFrom="page">` +
    `  <wp:posOffset>${safeX}</wp:posOffset>` +
    `</wp:positionH>` +
    `<wp:positionV relativeFrom="page">` +
    `  <wp:posOffset>${safeY}</wp:posOffset>` +
    `</wp:positionV>` +
    `<wp:extent cx="${safeW}" cy="${safeH}"/>` +
    `<wp:wrapNone/>` +
    // ... text box content with runs ...
    `</wp:anchor>`
  );
}

<wp:wrapNone/> means the text box doesn't affect text flow — it floats freely at its absolute position, exactly like the original PDF content. relativeFrom="page" anchors the coordinates to the page origin rather than the text area, which is essential because PDFs use page-relative coordinates.

The bounds clamping (91440 EMU = approximately 0.1 points) prevents a common crash in Word where text boxes positioned outside the page area cause the file to be reported as corrupted.

The OCR fallback for scanned PDFs

When extractNativeTextItems() returns fewer than 5 text items — which happens with scanned documents, image-only PDFs, or PDFs where text was saved as outlines — the tool switches to Tesseract.js OCR:

if (nativeResult && nativeResult.items.length > 5) {
  // use native extraction
} else {
  // render page at 3× scale for OCR
  const vpScaled = page.getViewport({ scale: RENDER_SCALE }); // RENDER_SCALE = 3
  const canvas   = document.createElement('canvas');
  canvas.width   = Math.round(vpScaled.width);
  canvas.height  = Math.round(vpScaled.height);

  await page.render({ canvasContext: ctx, viewport: vpScaled }).promise;

  const tessData = await ocrPageCanvas(canvas, opts.ocrLang, onProgress);
  canvas.width = canvas.height = 0; // release GPU memory

  items = tessWordsToItems(tessData, RENDER_SCALE, pageWPt, pageHPt);
}

Rendering at 3× (216 DPI equivalent) before OCR significantly improves Tesseract accuracy compared to rendering at 1× or 2×. The 3× rendered pixel coordinates are then divided back by the render scale to get PDF point coordinates, which are then converted to EMU for placement in the docx.

Tesseract provides word-level bounding boxes (word.bbox) with confidence scores. Words with confidence below 15% are discarded — they're almost certainly noise or artifacts rather than real text.

The Pixel Perfect mode — for when visual fidelity matters more than editability

For PDFs where layout accuracy matters more than editability — forms, certificates, complex multi-column layouts — the pixel pipeline renders each page as a JPEG and embeds it inline in the docx:

async function canvasToJpeg(canvas, quality = 0.93) {
  const blob = await new Promise(res =>
    canvas.toBlob(res, 'image/jpeg', quality)
  );
  const bytes = await blobToUint8Array(blob);
  canvas.width = canvas.height = 0; // GPU memory release
  return bytes;
}

The JPEG quality options map to 0.82 (balanced), 0.93 (high, default), and 0.97 (maximum). High quality at 2× render scale produces JPEG images that are visually indistinguishable from the original PDF when viewed at normal sizes.

Each page image is embedded using <wp:inline> rather than <wp:anchor> — inline drawing elements in OOXML flow with the document and don't overlap, which is what you want when each page is the full-width content of a section.

The privacy architecture

The entire pipeline — PDF parsing, text extraction, OCR, DOCX assembly — runs locally in the browser. No bytes of your document touch any server.

For sensitive PDFs — contracts, financial statements, medical records, legal filings — this matters. The document you upload to a conversion service goes somewhere. It sits on a server. It may be retained. With ihatepdf.cv, the conversion happens in your browser tab and the result goes directly to your Downloads folder. The file never leaves your device.

Open DevTools → Network tab → convert a PDF. You'll see PDF.js and Tesseract.js loading once and being cached by the service worker. You'll see zero upload requests for your document.

When to use which mode

Ultra-Accurate Editable is the right choice when:

You need to edit the converted document — update names, fix typos, change dates
The PDF was generated digitally (not scanned) — Word, InDesign, Google Docs exports
You want selectable, copyable, searchable text in the output

Pixel Perfect is the right choice when:

Layout accuracy matters more than editability — forms, certificates, designed documents
The PDF has complex layouts that are difficult to reconstruct with text boxes
You want guaranteed visual fidelity and don't need to edit the content

Try it

ihatepdf.cv/pdf-to-word

Free. No account. No upload. No watermark. Both conversion modes available for every file, no paywalls.

If you work with PDFs professionally and have conversion cases that break — unusual layouts, complex tables, right-to-left scripts, mathematical content — I read comments. Edge cases are how the tool improves.

Part of an ongoing series on building a privacy-first PDF toolkit in the browser. The architecture overview is at ihatepdf.cv/technical-blog. Previous posts: PDF compression with Ghostscript-WASM · PDF to JPG at 600 DPI.

How I Built a PDF to JPG Converter That Renders at 600 DPI Inside a Browser Tab

Pranav Mailarpawar — Wed, 25 Mar 2026 16:14:08 +0000

The complete engineering story behind high-resolution PDF-to-image conversion using PDF.js, canvas memory management, and device-adaptive processing

Most online PDF to JPG converters cap output at 150 DPI. Some go to 300 DPI if you pay. Very few reach 600 DPI, and those that do require uploading your file to their servers.
The PDF to JPG converter inside ihatepdf.cv supports up to 600 DPI output — completely free, with zero server upload. Every pixel is rendered locally in your browser. Here's exactly how it works, why 600 DPI matters, and what engineering problems had to be solved to make it work on devices ranging from an iPhone to a 32GB workstation.

Why DPI matters for PDF to image conversion
DPI stands for dots per inch — it describes how many pixels represent each inch of the original document.
72 DPI is the browser's base resolution. One CSS pixel equals one device pixel at 1× zoom. This is what you get from a naive canvas.toBlob() call without any scaling. Fine for a thumbnail. Terrible for anything else.
150 DPI is adequate for screen viewing and social media. Text is sharp enough to read. Images look acceptable. File sizes are reasonable.
300 DPI is the standard for professional printing. Business cards, brochures, and office documents are typically printed at 300 DPI. This is what most professional tools default to.
600 DPI is for archival purposes, large-format printing, and situations where you need to zoom into the output image and still see crisp detail — scanning workflows, medical records, engineering drawings, high-resolution reproductions.
The way ihatepdf.cv achieves these DPI targets is by treating DPI as a scale multiplier from the browser's 72 DPI base:
javascriptconst dpiToScale = (dpi) => dpi / 72;

// 150 DPI → 2.08x scale
// 300 DPI → 4.17x scale
// 600 DPI → 8.33x scale
That 8.33× scale at 600 DPI is where the engineering gets interesting.

The canvas size problem
Browsers impose a hard limit on canvas dimensions: 16,384 pixels on most modern browsers (Chrome, Firefox, Safari). At 8.33× scale, a standard A4 PDF page (595 × 842 points at 72 DPI) becomes:
595 × 8.33 = 4,956 px wide
842 × 8.33 = 7,014 px tall
That's within the 16,384 limit for a standard page. But a legal-size document, a wide-format architectural drawing, or a landscape slide deck at 600 DPI can easily exceed it.
The solution is getOptimalScale():
javascriptconst getOptimalScale = (viewport, requestedScale) => {
const maxDimension = 16384;
const testWidth = viewport.width * requestedScale;
const testHeight = viewport.height * requestedScale;

if (testWidth > maxDimension || testHeight > maxDimension) {
const scaleFactor = Math.min(
maxDimension / viewport.width,
maxDimension / viewport.height
);
return scaleFactor * 0.95; // 5% safety margin
}
return requestedScale;
};
Before rendering any page, the tool calculates whether the requested scale would exceed the canvas limit. If it would, it automatically reduces the scale to the maximum safe value for that specific page's dimensions. The 5% safety margin accounts for browsers that enforce 16,383 rather than 16,384.

Device pixel ratio — the hidden multiplier
Modern screens have device pixel ratios above 1×. A MacBook Pro Retina display is 2×. Some Android phones are 3×. ihatepdf.cv accounts for this:
javascriptconst renderPageToCanvas = async (page, targetScale) => {
const viewport = page.getViewport({ scale: targetScale });
const pixelRatio = Math.min(window.devicePixelRatio || 1, 2); // cap at 2×

canvas.width = Math.floor(viewport.width * pixelRatio);
canvas.height = Math.floor(viewport.height * pixelRatio);

const ctx = canvas.getContext('2d', {
alpha: false, // white background — JPEG has no alpha channel
willReadFrequently: false
});

ctx.fillStyle = 'white';
ctx.fillRect(0, 0, canvas.width, canvas.height);
ctx.scale(pixelRatio, pixelRatio);
ctx.imageSmoothingEnabled = true;
ctx.imageSmoothingQuality = 'high';

await page.render({
canvasContext: ctx,
viewport,
intent: 'print', // not 'display' — higher quality rendering
enableWebGL: false,
renderInteractiveForms: false,
}).promise;

return canvas;
};
Three things worth noting here:
alpha: false — PDFs have no transparent background. Setting alpha to false avoids the browser creating an alpha channel it never needs, saving memory.
intent: 'print' — PDF.js has two rendering intents: display and print. Print intent uses higher-quality glyph rendering and anti-aliasing, which produces noticeably sharper text especially at high DPI.
pixelRatio capped at 2× — Going to 3× on a high-DPI phone would triple memory usage for a visual improvement that's imperceptible at normal viewing sizes. The cap prevents memory exhaustion on mobile.

Memory management — the real challenge
This is what separates a tool that actually works from one that crashes your browser tab.
At 600 DPI, each A4 page canvas uses approximately:
4,956 × 7,014 px × 4 bytes (RGBA) = ~139 MB of RAM
Plus an equivalent amount of GPU texture memory for the canvas. Plus the PDF.js rendering buffers. For a 50-page document at 600 DPI, the naive approach allocates ~7 GB — which immediately crashes any browser.
The solution is explicit canvas disposal after each page:
javascriptconst canvas = await renderPageToCanvas(page, optimizedScale);

// ... create blob, trigger download ...

canvas.width = 0; // ← releases GPU texture memory immediately
canvas.height = 0;
// canvas goes out of scope → GC collects RAM
Setting canvas dimensions to zero is not obvious. Simply removing the canvas reference doesn't immediately release GPU memory in most browsers — the GPU texture allocation persists until the browser's garbage collector runs, which can be seconds later. Setting width and height to zero forces immediate GPU memory deallocation.
Between batches, the tool adds a deliberate 2-second pause:
javascriptif (batchIndex < batches.length - 1) {
await new Promise(resolve => setTimeout(resolve, 2000));
if (window.gc) window.gc(); // hint — browser may ignore
}
Chrome's garbage collector typically triggers after ~1–1.5 seconds of idle time. The 2-second pause gives it time to run and reclaim memory before the next batch begins.

Device-adaptive limits
The same code runs on a 2GB RAM phone and a 32GB workstation. Rather than applying one-size-fits-all limits, ihatepdf.cv detects device capabilities and adjusts automatically:
javascriptconst getDeviceCapabilities = () => {
const isMobile = /Android|iPhone/i.test(navigator.userAgent);
const isTablet = /(tablet|ipad)/i.test(navigator.userAgent);
const deviceMem = navigator.deviceMemory || 4; // not available in Safari

if (isMobile && screen.width < 768) {
return { maxFileSize: 50 * 1024 * 1024, maxDPI: 300, maxPagesPerBatch: 10 };
}
if (isTablet) {
return { maxFileSize: 75 * 1024 * 1024, maxDPI: 450, maxPagesPerBatch: 25 };
}
if (deviceMem < 4) {
return { maxFileSize: 100 * 1024 * 1024, maxDPI: 450, maxPagesPerBatch: 30 };
}
return { maxFileSize: 150 * 1024 * 1024, maxDPI: 600, maxPagesPerBatch: 50 };
};
A phone user still gets PDF to JPG conversion — just capped at 300 DPI and 10 pages per batch instead of 600 DPI and 50 pages. They get the tool, scaled to what their device can handle.
Before any large conversion, memory usage is estimated:
javascriptconst estimateMemoryUsage = (fileSize, pageCount, scale, format) => {
const baseMemoryPerPage = 5 * 1024 * 1024; // 5 MB at scale 1.0
const scaleFactor = Math.pow(scale, 2); // quadratic: 2× scale = 4× memory
const formatMultiplier = format === 'png' ? 1.5 : 1.0;
const estimated = pageCount * baseMemoryPerPage * scaleFactor * formatMultiplier;
return { estimated, withSafety: estimated * 1.5 };
};
Memory scales quadratically with DPI — doubling DPI quadruples memory usage because both dimensions double. A user trying to convert 50 pages at 600 DPI sees a warning before the browser runs out of memory rather than a silent crash.

JPEG vs PNG — when to use each
ihatepdf.cv supports both output formats. The choice matters:
JPEG — lossy compression. Adjustable quality from 60% to 100%. 300 DPI JPEG at 85% quality is typically 500KB–2MB per page. The right choice for photos, scanned documents, presentations — anything where some quality loss is imperceptible in practice.
PNG — lossless compression. No quality setting. 300 DPI PNG is typically 3–8MB per page. The right choice for documents with sharp lines, text-heavy pages, technical diagrams, or any situation where pixel-perfect reproduction is required.
For archival purposes at 600 DPI, PNG is almost always the right answer — the file sizes are large but the quality guarantee is absolute.

The four DPI presets and what they're for
Rather than exposing a raw DPI slider and leaving users to guess, ihatepdf.cv maps to four practical use cases:
PresetDPIJPEG QualityBest forWeb15085%Social media, email, web embeddingPrint30095%Office printing, CVs, brochuresProfessional50098%High-end printing, detailed documentsArchival600100%Maximum quality, large format, archiving
The Archival preset is only shown on devices that can handle it — it is hidden on phones and tablets where it would cause memory issues.

Privacy — verifiable, not just claimed
The entire conversion pipeline runs locally:
javascript// The complete data lifecycle — no network
FileReader.readAsArrayBuffer(file) // → browser memory
→ pdfjsLib.getDocument({ data }) // → PDF.js processing (local)
→ page.render({ canvasContext }) // → Canvas API (local)
→ canvas.toBlob('image/jpeg') // → Blob in memory
→ URL.createObjectURL(blob) // → local object URL
→ anchor.click() // → device storage
// Zero network requests for file data
Open DevTools → Network tab → convert a PDF to JPG. The upload column shows 0 bytes for your document. Not a policy. Not a claim. A verifiable architectural fact.

Try it
ihatepdf.cv/pdf-to-jpg
Free. No account. No upload. No watermark on output. Supports JPEG and lossless PNG up to 600 DPI — the same output quality as tools that charge $20/month, running entirely in your browser tab.
If you process high-resolution documents professionally and have questions about the implementation, or if you find edge cases I haven't handled yet, I read comments.

Part of an ongoing series on building a privacy-first PDF toolkit entirely in the browser. The full architecture overview is at ihatepdf.cv/technical-blog. The compression deep-dive is at ihatepdf.cv/compress-pdf.ShareContentimport React, {
useState,
useEffect,
useRef,
useCallback,
Suspense,
} from "react";
import { useNavigate, useLocation } from "react-router-dom";
import ClarityAnalytics from "./ClarityAnalytics";
import {
ChevronDown,
ArrowRight,
ChevronUp,
LayoutDashboard,
Sparkles,
} from "lucipastedimport React, { useState, useEffect } from "react";
import {
FileText,
Cpu,
HardDrive,
Zap,
Shield,
ChevronRight,
Code,
Database,
Layers,
Brain,
Lock,
Activity,
MessageSquare,
Key,
} from "lucide-react";

function Blog() {
const [activeSection, setActiveSection] = useStpasted#!/usr/bin/env node
/**

generate-seo-pages.js — ihatepdf.cv
Generates unique index.html for every tool route + static blog pages.
BUILD: "vite build && node generate-seo-pages.js" */ import fs from 'fs' import path from 'path' import { fileURLToPath } from 'url' import { POSTS } from '.pasted<!DOCTYPE html>

generate-seo-pages.js — ihatepdf.cv
Generates unique index.html for every tool route + static blog pages.
BUILD: "vite build && node generate-seo-pages.js" / import fs from 'fs' import path from 'path' import { fileURLToPath } from 'url' import { POSTS } from '.pasted#!/usr/bin/env node /*
generate-seo-pages.js — ihatepdf.cv
Generates unique index.html for every tool route + static blog pages.
BUILD: "vite build && node generate-seo-pages.js" */ import fs from 'fs' import path from 'path' import { fileURLToPath } from 'url' import { POSTS } from '.pastedimport React, { useState, useEffect } from "react";

const readFileAsArrayBuffer = (file) => {
return new Promise((resolve, reject) => {
const reader = new FileReader();
reader.onload = () => resolve(reader.result);
reader.onerror = reject;
reader.readAsArrayBuffer(file);
});
};
pasted1 Blogger https://www.blogger.com 100
2 WordPress.com https://wordpress.com 100
3 LinkedIn Articles https://www.linkedin.com 99
4 Reddit (Article Submissions) https://www.reddit.com 99
5 Google Sites https://sites.google.com 98
6 Medium https://medium.com 96
7 GitHub Pages https://pages.github.com 9pasted<!DOCTYPE html>

generate-seo-pages.js — ihatepdf.cv
Generates unique index.html for every tool route + static blog pages.
BUILD: "vite build && node generate-seo-pages.js" */ import fs from 'fs' import path from 'path' import { fileURLToPath } from 'url' import { POSTS } from '.pastedimport React, { useState, useEffect, useRef } from "react";

// ── Scroll progress hook ──────────────────────────────────────────────────────
function useScrollProgress() {
const [progress, setProgress] = useState(0);
useEffect(() => {
const onScroll = () => {
const total = document.dpasted#!/usr/bin/env node
/**

generate-seo-pages.js — ihatepdf.cv
Generates unique index.html for every tool route + static blog pages.
BUILD: "vite build && node generate-seo-pages.js" */ import fs from 'fs' import path from 'path' import { fileURLToPath } from 'url' import { POSTS } from '.pastedimport React, { useState, useEffect } from "react";

const IDB_STORE_NAME = "ihatepdf-store";
const IDB_DB_NAME = "ihatepdf_DB";
const HISTORY_KEY = "ihatepdf_history";

const initDB = () => {
return new Promise((resolve, reject) => {
const request = indexedDB.open(IDB_DB_NAME, 1);
requestpastedimport React, { useState, useEffect } from "react";

const IDB_STORE_NAME = "ihatepdf-store";
const IDB_DB_NAME = "ihatepdf_DB";
const HISTORY_KEY = "ihatepdf_history";

const readFileAsArrayBuffer = (file) => {
return new Promise((resolve, reject) => {
const reader = new FileReader();
reapasted

I Ran Ghostscript Inside a Browser Tab to Build a Free PDF Compressor

Pranav Mailarpawar — Tue, 24 Mar 2026 15:27:55 +0000

How WebAssembly turned a 50-year-old PDF compression engine into a privacy-first browser tool

A few weeks ago a friend sent me a scanned contract. It was 18MB — too large to attach to a reply email, too sensitive to upload to a random compression website.
The "too sensitive" part is the one most people skip past. They just upload it. Most free PDF compressors work by sending your file to their servers, running compression remotely, and sending the result back. That's a reasonable architecture. It's also a data flow that includes your document passing through infrastructure you don't control, being stored temporarily on someone else's disk, and processed by systems whose security posture you can't verify.
For a contract, a tax return, an NDA — that matters.
So I built the compression tool inside ihatepdf.cv differently. Everything runs in your browser tab. Your file never leaves your device. Here's exactly how.

The engine: Ghostscript compiled to WebAssembly
Ghostscript is not new software. It has been the gold standard for PostScript and PDF processing since 1988. Adobe Acrobat uses it internally. Professional print shops use it. It is written in C and has been battle-tested on hundreds of millions of documents.
The key insight: Ghostscript can be compiled to WebAssembly. That means the same engine that runs on servers can run inside a browser tab, at near-native speed, with no server required.
The compression pipeline uses a Web Worker so the main thread stays responsive while Ghostscript processes the PDF:
javascriptconst worker = new Worker('/background-worker.js');

worker.postMessage({
data: {
psDataURL: blobUrl,
config: config,
},
target: 'wasm',
});

worker.onmessage = async (e) => {
const response = await fetch(e.data);
const compressedBlob = await response.blob();
// download the result
};
The user uploads a file, it becomes a Blob URL, the Blob URL is handed to the worker, Ghostscript processes it inside WebAssembly, and the result comes back as another Blob. Nothing goes over the network. Nothing is stored on any server. The whole thing happens inside the browser's sandboxed environment.

The five optimizations Ghostscript applies simultaneously
This is what separates proper PDF compression from naive approaches that just re-export the file.

Image downsampling Photos and raster graphics embedded in PDFs are often stored at their original resolution — 600 DPI from a scanner, 300 DPI from a camera. For screen viewing, 150 DPI is visually identical. Ghostscript resamples images using bicubic interpolation, which is the highest-quality downsampling algorithm available. The result is smaller with no perceptible visual difference at normal viewing sizes.
JPEG recompression After downsampling, images are re-encoded at a quality level matched to the compression preset: javascriptconst qualityToJpegQuality = { '/screen': 40, // 72 DPI — maximum compression '/ebook': 60, // 150 DPI — balanced '/printer': 80, // 300 DPI — print quality '/prepress': 92, // 300 DPI — professional print };
Font subsetting This one surprises people. Embedded fonts in PDFs often contain the entire font family — every character, every glyph, including ones your document never uses. A single embedded font can be 200–400KB. Font subsetting trims the embedded data to only characters actually present in your document. For documents using common fonts, this alone can reduce file size by 20–30%.
Metadata stripping Every PDF created by Word, Acrobat, Google Docs, or any other tool embeds metadata: author name, creation software, revision history, thumbnail previews. This data adds size and exposes information you probably don't need to include when sharing. Ghostscript strips it during compression.
Stream recompression The content streams that encode page content are recompressed using the most efficient lossless algorithm. Text and vector graphics are entirely unaffected — they are never converted to pixels, which is why text stays perfectly sharp at every compression level.

Why text never gets blurry
This is the most common concern and the most important thing to understand about PDF compression.
Text in a PDF is not stored as an image. It is stored as vector instructions: draw this glyph, at these coordinates, with this font, at this size. Vector data has no resolution. It is mathematically perfect at every zoom level.
Compression only affects raster content — photos, scanned pages, embedded images. A document that is entirely text and vector graphics will compress almost nothing using image downsampling, because there are no raster images to downsample. But it will still benefit from font subsetting and stream recompression.

The three presets and when to use each
Rather than exposing Ghostscript's raw configuration options, the tool maps to three practical use cases:
Light (20–30% reduction): Uses /printer quality — 300 DPI images, 80% JPEG quality. Output is indistinguishable from the original. Use this for design portfolios, documents you will print, or any case where you want the smallest reduction in quality.
Medium (40–50% reduction): Uses /ebook quality — 150 DPI images, 60% JPEG quality. This is the sweet spot for CVs, contracts, reports, and email attachments. Looks identical on screen. Most people cannot tell the difference between a Medium-compressed document and the original when reading normally.
Heavy (60–70% reduction): Uses /screen quality — 72 DPI images, 40% JPEG quality. Maximum compression. Text stays perfectly sharp; photos become noticeably softer at high zoom. Use this for archiving, upload portals with strict size limits, or anywhere you need to get under 1–2MB.

The memory management problem
Processing large PDFs in a browser is harder than it sounds. A 50MB PDF with high-resolution images can consume 200–300MB of RAM during processing — 3–5× overhead is normal. On mobile devices with 2–4GB total RAM, this matters.
The tool estimates memory requirements before starting:
javascriptconst getDeviceCapabilities = () => {
const isMobile = /Android|iPhone/i.test(navigator.userAgent);
const deviceMem = navigator.deviceMemory || 4;

if (isMobile && screen.width < 768) {
return { maxFileSize: 50 * 1024 * 1024 }; // 50MB on phones
}
if (deviceMem < 4) {
return { maxFileSize: 100 * 1024 * 1024 }; // 100MB on low memory
}
return { maxFileSize: 150 * 1024 * 1024 }; // 150MB on desktop
};
navigator.deviceMemory is not available in Safari, so the fallback assumes 4GB — conservative enough to handle most cases without crashing.

The privacy architecture — verifiable, not just claimed
Most privacy claims are policies. "We delete files after 2 hours." "We don't share data." These are statements you have to trust.
The architecture here makes the claim verifiable. Open DevTools → Network tab → compress a PDF. Watch the network requests. You will see the Ghostscript WASM file load once and get cached. You will see zero upload requests for your document. No bytes of your PDF travel over the network.
After first load, the tool also works fully offline. The service worker caches the WebAssembly libraries:
javascriptself.addEventListener('install', (e) => {
e.waitUntil(
caches.open('ihatepdf-v1').then((cache) => cache.addAll([
'/',
'https://unpkg.com/pdf-lib@1.17.1/dist/pdf-lib.min.js',
// ghostscript wasm + other libraries
]))
);
});
Disconnect from WiFi. Reload the page. Compress a PDF. It works. There is no server to connect to because there is no server involved.

The honest trade-off
A cloud server with a dedicated CPU will compress a 150MB PDF faster than Ghostscript-WASM running in a browser tab on a four-year-old laptop.
If you are compressing large volumes of very large files and speed is the priority, a server-based tool is genuinely better for that use case.
For everything else — privacy, offline use, no account, no size limits beyond your device's RAM, no watermarks on the output — the local approach wins. The Ghostscript engine is identical either way. The compression quality is the same. The only difference is where the processing happens.

Try it
ihatepdf.cv/compress-pdf
No account. No upload. No watermark. The source of the compression quality is the same Ghostscript engine that professional tools use — it just runs on your device instead of theirs.
If you process sensitive documents and have questions about how the architecture works, or if something is broken, I read comments.

This is part of an ongoing series on building a privacy-first PDF toolkit entirely in the browser using WebAssembly. The technical deep-dive on the full architecture is at ihatepdf.cv/technical-blog

I Stopped Emailing Myself Photos — Here’s the Tool That Fixed Everything

Pranav Mailarpawar — Mon, 23 Mar 2026 20:08:03 +0000

How a free, privacy-first browser tool quietly became my go-to for converting images to PDF

There’s a ritual most of us have performed at least once: taking a dozen photos of something — receipts, a whiteboard, handwritten notes, a product — and then spending the next ten minutes trying to figure out how to send them as one clean file.

You zip them. The recipient can’t open the zip. You try Google Drive. They don’t have a Google account. You send them one by one. They get confused about the order.

Eventually, someone says: “Can you just send it as a PDF?”

Yes. Obviously. But converting images to PDF has, somehow, always been more painful than it should be. Until I found ihatepdf.cv.

What Is ihatepdf.cv?
ihatepdf.cv is a free, browser-based PDF toolkit — and the name tells you everything about the spirit of the product. It was clearly built by someone who has dealt with one too many bloated, subscription-gated, ad-riddled PDF tools and decided to do something about it.

The platform offers a suite of PDF utilities, but the one that’s earned a permanent tab in my browser is the JPG to PDF converter — or more precisely, the Images to PDF tool at ihatepdf.cv/images-to-pdf.

The Part That Actually Surprised Me: Your Files Never Leave Your Device
Most online file converters have a quiet business model: you upload your files, they process them on their servers, and somewhere in the fine print it says they might retain your data for “service improvement.”

ihatepdf.cv takes a fundamentally different stance — and they’re upfront about it.

Everything happens in the browser. Your files, your control.

The image-to-PDF conversion runs entirely inside your browser tab using PDF-lib, a JavaScript library that executes locally on your machine. Nothing is uploaded. Nothing is transmitted. No file ever touches an external server. What looks like a web service is actually a local application that just happens to live in your browser.

This isn’t a small footnote in a privacy policy — it’s the core design decision behind the entire platform. ihatepdf.cv was built on the principle that your files belong to you, and respecting your privacy means making it technically impossible for your documents to be stored, analyzed, or shared without your knowledge.

When you convert an image on ihatepdf.cv, here’s what doesn’t happen:

Your file is not uploaded to any server
No third party ever receives or processes your document
Nothing is retained after you close the tab
There are no accounts, no session tokens tied to your files, no tracking of what you converted
The result is a tool you can use with complete confidence — whether you’re converting a personal photo, a financial document, a medical record, or sensitive client work. The conversion happens in your browser, your files stay on your device, and that’s where it ends.

This is what genuine privacy looks like in a web tool. Not a promise. An architectural guarantee.

Using It Is Embarrassingly Simple
Here’s what the workflow actually looks like:

Step 1: Go to ihatepdf.cv/images-to-pdf and click Choose Files — or just drag and drop images directly into the upload zone.

Step 2: Your images appear as numbered thumbnails. You can remove any you don’t want. The numbers show you the order they’ll appear in the final PDF.

Step 3: Click Convert to PDF. A spinner appears for a second or two.

Step 4: Your PDF downloads automatically.

Write on Medium
That’s it. No account creation. No email verification. No watermarks. No “upgrade to Pro to download.” The whole thing takes less time than finding the right app on your phone.

What It Handles Well
JPG and PNG support — the two formats that cover about 95% of real-world image use cases. Whether you’re dealing with camera photos (almost always JPG) or screenshots and graphics (usually PNG), ihatepdf.cv handles both natively.

Batch conversion — you can upload as many images as you want in a single session. They all get stitched into one PDF in the order you uploaded them.

Original quality preservation — images are embedded at their source resolution. There’s no recompression, no quality loss. What you put in is what comes out, pixel for pixel.

Works offline — after the initial page load, the converter works without an internet connection. The processing is all local.

Mobile-friendly — the interface is responsive and includes explicit support for iOS Safari, which is historically one of the harder browsers to get file downloads working correctly on.

The Use Cases That Make This Indispensable
Once you have a fast, frictionless image-to-PDF tool, you start reaching for it constantly. A few situations where I’ve found it genuinely useful:

Expense reports. Snap photos of receipts throughout the week, then dump them all into ihatepdf.cv on Friday afternoon. One PDF, one attachment, done.

Scanned documents. If you’re using your phone camera as a scanner — and most people are at this point — the output is a folder full of JPGs. ihatepdf.cv turns that folder into a proper document.

Client deliverables. Designers and photographers often need to send proofs or samples. A PDF looks more intentional than a ZIP file of images and opens cleanly on every device.

Portfolios. Compile a selection of work images into a single, shareable document without needing InDesign or Canva.

Archiving paperwork. Utility bills, insurance documents, anything you’ve photographed for record-keeping purposes — PDFs are far more reliably searchable and organized than a pile of JPGs.

A Few Practical Tips
Name your files before uploading. ihatepdf.cv doesn’t currently support drag-to-reorder within the interface. If you need a specific page sequence, naming your files 001_, 002_, 003_ before uploading ensures they come in the right order.

Very large images slow things down. Because everything is processed in-browser, images above 20MB can noticeably slow the conversion. A quick resize beforehand keeps things snappy.

Combine with other ihatepdf.cv tools. If the resulting PDF is too large to email, the ihatepdf.cv compress tool can reduce the file size without a noticeable quality difference. If you need to add page numbers to a long document, that’s another tool on the same platform. The whole suite is designed to be used together.

Why This Approach to Software Matters
There’s a broader design philosophy at work here that I think is worth naming.

Most consumer software has drifted toward extracting as much value from users as possible: subscriptions for basic features, dark patterns that obscure free tiers, data collection baked into every interaction.

ihatepdf.cv is a quiet counterexample. It’s free. It’s private by design. It doesn’t require an account. It doesn’t ask for anything in return. The tool exists to solve a specific problem as efficiently as possible, and then it gets out of your way.

That’s rare. It’s worth pointing at when you find it.

The Bottom Line
If you regularly deal with images that need to become documents — for work, for admin, for clients, for record-keeping — ihatepdf.cv/images-to-pdf is worth bookmarking right now.

It’s fast, it’s free, it works without uploading your files anywhere, and it produces clean, full-quality PDFs every time. There’s genuinely no catch.

The next time someone asks you to “send it as a PDF,” you’ll know exactly where to go.

Try it for yourself at ihatepdf.cv — no account needed.