﻿<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <atom:link href="https://www.hibit.dev/rss/posts/276" rel="self" type="application/rss+xml" />
        <title><![CDATA[On-the-fly image resizing with Nginx]]></title>
        <description><![CDATA[<p>If you've ever managed a web server that serves images to thousands of users, you've probably run into the problem of serving the right image size to the right context. A 1200x800 hero image looks great on a desktop, but it's pure waste on a mobile screen or a thumbnail grid. The traditional answer to this has been generating multiple image variants at upload time, but that approach gets messy fast. A cleaner and more flexible solution is to resize images directly at the server level, on demand, using nothing more than nginx and its built-in image filter module. This guide walks you through setting that up from scratch, including caching so your server isn't processing the same image twice.</p>]]></description>
        <link><![CDATA[https://www.hibit.dev/posts/276/on-the-fly-image-resizing-with-nginx]]></link>
        <pubDate>Mon, 09 Mar 2026 09:30:03 +0000</pubDate>
        <language>en</language>
        <category>systems</category>

        <image>
            <title>on-the-fly-image-resizing-with-nginx</title>
            <link><![CDATA[https://www.hibit.dev/posts/276/on-the-fly-image-resizing-with-nginx]]></link>
            <url><![CDATA[https://www.hibit.dev/images/posts/2026/03/1/headers/2540_nginx_image_resize.png]]></url>
            <width>200></width>
            <height>200></height>
        </image>
    </channel>
</rss>
