<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Html-to-Pdf on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/html-to-pdf/</link>
    <description>Recent content in Html-to-Pdf on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 25 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/html-to-pdf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted PDF Document Generation: WeasyPrint vs wkhtmltopdf vs Typst vs Paged.js (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-06-25-self-hosted-pdf-document-generation-weasyprint-wkhtmltopdf-typst-pagedjs/</link>
      <pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-25-self-hosted-pdf-document-generation-weasyprint-wkhtmltopdf-typst-pagedjs/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every business application eventually needs to produce a PDF — invoices, contracts, reports, certificates, compliance documents, eBooks, and receipts. The conventional approach is to pay a cloud API service per document, but for organizations generating thousands of PDFs monthly, the costs add up quickly while sensitive document data crosses third-party servers. Self-hosting your PDF generation stack eliminates per-document costs, keeps data on-premises, and gives you full control over rendering quality.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
