<?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: zhang jimmy</title>
    <description>The latest articles on DEV Community by zhang jimmy (@zhang_jimmy_54a0414571400).</description>
    <link>https://dev.to/zhang_jimmy_54a0414571400</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%2F4232896%2F9863f05f-9b37-4da3-9bd2-b3b6dc7da6a6.png</url>
      <title>DEV Community: zhang jimmy</title>
      <link>https://dev.to/zhang_jimmy_54a0414571400</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zhang_jimmy_54a0414571400"/>
    <language>en</language>
    <item>
      <title>Your Slides Don't Belong on Someone Else's Server</title>
      <dc:creator>zhang jimmy</dc:creator>
      <pubDate>Sun, 08 Nov 2026 00:04:38 +0000</pubDate>
      <link>https://dev.to/zhang_jimmy_54a0414571400/your-slides-dont-belong-on-someone-elses-server-1jj</link>
      <guid>https://dev.to/zhang_jimmy_54a0414571400/your-slides-dont-belong-on-someone-elses-server-1jj</guid>
      <description>&lt;p&gt;&lt;em&gt;Five free PowerPoint tools, compared honestly — and why "runs in your browser" matters more than another AI feature&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Last quarter I watched a colleague hover over an "Upload" button for a full minute. The file was a board deck — unreleased numbers, names, the works. The tool she was using would happily merge her two PowerPoint files, but only after they took a trip to a server she'd never heard of, in a country she couldn't name.&lt;/p&gt;

&lt;p&gt;She closed the tab. I went and built the tool she actually needed.&lt;/p&gt;

&lt;p&gt;This is a short, honest comparison of the free ways to merge and compress PowerPoint files today, and the one question I now ask of every file tool: where does my file actually go?&lt;/p&gt;

&lt;h2&gt;
  
  
  The usual suspects
&lt;/h2&gt;

&lt;p&gt;Smallpdf, iLovePDF and Sejda are polished, and for ordinary PDFs they're fine. But read the fine print: they process PDFs, not native PowerPoint files, and their free tiers ration you — Smallpdf's free plan covers about two tasks a day across the whole site, iLovePDF limits per tool, Sejda per hour. Your file is uploaded, processed on their infrastructure, and (to their credit) deleted after a while. "After a while" is doing a lot of work in that sentence.&lt;/p&gt;

&lt;h2&gt;
  
  
  The desktop route
&lt;/h2&gt;

&lt;p&gt;PowerPoint itself can merge decks, and LibreOffice can too. Zero upload risk, but you're tied to installed software, the merge workflow is clunky, and compression basically means hunting down images one by one. Fine for you; useless for the colleague on a borrowed laptop.&lt;/p&gt;

&lt;h2&gt;
  
  
  The browser-native route
&lt;/h2&gt;

&lt;p&gt;A PPTX file is really just a zip of XML and media. That means a modern browser has everything needed to merge decks and re-encode images locally — no server round-trip at all. That's how I built &lt;a href="https://aippt.org" rel="noopener noreferrer"&gt;AIPPT.org&lt;/a&gt;: its merge and compress tools run 100% in your browser. Your file is never uploaded, there's no account, no watermark, and no task counter ticking down. Merging keeps each deck's design and the result stays fully editable; on an image-heavy 3.9 MB test deck, compression cut 68–84% in under a second, locally.&lt;/p&gt;

&lt;p&gt;There's also an AI generator on the site that drafts decks from a topic, text or PDF — but honestly, the local tools are the part I wish had existed years ago.&lt;/p&gt;

&lt;h2&gt;
  
  
  The takeaway
&lt;/h2&gt;

&lt;p&gt;For a grocery list, any tool works. For a board deck, a client's unreleased roadmap, or a student's thesis, "your file never leaves your device" isn't a feature — it's the whole point. Next time a tool asks you to upload a sensitive file, ask who else gets a copy, and for how long. If the answer is fuzzy, keep your files home.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>tools</category>
      <category>privacy</category>
      <category>presentation</category>
    </item>
  </channel>
</rss>
