<?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: TimelyUps</title>
    <description>The latest articles on DEV Community by TimelyUps (@timelyups).</description>
    <link>https://dev.to/timelyups</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%2F4170278%2F304ed235-c168-4b11-b434-63b8f45682b9.png</url>
      <title>DEV Community: TimelyUps</title>
      <link>https://dev.to/timelyups</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/timelyups"/>
    <language>en</language>
    <item>
      <title>I Built Free PDF Tools That Run 100% in the Browser — No Server, No Uploads</title>
      <dc:creator>TimelyUps</dc:creator>
      <pubDate>Sat, 24 Oct 2026 05:21:56 +0000</pubDate>
      <link>https://dev.to/timelyups/i-built-free-pdf-tools-that-run-100-in-the-browser-no-server-no-uploads-12ik</link>
      <guid>https://dev.to/timelyups/i-built-free-pdf-tools-that-run-100-in-the-browser-no-server-no-uploads-12ik</guid>
      <description>&lt;p&gt;Pakistan's news readers needed simple, trustworthy utilities — merge a PDF, turn photos into a PDF, pull images out of a PDF — without uploading personal documents to a random server. So I built them as a fully client-side toolset on our news site. Here is how, and what I learned.&lt;/p&gt;

&lt;h2&gt;
  
  
  The architecture: everything in the browser
&lt;/h2&gt;

&lt;p&gt;The stack is deliberately boring: two CDN libraries, zero backend.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;pdf-lib&lt;/strong&gt; handles merge and JPG-to-PDF assembly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;pdf.js&lt;/strong&gt; (Mozilla's renderer) handles PDF-to-JPG page rasterization.
Every operation runs in the browser with chunked async steps, so the UI never freezes on a 50-page document. The key privacy property: &lt;strong&gt;files never leave the device&lt;/strong&gt;. There is no upload endpoint at all.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Lessons from shipping to real users
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Memory is the real limit, not CPU.&lt;/strong&gt; Rasterizing PDF pages at print resolution eats RAM fast. I cap export resolution and process pages sequentially instead of in parallel.&lt;br&gt;
&lt;strong&gt;2. Mobile Safari is the QA department.&lt;/strong&gt; Half our traffic is mobile. pdf.js rendering on older Android WebViews needed explicit fallbacks for missing OffscreenCanvas support.&lt;br&gt;
&lt;strong&gt;3. Small UX details carry the product.&lt;/strong&gt; A drag-and-drop zone, per-file remove buttons, and a visible "your files never upload" notice did more for trust than any feature.&lt;br&gt;
&lt;strong&gt;4. No-backend means no bills.&lt;/strong&gt; Hosting is a static page. The tools cost essentially nothing to run at scale — a meaningful property when your audience is price-sensitive students and job applicants.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;The tools are live and free: &lt;a href="https://timelyups.com/tools/pdf-tools/" rel="noopener noreferrer"&gt;TimelyUps PDF Tools — merge PDFs, JPG to PDF, PDF to JPG, all in your browser&lt;/a&gt;. Feedback and bug reports welcome in the comments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I run &lt;a href="https://timelyups.com/" rel="noopener noreferrer"&gt;TimelyUps&lt;/a&gt;, a Pakistan-focused digital news outlet where we also ship free online tools for our readers.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>pdf</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
