<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Images on BareProxy.com</title>
    <link>https://bareproxy.com/tags/images/</link>
    <description>Recent content in Images on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/images/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy Image Optimizer Plugin: Resizing and WebP and AVIF Conversion on the Fly</title>
      <link>https://bareproxy.com/bareproxy-image-optimizer-plugin-resizing-and-webp-and-avif-conversion-on-the-fly/</link>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-image-optimizer-plugin-resizing-and-webp-and-avif-conversion-on-the-fly/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Status: planned, number 20 of 21 in BareProxy&amp;rsquo;s build order.&lt;/strong&gt; The plugins are built easiest first, and this one is about a week of coding: the plugin plus an image encoder running beside BareProxy. It comes after the AI crawler payment gate plugin. This post describes what it will do, and it will be updated as it is built.&lt;/p&gt;&#xA;&lt;p&gt;Images are most of the bytes on most pages. A site&amp;rsquo;s folder usually holds one large JPEG or PNG per picture, and every visitor downloads it whole, whether the screen is a phone or a 4K monitor. Modern browsers can take WebP and AVIF, which are often a third to half the size for the same picture. Few sites make those copies, because it means a build step, a toolchain and twice the files.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
