<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>image processing on Publishing House</title>
    <link>https://publishinghouse.org/tags/image-processing/</link>
    <description>Recent content in image processing on Publishing House</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://publishinghouse.org/tags/image-processing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hugo Image Processing: Resizing, Optimizing, and Serving Images</title>
      <link>https://publishinghouse.org/hugo-image-processing-resizing-optimizing-and-serving-images/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/hugo-image-processing-resizing-optimizing-and-serving-images/</guid>
      <description>Hugo has a built-in image processing pipeline that handles resizing, format conversion, and optimization at build time — no external service, no plugin, no JavaScript-based lazy loading required. For publishing sites where images are a significant part of content, understanding Hugo&amp;rsquo;s image processing is worth the investment. The result is faster pages with properly sized images served in modern formats, generated automatically from source files.
Page Resources vs Global Resources Hugo works with images in two contexts:</description>
    </item>
    
  </channel>
</rss>
