<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: PDFDistrict</title>
    <description>The latest articles on DEV Community by PDFDistrict (@pdfdistrict).</description>
    <link>https://dev.to/pdfdistrict</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4258135%2F69bce6dd-45ca-4867-b29a-8778be5fdce2.png</url>
      <title>DEV Community: PDFDistrict</title>
      <link>https://dev.to/pdfdistrict</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pdfdistrict"/>
    <language>en</language>
    <item>
      <title>I built 21 free PDF tools that never upload your files</title>
      <dc:creator>PDFDistrict</dc:creator>
      <pubDate>Sun, 22 Nov 2026 01:25:40 +0000</pubDate>
      <link>https://dev.to/pdfdistrict/i-built-21-free-pdf-tools-that-never-upload-your-files-242p</link>
      <guid>https://dev.to/pdfdistrict/i-built-21-free-pdf-tools-that-never-upload-your-files-242p</guid>
      <description>&lt;p&gt;Every time I needed to merge two PDFs or sign a form, I ended up on a site that uploaded the file to a server. That's fine for a restaurant menu. It's less fine for a contract, an ID or a bank statement.&lt;/p&gt;

&lt;p&gt;So I built &lt;a href="https://pdfdistrict.com" rel="noopener noreferrer"&gt;PDFDistrict&lt;/a&gt;, a set of 21 free PDF tools where all the processing happens in your browser. The file is read into memory, processed there, and handed back as a download. Nothing is sent to a server.&lt;/p&gt;

&lt;p&gt;This post covers how it works, what I learned, what it can't do, and how to check the "no upload" claim yourself instead of taking my word for it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it's built
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A plain static site: HTML, CSS and JavaScript, no framework.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://pdf-lib.js.org/" rel="noopener noreferrer"&gt;pdf-lib&lt;/a&gt; does the editing: merge, split, rotate, add text, images and signatures, page numbers, watermarks and metadata.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://mozilla.github.io/pdf.js/" rel="noopener noreferrer"&gt;pdf.js&lt;/a&gt; does the rendering: thumbnails, previews, PDF to JPG/PNG and PDF to text.&lt;/li&gt;
&lt;li&gt;No backend. The server only hands out the website files.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I built it with Claude as a coding assistant along the way.&lt;/p&gt;

&lt;p&gt;Every tool works the same way: you pick a file, the browser opens it in memory, the library does the job, and you get the result as a normal download.&lt;/p&gt;

&lt;h2&gt;
  
  
  Things I learned building it
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Load the heavy libraries only when needed.&lt;/strong&gt; The PDF libraries are big, so the home page doesn't load them at all. They load the first time you open a tool, which keeps the site fast. Once a tool is open, it also keeps working if your connection drops halfway through.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Removing metadata is more than clearing the title and author.&lt;/strong&gt; A PDF can store its metadata in two places. If you only clear the obvious one (title, author, dates), a second hidden copy survives. To really strip it, both have to go.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. "Compress" in the browser has honest limits.&lt;/strong&gt; My compressor reorganizes how the file is stored, which helps with some PDFs. It doesn't re-encode images, so a 30 MB scanned document won't shrink much. I'd rather say that up front than promise magic.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Memory is the real ceiling.&lt;/strong&gt; Everything happens in the browser's memory, so files are capped at 100 MB. Bigger files work on a computer but get unreliable on phones.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to check that nothing is uploaded
&lt;/h2&gt;

&lt;p&gt;You don't have to trust me:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open a tool and your browser's developer tools, &lt;strong&gt;Network&lt;/strong&gt; tab.&lt;/li&gt;
&lt;li&gt;Clear the list, then drop in a PDF and run the tool.&lt;/li&gt;
&lt;li&gt;You'll see the site's own files and, since the site is free and ad-supported, some ad requests. What you won't see is your file being sent anywhere.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A second test: open a tool, turn off your Wi-Fi, and run it. It still works, because there's no server step.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it doesn't do
&lt;/h2&gt;

&lt;p&gt;Being browser-only has trade-offs, so to be clear:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No OCR.&lt;/li&gt;
&lt;li&gt;No PDF to Word.&lt;/li&gt;
&lt;li&gt;It can't edit the text that's already inside a PDF (you can add text on top).&lt;/li&gt;
&lt;li&gt;It can't open password-protected files.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For those jobs, a server-based tool or a desktop app is the better choice.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 21 tools
&lt;/h2&gt;

&lt;p&gt;Merge, split, compress, organize, reorder, rotate, delete pages, extract pages, crop, sign, add text, add an image, watermark, page numbers, image to PDF, PDF to JPG, PDF to PNG, PDF to text, resize images to PDF, remove metadata and preview. The site is in English and &lt;a href="https://pdfdistrict.com/es/" rel="noopener noreferrer"&gt;Spanish&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It's free and needs no account: &lt;a href="https://pdfdistrict.com" rel="noopener noreferrer"&gt;pdfdistrict.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I'd love feedback, especially on what's missing or broken.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>webdev</category>
      <category>privacy</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
