<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>SnapForge</title>
  <link>https://snapforge.xyz/</link>
  <atom:link href="https://snapforge.xyz/feed.xml" rel="self" type="application/rss+xml"/>
  <description>Screenshot annotation CLI</description>
  <language>en-us</language>
  <lastBuildDate>Tue, 19 May 2026 04:00:00 -0000</lastBuildDate>
  <item>
    <title>Batch Screenshot Optimisation: Numbers</title>
    <link>https://snapforge.xyz/blog/png-to-webp-pipeline.html</link>
    <guid>https://snapforge.xyz/blog/png-to-webp-pipeline.html</guid>
    <pubDate>Sun, 19 Apr 2026 04:00:00 -0000</pubDate>
    <description>Screenshots for documentation pages load slowly because nobody optimises them. A typical macOS Retina screenshot of a browser window comes in at 800 KB to 3 MB as PNG. The same image as WebP at qualit...</description>
  </item>
  <item>
    <title>Why I Stopped Using Screenshot GUIs</title>
    <link>https://snapforge.xyz/blog/why-cli-screenshots.html</link>
    <guid>https://snapforge.xyz/blog/why-cli-screenshots.html</guid>
    <pubDate>Thu, 14 Aug 2025 04:00:00 -0000</pubDate>
    <description>Every documentation workflow I've seen relies on at least three separate applications: a screenshot tool, an image editor for annotations, and an optimiser for web delivery. Switching between them bre...</description>
  </item>
</channel>
</rss>