<?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: ExitCodeZer0</title>
    <description>The latest articles on DEV Community by ExitCodeZer0 (@exitcodezer0).</description>
    <link>https://dev.to/exitcodezer0</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3320269%2F39af047c-85b8-4135-b022-a561b4af5c1e.png</url>
      <title>DEV Community: ExitCodeZer0</title>
      <link>https://dev.to/exitcodezer0</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/exitcodezer0"/>
    <language>en</language>
    <item>
      <title>Why I Built a No-Fluff HTML PDF API (and What I Learned Shipping My First Dev Tool)</title>
      <dc:creator>ExitCodeZer0</dc:creator>
      <pubDate>Thu, 03 Jul 2025 18:17:10 +0000</pubDate>
      <link>https://dev.to/exitcodezer0/why-i-built-a-no-fluff-html-pdf-api-and-what-i-learned-shipping-my-first-dev-tool-26j8</link>
      <guid>https://dev.to/exitcodezer0/why-i-built-a-no-fluff-html-pdf-api-and-what-i-learned-shipping-my-first-dev-tool-26j8</guid>
      <description>&lt;p&gt;i've been lurking in dev spaces for a while, but only recently started actually shipping.&lt;/p&gt;

&lt;p&gt;earlier this week, i quietly launched my first microtool: &lt;a href="https://fileslap.com" rel="noopener noreferrer"&gt;fileslap.com&lt;/a&gt; — a simple HTML to PDF API with no signup, no SDKs, and no bloat.&lt;/p&gt;

&lt;p&gt;this post isn’t a pitch — just wanted to reflect on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;why i built it&lt;/li&gt;
&lt;li&gt;what i learned&lt;/li&gt;
&lt;li&gt;what i’d do differently next time&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  the problem
&lt;/h2&gt;

&lt;p&gt;i was building an internal dashboard and needed to export some styled reports to PDF.&lt;/p&gt;

&lt;p&gt;i tried:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;wkhtmltopdf (painful layout quirks)&lt;/li&gt;
&lt;li&gt;Puppeteer (too heavy for the job)&lt;/li&gt;
&lt;li&gt;3+ commercial APIs (signup walls, rate limits, weird formatting)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;all i wanted was to &lt;code&gt;curl&lt;/code&gt; a URL and get a clean PDF.&lt;/p&gt;




&lt;h2&gt;
  
  
  what i built
&lt;/h2&gt;

&lt;p&gt;so i wrote my own: a simple REST API that converts HTML → PDF using headless Chrome.&lt;/p&gt;

&lt;p&gt;it’s:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;zero-auth&lt;/li&gt;
&lt;li&gt;fast enough for realtime jobs&lt;/li&gt;
&lt;li&gt;dev-friendly by default (curlable + webhook-ready)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;free tier's live at &lt;a href="https://fileslap.com" rel="noopener noreferrer"&gt;fileslap.com&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  what i learned
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;launching is uncomfortable&lt;/strong&gt; — especially when you’re just getting started&lt;/li&gt;
&lt;li&gt;finishing touches take 3x longer than you think&lt;/li&gt;
&lt;li&gt;building something small forces sharp thinking&lt;/li&gt;
&lt;li&gt;you can &lt;em&gt;still&lt;/em&gt; over-engineer something that’s only ~100 lines of logic&lt;/li&gt;
&lt;li&gt;feedback &amp;gt; features&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  what’s next?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;i’m still figuring that out.&lt;/li&gt;
&lt;li&gt;i’ll probably keep shipping small tools like this — tools i wish existed, tools i’ll use myself, tools that stay out of your way.&lt;/li&gt;
&lt;li&gt;if you’ve worked on something similar or just want to jam on dev tooling, hit me up. i’m mostly quiet, occasionally useful.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;— ExitCodeZer0&lt;/p&gt;

</description>
      <category>devtools</category>
      <category>webdev</category>
      <category>indiehackers</category>
      <category>api</category>
    </item>
  </channel>
</rss>
