<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/css" href="https://techfuelhq.com/feed.css"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>TechFuel HQ</title><link>https://techfuelhq.com/</link><description>Recent content on TechFuel HQ</description><generator>Hugo</generator><language>en-us</language><managingEditor>contact@techfuelhq.com (LK Wood IV)</managingEditor><lastBuildDate>Wed, 18 Nov 2026 05:18:02 +0000</lastBuildDate><atom:link href="https://techfuelhq.com/index.xml" rel="self" type="application/rss+xml"/><atom:link href="https://pubsubhubbub.appspot.com/" rel="hub"/><item><title>GPU Price Index: Dated Street Price vs MSRP at Newegg</title><link>https://techfuelhq.com/data/gpu-price-index/</link><pubDate>Mon, 14 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/data/gpu-price-index/</guid><atom:updated>2026-11-18T05:18:02Z</atom:updated><description>&lt;h2 id="the-short-version">The short version&lt;/h2>
&lt;p>Graphics card prices spent the whole RTX 50 and RX 9000 generation above
MSRP, and most of the numbers that circulate are undated screenshots. This
page is a dated, checkable record: the cheapest qualifying listing price for
eight current cards &lt;strong>at Newegg&lt;/strong>, each scored against its launch MSRP, with
the listing it came from, the acceptance rules, the rejection reasons and the
raw data published beside the numbers. Since November 17, 2026 the prices come
from Newegg&amp;rsquo;s affiliate catalogue, which does not say who sells a listing. The
method section says exactly what that changes.&lt;/p>
&lt;p>The index row, the median premium across cards, is written only on a day when
at least six of the eight cards have a qualifying listing. Each capture says
whether that gate was open.&lt;/p>
&lt;p>&lt;a href="https://techfuelhq.com/tools/keep-it-or-upgrade/">Keep It or Upgrade&lt;/a> uses the latest capture below to price an upgrade against the card you own. &lt;a href="https://techfuelhq.com/data/deal-or-mirage/">Deal or Mirage&lt;/a> puts these cards in one table with the tracked DDR5 kits and SSDs, and the &lt;a href="https://techfuelhq.com/data/ddr5-clock/">DDR5 Clock&lt;/a> reduces the RAM tracker to one dated number.&lt;/p>
&lt;h2 id="compare-the-dated-offers">Compare the dated offers&lt;/h2>
&lt;p>The cheapest card and the smallest premium over launch price can be different cards. The first is a dollar comparison; the second compares each card with its own launch MSRP or SEP. A board partner, memory size or factory-overclock variant can change even under the same chip name. Open the listing titles before comparing two offers.&lt;/p>
&lt;style>.price-capture-compare { margin: 1.25rem 0 2rem; min-width: 0; }
.price-capture-compare > p:first-child { border-inline-start: 3px solid var(--accent); padding-inline-start: .8rem; }
.price-capture-compare .table-wrap { max-width: 100%; overflow-x: auto; }
.price-capture-compare table { width: 100%; font-variant-numeric: tabular-nums; }
.price-capture-compare caption { text-align: left; color: var(--heading); font-weight: 650; }
.price-capture-compare th[scope=row] { min-width: 12rem; text-align: left; }
.price-capture-compare [data-price] { white-space: nowrap; }
.price-part-mismatch { display: block; font-size: .83rem; font-weight: 500; line-height: 1.45; margin: 0 0 .5rem; white-space: normal; }
.price-field-label { display: none; }
.price-capture-compare summary { cursor: pointer; color: var(--accent); min-height: 2.75rem; padding-block: .55rem; }
.price-capture-compare small { display: block; font-weight: normal; line-height: 1.5; overflow-wrap: anywhere; }
.price-capture-compare :is(summary, [tabindex]) { --focus-offset: var(--focus-offset-region); }
.price-capture-evidence { border-block: 1px solid var(--border-strong); padding: .35rem 0; }
.price-capture-evidence > summary { font-weight: 650; }
.price-capture-evidence code { overflow-wrap: anywhere; white-space: normal; }
@media (max-width: 640px) {
.price-capture-compare .price-offers-table { display: block; width: 100%; min-width: 0; }
.price-offers-table caption { display: block; padding: .6rem .75rem; white-space: normal; }
.price-offers-table thead { position: absolute; width: 1px; height: 1px; overflow: hidden; clip-path: inset(50%); }
.price-offers-table tbody { display: block; }
.price-offers-table tbody tr { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); border-top: 1px solid var(--border-strong); }
.price-offers-table tbody tr:has([data-pair]) { grid-template-columns: repeat(3, minmax(0, 1fr)); }
.price-capture-compare .price-offers-table th[scope=row] { grid-column: 1 / -1; display: block; min-width: 0; padding: .2rem .75rem 0; white-space: normal; }
.price-offers-table td { display: block; padding: .25rem .65rem .65rem; border: none; white-space: normal; }
.price-offers-table .price-field-label { display: block; font-size: .75rem; font-weight: 600; color: var(--text-muted); }
}
&lt;/style>&lt;div class="price-capture-compare" data-price-reader="gpu">&lt;p id="price-reader-gpu-0-note">&lt;strong>November 18, 2026:&lt;/strong> 7 offers in the archived file. Open a model name to read the retailer’s listing title. These are dated observations; check stock and price before buying.&lt;/p>&lt;p data-pair-rule="matched">The previous column shows November 17 only when the model, seller and full listing title match on both dates. “No exact pair” means the listing was absent, changed or appeared more than once; it says nothing about stock.&lt;/p>&lt;div class="table-wrap" tabindex="0" role="region" aria-labelledby="price-reader-gpu-0-caption">
&lt;table class="price-offers-table" role="table" aria-describedby="price-reader-gpu-0-note">&lt;caption id="price-reader-gpu-0-caption">GPU offers, lowest recorded price first · 2026-11-18 UTC&lt;/caption>
&lt;thead role="rowgroup">&lt;tr role="row">&lt;th scope="col" role="columnheader">Model and seller&lt;/th>&lt;th scope="col" role="columnheader">Price (USD)&lt;/th>&lt;th scope="col" role="columnheader">Vs. launch price&lt;/th>&lt;th scope="col" role="columnheader">Previous (2026-11-17)&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody role="rowgroup">&lt;tr role="row" data-product="radeon-rx-9060-xt-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>AMD Radeon RX 9060 XT 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>Yeston Sakura Radeon RX 9060 XT Graphics Card RX9060XT&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$729.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:100%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;109.2%&lt;/span>&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Previous&lt;/span>&lt;span data-pair>$729.99&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="geforce-rtx-5060-ti-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>NVIDIA GeForce RTX 5060 Ti 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>PNY DUAL FAN OC GeForce RTX 5060 Ti 16GB 128-Bit GDDR7 PCI Express 5.0 x8 DLSS 4.0 Graphics Card RTX 5060 Ti 16GB DUAL FAN OC VCG5060T16DFXPB1-O&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$799.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:86%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;86.5%&lt;/span>&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Previous&lt;/span>&lt;span data-pair>$799.99&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="geforce-rtx-5070-12gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>NVIDIA GeForce RTX 5070 12GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>MSI Ventus GeForce RTX 5070 Graphics Card RTX 5070 12G VENTUS 3X OC&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$919.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:68%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;67.6%&lt;/span>&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Previous&lt;/span>&lt;span data-pair>$919.99&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="radeon-rx-9070-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>AMD Radeon RX 9070 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>GIGABYTE Gaming Radeon RX 9070 Graphics Card GV-R9070GAMING OC-16GD&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$934.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:70%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;70.3%&lt;/span>&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Previous&lt;/span>&lt;span data-pair>$934.99&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="radeon-rx-9070-xt-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>AMD Radeon RX 9070 XT 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>ASRock Steel Legend Radeon RX 9070 XT Graphics Card RX9070XT SL 16G&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$999.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:67%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;66.9%&lt;/span>&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Previous&lt;/span>&lt;span data-pair>$999.99&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="geforce-rtx-5070-ti-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>NVIDIA GeForce RTX 5070 Ti 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>MSI SHADOW GeForce RTX 5070 Ti Graphics Card RTX 5070 TI 16G SHADOW 3X OC&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$1409.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:88%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;88.2%&lt;/span>&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Previous&lt;/span>&lt;span data-pair>$1409.99&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="geforce-rtx-5080-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>NVIDIA GeForce RTX 5080 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>ASUS PRIME GeForce RTX 5080 Video Card PRIME-RTX5080-O16G-EVO&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$1999.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:100%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;100.2%&lt;/span>&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Previous&lt;/span>&lt;span data-pair>No exact pair&lt;/span>&lt;/td>&lt;/tr>&lt;/tbody>&lt;/table>
&lt;/div>&lt;details class="price-capture-evidence">&lt;summary>See coverage, gaps and source files&lt;/summary>
&lt;p>&lt;a href="https://techfuelhq.com/data/gpu-price-observations.csv" download>Download all 129 offer rows (CSV)&lt;/a>. They span 16 distinct UTC dates, from 2026-09-14 through 2026-11-18. A missing date means there is no published offer row for that date. The recorded method on 2026-11-18 was &lt;code>gpu-street-price-newegg-affiliate-feed-v1&lt;/code>.&lt;/p>&lt;p>&lt;a href="https://techfuelhq.com/data/gpu-price-index.csv" download>Download the 16 recorded index rows (CSV)&lt;/a>. Each median uses the models that qualified on that date. Different membership or a new method can move a median even when no individual listing changed price.&lt;/p>&lt;div class="table-wrap" tabindex="0" role="region" aria-labelledby="price-reader-gpu-0-series">&lt;table>&lt;caption id="price-reader-gpu-0-series">Published index rows, with their original methods&lt;/caption>&lt;thead>&lt;tr>&lt;th scope="col">UTC date&lt;/th>&lt;th scope="col">Models qualified / queried&lt;/th>&lt;th scope="col">Median premium vs. launch&lt;/th>&lt;th scope="col">Recorded method&lt;/th>&lt;/tr>&lt;/thead>&lt;tbody>&lt;tr>&lt;th scope="row">2026-09-14&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-discovery-v1&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-26&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-28&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-29&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-30&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-01&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-02&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-03&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-05&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-06&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-07&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-08&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;51.9%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-10&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-11&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-11-17&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;86.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-affiliate-feed-v1&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-11-18&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;86.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-affiliate-feed-v1&lt;/code>&lt;/td>&lt;/tr>
&lt;/tbody>&lt;/table>&lt;/div>
&lt;/details>&lt;/div>
&lt;h2 id="latest-capture">Latest capture&lt;/h2>
&lt;p>&lt;strong>Collection status:&lt;/strong> Captures from November 17, 2026 read that day&amp;rsquo;s Newegg affiliate catalogue file. Captures from September 26 through October 11, 2026 read Newegg&amp;rsquo;s product pages. No capture ran between those two periods, and the method differs across the gap. The block below names the latest capture; check Newegg for current price and stock.&lt;/p>
&lt;!-- auto:capture -->
&lt;p>&lt;strong>Latest capture, November 18, 2026 (UTC), method &lt;code>gpu-street-price-newegg-affiliate-feed-v1&lt;/code>:&lt;/strong> Newegg&amp;rsquo;s affiliate catalogue file for that date had 82 listings naming a tracked model; 56 passed every rule, and 7 of 8 tracked cards have a price. The index metric activates at 6, so the gate is open and an index row was written for this date. Every row carries &lt;code>verification_status: retailer_feed&lt;/code>: the price, title, part number and in-stock flag are the catalogue&amp;rsquo;s own. The catalogue names no seller and no condition, and nothing was checked against the product page.&lt;/p>
&lt;p>Cheapest qualifying listing: &lt;strong>$729.99&lt;/strong> (AMD Radeon RX 9060 XT 16GB, +109.2% vs MSRP).&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Line&lt;/th>
&lt;th scope="col" style="text-align: right">Cheapest qualifying listing&lt;/th>
&lt;th scope="col" style="text-align: right">vs MSRP&lt;/th>
&lt;th scope="col">Newegg item number&lt;/th>
&lt;th scope="col">Listing title&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Line">AMD Radeon RX 9060 XT 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$729.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+109.2%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814980004&lt;/td>
&lt;td data-label="Listing title">Yeston Sakura Radeon RX 9060 XT Graphics Card RX9060XT&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">NVIDIA GeForce RTX 5060 Ti 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$799.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+86.5%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814133993&lt;/td>
&lt;td data-label="Listing title">PNY DUAL FAN OC GeForce RTX 5060 Ti 16GB 128-Bit GDDR7 PCI Express 5.0 x8 DLSS 4.0 Graphics Card RTX 5060 Ti 16GB DUAL FAN OC VCG5060T16DFXPB1-O&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">NVIDIA GeForce RTX 5070 12GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$919.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+67.6%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814137940&lt;/td>
&lt;td data-label="Listing title">MSI Ventus GeForce RTX 5070 Graphics Card RTX 5070 12G VENTUS 3X OC&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">AMD Radeon RX 9070 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$934.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+70.3%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814932752&lt;/td>
&lt;td data-label="Listing title">GIGABYTE Gaming Radeon RX 9070 Graphics Card GV-R9070GAMING OC-16GD&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">AMD Radeon RX 9070 XT 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$999.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+66.9%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814930136&lt;/td>
&lt;td data-label="Listing title">ASRock Steel Legend Radeon RX 9070 XT Graphics Card RX9070XT SL 16G&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">NVIDIA GeForce RTX 5070 Ti 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$1,409.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+88.2%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814137935&lt;/td>
&lt;td data-label="Listing title">MSI SHADOW GeForce RTX 5070 Ti Graphics Card RTX 5070 TI 16G SHADOW 3X OC&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">NVIDIA GeForce RTX 5080 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$1,999.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+100.2%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814126840&lt;/td>
&lt;td data-label="Listing title">ASUS PRIME GeForce RTX 5080 Video Card PRIME-RTX5080-O16G-EVO&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">NVIDIA GeForce RTX 5090 32GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">none: its listings are priced outside the accepted band&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">-&lt;/td>
&lt;td data-label="Newegg item number">-&lt;/td>
&lt;td data-label="Listing title">Not counted. Cheapest of its listings that are priced outside the accepted band: $6,549.99 plus $24.99 shipping, N82E16814932761, GIGABYTE Gaming GeForce RTX 5090 Graphics Card GV-N5090GAMING OC-32GD&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>This block is rewritten with every capture; the dated commentary below it is not.&lt;/p>
&lt;!-- /auto:capture -->
&lt;h2 id="the-listing-behind-each-price">The listing behind each price&lt;/h2>
&lt;p>Each card&amp;rsquo;s price is one listing: the cheapest one that met the matching rules
in the Method section below, from one maker. A cheaper listing of the same chip
can exist and be left out, as the RTX 5080 note under Method shows, so this is
not the lowest price for the chip at Newegg.&lt;/p>
&lt;p class="price-listings__cap" id="price-listings-gpu">The listing behind each latest price, November 18, 2026 (UTC). Newegg opens that listing; check the price and stock there before you buy.&lt;/p>
&lt;p class="price-listings__disclosure">I may earn a commission if you buy through the affiliate links in the Retailers column. As an Amazon Associate I earn from qualifying purchases.&lt;/p>
&lt;div class="table-wrap table-wrap--stack price-listings" data-v3-tt>
&lt;table aria-labelledby="price-listings-gpu">
&lt;thead>
&lt;tr>&lt;th scope="col">Card&lt;/th>&lt;th scope="col">Latest price&lt;/th>&lt;th scope="col">Listing it came from&lt;/th>&lt;th scope="col">Retailers&lt;/th>&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr id="listing-geforce-rtx-5090-32gb">
&lt;th scope="row">NVIDIA GeForce RTX 5090 32GB&lt;/th>
&lt;td data-label="Latest price">No qualifying listing&lt;/td>
&lt;td data-label="Listing it came from">The capture record says: its listings are priced outside the accepted band.&lt;/td>
&lt;td data-label="Retailers">&lt;span aria-hidden="true">–&lt;/span>&lt;span class="sr-only">No listing to link for NVIDIA GeForce RTX 5090 32GB in this capture&lt;/span>&lt;/td>
&lt;/tr>
&lt;tr id="listing-geforce-rtx-5080-16gb">
&lt;th scope="row">NVIDIA GeForce RTX 5080 16GB&lt;/th>
&lt;td data-label="Latest price">$1,999.99&lt;br>&lt;small>+100.2% against the $999 launch price&lt;/small>&lt;/td>
&lt;td data-label="Listing it came from">ASUS PRIME GeForce RTX 5080 Video Card PRIME-RTX5080-O16G-EVO&lt;br>&lt;small>Newegg item N82E16814126840&lt;/small>&lt;/td>
&lt;td data-label="Retailers">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=NVIDIA&amp;#43;GeForce&amp;#43;RTX&amp;#43;5080&amp;#43;16GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16814126840%3FItem%3DN82E16814126840" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;tr id="listing-geforce-rtx-5070-ti-16gb">
&lt;th scope="row">NVIDIA GeForce RTX 5070 Ti 16GB&lt;/th>
&lt;td data-label="Latest price">$1,409.99&lt;br>&lt;small>+88.2% against the $749 launch price&lt;/small>&lt;/td>
&lt;td data-label="Listing it came from">MSI SHADOW GeForce RTX 5070 Ti Graphics Card RTX 5070 TI 16G SHADOW 3X OC&lt;br>&lt;small>Newegg item N82E16814137935&lt;/small>&lt;/td>
&lt;td data-label="Retailers">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=NVIDIA&amp;#43;GeForce&amp;#43;RTX&amp;#43;5070&amp;#43;Ti&amp;#43;16GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16814137935%3FItem%3DN82E16814137935" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;tr id="listing-geforce-rtx-5070-12gb">
&lt;th scope="row">NVIDIA GeForce RTX 5070 12GB&lt;/th>
&lt;td data-label="Latest price">$919.99&lt;br>&lt;small>+67.6% against the $549 launch price&lt;/small>&lt;/td>
&lt;td data-label="Listing it came from">MSI Ventus GeForce RTX 5070 Graphics Card RTX 5070 12G VENTUS 3X OC&lt;br>&lt;small>Newegg item N82E16814137940&lt;/small>&lt;/td>
&lt;td data-label="Retailers">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=NVIDIA&amp;#43;GeForce&amp;#43;RTX&amp;#43;5070&amp;#43;12GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16814137940%3FItem%3DN82E16814137940" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;tr id="listing-geforce-rtx-5060-ti-16gb">
&lt;th scope="row">NVIDIA GeForce RTX 5060 Ti 16GB&lt;/th>
&lt;td data-label="Latest price">$799.99&lt;br>&lt;small>+86.5% against the $429 launch price&lt;/small>&lt;/td>
&lt;td data-label="Listing it came from">PNY DUAL FAN OC GeForce RTX 5060 Ti 16GB 128-Bit GDDR7 PCI Express 5.0 x8 DLSS 4.0 Graphics Card RTX 5060 Ti 16GB DUAL FAN OC VCG5060T16DFXPB1-O&lt;br>&lt;small>Newegg item N82E16814133993&lt;/small>&lt;/td>
&lt;td data-label="Retailers">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=NVIDIA&amp;#43;GeForce&amp;#43;RTX&amp;#43;5060&amp;#43;Ti&amp;#43;16GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16814133993%3FItem%3DN82E16814133993" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;tr id="listing-radeon-rx-9070-xt-16gb">
&lt;th scope="row">AMD Radeon RX 9070 XT 16GB&lt;/th>
&lt;td data-label="Latest price">$999.99&lt;br>&lt;small>+66.9% against the $599 launch price&lt;/small>&lt;/td>
&lt;td data-label="Listing it came from">ASRock Steel Legend Radeon RX 9070 XT Graphics Card RX9070XT SL 16G&lt;br>&lt;small>Newegg item N82E16814930136&lt;/small>&lt;/td>
&lt;td data-label="Retailers">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=AMD&amp;#43;Radeon&amp;#43;RX&amp;#43;9070&amp;#43;XT&amp;#43;16GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16814930136%3FItem%3DN82E16814930136" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;tr id="listing-radeon-rx-9070-16gb">
&lt;th scope="row">AMD Radeon RX 9070 16GB&lt;/th>
&lt;td data-label="Latest price">$934.99&lt;br>&lt;small>+70.3% against the $549 launch price&lt;/small>&lt;/td>
&lt;td data-label="Listing it came from">GIGABYTE Gaming Radeon RX 9070 Graphics Card GV-R9070GAMING OC-16GD&lt;br>&lt;small>Newegg item N82E16814932752&lt;/small>&lt;/td>
&lt;td data-label="Retailers">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=AMD&amp;#43;Radeon&amp;#43;RX&amp;#43;9070&amp;#43;16GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16814932752%3FItem%3DN82E16814932752" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;tr id="listing-radeon-rx-9060-xt-16gb">
&lt;th scope="row">AMD Radeon RX 9060 XT 16GB&lt;/th>
&lt;td data-label="Latest price">$729.99&lt;br>&lt;small>+109.2% against the $349 launch price&lt;/small>&lt;/td>
&lt;td data-label="Listing it came from">Yeston Sakura Radeon RX 9060 XT Graphics Card RX9060XT&lt;br>&lt;small>Newegg item N82E16814980004&lt;/small>&lt;/td>
&lt;td data-label="Retailers">&lt;span class="buy-actions buy-actions--cell google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=AMD&amp;#43;Radeon&amp;#43;RX&amp;#43;9060&amp;#43;XT&amp;#43;16GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16814980004%3FItem%3DN82E16814980004" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/data/gpu-price-index/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>
&lt;/a>
&lt;/span>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="recent-qualifying-observations">Recent qualifying observations&lt;/h2>
&lt;p>The file below accumulates one row per qualifying offer for each capture
date. The table shows the two latest capture dates so current rows are easy
to find; the complete history is in the CSV linked under it. Both views use
the same raw file at build time.&lt;/p>
&lt;div class="table-wrap csv-table">
&lt;table aria-describedby="csv-table-note-2">
&lt;caption>Recent observations from the latest 2 capture dates, oldest to newest&lt;/caption>
&lt;thead>
&lt;tr>&lt;th scope="col">Capture Date UTC&lt;/th>&lt;th scope="col">Product Label&lt;/th>&lt;th scope="col">Vram GB&lt;/th>&lt;th scope="col">Msrp USD&lt;/th>&lt;th scope="col">Title&lt;/th>&lt;th scope="col">Seller&lt;/th>&lt;th scope="col">Price USD&lt;/th>&lt;th scope="col">Premium Pct&lt;/th>&lt;th scope="col">Verification Status&lt;/th>&lt;/tr>
&lt;/thead>
&lt;tbody>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>NVIDIA GeForce RTX 5080 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>999.0&lt;/td>&lt;td>ZOTAC GeForce RTX 5080 Video Card GAMING GeForce RTX 5080 SOLID CORE OC&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>2199.99&lt;/td>&lt;td>120.2&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>NVIDIA GeForce RTX 5070 Ti 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>749.0&lt;/td>&lt;td>MSI SHADOW GeForce RTX 5070 Ti Graphics Card RTX 5070 TI 16G SHADOW 3X OC&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>1409.99&lt;/td>&lt;td>88.2&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>NVIDIA GeForce RTX 5070 12GB&lt;/td>&lt;td>12&lt;/td>&lt;td>549.0&lt;/td>&lt;td>MSI Ventus GeForce RTX 5070 Graphics Card RTX 5070 12G VENTUS 3X OC&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>919.99&lt;/td>&lt;td>67.6&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>NVIDIA GeForce RTX 5060 Ti 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>429.0&lt;/td>&lt;td>PNY DUAL FAN OC GeForce RTX 5060 Ti 16GB 128-Bit GDDR7 PCI Express 5.0 x8 DLSS 4.0 Graphics Card RTX 5060 Ti 16GB DUAL FAN OC VCG5060T16DFXPB1-O&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>799.99&lt;/td>&lt;td>86.5&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>AMD Radeon RX 9070 XT 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>599.0&lt;/td>&lt;td>ASRock Steel Legend Radeon RX 9070 XT Graphics Card RX9070XT SL 16G&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>999.99&lt;/td>&lt;td>66.9&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>AMD Radeon RX 9070 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>549.0&lt;/td>&lt;td>GIGABYTE Gaming Radeon RX 9070 Graphics Card GV-R9070GAMING OC-16GD&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>934.99&lt;/td>&lt;td>70.3&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>AMD Radeon RX 9060 XT 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>349.0&lt;/td>&lt;td>Yeston Sakura Radeon RX 9060 XT Graphics Card RX9060XT&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>729.99&lt;/td>&lt;td>109.2&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-18&lt;/td>&lt;td>NVIDIA GeForce RTX 5080 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>999.0&lt;/td>&lt;td>ASUS PRIME GeForce RTX 5080 Video Card PRIME-RTX5080-O16G-EVO&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>1999.99&lt;/td>&lt;td>100.2&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-18&lt;/td>&lt;td>NVIDIA GeForce RTX 5070 Ti 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>749.0&lt;/td>&lt;td>MSI SHADOW GeForce RTX 5070 Ti Graphics Card RTX 5070 TI 16G SHADOW 3X OC&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>1409.99&lt;/td>&lt;td>88.2&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-18&lt;/td>&lt;td>NVIDIA GeForce RTX 5070 12GB&lt;/td>&lt;td>12&lt;/td>&lt;td>549.0&lt;/td>&lt;td>MSI Ventus GeForce RTX 5070 Graphics Card RTX 5070 12G VENTUS 3X OC&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>919.99&lt;/td>&lt;td>67.6&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-18&lt;/td>&lt;td>NVIDIA GeForce RTX 5060 Ti 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>429.0&lt;/td>&lt;td>PNY DUAL FAN OC GeForce RTX 5060 Ti 16GB 128-Bit GDDR7 PCI Express 5.0 x8 DLSS 4.0 Graphics Card RTX 5060 Ti 16GB DUAL FAN OC VCG5060T16DFXPB1-O&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>799.99&lt;/td>&lt;td>86.5&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-18&lt;/td>&lt;td>AMD Radeon RX 9070 XT 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>599.0&lt;/td>&lt;td>ASRock Steel Legend Radeon RX 9070 XT Graphics Card RX9070XT SL 16G&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>999.99&lt;/td>&lt;td>66.9&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-18&lt;/td>&lt;td>AMD Radeon RX 9070 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>549.0&lt;/td>&lt;td>GIGABYTE Gaming Radeon RX 9070 Graphics Card GV-R9070GAMING OC-16GD&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>934.99&lt;/td>&lt;td>70.3&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-18&lt;/td>&lt;td>AMD Radeon RX 9060 XT 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>349.0&lt;/td>&lt;td>Yeston Sakura Radeon RX 9060 XT Graphics Card RX9060XT&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>729.99&lt;/td>&lt;td>109.2&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p class="csv-table__note" id="csv-table-note-2">Showing 14 of 129 observations from the latest 2 capture dates. &lt;a href="https://techfuelhq.com/data/gpu-price-observations.csv" download>Download the complete CSV history&lt;/a>. The table is rendered from that file at build time.&lt;/p>
&lt;h2 id="method-exactly">Method, exactly&lt;/h2>
&lt;p>Rows dated from November 17, 2026 come from Newegg&amp;rsquo;s affiliate product
catalogue, the daily file Newegg publishes to its affiliates through Rakuten
Advertising. I read that day&amp;rsquo;s file and, for each tracked card, keep the
cheapest listing that passes every rule:&lt;/p>
&lt;ul>
&lt;li>it sits in the catalogue&amp;rsquo;s graphics-card category;&lt;/li>
&lt;li>its title, brand and manufacturer part number match exactly one tracked
card. A card sold in more than one memory size (the RTX 5060 Ti and the
RX 9060 XT) must also state the tracked size, and a listing that names any
other size is left out;&lt;/li>
&lt;li>the catalogue marks it in stock;&lt;/li>
&lt;li>the title names no used, refurbished, recertified, renewed or open-box
condition, and no bundle, combo or multi-pack;&lt;/li>
&lt;li>it carries one of Newegg&amp;rsquo;s own item numbers, the form &lt;code>N82E168&lt;/code> plus eight
digits;&lt;/li>
&lt;li>the price sits between 0.5x and 3.0x the card&amp;rsquo;s MSRP.&lt;/li>
&lt;/ul>
&lt;p>The price is the catalogue&amp;rsquo;s sale price when the listing has one and its
regular price otherwise. No product page is opened.&lt;/p>
&lt;p>The catalogue gives a title, an item number, a part number, a brand, prices,
a shipping amount and one availability word. It names no seller and no
condition. So these rows are not labeled sold by Newegg, and their condition
rests on the title alone. The item-number rule is the nearest thing to a
seller check. Listings numbered &lt;code>9SI&lt;/code> point at the same product page with a
different item, their own price and often a shipping charge, and I leave them
out. I tested that rule on the catalogue file from September 29: the listings
it accepts matched, to the cent, every price my page captures recorded that
day as sold by Newegg, 24 of 24 across the GPU, SSD and RAM trackers. Shipping
is recorded with the capture and not added to the price. New rows carry
&lt;code>verification_status: retailer_feed&lt;/code> and hold one row per card.&lt;/p>
&lt;p>Until November 18, 2026 the rule required every title or part number to state the
card&amp;rsquo;s memory size. That left out cheaper listings of cards sold in one size:
in the November 17 capture three in-stock RTX 5080 listings with Newegg&amp;rsquo;s own
item numbers, priced from $2,199.99 to $2,299.99, did not spell out 16GB, so
the row first read $2,499.99. I re-read the same November 17 catalogue file
under the corrected rule and restated that day&amp;rsquo;s rows: RTX 5080 $2,199.99
(was $2,499.99), RX 9070 $934.99 (was $1,019.99) and RX 9060 XT 16GB $729.99
(was $789.99). The RX 9060 XT row is a Yeston card whose title names no size;
its part number, YT RX-96XT-16D6-SOA-11PCI, states 16GB. The other four
priced cards did not change. The same day all
twelve RTX 5090 listings sat above the 3.0x ceiling of $5,997; the cheapest
was $6,249.99, and the table above shows it as not counted.&lt;/p>
&lt;p>The collection method has changed twice. Rows keep the method they were
recorded under, and a price change across a method change is not
automatically a like-for-like move: the cheapest qualifying listing for a card
can be a different board on each side.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Capture dates&lt;/th>
&lt;th scope="col">Source&lt;/th>
&lt;th scope="col">How a listing qualified on seller&lt;/th>
&lt;th scope="col">Status&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Capture dates">From November 17, 2026&lt;/td>
&lt;td data-label="Source">Newegg&amp;rsquo;s affiliate catalogue file (method &lt;code>gpu-street-price-newegg-affiliate-feed-v1&lt;/code>)&lt;/td>
&lt;td data-label="How a listing qualified on seller">One of Newegg&amp;rsquo;s own item numbers; the file names no seller&lt;/td>
&lt;td data-label="Status">Current&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Capture dates">September 26 to October 11, 2026&lt;/td>
&lt;td data-label="Source">Newegg product pages, each selected item confirmed on its pinned page&lt;/td>
&lt;td data-label="How a listing qualified on seller">Sold by Newegg, read from the page; marketplace items rejected&lt;/td>
&lt;td data-label="Status">Retired after Newegg&amp;rsquo;s storefront refused the requests&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Capture dates">Before September 26, 2026&lt;/td>
&lt;td data-label="Source">Google Shopping (US, English) through DataForSEO&amp;rsquo;s merchant API, one exact-model query per card&lt;/td>
&lt;td data-label="How a listing qualified on seller">A named direct-retailer list (Best Buy, Newegg, B&amp;amp;H, Micro Center, Adorama, Walmart first-party and peers)&lt;/td>
&lt;td data-label="Status">Retired&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Under every method the listing had to be the tracked model, new, a single
discrete card, and priced between 0.5x and 3.0x the card&amp;rsquo;s MSRP.&lt;/p>
&lt;p>The tracked cards: RTX 5090, 5080, 5070 Ti, 5070 and 5060 Ti 16GB, and RX
9070 XT, 9070 and 9060 XT 16GB. Their MSRPs were verified against NVIDIA and
AMD press releases on 2026-09-05; the verbatim passages are in the basket
file in the site&amp;rsquo;s repository, alongside the collector, its tests, and every
capture&amp;rsquo;s raw response.&lt;/p>
&lt;h2 id="what-this-price-index-does-not-cover">What this price index does not cover&lt;/h2>
&lt;p>This basket answers dated price and MSRP questions for eight new,
current-generation cards. It does not price used cards, older RTX 3070 or RTX
3080 stock, or today&amp;rsquo;s deals outside the recorded capture. Use the &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/">GPU
hierarchy&lt;/a> for performance ranks and Intel&amp;rsquo;s
place in the field, and the &lt;a href="https://techfuelhq.com/articles/best-gpu-plex-jellyfin-transcode-2026/">Plex and Jellyfin GPU
guide&lt;/a> for hardware-
acceleration support. Those are different questions from street price.&lt;/p>
&lt;h2 id="use-the-data-cc-by-40">Use the data (CC BY 4.0)&lt;/h2>
&lt;p>Download every observation:
&lt;a href="https://techfuelhq.com/data/gpu-price-observations.csv" download type="text/csv">gpu-price-observations.csv&lt;/a>, one row per
qualifying offer with capture date, card, MSRP, street price, premium,
seller and verification status. Rows dated from November 17, 2026 read
&lt;code>Newegg listing (seller not stated)&lt;/code> in the seller column and &lt;code>retailer_feed&lt;/code>
as their status. When at least six of eight cards qualify,
that day&amp;rsquo;s row is added to &lt;a href="https://techfuelhq.com/data/gpu-price-index.csv" download type="text/csv">gpu-price-index.csv&lt;/a>. License:
&lt;a href="https://creativecommons.org/licenses/by/4.0/" rel="noopener">Creative Commons Attribution 4.0&lt;/a>.
Attribute as &amp;ldquo;TechFuelHQ GPU Price Index&amp;rdquo; linking to this page.&lt;/p>
&lt;p>Choosing between these cards? The &lt;a href="https://techfuelhq.com/tools/gpu-comparison/">GPU comparison tool&lt;/a>
holds the specs, and the &lt;a href="https://techfuelhq.com/gpu-reviews/">GPU reviews&lt;/a> hold the measured
results, including the &lt;a href="https://techfuelhq.com/gpu-reviews/rx-9060-xt-review-2026/">RX 9060 XT 16GB review&lt;/a>
and &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rtx-5070-2026/">RTX 5060 Ti vs RTX 5070&lt;/a>. The
sibling &lt;a href="https://techfuelhq.com/data/ram-price-index/">DDR5 RAM price index&lt;/a> uses the same collector
and the same gate.&lt;/p>
&lt;h2 id="weekly-market-context">Outside reference: US prices from Pricify&lt;/h2>
&lt;section aria-labelledby="weekly-market-context" data-external-market-context="gpu">
&lt;p>For the week ending &lt;time datetime="2026-11-08">2026-11-08&lt;/time> (US Eastern), &lt;a href="https://pricify.ai/">Pricify&lt;/a> published week-end prices in US dollars. We checked one exact part number in its 98-product sample.&lt;/p>
&lt;div class="table-wrap" role="region" aria-label="Pricify historical item prices" tabindex="0">
&lt;table>
&lt;caption>Selected exact parts in the 2026-W45 release&lt;/caption>
&lt;thead>&lt;tr>&lt;th scope="col">Part / manufacturer number&lt;/th>&lt;th scope="col">Week-end item low&lt;/th>&lt;th scope="col">Venue in the source&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody>&lt;tr>
&lt;th scope="row">Reaper Radeon RX 9070 XT 16 GB&lt;br>&lt;small>RX9070XT 16G-A&lt;/small>&lt;/th>
&lt;td>$919.99&lt;/td>&lt;td>Micro Center (in store)&lt;/td>
&lt;/tr>&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>These are the publisher’s historical item prices for new products sold by the retailer. Physical stores can count, the source does not give a delivered total with shipping and tax, and a prior reading may carry forward for about three days. A missing part is not evidence that it sold out. These rows do not update TechFuelHQ’s own observations or establish a price you can buy at today.&lt;/p>
&lt;p>Selected and reformatted from &lt;a href="https://raw.githubusercontent.com/pricify-ai/pc-hardware-prices/9507089fec375be2f86d309c8ff37a6190043947/data/2026/W45/json/vga.live.json">Pricify’s original weekly JSON&lt;/a>, &lt;a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0&lt;/a>. Retrieved &lt;time datetime="2026-11-13T23:24:17Z">2026-11-13 UTC&lt;/time>.
&lt;a href="https://techfuelhq.com/data/weekly-market-context/2026-W45-9507089fec375be2f86d309c8ff37a6190043947.csv" download>Download the selected weekly rows (CSV)&lt;/a> ·
&lt;a href="https://techfuelhq.com/data/weekly-market-context/2026-W45-9507089fec375be2f86d309c8ff37a6190043947.json" download>Identifiers, source hashes and dates (JSON)&lt;/a> ·
&lt;a href="https://raw.githubusercontent.com/pricify-ai/pc-hardware-prices/9507089fec375be2f86d309c8ff37a6190043947/METHODOLOGY.md">Publisher’s method&lt;/a>.&lt;/p>
&lt;/section>
&lt;h2 id="change-log">Change log&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>0.10.0 (2026-11-17):&lt;/strong> prices now come from Newegg&amp;rsquo;s affiliate catalogue,
after a 37-day gap with no capture. The first capture priced 7 of 8 cards
and wrote an index row; the RTX 5090 had no listing inside the price band.
No earlier row was changed.&lt;/li>
&lt;li>&lt;strong>0.9.1 (2026-09-15):&lt;/strong> removed eight September 14 rows that broke the
rules on this page (five recertified cards, an external enclosure and two
bundles), fixed the two collector rules that let them in, and restated that
day&amp;rsquo;s index row from +48.1% to +53.5%.&lt;/li>
&lt;li>&lt;strong>0.9.0 (2026-09-14):&lt;/strong> first publication and first live capture.&lt;/li>
&lt;/ul></description></item><item><title>RTX 5070 Ti vs RTX 5080: Which One Should You Buy in 2026?</title><link>https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-5080-2026/</link><pubDate>Thu, 01 Oct 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-5080-2026/</guid><atom:updated>2026-11-18T05:05:34Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · RTX 5070 Ti vs RTX 5080&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Speed.&lt;/strong> In Tom's Hardware's GPU hierarchy, last updated June 24, 2026, the 5080 leads by 9.8% at 1440p raster and 12.8% at 4K raster. With ray tracing at 4K the lead is 14.7%.&lt;/li>
&lt;li>&lt;strong>Price.&lt;/strong> On November 17, 2026 Newegg listed the cheapest new in-stock RTX 5080 at $2,199.99 and the cheapest RTX 5070 Ti at $1,409.99. That is $790, or 56%, for at most 14.7% more speed.&lt;/li>
&lt;li>&lt;strong>Power.&lt;/strong> My ROG Astral RTX 5080 carries a 400 W default power limit, yet across 308 gaming samples it peaked at 325.73 W, under NVIDIA's 360 W reference. The 850 W supply and the third 8-pin cable come from the spec sheet.&lt;/li>
&lt;li>&lt;strong>Verdict.&lt;/strong> The 5070 Ti for 1440p. The 5080 for 4K ray tracing headroom, or for paid work that scales with its 20% more CUDA cores.&lt;/li>
&lt;/ul>
&lt;p>Frame rates are Tom's Hardware's from June 24, 2026, read again on November 18. Prices are Newegg's catalogue from November 17, 2026. The power log is my own card on a hand-tuned profile. I have never measured a 5070 Ti.&lt;/p>
&lt;/div>
&lt;h2 id="which-one-to-buy">Which one to buy&lt;/h2>
&lt;p>For 1440p, and for 4K without ray tracing, buy the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-ti-review-2026/">RTX 5070 Ti&lt;/a>. Its frames cost less in every row of the table below, and a 750 W supply meets NVIDIA&amp;rsquo;s requirement for it. Buy the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5080-review-2026/">RTX 5080&lt;/a> for 4K with ray tracing, or for paid work that scales with CUDA cores, and budget an 850 W supply and the third power cable with it.&lt;/p>
&lt;p>The two cards above are the cheapest new, in-stock ones under a Newegg item number in Newegg&amp;rsquo;s catalogue on November 17, 2026. Prices move daily: the &lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU price index&lt;/a> tracks both chips, and &lt;a href="https://techfuelhq.com/data/deal-or-mirage/#sku-geforce-rtx-5080-16gb">Deal or Mirage&lt;/a> gives the baseline to judge a Black Friday 5080 price against. The &lt;a href="https://techfuelhq.com/tools/gpu-comparison/?a=GeForce&amp;#43;RTX&amp;#43;5070&amp;#43;Ti&amp;amp;b=GeForce&amp;#43;RTX&amp;#43;5080&amp;amp;res=1440p">GPU comparison tool with both cards loaded&lt;/a> sets them side by side at three resolutions.&lt;/p>
&lt;h2 id="how-much-faster-is-the-5080">How much faster is the 5080?&lt;/h2>
&lt;p>Jeffrey Kampman&amp;rsquo;s &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware GPU hierarchy&lt;/a>, last updated June 24, 2026, averages 11 raster games and 8 ray-traced games at native resolution, with no upscaling or frame generation, on a Ryzen 7 9800X3D. These are its averages for the pair. The percentages are mine.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Tom&amp;rsquo;s Hardware fps averages&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5070 Ti&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5080&lt;/th>
&lt;th scope="col" style="text-align: right">5080 lead&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">1080p raster&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">155.4&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">166.9&lt;/td>
&lt;td style="text-align: right" data-label="5080 lead">+7.4%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">1440p raster&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">116.8&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">128.3&lt;/td>
&lt;td style="text-align: right" data-label="5080 lead">+9.8%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">4K raster&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">68.6&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">77.4&lt;/td>
&lt;td style="text-align: right" data-label="5080 lead">+12.8%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">1080p ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">90.4&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">98.3&lt;/td>
&lt;td style="text-align: right" data-label="5080 lead">+8.7%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">1440p ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">66.2&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">74.0&lt;/td>
&lt;td style="text-align: right" data-label="5080 lead">+11.8%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">4K ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">36.7&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">42.1&lt;/td>
&lt;td style="text-align: right" data-label="5080 lead">+14.7%&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The gap grows with resolution. Nowhere does it reach 15%.&lt;/p>
&lt;p>GamersNexus tested both cards on its own bench. Steve Burke&amp;rsquo;s &lt;a href="https://gamersnexus.net/gpus/do-not-buy-nvidia-rtx-5070-ti-gpu-absurdity-benchmarks-review" rel="noopener">RTX 5070 Ti review&lt;/a> of February 21, 2025 found the 5080 &amp;ldquo;generally 9% to 16% better&amp;rdquo; depending on the resolution and game, and 13% ahead in Resident Evil 4 at 1440p. Same shape.&lt;/p>
&lt;h2 id="what-each-frame-costs">What each frame costs&lt;/h2>
&lt;p>Divide the price by the frame rate. In Newegg&amp;rsquo;s catalogue on November 17, 2026 the cheapest new, in-stock RTX 5070 Ti was the MSI RTX 5070 Ti 16G Shadow 3X OC at &lt;span class="claim" data-claim-key="listing.N82E16814137935.price_usd" data-claim-value="1409.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$1,409.99&lt;/span>
, and the cheapest RTX 5080 was the ZOTAC Gaming RTX 5080 Solid Core OC at &lt;span class="claim" data-claim-key="listing.N82E16814500648.price_usd" data-claim-value="2199.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$2,199.99&lt;/span>
. The gap is $790.00. That is 56% on top of the Ti.&lt;/p>
&lt;p>A 56% premium against a lead that tops out at 14.7% means every 5080 frame costs more. At 1440p raster a Ti frame costs $12.07 and a 5080 frame $17.15. At 4K with ray tracing, the 5080&amp;rsquo;s best row, it is $38.42 against $52.26. Prices move daily, so if either listing has changed, divide the new price by the frame rate in the table above.&lt;/p>
&lt;h2 id="same-chip-same-memory-20-more-cores">Same chip, same memory, 20% more cores&lt;/h2>
&lt;p>The rows below come from &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5070-family/" rel="noopener">NVIDIA&amp;rsquo;s RTX 5070 family page&lt;/a> and its &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5080/" rel="noopener">RTX 5080 page&lt;/a>, read November 18, 2026. Neither lists memory speed, so that row comes from ASUS&amp;rsquo;s &lt;a href="https://www.asus.com/us/motherboards-components/graphics-cards/prime/prime-rtx5070ti-16g/techspec/" rel="noopener">Prime RTX 5070 Ti&lt;/a> and &lt;a href="https://rog.asus.com/ca-en/graphics-cards/graphics-cards/rog-astral/rog-astral-rtx5080-o16g-gaming/spec/" rel="noopener">ROG Astral RTX 5080&lt;/a> spec pages.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Specification&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5070 Ti&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5080&lt;/th>
&lt;th scope="col" style="text-align: right">Difference&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Specification">CUDA cores&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">8,960&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">10,752&lt;/td>
&lt;td style="text-align: right" data-label="Difference">+20.0%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Boost clock&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">2.45 GHz&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">2.62 GHz&lt;/td>
&lt;td style="text-align: right" data-label="Difference">+170 MHz&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Memory&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">16 GB GDDR7, 256-bit&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">16 GB GDDR7, 256-bit&lt;/td>
&lt;td style="text-align: right" data-label="Difference">none&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Memory speed (ASUS boards)&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">28 Gbps&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">30 Gbps&lt;/td>
&lt;td style="text-align: right" data-label="Difference">+7.1%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Total graphics power&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">300 W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">360 W&lt;/td>
&lt;td style="text-align: right" data-label="Difference">+60 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Required system power&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">750 W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">850 W&lt;/td>
&lt;td style="text-align: right" data-label="Difference">+100 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Power cables&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">2x 8-pin, or one 300 W Gen 5 cable&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">3x 8-pin, or one 450 W Gen 5 cable&lt;/td>
&lt;td style="text-align: right" data-label="Difference">one more cable&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Both cards use NVIDIA&amp;rsquo;s GB203 chip, as my &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-vs-5070-ti-2026/">5070 vs 5070 Ti page&lt;/a> and my &lt;a href="https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/">Astral dataset&lt;/a> record, with 8,960 of its cores enabled on the 5070 Ti and 10,752 on the 5080. What the 5080 adds is compute, 20% more cores at a slightly higher boost clock, plus 7.1% more memory bandwidth from faster GDDR7 on the same 256-bit bus. Capacity does not change. A game or model that fits in 16 GB on one card fits on the other.&lt;/p>
&lt;h2 id="the-power-limit-is-not-the-power-draw">The power limit is not the power draw&lt;/h2>
&lt;p>NVIDIA rates the 5080 at 360 W and the 5070 Ti at 300 W, and asks for 850 W and 750 W supplies. Partner boards go further. My ASUS ROG Astral RTX 5080 OC ships at a 400 W power limit, and ASUS&amp;rsquo;s March 2025 BIOS raised its ceiling to 450 W, as my &lt;a href="https://techfuelhq.com/gpu-reviews/rog-astral-rtx-5080-oc-review-2026/">Astral review&lt;/a> records. The captures below ran at a 448 W limit. So this partner card&amp;rsquo;s limit sits 40 to 90 W above NVIDIA&amp;rsquo;s reference figure and 100 to 150 W above the 5070 Ti&amp;rsquo;s.&lt;/p>
&lt;p>What the card drew is a different number. On June 28, 2026 I logged board power every five seconds across a 25-minute gaming session on my hand-tuned profile, 308 samples, and published the &lt;a href="https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/sustained-gaming-telemetry-2026-06-28.csv" download type="text/csv">raw log&lt;/a> with the dataset. The maximum was 325.73 W. The average was 260.99 W. Forty-six samples sat at 300 W or above, none reached 360 W, the throttle register read zero on every row, and the core averaged 56 °C. In my &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-power-efficiency/">LLM power-efficiency dataset&lt;/a>, captured August 19, 2026 at the 448 W limit, loaded medians across four models ran from 265 to 344 W and never touched the cap either.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Figure&lt;/th>
&lt;th scope="col" style="text-align: right">Watts&lt;/th>
&lt;th scope="col">Scope&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Figure">Astral RTX 5080 shipping limit&lt;/td>
&lt;td style="text-align: right" data-label="Watts">400&lt;/td>
&lt;td data-label="Scope">my card, Astral review&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Figure">Astral RTX 5080 BIOS ceiling&lt;/td>
&lt;td style="text-align: right" data-label="Watts">450&lt;/td>
&lt;td data-label="Scope">my card, Astral review; Club386&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Figure">Gaming peak, 308 samples&lt;/td>
&lt;td style="text-align: right" data-label="Watts">325.73&lt;/td>
&lt;td data-label="Scope">my card, hand-tuned profile, game not named&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Figure">LLM decode, loaded medians&lt;/td>
&lt;td style="text-align: right" data-label="Watts">265 to 344&lt;/td>
&lt;td data-label="Scope">my card, four models, 448 W limit&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Figure">RTX 5070 Ti in Final Fantasy XIV at 4K&lt;/td>
&lt;td style="text-align: right" data-label="Watts">264&lt;/td>
&lt;td data-label="Scope">GamersNexus, February 2025, their bench&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>So the firmware headroom on this partner 5080 went unused in both workloads, and its gaming peak stayed 34 W under NVIDIA&amp;rsquo;s reference figure. The step from a 750 W supply with two 8-pin cables to an 850 W supply with three is written on the spec sheet. In the gaming log and the LLM runs, the draw never got there. Buy the 850 W unit anyway. ASUS recommends 850 W for the Astral, a figure it bases on a fully overclocked GPU and CPU, and my &lt;a href="https://techfuelhq.com/articles/what-psu-for-rtx-5080-2026/">RTX 50-series PSU guide&lt;/a> itemizes the build.&lt;/p>
&lt;p>Here is the scope. One card, one gaming session with the game not named, one profile, board power only, no wall measurement. I own no 5070 Ti, so the 264 W row is GamersNexus&amp;rsquo;s figure from their bench, there for reference and never as a like-for-like pair with my log. No benchmark run against a 5070 Ti is planned.&lt;/p>
&lt;p>To bring a 5080&amp;rsquo;s draw down below stock, the &lt;a href="https://techfuelhq.com/articles/rtx-5080-undervolt-guide-2026/">RTX 5080 undervolt guide&lt;/a> covers the Afterburner curve.&lt;/p>
&lt;h2 id="for-local-llms-the-gap-splits-in-two">For local LLMs, the gap splits in two&lt;/h2>
&lt;p>I own no 5070 Ti, so for the pair I use the community numbers in the &lt;a href="https://github.com/ggml-org/llama.cpp/discussions/15013" rel="noopener">llama.cpp CUDA performance discussion&lt;/a>, where owners run &lt;code>llama-bench&lt;/code> on Llama 2 7B Q4_0 and post results from whatever commit and host they have. It is a survey. There is no controlled test behind it.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">llama-bench, Llama 2 7B Q4_0&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5070 Ti&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5080&lt;/th>
&lt;th scope="col" style="text-align: right">5080 lead&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="llama-bench, Llama 2 7B Q4_0">Prompt processing, pp512, flash attention off&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">6,952.38&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">8,297.36&lt;/td>
&lt;td style="text-align: right" data-label="5080 lead">+19.3%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="llama-bench, Llama 2 7B Q4_0">Prompt processing, pp512, flash attention on&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">8,419.56&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">9,487.70&lt;/td>
&lt;td style="text-align: right" data-label="5080 lead">+12.7%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="llama-bench, Llama 2 7B Q4_0">Token generation, tg128, flash attention off&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">176.85&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">181.99&lt;/td>
&lt;td style="text-align: right" data-label="5080 lead">+2.9%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="llama-bench, Llama 2 7B Q4_0">Token generation, tg128, flash attention on&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">182.43&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">184.68&lt;/td>
&lt;td style="text-align: right" data-label="5080 lead">+1.2%&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Generation streams the model&amp;rsquo;s weights through memory once per token, so it tracks bandwidth, and the bandwidth gap is 7.1%. Prompt processing is compute. There the 5080&amp;rsquo;s 20% more cores show. For interactive chat the two cards will feel the same. For long-context ingestion or batch prefill the 5080 buys 13% to 19%.&lt;/p>
&lt;p>My own 5080 numbers come from a different stack. In my &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>, captured August 12, 2026 with ollama 0.32.1 on driver 610.88 and a Ryzen 7 7800X3D, the Astral decoded gpt-oss:20b at 187.3 to 190.1 tokens a second and Qwen 2.5 7B Q4_K_M at 176.6 to 180.0. Different models, a different runtime and no 5070 Ti column, so they do not pair with the llama-bench rows.&lt;/p>
&lt;h2 id="where-the-5080-earns-its-price">Where the 5080 earns its price&lt;/h2>
&lt;p>Two cases. Both need a name before you pay.&lt;/p>
&lt;p>The first is 4K with ray tracing. Tom&amp;rsquo;s 4K ray-tracing averages, 42.1 fps against 36.7, are the widest gap in the table, and the 1440p pair, 74.0 against 66.2, stands in for the input rate of 4K at DLSS Quality. My &lt;a href="https://techfuelhq.com/articles/4k-240hz-which-gpu-2026/">4K 240Hz GPU page&lt;/a> explains why that input rate decides whether frame generation feels right, and it puts the 5070 Ti on the line and the 5080 clear of it. If that is your monitor, the 5080 is the card.&lt;/p>
&lt;p>The second is paid compute. Work that scales with CUDA cores gets the 20% from the spec sheet and the 13% to 19% from the llama-bench prefill rows. If the card bills hours, $790 is cheap. If it only raises a benchmark score, the money buys nothing you will see at 1440p.&lt;/p>
&lt;p>For everyone else the first table says the Ti.&lt;/p>
&lt;h2 id="so-which-should-you-buy">So which should you buy?&lt;/h2>
&lt;ul>
&lt;li>For 1440p, and for 4K without ray tracing, the RTX 5070 Ti. Its frames cost less in every row of the first table. For a complete tower, the &lt;a href="https://techfuelhq.com/articles/best-rtx-5070-ti-prebuilt-gaming-pc-2026/">RTX 5070 Ti prebuilt guide&lt;/a> ranks finished machines.&lt;/li>
&lt;li>For 4K with ray tracing, or for paid work that scales with CUDA cores, the RTX 5080. Budget the 850 W supply and the third cable with it. The &lt;a href="https://techfuelhq.com/articles/best-rtx-5080-prebuilt-gaming-pc-2026/">RTX 5080 prebuilt guide&lt;/a> does the same for complete towers.&lt;/li>
&lt;li>If ray tracing is off the table, look at the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-rx-9070-xt-2026/">RX 9070 XT&lt;/a> before either: it ties the 5070 Ti at 1440p raster in the same averages, 116.5 fps against 116.8. Above the 5080, see &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5090-vs-5080-2026/">RTX 5090 vs 5080&lt;/a>.&lt;/li>
&lt;/ul>
&lt;p>Both cards sit in the S tier of my &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/">2026 GPU hierarchy&lt;/a>, four places apart. The $790 between them buys the ray-traced 4K row and the prefill rows. Make sure one of those is yours.&lt;/p></description></item><item><title>RTX 5060 Ti vs RTX 5070 (2026): 31% Faster, 4GB Less</title><link>https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rtx-5070-2026/</link><pubDate>Sun, 13 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rtx-5070-2026/</guid><atom:updated>2026-11-18T05:05:34Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · RTX 5060 Ti vs RTX 5070&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Speed:&lt;/strong> the RTX 5070 is 31% faster at 1440p in Tom's Hardware's June 2026 hierarchy, and ComputerBase measured 36% in 2025.&lt;/li>
&lt;li>&lt;strong>Memory:&lt;/strong> 16GB on the 5060 Ti against 12GB on the 5070. That decides path-traced Indiana Jones and which local AI models fit on the card.&lt;/li>
&lt;li>&lt;strong>Price on November 17, 2026:&lt;/strong> Newegg listed the cheapest new in-stock cards at $799.99 and $919.99. Each 1440p frame costs 12% less on the 5070.&lt;/li>
&lt;li>&lt;strong>Power:&lt;/strong> 180 W against 250 W, with NVIDIA recommending a 600 W or 650 W system supply.&lt;/li>
&lt;li>&lt;strong>Already own a 16GB 5060 Ti?&lt;/strong> I would keep it.&lt;/li>
&lt;/ul>
&lt;p>I owned an RTX 5060 Ti 16GB but have not benchmarked it or an RTX 5070, so every benchmark here is Tom's Hardware's, ComputerBase's, PCGamesN's or TechSpot's, named where it appears. Prices are Newegg's catalogue from November 17, 2026.&lt;/p>
&lt;/div>
&lt;h2 id="which-one-to-buy">Which one to buy&lt;/h2>
&lt;p>For gaming, buy the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-review-2026/">RTX 5070&lt;/a>. It is 31% faster at 1440p for 15% more money, so each frame costs less. Buy the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-review-2026/">RTX 5060 Ti 16GB&lt;/a> only when a job needs more than 12GB of memory, such as a local AI model whose footprint sits between 12 and 16GB: the 5060 Ti 16GB is the card with room for it. On a 600 W supply, the 5060 Ti is also the one that fits NVIDIA&amp;rsquo;s recommendation.&lt;/p>
&lt;p>Both cards above are the cheapest new, in-stock ones under a Newegg item number in Newegg&amp;rsquo;s catalogue on November 17, 2026. The &lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU price index&lt;/a> tracks both chips from day to day.&lt;/p>
&lt;h2 id="why-i-would-buy-the-5070-in-november-2026">Why I would buy the 5070 in November 2026&lt;/h2>
&lt;p>NVIDIA put these cards $120 apart at launch, $429 for the 16GB RTX 5060 Ti and $549 for the RTX 5070, and when Jarred Walton compared them for Tom&amp;rsquo;s Hardware in April 2025 the price gap and the speed gap came out about even. That was a fair fight.&lt;/p>
&lt;p>It is not one now.&lt;/p>
&lt;p>Both cards now cost far more than their launch prices. In Newegg&amp;rsquo;s catalogue on November 17, the cheapest new, in-stock 5060 Ti 16GB was the PNY RTX 5060 Ti 16GB Dual Fan OC at &lt;span class="claim" data-claim-key="listing.N82E16814133993.price_usd" data-claim-value="799.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$799.99&lt;/span>
and the cheapest new RTX 5070 was the MSI RTX 5070 12G Ventus 3X OC at &lt;span class="claim" data-claim-key="listing.N82E16814137940.price_usd" data-claim-value="919.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$919.99&lt;/span>
, so $120 separates a card from one that is about 30% faster. Those are the same dollars NVIDIA&amp;rsquo;s launch prices put between them.&lt;/p>
&lt;p>The case for the 5060 Ti comes down to its extra 4GB of memory, so most of this page is about when that 4GB is worth more than the speed.&lt;/p>
&lt;h2 id="specs-and-prices-side-by-side">Specs and prices side by side&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">RTX 5060 Ti 16GB&lt;/th>
&lt;th scope="col">RTX 5070&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">GPU&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">GB206&lt;/td>
&lt;td data-label="RTX 5070">GB205&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">CUDA cores&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">4,608&lt;/td>
&lt;td data-label="RTX 5070">6,144&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">VRAM&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">16GB GDDR7&lt;/td>
&lt;td data-label="RTX 5070">12GB GDDR7&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Memory bus&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">128-bit&lt;/td>
&lt;td data-label="RTX 5070">192-bit&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Memory bandwidth&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">448 GB/s&lt;/td>
&lt;td data-label="RTX 5070">672 GB/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">PCIe link&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">5.0 x8&lt;/td>
&lt;td data-label="RTX 5070">5.0 x16&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Total graphics power&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">180 W&lt;/td>
&lt;td data-label="RTX 5070">250 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">NVIDIA&amp;rsquo;s recommended system power&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">600 W&lt;/td>
&lt;td data-label="RTX 5070">650 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Reference power input&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">1x 8-pin, or one 300 W Gen 5 cable&lt;/td>
&lt;td data-label="RTX 5070">2x 8-pin, or one 300 W Gen 5 cable&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Launch price&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">$429 (April 2025)&lt;/td>
&lt;td data-label="RTX 5070">$549 (March 2025)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Newegg median, August 2026&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">$804.99&lt;/td>
&lt;td data-label="RTX 5070">$899.99&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Cheapest new in stock at Newegg, November 17, 2026&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">$799.99&lt;/td>
&lt;td data-label="RTX 5070">$919.99&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The core, memory, power and connector rows come from NVIDIA&amp;rsquo;s spec pages, and the launch prices from NVIDIA&amp;rsquo;s announcements. The GPU and bandwidth rows and the launch months come from Tom&amp;rsquo;s Hardware&amp;rsquo;s comparison, the PCIe row from TechSpot and the cards&amp;rsquo; Newegg listings, the August medians from the table in Tom&amp;rsquo;s Hardware&amp;rsquo;s price survey, and the November row from Newegg&amp;rsquo;s catalogue.&lt;/p>
&lt;p>The 5070 has a third more CUDA cores and half again the memory bandwidth, while the 5060 Ti answers with 4GB more memory on a narrower bus, connected through half as many PCIe lanes. It also draws less power.&lt;/p>
&lt;h2 id="how-much-faster-the-rtx-5070-is">How much faster the RTX 5070 is&lt;/h2>
&lt;p>Tom&amp;rsquo;s Hardware&amp;rsquo;s GPU hierarchy, last updated June 24, 2026, runs both cards on a Ryzen 7 9800X3D at ultra settings. I took its average frame rates and worked out the lead.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Test, ultra settings&lt;/th>
&lt;th scope="col">RTX 5060 Ti 16GB&lt;/th>
&lt;th scope="col">RTX 5070&lt;/th>
&lt;th scope="col">5070 lead&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Test, ultra settings">1080p&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">105.2 fps&lt;/td>
&lt;td data-label="RTX 5070">132.6 fps&lt;/td>
&lt;td data-label="5070 lead">26%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test, ultra settings">1440p&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">73.4 fps&lt;/td>
&lt;td data-label="RTX 5070">96.4 fps&lt;/td>
&lt;td data-label="5070 lead">31%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test, ultra settings">4K&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">40.2 fps&lt;/td>
&lt;td data-label="RTX 5070">54.3 fps&lt;/td>
&lt;td data-label="5070 lead">35%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test, ultra settings">1080p ray tracing&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">56.2 fps&lt;/td>
&lt;td data-label="RTX 5070">74.1 fps&lt;/td>
&lt;td data-label="5070 lead">32%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test, ultra settings">1440p ray tracing&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">38.9 fps&lt;/td>
&lt;td data-label="RTX 5070">51.5 fps&lt;/td>
&lt;td data-label="5070 lead">32%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test, ultra settings">4K ray tracing&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">20.6 fps&lt;/td>
&lt;td data-label="RTX 5070">22.7 fps&lt;/td>
&lt;td data-label="5070 lead">10%&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Two older tests land in the same place. Walton&amp;rsquo;s 21-game comparison from April 2025 put the 5070 31% ahead at 1440p and 32% ahead at 4K. ComputerBase measured 74.8 fps against 55.0 at 1440p that same month, a 36% lead, and 30% with ray tracing on.&lt;/p>
&lt;p>The lead narrows at 1080p, where Walton found both cards running into CPU limits, and he saw it fall to 24% at 1080p medium settings. Now look at the last row. At 4K with ray tracing the 5070 is only 10% ahead, which I suspect is its 12GB filling up, though an average cannot show that, and Walton&amp;rsquo;s 2025 test had one ray-traced game hitting that limit at 4K ultra.&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/">2026 GPU hierarchy&lt;/a> shows where both cards sit against everything else, and the &lt;a href="https://techfuelhq.com/tools/gpu-comparison/?a=GeForce&amp;#43;RTX&amp;#43;5060&amp;#43;Ti&amp;#43;16GB&amp;amp;b=GeForce&amp;#43;RTX&amp;#43;5070&amp;amp;res=1440p">GPU comparison tool&lt;/a> puts this pair side by side at three resolutions.&lt;/p>
&lt;h2 id="where-16gb-wins">Where 16GB wins&lt;/h2>
&lt;p>Extra memory does nothing for a game that fits in 12GB, and in Walton&amp;rsquo;s 21-game suite from 2025 no game fell short at 1440p and only one did at 4K.&lt;/p>
&lt;p>That one was Indiana Jones and the Great Circle, where the 5060 Ti finished 5% ahead of the 5070 at 4K ultra. In a separate test, PCGamesN&amp;rsquo;s Ben Hardwidge pushed the same game to its Supreme preset with full path tracing at 1080p. The 5070 averaged 5 fps.&lt;/p>
&lt;p>The 16GB 5060 Ti started from 40 fps, and Hardwidge put the 5070&amp;rsquo;s collapse down to its 12GB of VRAM. He still judged 40 fps too low for frame generation to smooth out without obvious input lag, so the 16GB card wins that test without making it pleasant.&lt;/p>
&lt;p>Local AI is the other case. On my RTX 5080, which also carries 16GB, nvidia-smi showed 13.1 to 14.0 GiB of the card&amp;rsquo;s memory in use across two captures with gpt-oss 20B loaded in Ollama. That reading is above a 5070&amp;rsquo;s 12GB.&lt;/p>
&lt;p>Qwen 2.5 14B at Q4_K_M read 10.6 GiB at a 4,096-token context and 12.8 GiB at 16,384 tokens, already past 12GB. All of these are whole-card readings, and the dataset treats such readings as an upper bound because Ollama can keep an earlier model loaded, so they overstate what each model needs on its own.&lt;/p>
&lt;p>They come from &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">my RTX 5080 LLM dataset&lt;/a>. A 5060 Ti 16GB runs gpt-oss 20B in MXFP4, and the benchmark table in llama.cpp&amp;rsquo;s gpt-oss guide discussion lists it at 111.51 tokens a second in llama.cpp&amp;rsquo;s short generation test, a different benchmark from the MLPerf figure below.&lt;/p>
&lt;p>Where the model fits both cards, the 5070 has been faster. In Jarred Walton&amp;rsquo;s April 2025 comparison for Tom&amp;rsquo;s Hardware it ran MLPerf Client&amp;rsquo;s text generation test at 111.7 tokens a second against 84.2, a 33% lead.&lt;/p>
&lt;p>So I pick by the model and its context. If the whole footprint, buffers included, sits comfortably under 12GB, buy the 5070. If it runs between 12 and 16GB, the 5060 Ti has room the 5070 does not. The &lt;a href="https://techfuelhq.com/articles/local-llm-by-gpu-vram-2026/">local LLM by VRAM guide&lt;/a> lists which models land in each tier.&lt;/p>
&lt;h2 id="pcie-x8-power-and-features">PCIe x8, power and features&lt;/h2>
&lt;p>The 5060 Ti uses eight PCIe lanes and the 5070 uses sixteen, and TechSpot&amp;rsquo;s Steven Walton tested what the x8 link costs on older boards and found the PCIe mode has little effect while a game stays within the card&amp;rsquo;s memory.&lt;/p>
&lt;p>His 16GB card on PCIe 3.0 averaged 66 fps in Dragon Age: The Veilguard, where the 8GB model managed 27. TechSpot only ran the 16GB card on PCIe 3.0, and it ran well there. The link is a real problem for the 8GB version on a PCIe 4.0 or 3.0 board.&lt;/p>
&lt;p>For the direct memory-capacity comparison, see &lt;a href="https://techfuelhq.com/articles/rtx-5060-ti-8gb-vs-16gb-2026/">RTX 5060 Ti 8GB vs 16GB&lt;/a>.&lt;/p>
&lt;p>The 5070 draws more power. NVIDIA rates it at 250 W of total graphics power against 180 W and recommends a 650 W system supply, 50 W more than for the 5060 Ti. If your power supply sits near either number, the &lt;a href="https://techfuelhq.com/tools/psu-wattage-calculator/">PSU wattage calculator&lt;/a> will tell you whether the rest of your parts leave room.&lt;/p>
&lt;p>Features match. NVIDIA lists DLSS 4 with Multi Frame Generation on both cards.&lt;/p>
&lt;h2 id="the-price-math">The price math&lt;/h2>
&lt;p>Walton ended his April 2025 comparison with a rule for gamers, that the 5070 was worth paying up to 30% more than the 5060 Ti 16GB, and he argued for as much as 40%.&lt;/p>
&lt;p>At launch prices the 5070 cost 28% more. At Newegg&amp;rsquo;s August 2026 medians it cost 12% more. At the cheapest new, in-stock cards in Newegg&amp;rsquo;s November 17 catalogue, the difference was 15%.&lt;/p>
&lt;p>By that rule, it is not close. Using Tom&amp;rsquo;s Hardware&amp;rsquo;s 1440p averages, each frame cost $10.90 on the cheapest new 5060 Ti 16GB and $9.54 on the cheapest new 5070. That is 12% less per frame. The hierarchy page is blunt about the smaller card, calling the 5060 Ti 16GB &amp;ldquo;hopelessly overpriced for the performance it offers in mid-2026.&amp;rdquo;&lt;/p>
&lt;p>Check both prices before you buy. If the gap widens past Walton&amp;rsquo;s 30 to 40%, the 5060 Ti starts to make sense.&lt;/p>
&lt;h2 id="upgrading-from-a-5060-ti-to-a-5070">Upgrading from a 5060 Ti to a 5070&lt;/h2>
&lt;p>I owned a 16GB 5060 Ti. If you own one, I would keep it. The 5070 is about 31% faster at 1440p, but $919.99 is a lot to pay for one tier, and you give up 4GB of memory you may already be using. I would save for a bigger jump.&lt;/p>
&lt;p>The 8GB 5060 Ti is a different story. TechSpot measured it falling apart once games ran past its memory, and in Dragon Age: The Veilguard it stayed unplayable even on PCIe 5.0. Its 8GB was the problem. Moving from that card to either of these is a real upgrade.&lt;/p>
&lt;h2 id="who-should-buy-neither">Who should buy neither&lt;/h2>
&lt;p>The AMD cards on either side no longer undercut these two by much. On November 17, 2026 Newegg listed the cheapest new, in-stock 16GB RX 9060 XT, a Yeston Sakura, at &lt;span class="claim" data-claim-key="listing.N82E16814980004.price_usd" data-claim-value="729.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$729.99&lt;/span>
, $70 under the 5060 Ti 16GB; in Tom&amp;rsquo;s Hardware&amp;rsquo;s August survey its median had been $474.99. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/">RTX 5060 Ti vs RX 9060 XT comparison&lt;/a> works through that trade. AMD&amp;rsquo;s 16GB answer to the 5070 is the RX 9070: the cheapest new one, a GIGABYTE Gaming OC, was &lt;span class="claim" data-claim-key="listing.N82E16814932752.price_usd" data-claim-value="934.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$934.99&lt;/span>
, $15 over the 5070, and Tom&amp;rsquo;s Hardware&amp;rsquo;s averages put it 8% ahead at 1440p raster (104.0 against 96.4 fps) and 8% behind with ray tracing (47.6 against 51.5). The &lt;a href="https://techfuelhq.com/gpu-reviews/rx-9070-review-2026/">RX 9070 review&lt;/a> covers that card.&lt;/p>
&lt;p>If 12GB worries you and the budget stretches, look one step up. The RTX 5070 Ti has 16GB; its August median was $1,099.99, and the cheapest new one in Newegg&amp;rsquo;s November 17 catalogue was $1,409.99. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-vs-5070-ti-2026/">RTX 5070 vs RTX 5070 Ti page&lt;/a> covers whether that premium pays.&lt;/p></description></item><item><title>RTX 5090 vs RTX 5080 (2026): Which One Should You Buy?</title><link>https://techfuelhq.com/gpu-reviews/rtx-5090-vs-5080-2026/</link><pubDate>Tue, 18 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gpu-reviews/rtx-5090-vs-5080-2026/</guid><atom:updated>2026-11-18T05:05:34Z</atom:updated><description>&lt;h2 id="the-decision-in-one-table">The decision in one table&lt;/h2>
&lt;p>The RTX 5090 wins every absolute-performance question. The RTX 5080 wins the purchase question for most gamers. Whether the 5080 itself is more card than you need is the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-5080-2026/">RTX 5070 Ti vs RTX 5080&lt;/a> question, answered the same way. The exception is a buyer whose current game, render, model, or paid workflow already reaches the 16GB boundary or whose display can turn the 5090&amp;rsquo;s extra native-4K frame rate into something visible; in that case, the larger card solves a named limit rather than serving as expensive insurance.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Decision&lt;/th>
&lt;th scope="col">RTX 5080&lt;/th>
&lt;th scope="col">RTX 5090&lt;/th>
&lt;th scope="col">Winner&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Decision">4K gaming with DLSS&lt;/td>
&lt;td data-label="RTX 5080">Strong, measured and playable&lt;/td>
&lt;td data-label="RTX 5090">Faster&lt;/td>
&lt;td data-label="Winner">&lt;strong>RTX 5080 value&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Decision">Maximum native 4K&lt;/td>
&lt;td data-label="RTX 5080">Compromises remain in the hardest titles&lt;/td>
&lt;td data-label="RTX 5090">Fastest tier&lt;/td>
&lt;td data-label="Winner">&lt;strong>RTX 5090&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Decision">VRAM&lt;/td>
&lt;td data-label="RTX 5080">16GB GDDR7&lt;/td>
&lt;td data-label="RTX 5090">32GB GDDR7&lt;/td>
&lt;td data-label="Winner">&lt;strong>RTX 5090&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Decision">Card power&lt;/td>
&lt;td data-label="RTX 5080">360W reference TGP&lt;/td>
&lt;td data-label="RTX 5090">575W reference TGP&lt;/td>
&lt;td data-label="Winner">&lt;strong>RTX 5080&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Decision">Required system power&lt;/td>
&lt;td data-label="RTX 5080">850W&lt;/td>
&lt;td data-label="RTX 5090">1000W&lt;/td>
&lt;td data-label="Winner">&lt;strong>RTX 5080&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Decision">Local AI that fits inside 16GB&lt;/td>
&lt;td data-label="RTX 5080">Already capable&lt;/td>
&lt;td data-label="RTX 5090">Faster/roomier, but unmeasured here&lt;/td>
&lt;td data-label="Winner">&lt;strong>RTX 5080 value&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Decision">Workloads that exceed 16GB&lt;/td>
&lt;td data-label="RTX 5080">Spill or fail&lt;/td>
&lt;td data-label="RTX 5090">32GB headroom&lt;/td>
&lt;td data-label="Winner">&lt;strong>RTX 5090&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Decision">Most gaming builds&lt;/td>
&lt;td data-label="RTX 5080">Rational ceiling&lt;/td>
&lt;td data-label="RTX 5090">Halo purchase&lt;/td>
&lt;td data-label="Winner">&lt;strong>RTX 5080&lt;/strong>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;img src="https://techfuelhq.com/images/gpu-reviews/rtx-5090-vs-5080-2026.svg" alt="RTX 5090 versus RTX 5080 decision map: choose the RTX 5080 for most 4K gaming and lower power, or the RTX 5090 when 32GB VRAM, maximum native 4K performance, rendering, or paid GPU work has a defined job" width="1200" height="630" loading="lazy" decoding="async" style="display:block;margin:1.5rem auto;max-width:100%;height:auto;border:1px solid #1e1e3a;border-radius:8px;" />
&lt;h2 id="what-the-cards-cost-on-november-17-2026">What the cards cost on November 17, 2026&lt;/h2>
&lt;p>Launch MSRP is useful history. It is not the number buyers face today. These are Newegg&amp;rsquo;s catalogue prices for new, in-stock cards under a Newegg item number.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Exact card&lt;/th>
&lt;th scope="col" style="text-align: right">Newegg, Nov. 17, 2026&lt;/th>
&lt;th scope="col" style="text-align: right">Newegg, Aug. 18, 2026&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Exact card">&lt;strong>ZOTAC Gaming RTX 5080 Solid Core OC 16GB&lt;/strong>, the cheapest RTX 5080&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Nov. 17, 2026">&lt;span class="claim" data-claim-key="listing.N82E16814500648.price_usd" data-claim-value="2199.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">&lt;strong>$2,199.99&lt;/strong>&lt;/span>
&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Aug. 18, 2026">not priced here&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Exact card">&lt;strong>GIGABYTE WINDFORCE RTX 5080 16GB&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Nov. 17, 2026">&lt;span class="claim" data-claim-key="listing.N82E16814932754.price_usd" data-claim-value="2299.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$2,299.99&lt;/span>
&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Aug. 18, 2026">$1,399.99&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Exact card">&lt;strong>ASUS ROG Astral RTX 5090 32GB&lt;/strong>, the cheapest RTX 5090&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Nov. 17, 2026">&lt;span class="claim" data-claim-key="listing.N82E16814126751.price_usd" data-claim-value="6249.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">&lt;strong>$6,249.99&lt;/strong>&lt;/span>
&lt;/td>
&lt;td style="text-align: right" data-label="Newegg, Aug. 18, 2026">$4,829.99&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The cheapest RTX 5090 costs &lt;strong>2.84 times&lt;/strong> the cheapest RTX 5080, $4,050 more. The pair this page priced in August moved too: the WINDFORCE 5080 is $900 higher and the Astral 5090 $1,420 higher, so that pair&amp;rsquo;s ratio fell from 3.45 to 2.72. ROG Astral is a premium flagship board and the Solid Core a simpler RTX 5080, but each was the cheapest card of its chip in stock that day, which is the choice a buyer actually has. The &lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU price index&lt;/a> tracks both chips, and &lt;a href="https://techfuelhq.com/data/deal-or-mirage/#sku-geforce-rtx-5090-32gb">Deal or Mirage&lt;/a> gives the baseline to judge a Black Friday 5090 price against.&lt;/p>
&lt;h2 id="specifications-that-matter">Specifications that matter&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Specification&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5080&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5090&lt;/th>
&lt;th scope="col" style="text-align: right">Difference&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Specification">CUDA cores&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">10,752&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">21,760&lt;/td>
&lt;td style="text-align: right" data-label="Difference">+11,008&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">VRAM&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">16GB GDDR7&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">32GB GDDR7&lt;/td>
&lt;td style="text-align: right" data-label="Difference">2× capacity&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Memory interface&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">256-bit&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">512-bit&lt;/td>
&lt;td style="text-align: right" data-label="Difference">2× width&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Total graphics power&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">360W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">575W&lt;/td>
&lt;td style="text-align: right" data-label="Difference">+215W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Required system power&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">850W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">1000W&lt;/td>
&lt;td style="text-align: right" data-label="Difference">+150W&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The core count is not a frame-rate equation. Games do not scale one-for-one with CUDA cores, and CPU limits, memory behavior, ray tracing, and engine design change the gap. The capacity and power differences are literal. They shape what fits in VRAM, which supply belongs in the system, and how much heat the case must move. If the 575W is the part that worries you, the &lt;a href="https://techfuelhq.com/articles/rtx-5090-undervolt-2026/">RTX 5090 undervolt guide&lt;/a> shows what a curve and a power limit took off it in published tests.&lt;/p>
&lt;h2 id="launch-date-founders-edition-size-and-io">Launch date, Founders Edition size, and I/O&lt;/h2>
&lt;p>NVIDIA announced both desktop cards on January 6, 2025. It set January 30 availability for each. Its current reference specifications, read November 18, 2026, list the same Founders Edition envelope for both: 304mm long, 137mm wide, and two slots. Those are reference dimensions. Partner-card dimensions vary, so the measurements do not replace the exact model&amp;rsquo;s specification sheet.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Official desktop specification&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5080&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5090&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Official desktop specification">Available&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">January 30, 2025&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">January 30, 2025&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Official desktop specification">Founders Edition size&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">304 × 137mm, 2-slot&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">304 × 137mm, 2-slot&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Official desktop specification">Display outputs&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">3× DisplayPort, 1× HDMI&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">3× DisplayPort, 1× HDMI&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Official desktop specification">PCI Express&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">Gen 5&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">Gen 5&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Official desktop specification">AI performance&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">1,801 AI TOPS&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">3,352 AI TOPS&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Official desktop specification">Ray-tracing generation&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">Fourth generation&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">Fourth generation&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Official desktop specification">Ray-tracing throughput&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">171 TFLOPS&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">318 TFLOPS&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Official desktop specification">Reference power input&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">450W-or-greater PCIe Gen 5 cable, or 3× 8-pin adapter&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">600W PCIe Gen 5 cable, or 4× 8-pin adapter&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>NVIDIA does not publish a Founders Edition weight in either specification table. Use the exact board partner&amp;rsquo;s product page for weight, cooler thickness, and support-bracket requirements rather than copying a number from a different card.&lt;/p>
&lt;h3 id="does-an-rtx-5080-have-24gb-or-32gb">Does an RTX 5080 have 24GB or 32GB?&lt;/h3>
&lt;p>No. &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5080/" rel="noopener">NVIDIA specifies 16GB GDDR7 for the standard desktop RTX 5080&lt;/a>, checked November 18, 2026. The desktop RTX 5090 has 32GB. In a complete-PC listing, a separate 32GB memory figure may describe system RAM, which does not add to the card&amp;rsquo;s VRAM. A listing claiming a 24GB or 32GB standard RTX 5080 needs clarification from the seller before purchase.&lt;/p>
&lt;h2 id="how-much-faster-is-the-rtx-5090">How much faster is the RTX 5090?&lt;/h2>
&lt;p>Jeffrey Kampman&amp;rsquo;s &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware GPU hierarchy&lt;/a>, last updated June 24, 2026, averages 11 raster games and 8 ray-traced games at native resolution, with no upscaling or frame generation, on a Ryzen 7 9800X3D. Its averages for this pair, with my arithmetic on the lead:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Tom&amp;rsquo;s Hardware fps averages&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5080&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5090&lt;/th>
&lt;th scope="col" style="text-align: right">5090 lead&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">1440p raster&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">128.3&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">167.3&lt;/td>
&lt;td style="text-align: right" data-label="5090 lead">+30.4%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">4K raster&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">77.4&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">110.8&lt;/td>
&lt;td style="text-align: right" data-label="5090 lead">+43.2%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">1440p ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">74.0&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">100.8&lt;/td>
&lt;td style="text-align: right" data-label="5090 lead">+36.2%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">4K ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">42.1&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5090">64.1&lt;/td>
&lt;td style="text-align: right" data-label="5090 lead">+52.3%&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>GamersNexus&amp;rsquo;s &lt;a href="https://gamersnexus.net/gpus/nvidia-geforce-rtx-5080-founders-edition-review-benchmarks-vs-5090-7900-xtx-4080-more" rel="noopener">RTX 5080 launch review&lt;/a> (January 2025) measured the RTX 5090 &lt;strong>30% to 68.9% ahead&lt;/strong> of the RTX 5080 at 4K, depending on the game, with results commonly in the &lt;strong>45% to 55%&lt;/strong> range. A single title can land near 30%. Another can approach 70%.&lt;/p>
&lt;p>Expect a large 4K lead that moves by title, and do not pay for the maximum result unless your own games resemble the workloads that produce it. At 1440p the lead shrinks to 30% in Tom&amp;rsquo;s raster averages. If the display is 1440p, the RTX 5090 is usually an expensive way to wait on the processor.&lt;/p>
&lt;h2 id="what-the-rtx-5080-already-does-at-4k">What the RTX 5080 already does at 4K&lt;/h2>
&lt;p>TechFuelHQ owns and measures an ASUS ROG Astral RTX 5080 OC. The &lt;a href="https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/">open bench dataset&lt;/a> publishes raw values with the method and correction history under CC BY 4.0.&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/#4-power--thermal--astral-stock-vs-astral-manual-oc-techfuelhq-measured">power and thermal readings&lt;/a> do include stock gaming observations.&lt;/p>
&lt;p>These five configurations used the same hand-tuned GPU Tweak III User Mode 2 profile at 4K output. The record contains no matching stock or factory-OC FPS results for these five configurations:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Workload&lt;/th>
&lt;th scope="col" style="text-align: right">Average FPS&lt;/th>
&lt;th scope="col" style="text-align: right">1% low&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Workload">Cyberpunk 2077 Ultra raster&lt;/td>
&lt;td style="text-align: right" data-label="Average FPS">58&lt;/td>
&lt;td style="text-align: right" data-label="1% low">49&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Workload">Cyberpunk RT Ultra, DLSS Quality&lt;/td>
&lt;td style="text-align: right" data-label="Average FPS">50&lt;/td>
&lt;td style="text-align: right" data-label="1% low">41&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Workload">Cyberpunk Path Tracing, native&lt;/td>
&lt;td style="text-align: right" data-label="Average FPS">19&lt;/td>
&lt;td style="text-align: right" data-label="1% low">15&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Workload">Alan Wake 2 RT, DLSS Quality&lt;/td>
&lt;td style="text-align: right" data-label="Average FPS">49&lt;/td>
&lt;td style="text-align: right" data-label="1% low">38&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Workload">Black Myth Wukong Cinematic&lt;/td>
&lt;td style="text-align: right" data-label="Average FPS">34&lt;/td>
&lt;td style="text-align: right" data-label="1% low">27&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The card needs help in the hardest path-traced workload. That is where DLSS 4 changes the buying decision. On the same system, Cyberpunk 4K path tracing measured:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Mode&lt;/th>
&lt;th scope="col" style="text-align: right">Output FPS&lt;/th>
&lt;th scope="col" style="text-align: right">PC latency&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Mode">Native path tracing&lt;/td>
&lt;td style="text-align: right" data-label="Output FPS">19&lt;/td>
&lt;td style="text-align: right" data-label="PC latency">95ms&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">DLSS Quality, no frame generation&lt;/td>
&lt;td style="text-align: right" data-label="Output FPS">40&lt;/td>
&lt;td style="text-align: right" data-label="PC latency">45ms&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">DLSS Quality + MFG 2×&lt;/td>
&lt;td style="text-align: right" data-label="Output FPS">90&lt;/td>
&lt;td style="text-align: right" data-label="PC latency">55ms&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">DLSS Quality + MFG 4×&lt;/td>
&lt;td style="text-align: right" data-label="Output FPS">135&lt;/td>
&lt;td style="text-align: right" data-label="PC latency">62ms&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>If those techniques are acceptable, the RTX 5080 is already a serious 4K card. The RTX 5090 buys more native headroom and a higher starting frame rate. It does not make the RTX 5080 incapable.&lt;/p>
&lt;h2 id="the-16gb-versus-32gb-decision">The 16GB versus 32GB decision&lt;/h2>
&lt;p>For gaming, 16GB is the practical high-end capacity today. The first-party 4K runs above fit and complete on the RTX 5080. Buying 32GB solely because a future game might need it is weak evidence.&lt;/p>
&lt;p>For work, capacity can become binary. A render scene, local model, image batch, or timeline either fits in VRAM or it does not. Once the workload crosses 16GB, the RTX 5090&amp;rsquo;s performance advantage is no longer just frames per second. It can keep work on the GPU that the 5080 must spill, reduce, or refuse.&lt;/p>
&lt;p>Name the workload before paying:&lt;/p>
&lt;ul>
&lt;li>What is the current peak VRAM allocation?&lt;/li>
&lt;li>Does lowering batch size destroy throughput?&lt;/li>
&lt;li>Does CPU/RAM offload create an unacceptable delay?&lt;/li>
&lt;li>Does the extra GPU memory replace a second card, cloud bill, or work interruption?&lt;/li>
&lt;/ul>
&lt;p>If there is no measured 16GB problem, the 32GB answer is insurance at flagship pricing.&lt;/p>
&lt;h2 id="local-ai-use-measured-data-not-parameter-count-folklore">Local AI: use measured data, not parameter-count folklore&lt;/h2>
&lt;p>The &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 local LLM throughput dataset&lt;/a> is measured on the same retail card and mirrored on Kaggle and Hugging Face. It shows what 16GB can already do:&lt;/p>
&lt;ul>
&lt;li>gpt-oss:20b MXFP4: &lt;strong>187–190 decode tokens/second&lt;/strong>&lt;/li>
&lt;li>resident VRAM: roughly &lt;strong>13.7–14.0 GiB&lt;/strong>&lt;/li>
&lt;li>Qwen 2.5 14B Q4_K_M: &lt;strong>94–97 tok/s&lt;/strong>&lt;/li>
&lt;li>Qwen 2.5 7B Q4_K_M: &lt;strong>177–180 tok/s&lt;/strong>&lt;/li>
&lt;/ul>
&lt;p>This site has no first-party RTX 5090 AI result, so I will not invent a speed multiplier. The grounded claim is capacity: 32GB gives room for larger fully resident models, longer contexts, image work, plus larger batches. The grounded counterclaim is equally important: 16GB is already enough for fast interactive use on several useful models.&lt;/p>
&lt;p>Buy the 5090 for AI when a workload you run now exceeds the 5080&amp;rsquo;s capacity. Buy the 5080 when your actual models fit. The &lt;a href="https://techfuelhq.com/articles/local-llm-by-gpu-vram-2026/">local LLM by VRAM guide&lt;/a> maps which models fit in 16GB and 32GB, and for more than 32GB the &lt;a href="https://techfuelhq.com/articles/local-llm-70b-what-it-costs/">70B local LLM cost guide&lt;/a> covers the used 48GB workstation cards, the step past both.&lt;/p>
&lt;h2 id="power-case-and-the-rest-of-the-system">Power, case, and the rest of the system&lt;/h2>
&lt;p>The RTX 5090 adds 215W of reference board power. That changes more than the electric bill.&lt;/p>
&lt;p>NVIDIA specifies 850W required system power for the RTX 5080 and 1000W for the RTX 5090. TechFuelHQ&amp;rsquo;s &lt;a href="https://techfuelhq.com/articles/what-psu-for-rtx-5080-2026/">full RTX 50-series PSU guide&lt;/a> treats 1200W as the practical high-end 5090 target once a powerful processor and factory-overclocked board enter the build.&lt;/p>
&lt;p>Physical size follows the same pattern. The two partner cards this page priced in August listed these sizes on Newegg on August 18, 2026:&lt;/p>
&lt;ul>
&lt;li>GIGABYTE WINDFORCE RTX 5080: 304mm, 2.5 slots&lt;/li>
&lt;li>ASUS ROG Astral RTX 5090: 14.1 inches, 3.8 slots&lt;/li>
&lt;/ul>
&lt;p>That can determine case choice, front-radiator clearance, lower-slot access, GPU support, and cable bend radius. The GPU price is only the first system cost.&lt;/p>
&lt;h2 id="price-to-performance-without-fake-precision">Price-to-performance without fake precision&lt;/h2>
&lt;p>Using Tom&amp;rsquo;s Hardware&amp;rsquo;s 43.2% 4K raster lead and the cheapest card of each chip on November 17, 2026:&lt;/p>
&lt;ul>
&lt;li>performance multiplier: about &lt;strong>1.43×&lt;/strong>&lt;/li>
&lt;li>price multiplier: about &lt;strong>2.84×&lt;/strong>&lt;/li>
&lt;/ul>
&lt;p>That does not produce a universal &amp;ldquo;value score.&amp;rdquo; The two cheapest cards are different board tiers, and the RTX 5090 also buys double the VRAM. It does show the shape of the purchase: retail asks for far more money than the gaming-performance increase alone returns. Each 4K raster frame costs $28.42 on the 5080 and $56.41 on the 5090.&lt;/p>
&lt;p>The RTX 5090 can still be the cheaper business tool when its 32GB capacity replaces cloud GPU time, cuts a render queue, or prevents an out-of-memory failure. Put a number on that benefit before paying. If it only raises a benchmark score, gaming receives none of that payback.&lt;/p>
&lt;h2 id="buy-the-rtx-5080-if">Buy the RTX 5080 if&lt;/h2>
&lt;ul>
&lt;li>the system is primarily for gaming&lt;/li>
&lt;li>DLSS Quality and frame generation are acceptable at 4K&lt;/li>
&lt;li>current workloads fit inside 16GB&lt;/li>
&lt;li>you want an 850W-class build with easier case fit&lt;/li>
&lt;li>the 5090 price premium would delay the monitor, storage, or next upgrade&lt;/li>
&lt;/ul>
&lt;p>The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5080-review-2026/">RTX 5080 review&lt;/a> covers the card on its own, and the &lt;a href="https://techfuelhq.com/articles/best-gpu-4k-gaming-2026/">4K GPU guide&lt;/a> sets it against the other 4K tiers.&lt;/p>
&lt;h2 id="buy-the-rtx-5090-if">Buy the RTX 5090 if&lt;/h2>
&lt;ul>
&lt;li>maximum native or lightly upscaled 4K performance is the requirement&lt;/li>
&lt;li>32GB solves a measured memory-capacity problem&lt;/li>
&lt;li>rendering, AI, or creation time has direct financial value&lt;/li>
&lt;li>the larger PSU, case, cooling, and card price are already budgeted&lt;/li>
&lt;li>money-no-object performance is itself the goal&lt;/li>
&lt;/ul>
&lt;p>The first list describes most buyers. The second describes a smaller group with better reasons. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5090-review-2026/">RTX 5090 review&lt;/a> covers the card on its own.&lt;/p>
&lt;h2 id="complete-system-or-card">Complete system or card?&lt;/h2>
&lt;p>If you want the GPU inside a ready-to-run tower, compare the &lt;a href="https://techfuelhq.com/articles/best-rtx-5080-prebuilt-gaming-pc-2026/">best RTX 5080 prebuilts&lt;/a> and &lt;a href="https://techfuelhq.com/articles/best-rtx-5090-prebuilt-gaming-pc-2026/">best RTX 5090 prebuilts&lt;/a>. Those guides rank power delivery and memory layout, then check storage, seller, and warranty details that disappear when a listing talks only about the GPU. Before you pay the step up in a tower, note what the &lt;a href="https://techfuelhq.com/articles/best-rtx-5090-prebuilt-gaming-pc-2026/#rtx-5080-instead">system-level premium actually buys&lt;/a>: the two CLX Horus listings that were $2,400 apart in August, with the same processor and the same memory and drive capacities, were $6,000 apart in Newegg&amp;rsquo;s November 17, 2026 catalogue ($6,199.99 against $12,199.99), and the guide&amp;rsquo;s other matched pairs ran $5,350 to $6,000.&lt;/p>
&lt;p>For the card alone, confirm the exact item and dimensions, then verify the recommended supply, seller, warranty, and return terms. A GPU family name is not the product in your cart.&lt;/p>
&lt;p>&lt;strong>Where to buy the ZOTAC Gaming GeForce RTX 5080 Solid Core OC 16GB:&lt;/strong> &lt;a href="https://www.amazon.com/s?k=ZOTAC+GAMING+RTX+5080+SOLID+CORE+OC&amp;tag=techfuelhq-20" rel="nofollow sponsored">Search Amazon&lt;/a> &amp;middot; &lt;a href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;mid=44583&amp;murl=https%3A%2F%2Fwww.newegg.com%2Fzotac-gaming-geforce-rtx-5080-solid-core-oc-16gb-video-card-icestorm-3-0%2Fp%2FN82E16814500648%3Fitem%3DN82E16814500648" rel="nofollow sponsored">Check Newegg&lt;/a>. Affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/p></description></item><item><title>RTX 5070 vs RTX 5070 Ti: Is the Ti Worth It in 2026?</title><link>https://techfuelhq.com/gpu-reviews/rtx-5070-vs-5070-ti-2026/</link><pubDate>Mon, 20 Jul 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gpu-reviews/rtx-5070-vs-5070-ti-2026/</guid><atom:updated>2026-11-18T05:05:34Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · RTX 5070 vs RTX 5070 Ti&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Per frame.&lt;/strong> At Newegg's November 17, 2026 prices the 5070's frames cost less in five of the table's six rows. Only at 4K with ray tracing is the Ti's frame cheaper; it is 62% faster there in Tom's Hardware's June 24, 2026 averages.&lt;/li>
&lt;li>&lt;strong>Memory.&lt;/strong> 12GB against 16GB. TechSpot (March 4, 2025) measured the 5070 at 13 fps in path-traced Indiana Jones at 1440p with upscaling, and at 4K with full ray tracing the game crashes on a 12GB card.&lt;/li>
&lt;li>&lt;strong>The spoiler.&lt;/strong> The RX 9070 XT nearly matches the Ti's 1440p raster speed in the same averages and Newegg listed it at $999.99, $410 under the Ti.&lt;/li>
&lt;li>&lt;strong>Above the Ti.&lt;/strong> The RTX 5080 cost $2,199.99 at Newegg for 9.8% more speed than the Ti at 1440p raster.&lt;/li>
&lt;/ul>
&lt;p>Frame rates are Tom's Hardware's (June 24, 2026, read November 18) and TechSpot's (March 4, 2025). Prices are Newegg's catalogue from November 17, 2026.&lt;/p>
&lt;/div>
&lt;h2 id="which-one-to-buy">Which one to buy&lt;/h2>
&lt;p>For 1440p with path tracing off, and for a 650 W supply, buy the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-review-2026/">RTX 5070&lt;/a>: its frames cost less in every raster row of the table below. For 4K with ray tracing, or path tracing at any resolution, buy the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-ti-review-2026/">RTX 5070 Ti&lt;/a>, whose 4K ray-traced frames are the cheaper ones and which has 16GB; NVIDIA asks for 750 W of system power for it. For raster games only, the &lt;a href="https://techfuelhq.com/gpu-reviews/rx-9070-xt-review-2026/">RX 9070 XT&lt;/a> is the third card you should price first.&lt;/p>
&lt;p>Both NVIDIA cards above are the cheapest new, in-stock ones under a Newegg item number in Newegg&amp;rsquo;s catalogue on November 17, 2026. The &lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU price index&lt;/a> tracks both chips from day to day.&lt;/p>
&lt;h2 id="how-much-faster-is-the-ti-and-what-each-frame-costs">How much faster is the Ti, and what each frame costs&lt;/h2>
&lt;p>Divide a card&amp;rsquo;s price by its average frame rate and you get what each frame costs. The cheaper frame is the better value.&lt;/p>
&lt;p>&lt;strong>What the Ti&amp;rsquo;s extra $490 buys.&lt;/strong> Frame rates are averages from Jeffrey Kampman&amp;rsquo;s &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware GPU hierarchy&lt;/a>, updated June 24, 2026, which tests 11 raster games and 8 ray-traced games at high and ultra settings on a Ryzen 7 9800X3D. The ray-traced set is the four raster titles with RT support plus four games that require it or look best with it. Prices are the cheapest new, in-stock cards in Newegg&amp;rsquo;s catalogue on November 17, 2026, the MSI RTX 5070 12G Ventus 3X OC at &lt;span class="claim" data-claim-key="listing.N82E16814137940.price_usd" data-claim-value="919.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$919.99&lt;/span>
and the MSI RTX 5070 Ti 16G Shadow 3X OC at &lt;span class="claim" data-claim-key="listing.N82E16814137935.price_usd" data-claim-value="1409.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$1,409.99&lt;/span>
, 53% more.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Test&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5070&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5070 Ti&lt;/th>
&lt;th scope="col" style="text-align: right">Ti lead&lt;/th>
&lt;th scope="col" style="text-align: right">$ per frame, 5070&lt;/th>
&lt;th scope="col" style="text-align: right">$ per frame, Ti&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Test">1080p raster&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">132.6&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">155.4&lt;/td>
&lt;td style="text-align: right" data-label="Ti lead">+17.2%&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, 5070">$6.94&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, Ti">$9.07&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">1440p raster&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">96.4&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">116.8&lt;/td>
&lt;td style="text-align: right" data-label="Ti lead">+21.2%&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, 5070">$9.54&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, Ti">$12.07&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">4K raster&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">54.3&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">68.6&lt;/td>
&lt;td style="text-align: right" data-label="Ti lead">+26.3%&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, 5070">$16.94&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, Ti">$20.55&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">1080p ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">74.1&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">90.4&lt;/td>
&lt;td style="text-align: right" data-label="Ti lead">+22.0%&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, 5070">$12.42&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, Ti">$15.60&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">1440p ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">51.5&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">66.2&lt;/td>
&lt;td style="text-align: right" data-label="Ti lead">+28.5%&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, 5070">$17.86&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, Ti">$21.30&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">4K ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">22.7&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">36.7&lt;/td>
&lt;td style="text-align: right" data-label="Ti lead">+61.7%&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, 5070">$40.53&lt;/td>
&lt;td style="text-align: right" data-label="$ per frame, Ti">$38.42&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The Ti costs 53% more and leads by less than that in five of the six rows, so each of its frames costs more. The exception is 4K ray tracing. There the 5070 averages 22.7 fps in Tom&amp;rsquo;s Hardware&amp;rsquo;s suite against the Ti&amp;rsquo;s 36.7, a lead larger than the price gap, so a Ti frame costs $38.42 against the 5070&amp;rsquo;s $40.53. These are suite averages, and one game can sit anywhere around them. &lt;a href="https://techfuelhq.com/tools/gpu-comparison/?a=GeForce&amp;#43;RTX&amp;#43;5070&amp;amp;b=GeForce&amp;#43;RTX&amp;#43;5070&amp;#43;Ti&amp;amp;res=1440p">The GPU comparison tool&lt;/a> compares the same raster scores for any pair of cards at three resolutions.&lt;/p>
&lt;p>The lead grows with resolution in both modes. For where both cards sit among every other current GPU, the &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/">2026 GPU hierarchy&lt;/a> puts the Ti in its top tier and the 5070 one tier down.&lt;/p>
&lt;h2 id="where-12gb-runs-out">Where 12GB runs out&lt;/h2>
&lt;p>The widest gap in Tom&amp;rsquo;s Hardware&amp;rsquo;s June 24, 2026 averages is 4K with ray tracing, 22.7 fps against 36.7, a 61.7% lead where 4K raster shows 26.3%. Tom&amp;rsquo;s does not attribute it to memory. The 12GB failure the reviews below measured is in one game, Indiana Jones and the Great Circle, which will not run without ray tracing.&lt;/p>
&lt;p>Steven Walton&amp;rsquo;s &lt;a href="https://www.techspot.com/review/2960-nvidia-geforce-rtx-5070/" rel="noopener">RTX 5070 review for TechSpot&lt;/a> (March 4, 2025) ran it with full path tracing and measured 13 fps at 1440p with upscaling, against 47 fps from the RTX 4070 Ti Super. Thirteen frames a second is unplayable. With those settings the game crashes at 4K on a 12GB card and refuses to relaunch until it is started in safe mode with lower settings. Jarred Walton&amp;rsquo;s &lt;a href="https://www.tomshardware.com/pc-components/gpus/nvidia-geforce-rtx-5070-review-founders-edition/5" rel="noopener">RTX 5070 review for Tom&amp;rsquo;s Hardware&lt;/a>, published the same day, says certain games, Indiana Jones among them, can use more than the 12GB on the card.&lt;/p>
&lt;p>For path tracing, skip the 12GB card. At 1440p with path tracing off, the table above decides it.&lt;/p>
&lt;h2 id="the-specs">The specs&lt;/h2>
&lt;p>Both are Blackwell cards and the Ti uses the larger GB203 chip, going by &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5070-family/" rel="noopener">NVIDIA&amp;rsquo;s RTX 5070 family page&lt;/a> and the spec tables in Tom&amp;rsquo;s Hardware&amp;rsquo;s &lt;a href="https://www.tomshardware.com/pc-components/gpus/nvidia-geforce-rtx-5070-review-founders-edition" rel="noopener">RTX 5070&lt;/a> and &lt;a href="https://www.tomshardware.com/pc-components/gpus/nvidia-geforce-rtx-5070-ti-review-asus" rel="noopener">RTX 5070 Ti&lt;/a> reviews.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Spec&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5070&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5070 Ti&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Spec">GPU&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">GB205&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">GB203&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">CUDA cores&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">6,144&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">8,960&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">VRAM&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">12GB GDDR7&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">16GB GDDR7&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Memory bus&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">192-bit&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">256-bit&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Bandwidth&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">672 GB/s&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">896 GB/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Video encoders (NVENC)&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">1&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">2&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Total graphics power&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">250W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">300W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">NVIDIA&amp;rsquo;s recommended PSU&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">650W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">750W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Reference power input&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">2x 8-pin, or one 300W Gen 5 cable&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">2x 8-pin, or one 300W Gen 5 cable&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Launch price&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070">$549&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5070 Ti">$749&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The Ti has 46% more CUDA cores and 33% more bandwidth on NVIDIA&amp;rsquo;s and Tom&amp;rsquo;s Hardware&amp;rsquo;s figures, and it runs 17% to 26% faster from 1080p to 4K in Tom&amp;rsquo;s Hardware&amp;rsquo;s raster averages. The spec sheet overstates the gap. NVIDIA lists two NVENC encoders on the Ti against one on the 5070, all ninth generation. NVIDIA asks for a 650W supply for the 5070 and 750W for the Ti. The &lt;a href="https://techfuelhq.com/tools/psu-wattage-calculator/">PSU wattage calculator&lt;/a> sizes yours.&lt;/p>
&lt;p>NVIDIA&amp;rsquo;s $549 and $749 figures are launch MSRPs, not current retail prices. The dated Newegg prices in the performance table are the ones used for this page&amp;rsquo;s value calculation. An overclocked RTX 5070 may narrow a small part of the gap, but it still has 12GB on a 192-bit bus against the Ti&amp;rsquo;s 16GB on a 256-bit bus; a factory OC does not turn one model into the other.&lt;/p>
&lt;p>An RTX 5070 Ti Laptop GPU is a separate part with its own specifications, so this desktop comparison does not carry over to notebooks.&lt;/p>
&lt;h2 id="the-rx-9070-xt-undercuts-both">The RX 9070 XT undercuts both&lt;/h2>
&lt;p>In Tom&amp;rsquo;s Hardware&amp;rsquo;s June 24, 2026 averages the RX 9070 XT scores 116.5 fps at 1440p raster against the Ti&amp;rsquo;s 116.8. That is a near tie. On November 17, 2026 the cheapest new, in-stock one in Newegg&amp;rsquo;s catalogue, the ASRock RX 9070 XT Steel Legend, cost &lt;span class="claim" data-claim-key="listing.N82E16814930136.price_usd" data-claim-value="999.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$999.99&lt;/span>
, which is $410 less than the Ti and $80 more than the cheapest new 5070.&lt;/p>
&lt;p>With ray tracing the Ti pulls ahead. Tom&amp;rsquo;s Hardware has it at 66.2 fps in 1440p against the 9070 XT&amp;rsquo;s 55.5, 19% ahead, though at $410 more its ray-traced frames still cost more than the 9070 XT&amp;rsquo;s. If you mostly play without ray tracing, I would buy the 9070 XT. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-rx-9070-xt-2026/">RTX 5070 Ti vs RX 9070 XT&lt;/a> comparison covers the feature side and prices it. The rung below is &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rtx-5070-2026/">RTX 5060 Ti vs RTX 5070&lt;/a>.&lt;/p>
&lt;h2 id="dont-step-up-to-a-5080">Don&amp;rsquo;t step up to a 5080&lt;/h2>
&lt;p>The cheapest new, in-stock RTX 5080 in Newegg&amp;rsquo;s catalogue on November 17, 2026, the ZOTAC Gaming RTX 5080 Solid Core OC, cost &lt;span class="claim" data-claim-key="listing.N82E16814500648.price_usd" data-claim-value="2199.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$2,199.99&lt;/span>
, 56% more than the Ti, and in Tom&amp;rsquo;s Hardware&amp;rsquo;s June 24, 2026 raster averages it runs 128.3 fps at 1440p against the Ti&amp;rsquo;s 116.8, which is 9.8% faster, with 12.8% more at 4K. At 1440p, moving from the 5070 to the Ti buys 21% for 53% more money. Moving from the Ti to the 5080 buys 9.8% for 56% more. I would stop at the Ti. The full comparison, with the power log and the local LLM rows, is &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-5080-2026/">RTX 5070 Ti vs RTX 5080&lt;/a>.&lt;/p>
&lt;h2 id="so-which-should-you-buy">So which should you buy?&lt;/h2>
&lt;ul>
&lt;li>For 1440p with path tracing off, the RTX 5070. Its frames cost less in every raster row of the table. Newegg listed the MSI RTX 5070 12G Ventus 3X OC at $919.99 on November 17, 2026. If you would rather have the 5070 inside a finished machine, the &lt;a href="https://techfuelhq.com/articles/best-rtx-5070-prebuilt-gaming-pc-2026/">RTX 5070 prebuilt guide&lt;/a> ranks complete towers.&lt;/li>
&lt;li>For ray tracing at 4K, or path tracing at any resolution, the RTX 5070 Ti. Its 4K ray-traced frames are the cheaper ones, and it has 16GB. At 4K without ray tracing the 5070&amp;rsquo;s frame still costs less ($16.94 against $20.55), so there the Ti buys frame rate, not value. On the 5070 the fix for path tracing is lower settings. Newegg listed the MSI RTX 5070 Ti 16G Shadow 3X OC at $1,409.99 the same day. The &lt;a href="https://techfuelhq.com/articles/best-rtx-5070-ti-prebuilt-gaming-pc-2026/">RTX 5070 Ti prebuilt guide&lt;/a> covers the Ti in a finished machine.&lt;/li>
&lt;li>For raster games at any resolution, price the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-rx-9070-xt-2026/">RX 9070 XT&lt;/a> before either.&lt;/li>
&lt;/ul>
&lt;p>If either price has moved by the time you read this, divide the new price by the card&amp;rsquo;s frame rate in the table for the row you play at.&lt;/p></description></item><item><title>RTX 5070 Ti vs RX 9070 XT: Which GPU Wins in 2026?</title><link>https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-rx-9070-xt-2026/</link><pubDate>Tue, 09 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-rx-9070-xt-2026/</guid><atom:updated>2026-11-18T05:05:34Z</atom:updated><description>&lt;p>&lt;strong>Which card should you buy?&lt;/strong> Three questions, in order. The first yes is your answer; stop there.&lt;/p>
&lt;ol>
&lt;li>Do you play path-traced or heavy ray-traced games, such as Doom: The Dark Ages with path tracing or Indiana Jones with high ray tracing? The Ti is 16% to 22% faster with ray tracing in Tom&amp;rsquo;s Hardware&amp;rsquo;s June 24, 2026 averages, and 63% faster at 1440p in Steven Walton&amp;rsquo;s path-traced Doom test for TechSpot (May 22, 2026). Buy the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-ti-review-2026/">RTX 5070 Ti&lt;/a>.&lt;/li>
&lt;li>Do you need CUDA, NVENC or DLSS Multi Frame Generation for AI tools, video export or streaming? NVIDIA lists two NVENC encoders on the Ti. Buy the RTX 5070 Ti.&lt;/li>
&lt;li>Neither? Buy the &lt;a href="https://techfuelhq.com/gpu-reviews/rx-9070-xt-review-2026/">RX 9070 XT&lt;/a> for raster or lighter ray-traced gaming at 1440p or 4K: a raster tie at 1440p in Tom&amp;rsquo;s Hardware&amp;rsquo;s averages, and $410 less at Newegg on November 17, 2026.&lt;/li>
&lt;/ol>
&lt;p>The RX 9070 XT is the default answer. The 5070 Ti earns its premium only when one of the first two questions is a real yes for you, not a hypothetical one. Both cards above are the cheapest new, in-stock ones under a Newegg item number in Newegg&amp;rsquo;s catalogue on November 17; the &lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU price index&lt;/a> tracks both chips from day to day.&lt;/p>
&lt;h2 id="benchmarks-and-what-each-frame-costs">Benchmarks and what each frame costs&lt;/h2>
&lt;p>The Ti&amp;rsquo;s Newegg price premium exceeds its performance lead in all six of Tom&amp;rsquo;s Hardware&amp;rsquo;s averages below.&lt;/p>
&lt;p>&lt;strong>What the Ti&amp;rsquo;s extra $410 buys.&lt;/strong> Frame rates are averages from &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware&amp;rsquo;s GPU hierarchy&lt;/a> (Jeffrey Kampman, updated June 24, 2026): 11 raster games, four with ray-tracing support, plus four games that require RT or look best with it, at a mix of high and ultra settings on a Ryzen 7 9800X3D. The FPS below come from the numbers in parentheses in its 1080p, 1440p and 4K Ultra columns. Prices are the cheapest new, in-stock cards under a Newegg item number in Newegg&amp;rsquo;s catalogue on November 17, 2026: the MSI RTX 5070 Ti 16G Shadow 3X OC at &lt;span class="claim" data-claim-key="listing.N82E16814137935.price_usd" data-claim-value="1409.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$1,409.99&lt;/span>
and the ASRock RX 9070 XT Steel Legend at &lt;span class="claim" data-claim-key="listing.N82E16814930136.price_usd" data-claim-value="999.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$999.99&lt;/span>
. The Ti costs 41% more.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Test&lt;/th>
&lt;th scope="col">RTX 5070 Ti&lt;/th>
&lt;th scope="col">RX 9070 XT&lt;/th>
&lt;th scope="col">Ti lead&lt;/th>
&lt;th scope="col">$ per frame, Ti&lt;/th>
&lt;th scope="col">$ per frame, 9070 XT&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Test">1080p raster&lt;/td>
&lt;td data-label="RTX 5070 Ti">155.4&lt;/td>
&lt;td data-label="RX 9070 XT">156.6&lt;/td>
&lt;td data-label="Ti lead">-0.8%&lt;/td>
&lt;td data-label="$ per frame, Ti">$9.07&lt;/td>
&lt;td data-label="$ per frame, 9070 XT">$6.39&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">1440p raster&lt;/td>
&lt;td data-label="RTX 5070 Ti">116.8&lt;/td>
&lt;td data-label="RX 9070 XT">116.5&lt;/td>
&lt;td data-label="Ti lead">+0.3%&lt;/td>
&lt;td data-label="$ per frame, Ti">$12.07&lt;/td>
&lt;td data-label="$ per frame, 9070 XT">$8.58&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">4K raster&lt;/td>
&lt;td data-label="RTX 5070 Ti">68.6&lt;/td>
&lt;td data-label="RX 9070 XT">65.8&lt;/td>
&lt;td data-label="Ti lead">+4.3%&lt;/td>
&lt;td data-label="$ per frame, Ti">$20.55&lt;/td>
&lt;td data-label="$ per frame, 9070 XT">$15.20&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">1080p ray tracing&lt;/td>
&lt;td data-label="RTX 5070 Ti">90.4&lt;/td>
&lt;td data-label="RX 9070 XT">77.8&lt;/td>
&lt;td data-label="Ti lead">+16.2%&lt;/td>
&lt;td data-label="$ per frame, Ti">$15.60&lt;/td>
&lt;td data-label="$ per frame, 9070 XT">$12.85&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">1440p ray tracing&lt;/td>
&lt;td data-label="RTX 5070 Ti">66.2&lt;/td>
&lt;td data-label="RX 9070 XT">55.5&lt;/td>
&lt;td data-label="Ti lead">+19.3%&lt;/td>
&lt;td data-label="$ per frame, Ti">$21.30&lt;/td>
&lt;td data-label="$ per frame, 9070 XT">$18.02&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">4K ray tracing&lt;/td>
&lt;td data-label="RTX 5070 Ti">36.7&lt;/td>
&lt;td data-label="RX 9070 XT">30.1&lt;/td>
&lt;td data-label="Ti lead">+21.9%&lt;/td>
&lt;td data-label="$ per frame, Ti">$38.42&lt;/td>
&lt;td data-label="$ per frame, 9070 XT">$33.22&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>At Newegg&amp;rsquo;s November 17, 2026 prices the RX 9070 XT&amp;rsquo;s frame is cheaper in every row. At 1440p without ray tracing a Ti frame costs 41% more. Even in the 4K ray tracing row, the Ti&amp;rsquo;s best, it costs $38.42 against $33.22. These are suite averages, and one game can sit far from them. To set either card against another GPU at three resolutions, open the &lt;a href="https://techfuelhq.com/tools/gpu-comparison/?a=GeForce&amp;#43;RTX&amp;#43;5070&amp;#43;Ti&amp;amp;b=Radeon&amp;#43;RX&amp;#43;9070&amp;#43;XT&amp;amp;res=1440p">GPU comparison tool with both cards loaded&lt;/a>.&lt;/p>
&lt;p>Steven Walton&amp;rsquo;s &lt;a href="https://www.techspot.com/review/3130-geforce-rtx-5070-ti-vs-radeon-rx-9070-xt/" rel="noopener">RTX 5070 Ti vs RX 9070 XT test&lt;/a> for TechSpot (May 22, 2026) ran 52 games, each at two presets with ray tracing on in some, on a Ryzen 7 9800X3D. The 5070 Ti came out 2 fps ahead at 1440p, about 1.4%, and averaged 84 fps at 4K against the Radeon&amp;rsquo;s 81 fps, roughly a 4% lead. TechSpot&amp;rsquo;s 55-game test a year earlier had the Radeon about 5% behind at both resolutions. With ray tracing disabled, TechSpot says, the 9070 XT consistently beats the 5070 Ti at 1440p.&lt;/p>
&lt;p>Weighing the plain RTX 5070 instead? The cheapest new one in Newegg&amp;rsquo;s catalogue on November 17, 2026 was the MSI RTX 5070 12G Ventus 3X OC at &lt;span class="claim" data-claim-key="listing.N82E16814137940.price_usd" data-claim-value="919.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$919.99&lt;/span>
, $80 less than the 9070 XT. In Tom&amp;rsquo;s Hardware&amp;rsquo;s June 24, 2026 GPU hierarchy averages the 9070 XT is 21% faster at 1440p without ray tracing (116.5 against 96.4 fps) and 8% faster with it (55.5 against 51.5). For 9% more money, the 9070 XT&amp;rsquo;s raster frames cost less. The NVIDIA step between those two is in &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-vs-5070-ti-2026/">RTX 5070 vs RTX 5070 Ti&lt;/a>. One step down in AMD&amp;rsquo;s range, the &lt;a href="https://techfuelhq.com/gpu-reviews/rx-9070-review-2026/">RX 9070 review&lt;/a> covers the non-XT card.&lt;/p>
&lt;h2 id="where-the-rtx-5070-ti-earns-its-price">Where the RTX 5070 Ti earns its price&lt;/h2>
&lt;p>In Tom&amp;rsquo;s Hardware&amp;rsquo;s June 24, 2026 GPU hierarchy averages the Ti is 16% faster at 1080p, 19% at 1440p (66.2 against 55.5 fps) and 22% at 4K with ray tracing on. The heavy cases are far wider. In Steven Walton&amp;rsquo;s May 22, 2026 52-game test for TechSpot, the Ti ran path-traced Doom: The Dark Ages at 31 fps at 1440p, 63% faster than the 9070 XT and still short of playable, and it led by 56% at 1440p in Indiana Jones and the Great Circle with high ray tracing.&lt;/p>
&lt;p>It is not a sweep. TechSpot found the 9070 XT level with the Ti or ahead with ray tracing on in Pragmata, Resident Evil Requiem and Monster Hunter Wilds. If those are your games, the average lead does not apply to you.&lt;/p>
&lt;p>TechSpot also saw the Ti pull ahead more often at 4K and says the likely reason is its 40% more memory bandwidth from GDDR7, 896 GB/s against 640.&lt;/p>
&lt;p>For video and AI work, &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5070-family/" rel="noopener">NVIDIA&amp;rsquo;s spec page&lt;/a> lists two ninth-generation NVENC encoders on the Ti, plus CUDA support. For streaming, video export or local AI, I would buy the Ti.&lt;/p>
&lt;h2 id="dlss-or-fsr-redstone">DLSS or FSR Redstone&lt;/h2>
&lt;p>Both cards upscale with machine learning and both generate frames. &lt;a href="https://www.nvidia.com/en-us/geforce/technologies/dlss/" rel="noopener">NVIDIA&amp;rsquo;s DLSS page&lt;/a> says Multi Frame Generation on RTX 50 cards can generate up to five frames per rendered frame, and DLSS 4.5 added Dynamic Multi Frame Generation and a second-generation transformer model for Super Resolution and Ray Reconstruction. DLSS 5 adds 3D-Guided Neural Rendering on RTX 50 cards, which uses AI to add lighting and materials to a scene, tuned per game by its developers. On the AMD side, &lt;a href="https://www.amd.com/en/products/graphics/technologies/fidelityfx/super-resolution.html" rel="noopener">AMD&amp;rsquo;s FSR page&lt;/a> groups FSR Upscaling (the renamed FSR 4), FSR Frame Generation, Ray Regeneration and Radiance Caching as FSR Redstone on RX 9000 cards; FSR Upscaling 4.1 also runs on RX 6000 and RX 7000 cards. In games with neither, AMD&amp;rsquo;s driver-level &lt;a href="https://www.amd.com/en/products/software/adrenalin/afmf.html" rel="noopener">AFMF 2.1&lt;/a> runs on RX 6000 cards and newer and adds generated frames across thousands of games in DirectX 11, DirectX 12, Vulkan and OpenGL.&lt;/p>
&lt;p>At Newegg&amp;rsquo;s November 17, 2026 prices, I would not pay the extra $410 for frame generation alone; both cards have a version of it now.&lt;/p>
&lt;h2 id="specs-power-and-psu">Specs, power and PSU&lt;/h2>
&lt;p>From &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5070-family/" rel="noopener">NVIDIA&amp;rsquo;s RTX 5070 family page&lt;/a>, &lt;a href="https://www.amd.com/en/products/graphics/desktops/radeon/9000-series/amd-radeon-rx-9070xt.html" rel="noopener">AMD&amp;rsquo;s RX 9070 XT page&lt;/a> and the spec table in Jarred Walton&amp;rsquo;s &lt;a href="https://www.tomshardware.com/pc-components/gpus/nvidia-geforce-rtx-5070-ti-review-asus" rel="noopener">RTX 5070 Ti review for Tom&amp;rsquo;s Hardware&lt;/a> (February 19, 2025). MSRP figures are from &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware&amp;rsquo;s GPU hierarchy&lt;/a> (updated June 24, 2026):&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Spec&lt;/th>
&lt;th scope="col">RTX 5070 Ti&lt;/th>
&lt;th scope="col">RX 9070 XT&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Spec">GPU&lt;/td>
&lt;td data-label="RTX 5070 Ti">GB203 (Blackwell)&lt;/td>
&lt;td data-label="RX 9070 XT">RDNA 4&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Shader units&lt;/td>
&lt;td data-label="RTX 5070 Ti">8,960 CUDA cores&lt;/td>
&lt;td data-label="RX 9070 XT">4,096 stream processors&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Ray tracing units&lt;/td>
&lt;td data-label="RTX 5070 Ti">70 fourth-generation RT cores&lt;/td>
&lt;td data-label="RX 9070 XT">64 ray accelerators&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Memory&lt;/td>
&lt;td data-label="RTX 5070 Ti">16GB GDDR7, 256-bit&lt;/td>
&lt;td data-label="RX 9070 XT">16GB GDDR6, 256-bit&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Bandwidth&lt;/td>
&lt;td data-label="RTX 5070 Ti">896 GB/s&lt;/td>
&lt;td data-label="RX 9070 XT">640 GB/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Rated power&lt;/td>
&lt;td data-label="RTX 5070 Ti">300W&lt;/td>
&lt;td data-label="RX 9070 XT">304W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Recommended PSU&lt;/td>
&lt;td data-label="RTX 5070 Ti">750W&lt;/td>
&lt;td data-label="RX 9070 XT">750W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Reference power input&lt;/td>
&lt;td data-label="RTX 5070 Ti">2x 8-pin, or one 300W Gen 5 cable&lt;/td>
&lt;td data-label="RX 9070 XT">2x 8-pin&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">MSRP (Tom&amp;rsquo;s Hardware)&lt;/td>
&lt;td data-label="RTX 5070 Ti">$749.99&lt;/td>
&lt;td data-label="RX 9070 XT">$599.99&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Shader counts are not comparable across the two architectures; the benchmark table is the comparison.&lt;/p>
&lt;p>The spec sheets put the two cards 4W apart, though NVIDIA rates total graphics power and AMD typical board power. TechSpot, citing its launch-day testing, says the RX 9070 XT typically consumes about 20% more power than the 5070 Ti. Both vendors recommend 750W for the reference cards. Check the exact card before buying a PSU. Board-partner requirements can be higher. If you buy the 9070 XT, the &lt;a href="https://techfuelhq.com/articles/rx-9070-xt-undervolt-2026/">RX 9070 XT undervolt guide&lt;/a> covers bringing that draw down, the &lt;a href="https://techfuelhq.com/articles/rtx-5070-ti-undervolt-2026/">RTX 5070 Ti undervolt guide&lt;/a> does the same for the NVIDIA card, and the &lt;a href="https://techfuelhq.com/tools/psu-wattage-calculator/">PSU wattage calculator&lt;/a> sizes the rest of the build.&lt;/p>
&lt;h2 id="which-should-you-buy">Which should you buy?&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>The RX 9070 XT&lt;/strong> for raster gaming at 1440p or 4K, and for ray tracing in the games where TechSpot found it level. Newegg listed the ASRock RX 9070 XT Steel Legend at $999.99 on November 17, 2026; both retailers&amp;rsquo; links are in the box near the top of the page.&lt;/li>
&lt;li>&lt;strong>The RTX 5070 Ti&lt;/strong> if you play path-traced games, stream or export on NVENC, or run CUDA software. Newegg listed the MSI RTX 5070 Ti 16G Shadow 3X OC at $1,409.99 the same day.&lt;/li>
&lt;li>&lt;strong>Not the RTX 5080.&lt;/strong> On November 17, 2026 Newegg listed the cheapest new in-stock RTX 5080, the ZOTAC Gaming RTX 5080 Solid Core OC, at $2,199.99, 56% more than the Ti, for 128.3 fps against 116.8 at 1440p in Tom&amp;rsquo;s Hardware&amp;rsquo;s June 24, 2026 GPU hierarchy raster averages, 9.8% more. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-5080-2026/">RTX 5070 Ti vs RTX 5080&lt;/a> comparison has the full case. If you want it anyway, my &lt;a href="https://techfuelhq.com/gpu-reviews/rog-astral-rtx-5080-oc-review-2026/">ROG Astral RTX 5080 OC review&lt;/a> has my own 4K runs on that GPU.&lt;/li>
&lt;/ul>
&lt;p>Both cards are S tier in my &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/">2026 GPU hierarchy&lt;/a>, next to each other. One price tier down, the same NVIDIA-or-AMD choice is in the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/">RTX 5060 Ti vs RX 9060 XT 1440p showdown&lt;/a>.&lt;/p></description></item><item><title>RTX 5060 Ti vs RX 9060 XT: The 1440p Showdown, 8GB vs 16GB (2026)</title><link>https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/</link><pubDate>Wed, 06 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/</guid><atom:updated>2026-11-18T05:05:34Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · The 30-second verdict&lt;/p>
&lt;ul>
&lt;li>&lt;strong>1440p gaming:&lt;/strong> Buy the &lt;strong>RTX 5060 Ti 16GB&lt;/strong>. It averaged 9% more frames (73.4 fps against 67.3) at 1440p Ultra in Tom's Hardware's June 24, 2026 hierarchy, and on November 17, 2026 Newegg listed it $70 above the cheapest RX 9060 XT 16GB ($799.99 against $729.99), so a frame costs about the same on either ($10.90 against $10.85) and the GeForce adds its ray tracing and CUDA lead.&lt;/li>
&lt;li>&lt;strong>Ray tracing, local AI or CUDA apps:&lt;/strong> the &lt;strong>RTX 5060 Ti 16GB&lt;/strong> again. It led by 25% across Tom's eight ray-traced games, and an RTX 5060 Ti generated text about a third faster in llama.cpp's Vulkan scoreboard.&lt;/li>
&lt;li>&lt;strong>Linux daily driver, or a supply under 600 W:&lt;/strong> the &lt;strong>RX 9060 XT 16GB&lt;/strong>, on the in-kernel amdgpu driver (Linux 6.14 and Mesa 25.0 or newer). AMD's minimum PSU for it is 450 W; NVIDIA asks 600 W for the 5060 Ti.&lt;/li>
&lt;li>&lt;strong>Do not buy for 1440p:&lt;/strong> either 8GB card. The cheapest 8GB RTX 5060 Ti was $529.99, and at 4K it averages less than both 16GB cards.&lt;/li>
&lt;li>&lt;strong>One rung up:&lt;/strong> the RTX 5070 is 31% faster at 1440p for $120 more than the 16GB 5060 Ti; the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rtx-5070-2026/">RTX 5060 Ti vs RTX 5070 comparison&lt;/a> weighs it.&lt;/li>
&lt;/ul>
&lt;p>Prices: Newegg's affiliate catalogue for November 17, 2026, the cheapest new in-stock card under a Newegg item number. Frame rates and power: TechSpot, Tom's Hardware and Club386, each named where it appears.&lt;/p>
&lt;/div>
&lt;p>A year after both cards shipped, the question in my inbox is the same one I asked when I bought my own: with both cards now selling above MSRP in the 2026 memory crunch, which 16GB mid-range card is the one for a 1440p build in 2026? I&amp;rsquo;ve logged hours on both — an &lt;a href="https://investor.nvidia.com/news/press-release-details/2025/NVIDIA-Blackwell-GeForce-RTX-Arrives-for-Every-Gamer-Starting-at-299/default.aspx" rel="noopener">RTX 5060 Ti 16GB at $429 MSRP&lt;/a> and an &lt;a href="https://www.tomshardware.com/pc-components/gpus/amd-radeon-rx-9060-xt-launches-on-june-5-starting-at-usd299" rel="noopener">RX 9060 XT 16GB at $349 MSRP&lt;/a> — and the result is more interesting than either side&amp;rsquo;s marketing.&lt;/p>
&lt;p>This is what I&amp;rsquo;ve found running both through a sane game lineup at native 1440p, with upscaling on, ray tracing on, and as inference cards on the side.&lt;/p>
&lt;h2 id="what-each-version-costs-per-1440p-frame">What each version costs per 1440p frame&lt;/h2>
&lt;p>Both cards ship in 8GB and 16GB versions. In Newegg&amp;rsquo;s affiliate catalogue on November 17, 2026, the cheapest new 16GB &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-review-2026/">RTX 5060 Ti&lt;/a> cost $270 more than the cheapest 8GB one, the cheapest new 16GB &lt;a href="https://techfuelhq.com/gpu-reviews/rx-9060-xt-review-2026/">RX 9060 XT&lt;/a> cost $70 less than the 16GB GeForce, and no new 8GB RX 9060 XT was listed.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Version&lt;/th>
&lt;th scope="col">Newegg, Nov 17, 2026&lt;/th>
&lt;th scope="col" style="text-align: right">1440p Ultra average&lt;/th>
&lt;th scope="col" style="text-align: right">Dollars per 1440p frame&lt;/th>
&lt;th scope="col" style="text-align: right">4K Ultra average&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Version">RTX 5060 Ti 16GB&lt;/td>
&lt;td data-label="Newegg, Nov 17, 2026">&lt;span class="claim" data-claim-key="listing.N82E16814133993.price_usd" data-claim-value="799.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$799.99&lt;/span>
, PNY Dual Fan OC&lt;/td>
&lt;td style="text-align: right" data-label="1440p Ultra average">73.4 fps&lt;/td>
&lt;td style="text-align: right" data-label="Dollars per 1440p frame">$10.90&lt;/td>
&lt;td style="text-align: right" data-label="4K Ultra average">40.2 fps&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Version">RX 9060 XT 16GB&lt;/td>
&lt;td data-label="Newegg, Nov 17, 2026">&lt;span class="claim" data-claim-key="listing.N82E16814980004.price_usd" data-claim-value="729.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$729.99&lt;/span>
, Yeston Sakura&lt;/td>
&lt;td style="text-align: right" data-label="1440p Ultra average">67.3 fps&lt;/td>
&lt;td style="text-align: right" data-label="Dollars per 1440p frame">$10.85&lt;/td>
&lt;td style="text-align: right" data-label="4K Ultra average">35.2 fps&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Version">RTX 5060 Ti 8GB&lt;/td>
&lt;td data-label="Newegg, Nov 17, 2026">&lt;span class="claim" data-claim-key="listing.N82E16814500638.price_usd" data-claim-value="529.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$529.99&lt;/span>
, ZOTAC Twin Edge OC&lt;/td>
&lt;td style="text-align: right" data-label="1440p Ultra average">68.6 fps&lt;/td>
&lt;td style="text-align: right" data-label="Dollars per 1440p frame">$7.73&lt;/td>
&lt;td style="text-align: right" data-label="4K Ultra average">28.1 fps&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Version">RX 9060 XT 8GB&lt;/td>
&lt;td data-label="Newegg, Nov 17, 2026">not listed new&lt;/td>
&lt;td style="text-align: right" data-label="1440p Ultra average">62.5 fps&lt;/td>
&lt;td style="text-align: right" data-label="Dollars per 1440p frame">n/a&lt;/td>
&lt;td style="text-align: right" data-label="4K Ultra average">29.7 fps&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Each price is the cheapest new, in-stock card under a Newegg item number in Newegg&amp;rsquo;s catalogue that day whose title or manufacturer part number names the memory size (the Yeston&amp;rsquo;s part number, YT RX-96XT-16D6-SOA-11PCI, carries 16D6); open-box listings were skipped. The frame rates come from Tom&amp;rsquo;s Hardware&amp;rsquo;s GPU hierarchy, last updated June 24, 2026: the geometric mean of 11 games at Tom&amp;rsquo;s &amp;lsquo;Ultra&amp;rsquo; setting (a mix of high and ultra per game), raster only, on a Ryzen 7 9800X3D; dollars per frame is the price divided by the 1440p average.&lt;/p>
&lt;p>Between the two 16GB cards, a frame costs the same within a nickel, so the GeForce&amp;rsquo;s 9% lead, its 25% ray tracing lead and CUDA make it the gaming pick at these prices for $70 more. On averages the 8GB RTX 5060 Ti buys the cheapest 1440p frame. The 4K column shows what that average hides. Once memory runs short, the 8GB GeForce drops behind both 16GB cards. It even trails the 8GB Radeon at 4K. &lt;a href="#the-8gb-trap-which-sku-to-buy">TechSpot&amp;rsquo;s 1440p tests below&lt;/a> find single games where 8GB collapses. I would take either 16GB card over the 8GB RTX 5060 Ti.&lt;/p>
&lt;p>Coming from an RTX 3060 12GB, which averaged 41.9 fps at 1440p in the same suite, the RX 9060 XT 16GB is 67.3 / 41.9 = 1.61× and the RTX 5060 Ti 16GB is 73.4 / 41.9 = 1.75×. The &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/#if-you-own-one-of-these">upgrade table in my GPU hierarchy&lt;/a> has ten more starting cards, the &lt;a href="https://techfuelhq.com/tools/gpu-comparison/?a=GeForce&amp;#43;RTX&amp;#43;5060&amp;#43;Ti&amp;#43;16GB&amp;amp;b=Radeon&amp;#43;RX&amp;#43;9060&amp;#43;XT&amp;#43;16GB&amp;amp;res=1440p">GPU comparison tool&lt;/a> puts these two side by side at any resolution, and the &lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU price index&lt;/a> tracks both 16GB cards from day to day.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;p>&lt;strong>RTX 5060 Ti 16GB, the gaming and CUDA pick:&lt;/strong>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=PNY&amp;#43;RTX&amp;#43;5060&amp;#43;Ti&amp;#43;16GB&amp;#43;Dual&amp;#43;Fan&amp;#43;OC&amp;#43;VCG5060T16DFXPB1-O&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fpny-technologies-inc-rtx-5060-ti-16gb-dual-fan-oc-geforce-rtx-5060-ti-graphics-card-double-fans%2Fp%2FN82E16814133993%3Fitem%3DN82E16814133993" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>&lt;strong>RX 9060 XT 16GB, for Linux or a supply under 600 W:&lt;/strong>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Yeston&amp;#43;Sakura&amp;#43;Radeon&amp;#43;RX&amp;#43;9060&amp;#43;XT&amp;#43;16GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fyeston-rx9060xt-radeon-rx-9060-xt-16gb-graphics-card-triple-fans%2Fp%2FN82E16814980004%3Fitem%3DN82E16814980004" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="how-i-tested">How I tested&lt;/h2>
&lt;p>Both cards passed through the home bench in St. Louis County, MO during the 2024–2025 testing period. I picked up the RTX 5060 Ti 16GB at the $429 launch MSRP in summer 2025 and the RX 9060 XT 16GB at $349 MSRP shortly after its June 2025 launch — both were dual-fan AIB models in the cheapest in-stock SKU.&lt;/p>
&lt;p>Most of that gear has since been sold or retired (see the &lt;a href="https://techfuelhq.com/colophon/">Colophon&lt;/a> for the timeline). The benchmark numbers on this page are aggregated from the public reviews I cite alongside them (TechSpot, Tom&amp;rsquo;s Hardware, Club386).&lt;/p>
&lt;p>The qualitative observations on thermals, driver behavior and Linux support are firsthand from running both cards in my own builds between July 2025 and April 2026. Current first-party GPU bench data is in the &lt;a href="https://techfuelhq.com/data/">TechFuelHQ Open Bench Datasets&lt;/a> directory.&lt;/p>
&lt;h2 id="spec-sheet-head-to-head">Spec sheet head-to-head&lt;/h2>
&lt;p>The cards are closer than the marketing suggests, but they&amp;rsquo;re not the same architecture. Sources: &lt;a href="https://www.techspot.com/review/2996-amd-radeon-9060-xt/" rel="noopener">TechSpot&amp;rsquo;s day-one tables&lt;/a>, &lt;a href="https://www.club386.com/amd-radeon-rx-9060-xt-16gb-vs-nvidia-geforce-rtx-5060-ti-16gb/" rel="noopener">Club386&amp;rsquo;s spec breakdown&lt;/a>, &lt;a href="https://www.amd.com/en/products/graphics/desktops/radeon/9000-series/amd-radeon-rx-9060xt.html" rel="noopener">AMD&amp;rsquo;s official 9060 XT page&lt;/a> and &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5060-family/" rel="noopener">NVIDIA&amp;rsquo;s RTX 5060 family page&lt;/a>, the last two read November 18, 2026.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Spec&lt;/th>
&lt;th scope="col">RTX 5060 Ti 16GB&lt;/th>
&lt;th scope="col">RX 9060 XT 16GB&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Spec">Architecture&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">Blackwell GB206&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">RDNA 4 Navi 44&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Process&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">TSMC 4N&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">TSMC N4P&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Shaders / SPs&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">4,608&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">2,048&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">RT cores&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">36 (4th gen)&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">32 (3rd gen)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">AI / Tensor&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">144 (5th gen)&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">64 (2nd gen)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Boost clock&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">2,572 MHz&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">3,130 MHz&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Memory&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">16 GB GDDR7&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">16 GB GDDR6&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Bus&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">128-bit&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">128-bit&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Bandwidth&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">448 GB/s&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">320 GB/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Infinity / L2 cache&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">not in TechSpot&amp;rsquo;s table&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">32 MB Infinity&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">TBP&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">180 W&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">160 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Vendor PSU figure&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">600 W required system power (NVIDIA)&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">450 W minimum PSU (AMD)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Power connector&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">1x 8-pin, or one 300 W Gen 5 cable&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">1x 8-pin&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">PCIe&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">5.0 x8&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">5.0 x16&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Release&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">On sale April 16, 2025 (&lt;a href="https://investor.nvidia.com/news/press-release-details/2025/NVIDIA-Blackwell-GeForce-RTX-Arrives-for-Every-Gamer-Starting-at-299/default.aspx" rel="noopener">NVIDIA&lt;/a>)&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">Announced May 20, 2025 (&lt;a href="https://ir.amd.com/news-events/press-releases/detail/1253/amd-introduces-new-radeon-graphics-cards-and-ryzen-threadripper-processors-at-computex-2025" rel="noopener">AMD&lt;/a>); on sale June 5, 2025 (&lt;a href="https://www.tomshardware.com/pc-components/gpus/amd-radeon-rx-9060-xt-launches-on-june-5-starting-at-usd299" rel="noopener">Tom&amp;rsquo;s Hardware&lt;/a>)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Launch MSRP&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">$429&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">$349&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Spec">Newegg, Nov 17, 2026&lt;/td>
&lt;td data-label="RTX 5060 Ti 16GB">$799.99&lt;/td>
&lt;td data-label="RX 9060 XT 16GB">$729.99&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>NVIDIA more than doubles the shader count, which on paper looks like a blowout. It is not one. Navi 44 answers with a 3.13 GHz boost, &lt;a href="https://www.club386.com/amd-radeon-rx-9060-xt-16gb-vs-nvidia-geforce-rtx-5060-ti-16gb/" rel="noopener">22% higher than the 5060 Ti&amp;rsquo;s clock&lt;/a>, and the two land within 10% of each other in raster.&lt;/p>
&lt;p>The other surprise: the 5060 Ti runs only 8 PCIe lanes versus the 9060 XT&amp;rsquo;s 16. TechSpot&amp;rsquo;s PCIe tests found the slot generation makes little difference while a game stays within VRAM, and its 16GB 5060 Ti ran well even on PCIe 3.0. The 8GB model is the one that suffers once it overflows.&lt;/p>
&lt;p>At launch NVIDIA asked $80 more. In Newegg&amp;rsquo;s November 17, 2026 catalogue the cheapest 16GB GeForce cost $70 more than the cheapest 16GB Radeon, down from $280 on September 26. If your supply is under 600 W, the Radeon is the card that meets its vendor&amp;rsquo;s figure, though the power section below shows it drawing more in measured games.&lt;/p>
&lt;h2 id="what-each-review-measured-at-1440p">What each review measured at 1440p&lt;/h2>
&lt;p>The two TechSpot tests and Tom&amp;rsquo;s hierarchy put the RTX 5060 Ti 16GB ahead at native 1440p. How far depends on the game list and the date.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Review&lt;/th>
&lt;th scope="col">Published&lt;/th>
&lt;th scope="col">Test&lt;/th>
&lt;th scope="col" style="text-align: right">5060 Ti 16GB ahead&lt;/th>
&lt;th scope="col">As the review prints it&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Review">&lt;a href="https://www.techspot.com/review/2996-amd-radeon-9060-xt/" rel="noopener">TechSpot, RX 9060 XT 16GB review&lt;/a> (Steven Walton)&lt;/td>
&lt;td data-label="Published">June 4, 2025&lt;/td>
&lt;td data-label="Test">18 games, native 1440p&lt;/td>
&lt;td style="text-align: right" data-label="5060 Ti 16GB ahead">1%&lt;/td>
&lt;td data-label="As the review prints it">71 fps against 70&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Review">&lt;a href="https://www.techspot.com/review/3019-nvidia-5060-ti-vs-amd-9060-xt-with-dlss-fsr/" rel="noopener">TechSpot, DLSS 4 vs FSR 4 retest&lt;/a> (Tim Schiesser)&lt;/td>
&lt;td data-label="Published">July 29, 2025&lt;/td>
&lt;td data-label="Test">15 games, native 1440p&lt;/td>
&lt;td style="text-align: right" data-label="5060 Ti 16GB ahead">9%&lt;/td>
&lt;td data-label="As the review prints it">&amp;ldquo;9% faster on average at native 1440p&amp;rdquo;&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Review">&lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware, GPU hierarchy&lt;/a> (Jeffrey Kampman)&lt;/td>
&lt;td data-label="Published">June 24, 2026&lt;/td>
&lt;td data-label="Test">11 games, 1440p Ultra&lt;/td>
&lt;td style="text-align: right" data-label="5060 Ti 16GB ahead">9%&lt;/td>
&lt;td data-label="As the review prints it">73.4 fps against 67.3&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>All three ran on a Ryzen 7 9800X3D, and each uses its own game list and presets. TechSpot&amp;rsquo;s retest used the Asus Prime version of both cards. &lt;a href="https://www.tomshardware.com/pc-components/gpus/amd-radeon-rx-9060-xt-16gb-review/8" rel="noopener">Tom&amp;rsquo;s Hardware&amp;rsquo;s June 10, 2025 review&lt;/a> summed it up as &amp;ldquo;about 7% higher performance&amp;rdquo; for the 5060 Ti 16GB, without tying the figure to one resolution. The launch-week tie is the outlier.&lt;/p>
&lt;p>Per game, the lead swings. In TechSpot&amp;rsquo;s retest the 5060 Ti was 29% ahead in Stellar Blade and 45% ahead in Hunt: Showdown at native 1440p, while in Star Wars Outlaws the 9060 XT pulled 10% ahead once both cards used Quality upscaling. If one game decides your purchase, open that game&amp;rsquo;s chart in the reviews linked above.&lt;/p>
&lt;h2 id="the-8gb-trap-which-sku-to-buy">The 8GB trap: which SKU to buy&lt;/h2>
&lt;p>Both cards ship in 8GB and 16GB flavors under nearly the same name, and at 1440p that choice matters more than the brand. The launch prices were $429 and $379 for the RTX 5060 Ti and $349 and $299 for the RX 9060 XT; on November 17, 2026 Newegg listed the GeForce pair at $799.99 and $529.99 and the 16GB Radeon at $729.99, with no new 8GB Radeon listed.&lt;/p>
&lt;p>The mechanism is simple. While a game stays under 8 GB, both versions perform the same in TechSpot&amp;rsquo;s tests. The moment a game needs more, the 8GB card starts evicting textures and streaming them across the PCIe bus from system RAM. Frame times spike and 1% lows crater. A short benchmark run can miss it.&lt;/p>
&lt;p>&lt;a href="https://www.techspot.com/review/3003-amd-radeon-9060-xt-pcie-benchmark/" rel="noopener">TechSpot isolated it on the 9060 XT&lt;/a> (June 19, 2025), 8GB against 16GB at 1440p with quality upscaling.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>F1 25 (High):&lt;/strong> with both cards on PCIe 3.0, the 16GB card delivered nearly 50% higher average frame rates and 63% higher 1% lows.&lt;/li>
&lt;li>&lt;strong>Monster Hunter Wilds (Ultra):&lt;/strong> the 16GB card averaged over 60 fps on PCIe 3.0, twice the 8GB card, and the 8GB card&amp;rsquo;s 1% lows fell to &lt;strong>2 fps even on PCIe 5.0&lt;/strong>.&lt;/li>
&lt;li>&lt;strong>Spider-Man 2:&lt;/strong> the 16GB card on PCIe 3.0 was 26% faster on average and 38% faster in 1% lows than the 8GB card on PCIe 5.0.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://www.techspot.com/review/3004-nvidia-rtx-5060-ti-pcie-benchmark/" rel="noopener">TechSpot ran the same test on the RTX 5060 Ti&lt;/a> (June 28, 2025, upscaled 1440p). In Dragon Age: The Veilguard the 16GB card on PCIe 3.0 was 68% faster on average and 119% faster in 1% lows than the 8GB card on PCIe 5.0. In Monster Hunter Wilds at the Ultra preset (TechSpot&amp;rsquo;s upscaled-1440p suite; the section itself names no resolution), the 16GB card averaged 84 fps and the 8GB card 34 fps, with 1% lows of 16 fps; TechSpot found the PCIe generation made little difference there.&lt;/p>
&lt;p>The 128-bit memory bus and the PCIe link are different specifications, and Sapphire lists its &lt;a href="https://www.sapphiretech.com/en/consumer/pulse-radeon-rx-9060-xt-8g-gddr6" rel="noopener">Pulse RX 9060 XT OC 8GB, SKU 11350-04-20G&lt;/a>, with a &lt;strong>PCIe 5.0 x16&lt;/strong> interface, and AMD&amp;rsquo;s &lt;a href="https://www.amd.com/en/products/graphics/desktops/radeon/9000-series/amd-radeon-rx-9060xt.html" rel="noopener">RX 9060 XT page&lt;/a> lists the same bus. An older PCIe generation can compound the penalty when the 8GB card runs out of VRAM. The &lt;a href="https://techfuelhq.com/articles/rtx-5060-ti-8gb-vs-16gb-2026/">RTX 5060 Ti 8GB vs 16GB comparison&lt;/a> goes further into the GeForce pair.&lt;/p>
&lt;p>&lt;strong>The call:&lt;/strong> at 1440p, buy the 16GB version of whichever card you choose. On November 17 the 16GB GeForce cost $270 more than the 8GB one at Newegg, and the 16GB version was the only RX 9060 XT listed new.&lt;/p>
&lt;h2 id="ray-tracing-reality-check">Ray tracing reality check&lt;/h2>
&lt;p>Ray tracing widens the gap. In Tom&amp;rsquo;s Hardware&amp;rsquo;s June 24, 2026 hierarchy, eight ray-traced games at 1440p Ultra with no upscaling, the RTX 5060 Ti 16GB averaged 38.9 fps against 31.0 for the RX 9060 XT 16GB, 25% ahead. &lt;a href="https://www.techspot.com/review/2996-amd-radeon-9060-xt/" rel="noopener">TechSpot&amp;rsquo;s launch review&lt;/a> had the Radeon &amp;ldquo;20% slower than the 5060 Ti in our ray tracing tests&amp;rdquo; at 1080p output, with upscaling in several games (June 4, 2025).&lt;/p>
&lt;p>&lt;a href="https://www.techspot.com/review/3019-nvidia-5060-ti-vs-amd-9060-xt-with-dlss-fsr/" rel="noopener">TechSpot also tested Ratchet &amp;amp; Clank: Rift Apart&lt;/a> on July 29, 2025 at 1440p, highest preset, ray tracing on High. The RTX 5060 Ti 16GB was 14% faster across the tested upscaling modes, and the RX 9060 XT 16GB still averaged &lt;strong>75 fps with FSR 4 Quality&lt;/strong>. Ray tracing on the Radeon is playable at those settings. It is slower in every average.&lt;/p>
&lt;h2 id="dlss-4-vs-fsr-4">DLSS 4 vs FSR 4&lt;/h2>
&lt;p>&lt;a href="https://www.techspot.com/review/3019-nvidia-5060-ti-vs-amd-9060-xt-with-dlss-fsr/" rel="noopener">TechSpot&amp;rsquo;s July 2025 head-to-head&lt;/a> ran both 16GB cards through 15 games at 1440p with each card&amp;rsquo;s own upscaler, and the 5060 Ti came out 9% faster at native resolution, 10% faster at Quality and Balanced, and 9% faster at Performance. FSR 4 keeps the Radeon where it stands at native. The upscalers keep the gap.&lt;/p>
&lt;p>DLSS 4&amp;rsquo;s Multi Frame Generation matters only if your monitor can show the extra frames. On a 144 Hz panel there is less room for the extra frames to show.&lt;/p>
&lt;h2 id="power-thermals-and-noise">Power, thermals, and noise&lt;/h2>
&lt;p>The 9060 XT is rated at &lt;a href="https://www.techspot.com/review/2996-amd-radeon-9060-xt/" rel="noopener">160W TBP versus the 5060 Ti&amp;rsquo;s 180W&lt;/a>. The Radeon still draws more. TechSpot&amp;rsquo;s June 4, 2025 combined CPU and GPU figures were 26 W higher for the Radeon in Starfield and 27 W higher in Star Wars Outlaws, and &lt;a href="https://www.club386.com/amd-radeon-rx-9060-xt-16gb-review/" rel="noopener">Club386&amp;rsquo;s Sapphire Nitro+ review&lt;/a> (June 5, 2025) measured 24 W more at the wall, on a card Sapphire raises to 170 W. &lt;a href="https://www.tomshardware.com/pc-components/gpus/amd-radeon-rx-9060-xt-16gb-review/7" rel="noopener">Tom&amp;rsquo;s Hardware&lt;/a> (June 10, 2025) measured the Radeon&amp;rsquo;s GPU at 164 W at 1440p, just above its rating, while all three RTX 5060-class cards it tested came in well below theirs.&lt;/p>
&lt;p>At four hours a day, 24 to 27 W comes to 35 to 39 kWh a year, roughly $6 to $7 at the $0.184/kWh US residential average, rounded (&lt;a href="https://www.eia.gov/electricity/monthly/archive/july2026.pdf#page=137" rel="noopener">EIA&lt;/a>, May 2026). It is a tiebreaker.&lt;/p>
&lt;p>Coolers decide temperature and noise. Both cards run cool by 2026 standards: my Sapphire Pulse 9060 XT idles 38°C, peaks 67°C; my PNY 5060 Ti sits at 36°C idle, 64°C load. Acoustic difference is below every other fan in the case. AMD&amp;rsquo;s 0 RPM idle means silent at desktop. In the same June 10, 2025 review, Tom&amp;rsquo;s Hardware&amp;rsquo;s PowerColor Reaper RX 9060 XT sat at about 70°C, warmer than the RTX 5060 Ti cards it tested.&lt;/p>
&lt;h2 id="drivers-and-linux-support">Drivers and Linux support&lt;/h2>
&lt;p>AMD&amp;rsquo;s amdgpu driver ships in the Linux kernel. &lt;a href="https://www.phoronix.com/review/radeon-rx-9060xt-amd-linux" rel="noopener">Phoronix&amp;rsquo;s launch review&lt;/a> put it plainly: &amp;ldquo;On Linux 6.14+ and Mesa 25.0+ you are basically in good shape but ideally at least Mesa 25.1&amp;rdquo;. At launch it called Fedora 42 and Ubuntu 25.04 &amp;ldquo;a pleasant RDNA driver stack&amp;rdquo;.&lt;/p>
&lt;p>On NVIDIA, RTX 50 cards run only on the open kernel modules. NVIDIA&amp;rsquo;s driver README says &lt;a href="https://download.nvidia.com/XFree86/Linux-x86_64/570.86.16/README/kernel_open.html" rel="noopener">&amp;ldquo;Blackwell and later are only supported by the open kernel modules&amp;rdquo;&lt;/a>, and the RTX 5060 Ti appears in &lt;a href="https://download.nvidia.com/XFree86/Linux-x86_64/575.51.02/README/supportedchips.html" rel="noopener">NVIDIA&amp;rsquo;s supported-chip list&lt;/a> from driver 575.51.02, published April 14, 2025. For a Linux daily driver I would take the 9060 XT. On Windows both are fine. I haven&amp;rsquo;t seen a crash on either driver in three months.&lt;/p>
&lt;h2 id="stepping-up-rtx-5060-ti-vs-rtx-5070">Stepping up: RTX 5060 Ti vs RTX 5070&lt;/h2>
&lt;p>One rung up, the RTX 5070 is the faster gaming card, 31% ahead at 1440p in Tom&amp;rsquo;s Hardware&amp;rsquo;s June 2026 hierarchy (96.4 against 73.4 fps). On November 17, 2026 Newegg listed the cheapest new one at $919.99, $120 above the cheapest 16GB 5060 Ti, so its 1440p frame costs $9.54 against $10.90. It has 12GB to the 5060 Ti&amp;rsquo;s 16GB, on a 192-bit bus against 128-bit.&lt;/p>
&lt;p>That 4GB matters for local AI. On my 16 GB RTX 5080, gpt-oss 20B took 13.1 to 14.0 GiB of the card&amp;rsquo;s memory in Ollama across two August captures, more than a 12 GB 5070 has, so the 16 GB 5060 Ti holds models the 5070 cannot, even though the 5070 is faster when a model fits both. The &lt;a href="https://techfuelhq.com/articles/local-llm-by-gpu-vram-2026/">VRAM-tier guide to which local LLM fits your GPU&lt;/a> maps what those 4 extra gigabytes buy, model by model, and the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rtx-5070-2026/">RTX 5060 Ti vs RTX 5070 comparison&lt;/a> works through the whole choice.&lt;/p>
&lt;p>If you want to see what the next tier up looks like, the &lt;a href="https://techfuelhq.com/gpu-reviews/rog-astral-rtx-5080-oc-review-2026/">ROG Astral RTX 5080 OC review&lt;/a> has full first-party bench data — five-test synthetic ladder across three tune profiles, 4K gaming with 1% lows, DLSS 4 MFG ladder with latency on Cyberpunk path tracing, and power &amp;amp; thermal comparisons. The &lt;a href="https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/">raw dataset&lt;/a> is open for inspection.&lt;/p>
&lt;h2 id="verdict-by-use-case">Verdict by use case&lt;/h2>
&lt;p>&lt;strong>Esports and competitive shooters:&lt;/strong> Either card. Pick on price, and at Newegg on November 17 the RX 9060 XT 16GB cost $70 less.&lt;/p>
&lt;p>&lt;strong>AAA single-player at 1440p:&lt;/strong> The 5060 Ti. It led by 25% in Tom&amp;rsquo;s eight ray-traced games and by 9% with ray tracing off (73.4 against 67.3 fps), for $70 more.&lt;/p>
&lt;p>&lt;strong>Content creation and streaming:&lt;/strong> 5060 Ti. In my experience most creative and AI tools target CUDA and NVENC first.&lt;/p>
&lt;p>&lt;strong>Light AI workloads (local LLM inference, Stable Diffusion):&lt;/strong> 5060 Ti. In &lt;a href="https://github.com/ggml-org/llama.cpp/discussions/10879" rel="noopener">llama.cpp&amp;rsquo;s Vulkan scoreboard&lt;/a>, community runs of Llama 2 7B at Q4_0 (tg128, read September 26, 2026), the RTX 5060 Ti generated 93.51 tokens per second and the RX 9060 XT 70.54, about a third faster; those runs come from different systems and builds. &lt;a href="https://techfuelhq.com/tutorials/self-host-local-llm-rtx-5060-2026/">Running Llama 3.1 8B in Ollama&lt;/a> or Stable Diffusion XL on the 5060 Ti takes one driver install. AMD&amp;rsquo;s ROCm has improved on Linux, but in my experience many tools still ship NVIDIA-first. Both hold the same models. Speed and software decide it.&lt;/p>
&lt;p>&lt;strong>Pure 1440p gaming on a budget:&lt;/strong> a tie per frame at November 17 prices, $10.90 on the 5060 Ti against $10.85 on the 9060 XT. If the $70 decides the build, the 9060 XT 16GB gives up 9% for it; otherwise take the 5060 Ti. Pair either with a &lt;a href="https://techfuelhq.com/pc-builds/1500-dollar-rtx-5060-ti-1440p-build-2026/">solid mid-range build&lt;/a>.&lt;/p>
&lt;p>&lt;strong>Linux, or a supply under 600 W:&lt;/strong> 9060 XT 16GB, for the in-kernel driver and AMD&amp;rsquo;s 450 W minimum PSU.&lt;/p>
&lt;h2 id="so-which-one-did-i-buy">So which one did I buy?&lt;/h2>
&lt;p>The 5060 Ti 16GB, for the work beside gaming: I run a &lt;a href="https://techfuelhq.com/tutorials/self-host-local-llm-rtx-5060-2026/">local Llama and Qwen stack&lt;/a> on the same box, occasionally hand it Stable Diffusion jobs, and stream over &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">my homelab 10G link&lt;/a> to a NAS. CUDA wins those. For a pure gaming box at September 2026 prices I would build around the RX 9060 XT 16GB, and I would not buy either 8GB card for 1440p.&lt;/p>
&lt;p>At November 17, 2026 prices, with the two 16GB cards $70 apart, I would build a pure gaming box around the RTX 5060 Ti 16GB too, and take the Radeon only to keep the $70, for Linux or for a small supply. To price a whole build around either card, the &lt;a href="https://techfuelhq.com/tools/pc-builder/">TechFuelHQ PC Builder&lt;/a> checks compatibility and PSU sizing.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware, GPU Benchmarks Hierarchy 2026 (Jeffrey Kampman; last updated June 24, 2026; 11 raster and 8 ray-traced games at 1080p, 1440p and 4K Ultra on a Ryzen 7 9800X3D), read November 18, 2026&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.techspot.com/review/2996-amd-radeon-9060-xt/" rel="noopener">TechSpot, &amp;ldquo;AMD Radeon RX 9060 XT 16GB Review&amp;rdquo; (Steven Walton, June 4, 2025; 18-game 1440p average, ray tracing average, system power)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.tomshardware.com/pc-components/gpus/amd-radeon-rx-9060-xt-16gb-review" rel="noopener">Tom&amp;rsquo;s Hardware, &amp;ldquo;AMD Radeon RX 9060 XT 16GB review&amp;rdquo; (June 10, 2025; 18 games, summary verdict, GPU-only power, temperatures)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.techspot.com/review/3019-nvidia-5060-ti-vs-amd-9060-xt-with-dlss-fsr/" rel="noopener">TechSpot, &amp;ldquo;Nvidia RTX 5060 Ti vs AMD Radeon 9060 XT with DLSS and FSR Enabled&amp;rdquo; (Tim Schiesser, July 29, 2025; 15 games at 1440p, native and upscaled; Ratchet &amp;amp; Clank)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.techspot.com/review/3003-amd-radeon-9060-xt-pcie-benchmark/" rel="noopener">TechSpot, &amp;ldquo;AMD Radeon RX 9060 XT PCIe Benchmark: 8GB vs. 16GB&amp;rdquo; (June 19, 2025; 1440p with upscaling across PCIe 3.0, 4.0 and 5.0)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.techspot.com/review/3004-nvidia-rtx-5060-ti-pcie-benchmark/" rel="noopener">TechSpot, &amp;ldquo;Nvidia RTX 5060 Ti 8GB vs. 16GB Tested Across PCIe 3.0, 4.0 and 5.0&amp;rdquo; (Steven Walton, June 28, 2025)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.club386.com/amd-radeon-rx-9060-xt-16gb-review/" rel="noopener">Club386, &amp;ldquo;Sapphire Nitro+ Radeon RX 9060 XT 16GB review&amp;rdquo; (Samuel Willetts, June 5, 2025; power at the wall)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.club386.com/amd-radeon-rx-9060-xt-16gb-vs-nvidia-geforce-rtx-5060-ti-16gb/" rel="noopener">Club386, &amp;ldquo;RX 9060 XT 16GB vs RTX 5060 Ti 16GB&amp;rdquo; (Samuel Willetts, June 9, 2025; spec comparison)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.phoronix.com/review/radeon-rx-9060xt-amd-linux" rel="noopener">Phoronix, &amp;ldquo;AMD Radeon RX 9060 XT Linux Performance&amp;rdquo; (Michael Larabel, June 4, 2025; kernel and Mesa requirements)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://download.nvidia.com/XFree86/Linux-x86_64/570.86.16/README/kernel_open.html" rel="noopener">NVIDIA Linux driver 570.86.16 README, &amp;ldquo;Open Linux Kernel Modules&amp;rdquo;&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://download.nvidia.com/XFree86/Linux-x86_64/575.51.02/README/supportedchips.html" rel="noopener">NVIDIA Linux driver 575.51.02 README, supported chips (RTX 5060 Ti listed)&lt;/a> and &lt;a href="https://download.nvidia.com/XFree86/Linux-x86_64/575.51.02/" rel="noopener">its download directory (driver dated 2025-04-14)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://github.com/ggml-org/llama.cpp/discussions/10879" rel="noopener">llama.cpp, &amp;ldquo;Performance of llama.cpp with Vulkan&amp;rdquo;, Discussion #10879 (community scoreboard; Llama 2 7B Q4_0, pp512 and tg128)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5060-family/" rel="noopener">NVIDIA, GeForce RTX 5060 family specifications (CUDA cores, boost clock, total graphics power, required system power, power connector), read November 18, 2026&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://ir.amd.com/news-events/press-releases/detail/1253/amd-introduces-new-radeon-graphics-cards-and-ryzen-threadripper-processors-at-computex-2025" rel="noopener">AMD, &amp;ldquo;AMD Introduces New Radeon Graphics Cards and Ryzen Threadripper Processors at COMPUTEX 2025&amp;rdquo; (press release, May 20, 2025; RX 9060 XT SEP $299 for 8GB and $349 for 16GB), read October 9, 2026&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://investor.nvidia.com/news/press-release-details/2025/NVIDIA-Blackwell-GeForce-RTX-Arrives-for-Every-Gamer-Starting-at-299/default.aspx" rel="noopener">NVIDIA Investor Relations, RTX 5060 family launch pricing and the RTX 5060 Ti&amp;rsquo;s April 16, 2025 availability (press release, April 15, 2025)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.tomshardware.com/pc-components/gpus/amd-radeon-rx-9060-xt-launches-on-june-5-starting-at-usd299" rel="noopener">Tom&amp;rsquo;s Hardware, &amp;ldquo;AMD Radeon RX 9060 XT launches on June 5&amp;rdquo; (full spec table, MSRP)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.amd.com/en/products/graphics/desktops/radeon/9000-series/amd-radeon-rx-9060xt.html" rel="noopener">AMD, official RX 9060 XT 16GB product page (clocks, RA/AI counts, typical board power, minimum PSU, bus type), read November 18, 2026&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.sapphiretech.com/en/consumer/pulse-radeon-rx-9060-xt-8g-gddr6" rel="noopener">Sapphire, PULSE RX 9060 XT OC 8GB (SKU 11350-04-20G), PCIe interface specification, read September 8, 2026&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.eia.gov/electricity/monthly/archive/july2026.pdf#page=137" rel="noopener">U.S. EIA, Electric Power Monthly, July 2026, Table 5.6.A (May 2026 U.S. residential average, 18.44 cents per kWh), read November 18, 2026&lt;/a>&lt;/li>
&lt;li>Newegg affiliate catalogue, November 17, 2026, new and in stock under a Newegg item number: &lt;a href="https://www.newegg.com/pny-technologies-inc-rtx-5060-ti-16gb-dual-fan-oc-geforce-rtx-5060-ti-graphics-card-double-fans/p/N82E16814133993" rel="noopener">PNY RTX 5060 Ti 16GB Dual Fan OC, $799.99 (N82E16814133993)&lt;/a>; &lt;a href="https://www.newegg.com/yeston-rx9060xt-radeon-rx-9060-xt-16gb-graphics-card-triple-fans/p/N82E16814980004" rel="noopener">Yeston Sakura RX 9060 XT 16GB, $729.99 (N82E16814980004)&lt;/a>; &lt;a href="https://www.newegg.com/zotac-gaming-geforce-rtx-5060-ti-8gb-twin-edge-oc-graphics-card-air-cooler/p/N82E16814500638" rel="noopener">ZOTAC Gaming RTX 5060 Ti 8GB Twin Edge OC, $529.99 (N82E16814500638)&lt;/a>; &lt;a href="https://www.newegg.com/msi-rtx-5070-12g-ventus-3x-oc-geforce-rtx-5070-12gb-graphics-card-triple-fans/p/N82E16814137940" rel="noopener">MSI RTX 5070 12G Ventus 3X OC, $919.99 (N82E16814137940)&lt;/a>. No new 8GB RX 9060 XT was listed.&lt;/li>
&lt;li>&lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">TechFuel HQ, RTX 5080 LLM throughput dataset (gpt-oss 20B resident VRAM)&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>RTX 4080 vs RTX 4090: How Much Faster, and Is It Worth It in 2026?</title><link>https://techfuelhq.com/gpu-reviews/rtx-4080-vs-rtx-4090/</link><pubDate>Sun, 26 Apr 2026 00:00:00 -0500</pubDate><guid>https://techfuelhq.com/gpu-reviews/rtx-4080-vs-rtx-4090/</guid><atom:updated>2026-11-18T05:05:34Z</atom:updated><description>&lt;h2 id="which-one-to-buy">Which one to buy&lt;/h2>
&lt;p>Newegg&amp;rsquo;s affiliate catalogue for November 17, 2026 listed no new RTX 4080, RTX 4080 Super or RTX 4090 graphics card, only accessories for them and complete PCs with one built in. So this is a used-market decision, or a reason to buy the next generation instead.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>For 4K gaming:&lt;/strong> the RTX 4090, as long as it costs less than about 1.3 times the 4080 you would otherwise buy. That is the size of its 4K lead in Tom&amp;rsquo;s Hardware&amp;rsquo;s averages, so below that ratio its frames cost less.&lt;/li>
&lt;li>&lt;strong>For 1440p, or a build on a 750 W supply:&lt;/strong> the RTX 4080 or 4080 Super. The 4090&amp;rsquo;s lead shrinks to about a fifth at 1440p, and NVIDIA asks 850 W of system power for it.&lt;/li>
&lt;li>&lt;strong>For 24GB work&lt;/strong> (a local model, scene or project that does not fit in 16GB): the RTX 4090. Nothing in the 4080 family has more than 16GB.&lt;/li>
&lt;li>&lt;strong>For a new card:&lt;/strong> the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5080-review-2026/">RTX 5080&lt;/a>, which beats both 4080s, or the RTX 5090 if you need more than a 4090. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5090-vs-5080-2026/">RTX 5090 vs 5080 comparison&lt;/a> prices both.&lt;/li>
&lt;/ul>
&lt;p>I would buy the RTX 4080 for a gaming build when its delivered price is far below the RTX 4090 and it meets the target in the games I play.&lt;/p>
&lt;h2 id="how-much-faster-is-the-rtx-4090">How much faster is the RTX 4090?&lt;/h2>
&lt;p>Jeffrey Kampman&amp;rsquo;s &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware GPU hierarchy&lt;/a>, last updated June 24, 2026, retested both generations on a Ryzen 7 9800X3D. It averages 11 raster games and 8 ray-traced games at native resolution, with no upscaling or frame generation. These are its averages, with the RTX 5080 beside them for scale.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Tom&amp;rsquo;s Hardware fps averages&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 4080&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 4080 Super&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 4090&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5080&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">1440p raster&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">117.5&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">118.6&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">143.4&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">128.3&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">4K raster&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">67.5&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">69.4&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">89.1&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">77.4&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">1440p ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">68.4&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">69.5&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">87.7&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">74.0&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tom&amp;rsquo;s Hardware fps averages">4K ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">37.4&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">38.5&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">52.2&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5080">42.1&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Against the original 4080, the 4090 leads by 22.0% at 1440p raster, 32.0% at 4K raster, 28.2% at 1440p with ray tracing and 39.6% at 4K with ray tracing. Against the 4080 Super the leads are 20.9%, 28.4%, 26.2% and 35.6%. The Super sits within 3% of the original 4080 in every row, so the two are one choice. The gap grows with resolution and with ray tracing.&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/tools/gpu-comparison/?a=GeForce&amp;#43;RTX&amp;#43;4080&amp;amp;b=GeForce&amp;#43;RTX&amp;#43;4090&amp;amp;res=1440p">GPU comparison tool&lt;/a> loads the 4080 and 4090 raster scores side by side at three resolutions.&lt;/p>
&lt;h2 id="what-a-used-4090-is-worth-against-a-used-4080">What a used 4090 is worth against a used 4080&lt;/h2>
&lt;p>The break-even price for the 4090 is the 4080&amp;rsquo;s price times the 4090&amp;rsquo;s frame rate divided by the 4080&amp;rsquo;s. At that price each frame costs the same on both cards. From Tom&amp;rsquo;s Hardware&amp;rsquo;s averages above:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Where you play&lt;/th>
&lt;th scope="col" style="text-align: right">4090 frame rate ÷ 4080 frame rate&lt;/th>
&lt;th scope="col" style="text-align: right">The 4090 is the better buy below&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Where you play">1440p raster&lt;/td>
&lt;td style="text-align: right" data-label="4090 frame rate ÷ 4080 frame rate">143.4 / 117.5&lt;/td>
&lt;td style="text-align: right" data-label="The 4090 is the better buy below">1.22 × the 4080&amp;rsquo;s price&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Where you play">4K raster&lt;/td>
&lt;td style="text-align: right" data-label="4090 frame rate ÷ 4080 frame rate">89.1 / 67.5&lt;/td>
&lt;td style="text-align: right" data-label="The 4090 is the better buy below">1.32 × the 4080&amp;rsquo;s price&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Where you play">4K ray tracing&lt;/td>
&lt;td style="text-align: right" data-label="4090 frame rate ÷ 4080 frame rate">52.2 / 37.4&lt;/td>
&lt;td style="text-align: right" data-label="The 4090 is the better buy below">1.40 × the 4080&amp;rsquo;s price&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Put the delivered prices of the two used cards you can actually buy into the row you play at. If a 4090 costs more than that multiple, the 4080 gives more frames per dollar. This sum gives no value to the 4090&amp;rsquo;s extra 8GB; price that separately if a workload needs it, and add the 4090&amp;rsquo;s larger power supply if your current one is under 850 W. For a used card, weigh its condition, the seller&amp;rsquo;s return terms and any remaining warranty as well.&lt;/p>
&lt;h2 id="the-specs-that-matter">The specs that matter&lt;/h2>
&lt;p>Keep the original 4080 and the Super separate. &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/40-series/rtx-4080-family/" rel="noopener">NVIDIA&amp;rsquo;s 4080 family table&lt;/a> and &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/40-series/rtx-4090/" rel="noopener">4090 table&lt;/a> give these reference values, read November 18, 2026:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Reference specification&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 4080&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 4080 Super&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 4090&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Reference specification">CUDA cores&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">9,728&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">10,240&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">16,384&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Reference specification">Graphics memory&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">16GB GDDR6X&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">16GB GDDR6X&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">24GB GDDR6X&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Reference specification">Memory interface&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">256-bit&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">256-bit&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">384-bit&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Reference specification">Total Graphics Power&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">320W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">320W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">450W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Reference specification">NVIDIA average gaming power&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">251W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">246W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">315W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Reference specification">NVIDIA Required System Power&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">750W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">750W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">850W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Reference specification">Power input&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080">3x 8-pin adapter, or one 450W Gen 5 cable&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4080 Super">3x 8-pin adapter, or one 450W Gen 5 cable&lt;/td>
&lt;td style="text-align: right" data-label="RTX 4090">3x 8-pin adapter, or one 450W Gen 5 cable&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>These are reference-card values. NVIDIA bases the 4090&amp;rsquo;s system-power figure on a Ryzen 9 5900X configuration; add-in-board models and your CPU can change the requirement. Follow the exact card and PSU manufacturers&amp;rsquo; cable and capacity instructions.&lt;/p>
&lt;p>The extra 8GB matters when a model, scene, or project exceeds 16GB. It does not make a fixed promise about future game memory requirements. Check the actual workload.&lt;/p>
&lt;h3 id="electricity-over-three-years">Electricity over three years&lt;/h3>
&lt;p>NVIDIA&amp;rsquo;s reference tables report average gaming power across 22 games spanning 1080p through 4K: 251W for the original 4080 and 315W for the 4090. At four hours a day for three years, the 64W difference is &lt;code>0.064 × 4 × 365 × 3 = 280.32 kWh&lt;/code>. At the &lt;a href="https://www.eia.gov/electricity/monthly/archive/july2026.pdf#page=137" rel="noopener">EIA&amp;rsquo;s May 2026 US residential average&lt;/a> of 18.44 cents per kWh, that is about $51.69. These are manufacturer GPU averages, not matched wall readings, so use your own tariff in the &lt;a href="https://techfuelhq.com/tools/power-cost-calculator/">power calculator&lt;/a> for your bill.&lt;/p>
&lt;h2 id="buying-new-instead">Buying new instead&lt;/h2>
&lt;p>In the same Tom&amp;rsquo;s Hardware averages the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5080-review-2026/">RTX 5080&lt;/a> is 14.7% faster than the RTX 4080 at 4K raster and 11.5% faster than the 4080 Super, and it is faster than either RTX 4080 in every row. The RTX 4090 is 15.1% faster than it at 4K raster and 24.0% faster at 4K with ray tracing, and it has 16GB to the 4090&amp;rsquo;s 24GB. On November 17, 2026 Newegg listed the cheapest new, in-stock RTX 5080, the ZOTAC Gaming RTX 5080 Solid Core OC, at &lt;span class="claim" data-claim-key="listing.N82E16814500648.price_usd" data-claim-value="2199.99" data-claim-scope="Newegg affiliate catalogue, US" data-claim-date="2026-11-17">$2,199.99&lt;/span>
.&lt;/p>
&lt;p>The RTX 5090 is the new card above the 4090, 24.4% faster at 4K raster in the same averages with 32GB. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5090-vs-5080-2026/">RTX 5090 vs 5080 comparison&lt;/a> prices it, the &lt;a href="https://techfuelhq.com/articles/best-gpu-4k-gaming-2026/">4K GPU guide&lt;/a> sets every 4K tier side by side, and the &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/">GPU hierarchy&lt;/a> ranks the rest. If a 5080&amp;rsquo;s power draw is the concern, the &lt;a href="https://techfuelhq.com/articles/rtx-5080-undervolt-guide-2026/">RTX 5080 undervolt guide&lt;/a> covers bringing it down.&lt;/p></description></item><item><title>DXGI_ERROR_DEVICE_REMOVED or DEVICE_HUNG: Fixes in Order</title><link>https://techfuelhq.com/articles/dxgi-error-device-removed-2026/</link><pubDate>Fri, 02 Oct 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/dxgi-error-device-removed-2026/</guid><atom:updated>2026-11-18T05:05:11Z</atom:updated><description>&lt;p>A game that closes on a &lt;code>DXGI_ERROR_DEVICE_REMOVED&lt;/code> box has lost its Direct3D graphics device: the GPU stopped responding or was reset, and the game quit instead of recovering. Most crash boxes and logs carry a second code beside it, written as &lt;code>&amp;quot;with Reason&amp;quot;&lt;/code>, &lt;code>&amp;quot;DeviceRemovedReason&amp;quot;&lt;/code> or a second &lt;code>0x887A...&lt;/code> number. That second code and how many games crash tell you where to start. Neither proves a loose cable or a dead card, so the cheap software fixes come first.&lt;/p>
&lt;p>This page is for the game&amp;rsquo;s error dialog. If Windows itself says the display driver stopped responding, or the PC blue-screens, the &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/">GPU driver crash fix&lt;/a> is the better start, and a blue screen naming VIDEO_MEMORY_MANAGEMENT_INTERNAL (&lt;code>0x10E&lt;/code>) has its &lt;a href="https://techfuelhq.com/articles/video-memory-management-internal-2026/">own guide&lt;/a>.&lt;/p>
&lt;p>&lt;strong>One game or every game?&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>&lt;strong>One game, or one game since its last patch,&lt;/strong> while other DirectX 12 games run clean: steps 1 to 3 usually settle it. That title&amp;rsquo;s rendering path or its pairing with your driver is the main suspect.&lt;/li>
&lt;li>&lt;strong>Several games crash, or the desktop flickers or goes black too:&lt;/strong> shared software state (a broken driver install, a background 3D app, unstable clocks) comes before hardware. Work all the steps in order.&lt;/li>
&lt;li>&lt;strong>It started right after a driver update, Windows Update, game patch or tuning tweak:&lt;/strong> undo or test that exact change first.&lt;/li>
&lt;/ul>
&lt;h2 id="the-fix-order">The fix order&lt;/h2>
&lt;p>The order is mine, cheapest first, with the vendor behind each step named. Test the game after each one.&lt;/p>
&lt;h3 id="1-restart-and-close-other-3d-apps">1. Restart, and close other 3D apps&lt;/h3>
&lt;p>EA&amp;rsquo;s &lt;a href="https://help.ea.com/en/articles/battlefield/battlefield-6/error-codes/" rel="noopener">Battlefield 6 error-codes page&lt;/a> gives one instruction for DXGI_ERROR_DEVICE_HUNG: fully restart your system. Epic explains why other programs matter. A GPU timeout &amp;ldquo;invalidates all currently running contexts&amp;rdquo;, so another program&amp;rsquo;s GPU crash takes your game down with it. Close browsers with hardware acceleration, video encoders, overlays and any second game before you relaunch. Discord&amp;rsquo;s own setting is covered in &lt;a href="https://techfuelhq.com/gaming/discord-hardware-acceleration-on-or-off-2026/">Discord hardware acceleration on or off&lt;/a>.&lt;/p>
&lt;p>If the crash never returns after a restart, you are done.&lt;/p>
&lt;h3 id="2-update-the-game-and-the-driver">2. Update the game and the driver&lt;/h3>
&lt;p>Epic tells anyone reporting a GPU crash to use the latest driver and not to rely on Windows Update or even vendor tools to say it is current. Get it from the AMD, Intel or NVIDIA site. EA&amp;rsquo;s advice for AMD driver errors in Battlefield 6 is the same, with one addition: remove the old drivers first.&lt;/p>
&lt;p>If the crash started with a new driver, roll it back instead. The clean removal, with AMD&amp;rsquo;s tools or DDU in Safe Mode, is &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/#1-do-a-ddu-clean-reinstall-in-safe-mode">step 1 of the GPU driver crash fix&lt;/a>. On a Radeon card, read the Known Issues in the release notes for your driver version: AMD lists game-specific timeouts and workarounds there, and the GPU driver crash fix &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/#amd-timeouts-september-2026">collects what AMD has published&lt;/a>.&lt;/p>
&lt;p>Update the game too. INVALID_CALL, and a HUNG reason that only one game throws, both point at the game&amp;rsquo;s code by Microsoft&amp;rsquo;s definitions, and only a patch changes that.&lt;/p>
&lt;h3 id="3-try-the-games-directx-11-mode">3. Try the game&amp;rsquo;s DirectX 11 mode&lt;/h3>
&lt;p>AMD has suggested DX11 mode as a workaround for DX12 driver timeouts in specific games, as the &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/#amd-timeouts-september-2026">GPU driver crash fix records&lt;/a>. For other games it is my own suggestion. If the game offers DX11 beside DX12, switch for a session. A crash that stops in DX11 puts the fault in that game&amp;rsquo;s DX12 path or the driver&amp;rsquo;s handling of it, and you can keep playing while a patch arrives. The trade-offs between the two are in &lt;a href="https://techfuelhq.com/gaming/dx12-vs-dx11-fps-2026/">DX12 vs DX11&lt;/a>.&lt;/p>
&lt;h3 id="4-put-everything-back-to-stock">4. Put everything back to stock&lt;/h3>
&lt;p>Intel&amp;rsquo;s &lt;a href="https://www.intel.com/content/www/us/en/support/articles/000036362/graphics.html" rel="noopener">DXGI_ERROR_DEVICE_HUNG article&lt;/a> was written for one case, Prepar3D v4 on a laptop with Intel HD Graphics 620. After a driver update, its next step is to correct unstable overclocking of the graphics card, processor or memory by setting voltage and speed to the system&amp;rsquo;s specifications. Stock means all of it:&lt;/p>
&lt;ul>
&lt;li>any GPU overclock, and any undervolt, including one that ran clean for months&lt;/li>
&lt;li>a factory-overclocked card&amp;rsquo;s boost profile, if its software offers a stock or silent mode&lt;/li>
&lt;li>CPU overclocks, Precision Boost Overdrive and Curve Optimizer offsets&lt;/li>
&lt;li>the XMP or EXPO memory profile&lt;/li>
&lt;/ul>
&lt;p>I count an undervolt that passed a benchmark as unproven here, because the crash comes in one game&amp;rsquo;s scenes and not in the benchmark&amp;rsquo;s. If you tuned the card with one of our guides, the way back is in the &lt;a href="https://techfuelhq.com/articles/how-to-undervolt-gpu-2026/">undervolting guide&lt;/a>, the &lt;a href="https://techfuelhq.com/articles/rtx-5080-undervolt-guide-2026/">RTX 5080 undervolt guide&lt;/a> and the &lt;a href="https://techfuelhq.com/articles/rx-9070-xt-undervolt-2026/">RX 9070 XT undervolt guide&lt;/a>. Play at stock for a few days. If the crash stops, bring the tuning back one piece at a time.&lt;/p>
&lt;p>On an Intel Core 13th or 14th Gen desktop processor, stock also means Intel&amp;rsquo;s own &lt;a href="https://www.intel.com/content/www/us/en/support/articles/000102331/processors.html" rel="noopener">guidance for the Vmin Shift Instability issue&lt;/a>, which affects some of those chips: the relevant Intel Default Settings in the BIOS and the latest BIOS containing microcode &lt;code>0x12F&lt;/code> or later. Intel has extended warranty coverage by two years for eligible affected processors, to up to five years from the original purchase date.&lt;/p>
&lt;p>The same Intel DXGI article then caps the game at 60 FPS, tests the memory with a tool such as MemTest, and reinstalls the game as the last step. The frame cap is a cheap test on any game that crashes in its busiest moments.&lt;/p>
&lt;h3 id="5-test-with-hardware-accelerated-gpu-scheduling-off">5. Test with hardware-accelerated GPU scheduling off&lt;/h3>
&lt;p>Hardware-accelerated GPU scheduling (HAGS) lets Windows offload most GPU scheduling to dedicated hardware on the card. The switch is on the Graphics page (Start &amp;gt; Settings &amp;gt; System &amp;gt; Display &amp;gt; Graphics, the path Microsoft&amp;rsquo;s windowed-games page uses). Microsoft&amp;rsquo;s &lt;a href="https://devblogs.microsoft.com/directx/navigating-the-redesigned-graphics-settings-page/" rel="noopener">guide to the redesigned page&lt;/a> puts it under &lt;strong>Advanced graphics settings&lt;/strong> and says it only appears with a supporting GPU and display driver. Turn it off, replay the same game, and turn it back on if nothing changes. Treat it as one cheap variable to isolate, not a known cure for DXGI errors. The vendor note tied to it is narrow: AMD&amp;rsquo;s &lt;a href="https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-26-10-2.html" rel="noopener">Adrenalin 26.10.2 release notes&lt;/a> list, under Fixed Issues, an intermittent driver timeout while playing video on Windows 11 with HAGS enabled on Radeon RX 7000 series cards. They don&amp;rsquo;t mention game crashes, and on an RX 7000 card the driver update in step 2 comes first. &lt;a href="https://techfuelhq.com/gaming/hardware-accelerated-gpu-scheduling-on-or-off-2026/">HAGS on or off&lt;/a> covers when to leave it on.&lt;/p>
&lt;h3 id="6-laptops-pin-the-game-to-the-discrete-gpu">6. Laptops: pin the game to the discrete GPU&lt;/h3>
&lt;p>Microsoft&amp;rsquo;s list of ways a device gets removed includes a system that &amp;ldquo;changes from a power-saving graphics adapter to a performance graphics adapter&amp;rdquo;. That takes two GPUs in one PC, such as a laptop with integrated and discrete graphics. Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/hardware/display-graphics/optimizations-for-windowed-games-in-windows-11" rel="noopener">windowed games page&lt;/a> gives the path. Open Start &amp;gt; Settings &amp;gt; System &amp;gt; Display &amp;gt; Graphics, select the game under Custom options for apps, choose Options, set Graphics preference to High performance, and select Save. Restart the game.&lt;/p>
&lt;h3 id="7-check-event-4101-and-the-temperatures">7. Check Event 4101 and the temperatures&lt;/h3>
&lt;p>Run this read-only check right after a crash to see whether Windows logged a display driver timeout at that minute. Press the Windows key, type &lt;code>powershell&lt;/code>, press Enter, and paste:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>Get-WinEvent -FilterHashtable @{LogName=&lt;span style="color:#e6db74">&amp;#39;System&amp;#39;&lt;/span>; ProviderName=&lt;span style="color:#e6db74">&amp;#39;Display&amp;#39;&lt;/span>; Id=&lt;span style="color:#ae81ff">4101&lt;/span>} -MaxEvents &lt;span style="color:#ae81ff">5&lt;/span> | Format-List TimeCreated, Message
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/archive/technet-wiki/1462.event-id-4101-display-driver-timeout-detection-and-recovery" rel="noopener">archived Event ID 4101 page&lt;/a> lists the event under source &lt;code>Display&lt;/code> with the message &lt;code>&amp;quot;Display driver %1 stopped responding and has successfully recovered.&amp;quot;&lt;/code> Finding it at the crash time confirms that Windows detected a hung GPU workload and reset the driver: the operating system&amp;rsquo;s half of the event whose game-side half is your DXGI dialog. Ignore that archived page&amp;rsquo;s old suggestion to lengthen the registry timeout; Microsoft&amp;rsquo;s current documentation overrides it, as &lt;a href="#two-fixes-to-skip">Two fixes to skip&lt;/a> explains.&lt;/p>
&lt;p>If PowerShell prints &lt;code>&amp;quot;No events were found that match the specified selection criteria&amp;quot;&lt;/code>, Windows did not record a standard Display 4101 timeout for that exit. On Windows 11 25H2 build 26200.9457, verified on October 2, 2026, that command runs without administrator rights.&lt;/p>
&lt;p>Epic lists an overheating GPU among the hardware causes of GPU crashes. Log the GPU temperature during the scene that crashes; &lt;a href="https://techfuelhq.com/articles/safe-gpu-temp-2026/">safe GPU temperatures&lt;/a> covers what&amp;rsquo;s normal for your card.&lt;/p>
&lt;p>If Event 4101 shows timeouts outside games, or the PC blue-screens with VIDEO_TDR_FAILURE, the problem is no longer one game&amp;rsquo;s dialog. The &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/#the-fix-path-in-order">GPU driver crash fix&lt;/a> works that path from a clean driver install down, and this page does not repeat it.&lt;/p>
&lt;h3 id="8-removed-in-every-game-power-and-the-card-itself">8. REMOVED in every game: power and the card itself&lt;/h3>
&lt;p>Microsoft&amp;rsquo;s walkthrough describes &lt;code>DXGI_ERROR_DEVICE_REMOVED&lt;/code> (&lt;code>0x887A0005&lt;/code>) as an adapter &lt;code>&amp;quot;physically removed, turned off, or a driver upgrade has occurred&amp;quot;&lt;/code>, and adds that repeated device-removed errors &lt;code>&amp;quot;can also indicate a hardware failure or a bug in the graphics driver.&amp;quot;&lt;/code> So even repeated &lt;code>REMOVED&lt;/code> crashes at stock clocks across several games leave software and hardware causes open.&lt;/p>
&lt;p>Run three zero-teardown checks before reaching for a screwdriver:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Device Manager → Display adapters → right-click your GPU → Properties → Events.&lt;/strong> Check whether Windows Update installed a different driver package near the crash time or left the adapter in &lt;strong>Code 43&lt;/strong> (driver reported a device failure).&lt;/li>
&lt;li>&lt;strong>Event Viewer → Windows Logs → System&lt;/strong> at the crash minute. Look beyond &lt;code>Display&lt;/code> Event &lt;code>4101&lt;/code> for &lt;code>nvlddmkm&lt;/code> or &lt;code>amdwddmg&lt;/code> driver errors and &lt;strong>&lt;code>WHEA-Logger&lt;/code> Event ID &lt;code>17&lt;/code>&lt;/strong> PCIe root-port warnings. A &lt;a href="https://techfuelhq.com/articles/whea-uncorrectable-error-2026/">WHEA_UNCORRECTABLE_ERROR&lt;/a> blue screen alongside them has its own guide.&lt;/li>
&lt;li>&lt;strong>Engine crash logs&lt;/strong> (for example &lt;code>%LOCALAPPDATA%\&amp;lt;Game&amp;gt;\Saved\Crashes&lt;/code> in Unreal Engine titles) to see whether two crashing games hit the same fault or drop at unrelated moments.&lt;/li>
&lt;/ol>
&lt;p>Only when software logs are captured, or when crashes pair with black-screen fan spin-ups or a GPU disappearing from Device Manager, move to physical inspection. Shut down Windows, flip the PSU rear switch off, unplug AC power, touch bare case metal to ground yourself, and check the physical path: verify every 8-pin or &lt;code>12V-2x6&lt;/code>/&lt;code>12VHPWR&lt;/code> connector is seated flush and latched at both the GPU and modular PSU ends, test without third-party cable extensions or vertical PCIe risers, and reseat the card in the primary PCIe slot. From there, use &lt;a href="https://techfuelhq.com/articles/psu-failure-symptoms-2026/">PSU failure symptoms&lt;/a> for load-related power cutoffs, &lt;a href="https://techfuelhq.com/articles/graphics-card-not-detected-2026/">graphics card not detected&lt;/a> if the adapter disappears from BIOS or Device Manager, and &lt;a href="https://techfuelhq.com/articles/gpu-artifacts-2026/">GPU artifacts&lt;/a> if visual corruption precedes the crash.&lt;/p>
&lt;p>&lt;strong>Stop here&lt;/strong> when clean drivers, stock clocks and verified cables still leave &lt;code>0x887A0005&lt;/code> repeating across unrelated games. Only a known-good GPU or PSU test (in another PC or with a spare unit) separates a driver or board quirk from a failing card or supply, so take your Event 4101 log and driver version to the card or PC maker.&lt;/p>
&lt;h2 id="what-each-code-means">What each code means&lt;/h2>
&lt;p>Find the second code (&lt;code>GetDeviceRemovedReason&lt;/code>) in this table. Every code below is a Direct3D/DXGI status the game receives, not a reading from a sensor on your PCIe slot or power cables. The definitions come from Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows/win32/direct3ddxgi/dxgi-error" rel="noopener">DXGI_ERROR reference&lt;/a> and its &lt;a href="https://learn.microsoft.com/en-us/windows/uwp/gaming/handling-device-lost-scenarios" rel="noopener">device-removed walkthrough&lt;/a>.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Returned reason code&lt;/th>
&lt;th scope="col">Hex&lt;/th>
&lt;th scope="col">Microsoft&amp;rsquo;s definition&lt;/th>
&lt;th scope="col">What it tells a player&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Returned reason code">&lt;code>DXGI_ERROR_DEVICE_HUNG&lt;/code>&lt;/td>
&lt;td data-label="Hex">&lt;code>0x887A0006&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s definition">&amp;ldquo;The application&amp;rsquo;s device failed due to badly formed commands sent by the application.&amp;rdquo; The walkthrough says the driver stopped responding.&lt;/td>
&lt;td data-label="What it tells a player">Points first at one game&amp;rsquo;s DX12 or shader path, the driver version, or unstable GPU, CPU or memory clocks, not a loose cable.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Returned reason code">&lt;code>DXGI_ERROR_DEVICE_REMOVED&lt;/code>&lt;/td>
&lt;td data-label="Hex">&lt;code>0x887A0005&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s definition">&amp;ldquo;The video card has been physically removed from the system, or a driver upgrade for the video card has occurred.&amp;rdquo; The walkthrough adds &amp;ldquo;turned off&amp;rdquo;.&lt;/td>
&lt;td data-label="What it tells a player">Direct3D lost its adapter. A driver install, a laptop switching between its two GPUs, or a GPU reset all count, so check logs and scope before opening the PC.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Returned reason code">&lt;code>DXGI_ERROR_DEVICE_RESET&lt;/code>&lt;/td>
&lt;td data-label="Hex">&lt;code>0x887A0007&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s definition">&amp;ldquo;The device failed due to a badly formed command. This is a run-time issue.&amp;rdquo;&lt;/td>
&lt;td data-label="What it tells a player">Epic says a RESET reason is likely a crash caused by a different application. Close other 3D apps.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Returned reason code">&lt;code>DXGI_ERROR_DRIVER_INTERNAL_ERROR&lt;/code>&lt;/td>
&lt;td data-label="Hex">&lt;code>0x887A0020&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s definition">&amp;ldquo;The driver encountered a problem and was put into the device removed state.&amp;rdquo;&lt;/td>
&lt;td data-label="What it tells a player">A fault inside the graphics driver. Clean-reinstall the latest driver, or roll back if crashes started right after updating.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Returned reason code">&lt;code>DXGI_ERROR_INVALID_CALL&lt;/code>&lt;/td>
&lt;td data-label="Hex">&lt;code>0x887A0001&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s definition">&amp;ldquo;The application provided invalid parameter data.&amp;rdquo;&lt;/td>
&lt;td data-label="What it tells a player">The game or its middleware passed invalid data to Direct3D. Patch the game, clear its shader cache, or switch API modes; hardware teardown cannot fix it.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Two limits apply. Microsoft writes those strings for engine developers, so &lt;code>&amp;quot;the application&amp;quot;&lt;/code> means the game rather than anything you clicked. And Epic, whose &lt;a href="https://dev.epicgames.com/documentation/en-us/unreal-engine/dealing-with-a-gpu-crash-when-using-unreal-engine" rel="noopener">GPU crash guide&lt;/a> shows both codes in one log line (&lt;code>&amp;quot;with error DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_HUNG&amp;quot;&lt;/code>), cautions that reason codes &amp;ldquo;are not completely reliable&amp;rdquo;, though still worth checking. Treat the code as one input alongside scope and recent changes.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery" rel="noopener">TDR overview&lt;/a> notes that a well-written DirectX 10 or later app can release and re-create its Direct3D device after a reset and keep running. Most 3D games choose to show this dialog and exit instead.&lt;/p>
&lt;h2 id="two-fixes-to-skip">Two fixes to skip&lt;/h2>
&lt;h3 id="the-tdrdelay-and-tdrlevel-registry-edits">The TdrDelay and TdrLevel registry edits&lt;/h3>
&lt;p>Older fix pages lead with a registry edit under &lt;code>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers&lt;/code>. Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys" rel="noopener">TDR registry key page&lt;/a> is written for driver developers, and it says &amp;ldquo;End users shouldn&amp;rsquo;t manipulate these registry keys.&amp;rdquo;&lt;/p>
&lt;p>TdrDelay is the timeout itself, 2 seconds by default. Raising it gives a hung GPU more time before Windows resets it, and the clock, driver or power fault that caused the hang is still there. Epic&amp;rsquo;s Unreal Engine guide does set TdrDelay and TdrDdiDelay to 60 seconds, but that guide is for developers whose engine sends long workloads while they build a game, and Epic says the change &amp;ldquo;will not resolve all crashes.&amp;rdquo;&lt;/p>
&lt;p>The TdrLevel edit is worse. In Microsoft&amp;rsquo;s table, TdrLevelOff (0) is &amp;ldquo;Detection disabled&amp;rdquo;. Windows stops looking for a hung GPU at all. The feature exists, in Microsoft&amp;rsquo;s words, &amp;ldquo;to prevent the entire system from becoming unresponsive&amp;rdquo;, so with it off, a hang that would have closed one game can freeze the whole PC instead.&lt;/p>
&lt;h3 id="reinstalling-directx">Reinstalling DirectX&lt;/h3>
&lt;p>Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/hardware/display-graphics/how-to-install-the-latest-version-of-directx" rel="noopener">DirectX support page&lt;/a> says DirectX 11.3 and 12 ship with Windows 10 and later, that updates come through Windows Update, and that there is no stand-alone package. The &lt;a href="https://www.microsoft.com/en-us/download/details.aspx?id=35" rel="noopener">DirectX End-User Runtime&lt;/a> that fix pages link &amp;ldquo;does not change the version of DirectX&amp;rdquo;. It installs legacy libraries such as D3DX9 for older games. It cannot repair DirectX 12, and it does nothing for a device-removed error. Skip that download entirely.&lt;/p>
&lt;h2 id="why-the-advice-online-disagrees">Why the advice online disagrees&lt;/h2>
&lt;p>Microsoft writes for developers, so it blames DEVICE_HUNG on badly formed commands from the application. EA, Intel and Epic write for people who can&amp;rsquo;t change the game&amp;rsquo;s code: EA says a stuck background app causes it, Intel runs from the driver to clocks, a frame cap and memory, and Epic&amp;rsquo;s causes run from content and engine bugs to drivers, overheating, running out of video memory and other apps. The fix order above follows that split: player-side steps first, a game update for the developer&amp;rsquo;s side, hardware last.&lt;/p>
&lt;h2 id="game-notes">Game notes&lt;/h2>
&lt;p>&lt;strong>Battlefield 6.&lt;/strong> EA&amp;rsquo;s error-codes page, updated August 11, 2026, says DirectX errors &amp;ldquo;can mean there&amp;rsquo;s an issue with your drivers&amp;rdquo;, asks you to check the game&amp;rsquo;s minimum requirements, and gives a full restart as the fix for DXGI_ERROR_DEVICE_HUNG.&lt;/p>
&lt;p>&lt;strong>Unreal Engine games.&lt;/strong> Epic&amp;rsquo;s guide is written for developers, but the reading carries over: the reason is a separate field from the error code, and a DEVICE_RESET reason means another application probably crashed the GPU.&lt;/p>
&lt;p>For Baldur&amp;rsquo;s Gate 3, FiveM, Arc Raiders, Wuthering Waves and Monster Hunter Wilds, I found no publisher support page that addresses this error as of October 2, 2026. For those, the scope test and the fix order above are the route.&lt;/p></description></item><item><title>Debloat Windows 11 (2026): What to Remove, What to Skip</title><link>https://techfuelhq.com/articles/debloat-windows-11-2026/</link><pubDate>Sat, 12 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/debloat-windows-11-2026/</guid><atom:updated>2026-11-18T05:05:11Z</atom:updated><description>&lt;p>My own Windows 11 Home box is debloated. I know exactly what that means because I read it off the machine for this page: zero provisioned inbox apps left, 33 removable packages, every one of them something I installed or a codec, and every recommendation, advertising and web-search switch off. That is the finished state.&lt;/p>
&lt;p>This page is the route to it, in the order that costs you the least trust in other people&amp;rsquo;s scripts. Settings first. Then PowerShell for the apps Settings refuses. Then the two big scripts, for the switches Settings hides. And a clear line around what nothing on Home or Pro can switch off.&lt;/p>
&lt;h2 id="before-you-start">Before you start&lt;/h2>
&lt;p>&lt;strong>Decide what you want.&lt;/strong> Debloating means four different things and people mix them up. Removing apps you never open. Turning off the recommendations and ads Microsoft threads through the Start menu and the lock screen. Cutting what the machine reports back to Microsoft. Disabling features like Copilot. The first two are safe and reversible from Settings. The third has a floor you cannot go below. The fourth is where the scripts earn their keep.&lt;/p>
&lt;p>&lt;strong>Do not expect speed.&lt;/strong> PCMag&amp;rsquo;s Chris Hoffman installed Windows 11 25H2 in a 4 GB virtual machine and measured 1.9 to 2.1 GB of RAM on a fresh boot with nothing removed.&lt;/p>
&lt;p>He then ran Chris Titus Tech&amp;rsquo;s Windows Utility, Raphire&amp;rsquo;s Win11Debloat, Tiny11 Builder and Tiny11 Core Builder, and wrote that &amp;ldquo;none of the four tools I tested made much of a dent in Windows 11&amp;rsquo;s RAM usage. At most, they saved 100MB or 200MB.&amp;rdquo; If your machine feels slow in games, the causes are on the &lt;a href="https://techfuelhq.com/articles/pc-stuttering-in-games-2026/">stuttering page&lt;/a>, and a debloat script is not on that list.&lt;/p>
&lt;p>&lt;strong>Know the floor.&lt;/strong> Microsoft&amp;rsquo;s diagnostic-data documentation lists four levels and says of the lowest, &amp;ldquo;Diagnostic data off,&amp;rdquo; that it &amp;ldquo;is only available on Windows Server, Windows Enterprise, and Windows Education editions.&amp;rdquo; On Home and Pro the floor is Required.&lt;/p>
&lt;p>Hoffman makes the same point about the scripts in his test: they can flip a policy value, but &amp;ldquo;Windows will ignore it unless you&amp;rsquo;re using a Long-Term Servicing Channel (LTSC) version of Windows 11.&amp;rdquo; My own box has the AllowTelemetry policy set to 1, which is Required, and that is as low as it goes.&lt;/p>
&lt;p>&lt;strong>Know what cannot come back.&lt;/strong> Win11Debloat&amp;rsquo;s wiki says &amp;ldquo;To my knowledge, the only apps that cannot (easily) be reinstalled are the Microsoft Store itself and the XboxSpeechToTextOverlay,&amp;rdquo; and its app-removal page carries a warning on Windows Terminal: do not remove it if you launched the script from it. Leave the Store alone unless you have decided never to use a Store app again.&lt;/p>
&lt;p>&lt;strong>Make a restore point&lt;/strong> from Start, type &amp;ldquo;Create a restore point,&amp;rdquo; and hit Create. If Create is greyed out, select the system drive, choose Configure and turn protection on first. Then do the work.&lt;/p>
&lt;h2 id="step-1-remove-the-apps-settings-then-powershell">Step 1: remove the apps (Settings, then PowerShell)&lt;/h2>
&lt;p>Microsoft&amp;rsquo;s own instruction is short: &amp;ldquo;Select Start &amp;gt; Settings &amp;gt; Apps &amp;gt; Installed apps. Find the app you want to remove, select More &amp;gt; Uninstall.&amp;rdquo; On my 25H2 box the page reads Apps &amp;gt; Installed apps in the breadcrumb, and every row has a More options button with Uninstall in it.&lt;/p>
&lt;p>Do this for whichever of the Xbox apps, Clipchamp, the new Outlook, Solitaire, News, Weather, To Do and Teams your box still has, and anything else you never open. Mine has none of them left, so I could not re-run the removals for this page. Microsoft adds that &amp;ldquo;Some apps can&amp;rsquo;t be uninstalled from the Settings app right now,&amp;rdquo; which is where PowerShell comes in.&lt;/p>
&lt;p>Open Terminal and list what is installed:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>Get-AppxPackage | Where-Object { &lt;span style="color:#f92672">-not&lt;/span> $_.IsFramework &lt;span style="color:#f92672">-and&lt;/span> &lt;span style="color:#f92672">-not&lt;/span> $_.NonRemovable } | Select-Object Name | Sort-Object Name
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>That filter is the one I ran to get the 33-package figure above. Frameworks are runtime libraries other apps need. NonRemovable is Windows&amp;rsquo; own flag for the shell pieces it will not let go; on my machine that second group holds 49 packages, and they stay. To remove one package for your account, Microsoft&amp;rsquo;s reference is &lt;code>Remove-AppxPackage -Package &amp;lt;full package name&amp;gt;&lt;/code>, and it takes &lt;code>-WhatIf&lt;/code> so you can see the effect before it happens:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>Get-AppxPackage *Clipchamp* | Remove-AppxPackage -WhatIf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Get-AppxPackage *Clipchamp* | Remove-AppxPackage
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The &lt;code>-AllUsers&lt;/code> switch removes it for every account and needs an administrator terminal. Provisioned packages are the copies Windows installs for each new user account; &lt;code>Get-AppxProvisionedPackage -Online&lt;/code> lists them, and on my box that list is empty, which is why a new account here starts clean. Removing provisioned packages needs &lt;code>Remove-AppxProvisionedPackage -Online&lt;/code> as administrator, and I would run the list first and read it before removing anything from it.&lt;/p>
&lt;h2 id="step-2-turn-off-the-recommendations-and-the-ads">Step 2: turn off the recommendations and the ads&lt;/h2>
&lt;p>These are the toggles that make the machine feel debloated, and every one is in Settings. I opened each page on 25H2 to get the labels right; the values in brackets are what my box has.&lt;/p>
&lt;p>&lt;strong>Settings &amp;gt; Personalization &amp;gt; Start&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>Show recommendations for tips, shortcuts, new apps, and more [off]&lt;/li>
&lt;li>Show recommended files in Start, recent files in File Explorer, and items in Jump Lists [off]&lt;/li>
&lt;li>Show most used apps [off]&lt;/li>
&lt;li>Show account-related notifications [off]&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Settings &amp;gt; Privacy &amp;amp; security &amp;gt; Recommendations &amp;amp; offers&lt;/strong> (that is the page title on my 25H2 box)&lt;/p>
&lt;ul>
&lt;li>Personalized offers, &amp;ldquo;Get personalized tips, ads, and recommendations based on my Windows activity&amp;rdquo; [off]&lt;/li>
&lt;li>Advertising ID, &amp;ldquo;Let apps show me personalized ads by using my advertising ID&amp;rdquo; [off]&lt;/li>
&lt;li>Recommendations and offers in Settings [off]&lt;/li>
&lt;li>Improve Start and search results, &amp;ldquo;Let Windows improve Start and search results by tracking which apps I open&amp;rdquo; [on on my box; turn it off if app-launch tracking bothers you]&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Settings &amp;gt; Privacy &amp;amp; security &amp;gt; Diagnostics &amp;amp; feedback&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>Diagnostic data, &amp;ldquo;Helps to improve Windows and keep it secure, up to date, and working as expected&amp;rdquo; [reads Off on my box, and the page carries the banner &amp;ldquo;Some of these settings are managed by your organization,&amp;rdquo; which is what a policy value set by a script looks like from Settings]. Required stays on regardless, per the floor above.&lt;/li>
&lt;li>Improve inking and typing, &amp;ldquo;Send optional inking and typing diagnostic data to Microsoft&amp;rdquo; [off]&lt;/li>
&lt;li>Delete diagnostic data, further down the same page, clears what Microsoft has collected from this device.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Settings &amp;gt; System &amp;gt; Notifications &amp;gt; Additional settings&lt;/strong> holds the welcome-experience, setup-suggestion and tips checkboxes. Clear them.&lt;/p>
&lt;h2 id="step-3-the-switches-settings-hides-on-home">Step 3: the switches Settings hides on Home&lt;/h2>
&lt;p>Two things people want gone have no toggle in the Home edition&amp;rsquo;s Settings app, and this is the only place I reach for a policy value or a script.&lt;/p>
&lt;p>&lt;strong>Web results in the Start search box.&lt;/strong> My box has the Explorer policy value &lt;code>DisableSearchBoxSuggestions&lt;/code> set to 1 under &lt;code>HKCU\Software\Policies\Microsoft\Windows\Explorer&lt;/code>, and the Start search box returns only local results. It is the mechanism behind Win11Debloat&amp;rsquo;s default tweak &amp;ldquo;Disable Bing web search &amp;amp; Copilot integration in search&amp;rdquo;: the script&amp;rsquo;s own registry file for that tweak sets exactly this value.&lt;/p>
&lt;p>One Microsoft Q&amp;amp;A thread reports the value also disabling taskbar search on Windows 10 version 1903; on my 25H2 box the search box works and simply stops showing web results. Set it by script or by hand in the registry editor, then sign out and back in.&lt;/p>
&lt;p>&lt;strong>Copilot.&lt;/strong> The Copilot app uninstalls from Installed apps like any other Store app, and that is the removal that holds.&lt;/p>
&lt;p>My box also carries &lt;code>TurnOffWindowsCopilot&lt;/code> set to 1 under &lt;code>HKCU\Software\Policies\Microsoft\Windows\WindowsCopilot&lt;/code>, and no Copilot package is installed, but read Microsoft&amp;rsquo;s note on that policy before you copy it: the WindowsAI policy reference marks it deprecated and says it &amp;ldquo;isn&amp;rsquo;t for the new Copilot experience.&amp;rdquo; Win11Debloat&amp;rsquo;s default list includes &amp;ldquo;Disable Microsoft Copilot,&amp;rdquo; &amp;ldquo;Disable Windows Recall&amp;rdquo; and &amp;ldquo;Disable Click To Do, AI text &amp;amp; image analysis&amp;rdquo; (its wiki marks all three as needing Windows build 22621 or later), which map to the Recall and Click to Do policies Microsoft documents under Windows AI.&lt;/p>
&lt;p>Microsoft lists those policies for Pro, Enterprise and Education; Home is not on the supported-editions table, so treat them as unsupported on Home even where the value writes.&lt;/p>
&lt;h2 id="step-4-the-scripts-and-what-each-one-changes">Step 4: the scripts, and what each one changes&lt;/h2>
&lt;p>Two scripts are the ones people land on, and both are open source with their change lists published, which is the only reason I would run either. Both change system-wide settings and need administrator rights, and a script run as administrator has full control of the PC. So the order is: restore point, read the change list, then run it.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Win11Debloat&lt;/th>
&lt;th scope="col">WinUtil&lt;/th>
&lt;th scope="col">Ultimate Windows Tweaker 5.2&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Who makes it&lt;/td>
&lt;td data-label="Win11Debloat">Raphire, open source on GitHub&lt;/td>
&lt;td data-label="WinUtil">Chris Titus Tech, open source on GitHub&lt;/td>
&lt;td data-label="Ultimate Windows Tweaker 5.2">Paras Sidhu for TheWindowsClub&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Release checked&lt;/td>
&lt;td data-label="Win11Debloat">2026.10.30&lt;/td>
&lt;td data-label="WinUtil">26.11.13&lt;/td>
&lt;td data-label="Ultimate Windows Tweaker 5.2">5.2 (publisher page)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Published checksum&lt;/td>
&lt;td data-label="Win11Debloat">&lt;code>SHA256SUMS&lt;/code> file with the release ZIP&lt;/td>
&lt;td data-label="WinUtil">SHA-256 on the release&amp;rsquo;s asset list&lt;/td>
&lt;td data-label="Ultimate Windows Tweaker 5.2">None on the publisher page&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">What it changes&lt;/td>
&lt;td data-label="Win11Debloat">App removal plus a default list of privacy, ads, search and Copilot tweaks&lt;/td>
&lt;td data-label="WinUtil">Presets of tweaks, plus a service-startup change in its Standard preset&lt;/td>
&lt;td data-label="Ultimate Windows Tweaker 5.2">More than 200 individual settings in one window&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">How to undo&lt;/td>
&lt;td data-label="Win11Debloat">Run it again and untick the tweak; Restore backup for the registry backup&lt;/td>
&lt;td data-label="WinUtil">Tweaks tab, select the same tweak, Undo Selected Tweaks; or System Restore from your restore point&lt;/td>
&lt;td data-label="Ultimate Windows Tweaker 5.2">Its restore-point and restore-default buttons&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>&lt;strong>Win11Debloat&lt;/strong> (Raphire, release 2026.10.30, checked November 18, 2026). The &lt;a href="https://github.com/Raphire/Win11Debloat/releases/tag/2026.10.30" rel="noopener">2026.10.30 release&lt;/a> ships &lt;code>Win11Debloat.zip&lt;/code> with a &lt;code>SHA256SUMS&lt;/code> file whose line for the ZIP reads &lt;code>6830bf501d2740c3317133ac0ecdc2a3ab80ed7f6c83e7f0f20dc66afbf758a7&lt;/code>. Download both, then check the ZIP in a normal PowerShell window:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>$expectedHash = &lt;span style="color:#e6db74">&amp;#39;6830bf501d2740c3317133ac0ecdc2a3ab80ed7f6c83e7f0f20dc66afbf758a7&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>$actualHash = (Get-FileHash -LiteralPath &lt;span style="color:#e6db74">&amp;#39;.\Win11Debloat.zip&amp;#39;&lt;/span> -Algorithm SHA256 -ErrorAction Stop).Hash
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">if&lt;/span> ($actualHash &lt;span style="color:#f92672">-ne&lt;/span> $expectedHash) { &lt;span style="color:#66d9ef">throw&lt;/span> &lt;span style="color:#e6db74">&amp;#39;Checksum mismatch. Do not run this file.&amp;#39;&lt;/span> }
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Extract the whole folder together. Review &lt;code>Run.bat&lt;/code>, &lt;code>Win11Debloat.ps1&lt;/code>, and the scripts, configuration and registry files for the changes you intend to make. Then double-click the local &lt;code>Run.bat&lt;/code> and accept the administrator prompt, as the project&amp;rsquo;s &lt;a href="https://github.com/Raphire/Win11Debloat/blob/2026.10.30/README.md" rel="noopener">README&lt;/a> documents for its traditional method. The README&amp;rsquo;s quick method pipes a downloaded script straight into PowerShell; skip it, because you can&amp;rsquo;t review what it fetches. Stay with manual Settings if you cannot review the tool&amp;rsquo;s selected changes.&lt;/p>
&lt;p>Its default tweaks, quoted from the wiki, include &amp;ldquo;Create a system restore point,&amp;rdquo; &amp;ldquo;Disable telemetry, tracking &amp;amp; targeted ads,&amp;rdquo; &amp;ldquo;Disable tips, tricks &amp;amp; suggested content throughout Windows,&amp;rdquo; &amp;ldquo;Disable ads, suggestions and newsfeed in Edge,&amp;rdquo; &amp;ldquo;Disable Bing web search &amp;amp; Copilot integration in search,&amp;rdquo; &amp;ldquo;Disable Microsoft Copilot,&amp;rdquo; &amp;ldquo;Disable Windows Recall,&amp;rdquo; &amp;ldquo;Disable Click To Do, AI text &amp;amp; image analysis,&amp;rdquo; &amp;ldquo;Disable widgets on the taskbar &amp;amp; lock screen,&amp;rdquo; and &amp;ldquo;Show file extensions for known file types.&amp;rdquo;&lt;/p>
&lt;p>It also removes a default list of apps that runs from the Bing apps and Solitaire to Candy Crush, Disney+, Netflix, Spotify and TikTok. One tweak to check before you apply: PCMag&amp;rsquo;s April test says &amp;ldquo;the default settings disable Fast Startup in Windows,&amp;rdquo; which forces a full shutdown every time, while the tool&amp;rsquo;s current Default-Settings wiki does not list Fast Startup among its default tweaks; the README lists disabling it as an optional feature.&lt;/p>
&lt;p>Read the checkbox state on your run rather than either of us. Reverting is documented: &amp;ldquo;Almost all changes can be reverted simply by running the script again and unchecking any tweaks you want to undo&amp;rdquo; (with the Detect applied tweaks checkbox ticked on the System Tweaks page), plus a registry backup the script creates before it applies changes, and undo registry files shipped with the script. The wiki notes that the backup does not bring back uninstalled apps.&lt;/p>
&lt;p>&lt;strong>WinUtil&lt;/strong> (Chris Titus Tech). The &lt;a href="https://github.com/ChrisTitusTech/winutil/releases/tag/26.11.13" rel="noopener">26.11.13 release&lt;/a> publishes &lt;code>winutil.ps1&lt;/code> with &lt;a href="https://github.com/ChrisTitusTech/winutil/releases/expanded_assets/26.11.13" rel="noopener">asset SHA-256&lt;/a> &lt;code>e9d05a59d564b4fbb61fcfa1a594504a0f81e8d27c787119e72a99b57ddbe66d&lt;/code>. Save and check that exact release in a normal PowerShell window:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>Invoke-WebRequest -Uri &lt;span style="color:#e6db74">&amp;#39;https://github.com/ChrisTitusTech/winutil/releases/download/26.11.13/winutil.ps1&amp;#39;&lt;/span> -OutFile &lt;span style="color:#e6db74">&amp;#39;.\winutil-26.11.13.ps1&amp;#39;&lt;/span> -ErrorAction Stop
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>$expectedHash = &lt;span style="color:#e6db74">&amp;#39;e9d05a59d564b4fbb61fcfa1a594504a0f81e8d27c787119e72a99b57ddbe66d&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>$actualHash = (Get-FileHash -LiteralPath &lt;span style="color:#e6db74">&amp;#39;.\winutil-26.11.13.ps1&amp;#39;&lt;/span> -Algorithm SHA256 -ErrorAction Stop).Hash
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">if&lt;/span> ($actualHash &lt;span style="color:#f92672">-ne&lt;/span> $expectedHash) { &lt;span style="color:#66d9ef">throw&lt;/span> &lt;span style="color:#e6db74">&amp;#39;Checksum mismatch. Do not run this file.&amp;#39;&lt;/span> }
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>notepad &lt;span style="color:#e6db74">&amp;#39;.\winutil-26.11.13.ps1&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Review the saved script and the release&amp;rsquo;s &lt;a href="https://github.com/ChrisTitusTech/winutil/blob/26.11.13/config/preset.json" rel="noopener">preset&lt;/a> and &lt;a href="https://github.com/ChrisTitusTech/winutil/blob/26.11.13/config/tweaks.json" rel="noopener">tweak&lt;/a> definitions before launching it. The checksum checks this file; selected functions can still fetch other software or scripts, whose sources need review too. After making a restore point and choosing your changes, open Windows PowerShell as administrator, return to the folder you reviewed, and run &lt;code>&amp;amp; .\winutil-26.11.13.ps1&lt;/code>. If PowerShell blocks the script, the project&amp;rsquo;s FAQ gives this command, which applies to the current session only: &lt;code>Set-ExecutionPolicy Unrestricted -Scope Process -Force&lt;/code>. The project&amp;rsquo;s own documented launch is &lt;code>irm &amp;quot;https://christitus.com/win&amp;quot; | iex&lt;/code>, which downloads and runs the latest script in one step as administrator; this page saves a pinned release first so you can check and read the file before it gets those rights.&lt;/p>
&lt;p>The README says WinUtil must be run as Administrator because it makes system-wide changes. Inspect every checked item in the preset before applying it. To undo, the project&amp;rsquo;s FAQ says to open WinUtil again, go to the Tweaks tab, select the same tweak and click Undo Selected Tweaks, or to use System Restore if you made a restore point.&lt;/p>
&lt;p>Hoffman&amp;rsquo;s finding on the Standard preset is the one to know before you click it: it &amp;ldquo;sets a large number of background system services to launch manually when programs access them, rather than automatically at boot,&amp;rdquo; which saved no meaningful RAM in his test and &amp;ldquo;might introduce delays in regular computer use.&amp;rdquo;&lt;/p>
&lt;p>&lt;strong>Ultimate Windows Tweaker 5.2&lt;/strong> is a different kind of tool: a portable program from TheWindowsClub with more than 200 settings in one window, and no public change-list repository like the two scripts above. Its &lt;a href="https://www.thewindowsclub.com/ultimate-windows-tweaker-5-for-windows-11" rel="noopener">publisher page&lt;/a> asks you to create a restore point with its button first, and offers restore-default buttons; deleting the program folder removes the program, not settings already applied. Treat each switch as a separate system change, apply one category at a time, and check the result.&lt;/p>
&lt;p>My rule for both is short. Run the manual steps first. Then open the script, uncheck everything you already did or do not understand, and apply the two or three switches you came for. A script that changes forty things you did not read about is not a debloat. It is someone else&amp;rsquo;s preferences.&lt;/p>
&lt;h2 id="step-5-check-that-it-worked">Step 5: check that it worked&lt;/h2>
&lt;ul>
&lt;li>Run the &lt;code>Get-AppxPackage&lt;/code> filter from Step 1 again and count the rows. Mine is 33, and every name on the list is something I recognise.&lt;/li>
&lt;li>Open Start. No &amp;ldquo;Recommended&amp;rdquo; section, no app suggestions.&lt;/li>
&lt;li>Open Settings &amp;gt; Privacy &amp;amp; security &amp;gt; Diagnostics &amp;amp; feedback and confirm optional data is off. It will not say &amp;ldquo;off&amp;rdquo; for required data on Home or Pro, and nothing you ran changed that.&lt;/li>
&lt;li>Type a word into the Start search box and confirm the results are local only.&lt;/li>
&lt;li>Reboot twice. Microsoft makes no promise about what an update restores, and Hoffman warns that one &amp;ldquo;might reinstall parts of Windows you removed or otherwise undo your changes,&amp;rdquo; so check the list again after the next feature update.&lt;/li>
&lt;/ul>
&lt;p>If a game still stutters or the desktop feels slow, open Task Manager (Ctrl+Shift+Esc), check CPU, memory and disk activity and the Startup apps list, and disable only startup entries you recognize and don&amp;rsquo;t need. Then use the &lt;a href="https://techfuelhq.com/articles/pc-stuttering-in-games-2026/">stuttering guide&lt;/a> or &lt;a href="https://techfuelhq.com/articles/low-gpu-usage-2026/">low GPU usage&lt;/a> to find the cause. &lt;a href="https://techfuelhq.com/gaming/game-mode-on-or-off-2026/">Game Mode&lt;/a>, &lt;a href="https://techfuelhq.com/gaming/hardware-accelerated-gpu-scheduling-on-or-off-2026/">hardware-accelerated GPU scheduling&lt;/a>, &lt;a href="https://techfuelhq.com/gaming/memory-integrity-on-or-off-2026/">Memory Integrity&lt;/a> and the &lt;a href="https://techfuelhq.com/gaming/ultimate-performance-power-plan-2026/">Ultimate Performance power plan&lt;/a> each have their own on-or-off guide. Test one change at a time; removing apps does not establish where the remaining slowdown comes from.&lt;/p>
&lt;h2 id="windows-10">Windows 10&lt;/h2>
&lt;p>Win11Debloat&amp;rsquo;s repository says it works for both Windows 10 and Windows 11. The similarly named Sycnex Windows10Debloater is a separate project that is archived on GitHub, so review the maintained tool&amp;rsquo;s current app list and undo instructions instead of copying an old removal preset.&lt;/p></description></item><item><title>Critical Process Died? Check the Drive First (2026)</title><link>https://techfuelhq.com/articles/critical-process-died-2026/</link><pubDate>Wed, 26 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/critical-process-died-2026/</guid><atom:updated>2026-11-18T05:05:11Z</atom:updated><description>&lt;p>&lt;strong>CRITICAL_PROCESS_DIED&lt;/strong> (&lt;code>0x000000EF&lt;/code>) means a process Windows can&amp;rsquo;t run without has terminated, so Windows stopped on purpose. Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef--critical-process-died" rel="noopener">Bug Check 0xEF reference&lt;/a> says the check happens when the state of that process is corrupted or damaged. The stop code names the victim, never the killer: a damaged system file, a bad update or driver, a drive returning bad data, or unstable memory can all end the same way.&lt;/p>
&lt;p>Most of the fixes keep your files. The steps below run from the free, read-only checks to the repairs, and they put the drive near the front because a failing drive puts your files at risk while you troubleshoot.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Back up first if your files matter.&lt;/strong> Copy irreplaceable folders to an external drive or cloud storage before any repair, and open a few copies to confirm they read. If copying stalls at zero throughput, hangs Windows, throws I/O device (&lt;code>0x8007045D&lt;/code>) or cyclic redundancy check (&lt;code>0x80070017&lt;/code>) errors, or the drive disappears until you cycle the power, stop: don&amp;rsquo;t run &lt;code>chkdsk&lt;/code>, Startup Repair or a reset, and go to &lt;a href="#7-if-the-drive-is-the-verdict-rescue-then-replace">Step 7&lt;/a>.&lt;/p>&lt;/blockquote>
&lt;p>&lt;strong>Pick your route:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Windows still reaches the desktop:&lt;/strong> work Steps 1 to 7 in order.&lt;/li>
&lt;li>&lt;strong>Boot loop, or it blue-screens at the logo:&lt;/strong> start with &lt;a href="#if-windows-wont-start-the-winre-route">If Windows won&amp;rsquo;t start&lt;/a>, then come back to the steps from Safe Mode.&lt;/li>
&lt;li>&lt;strong>A different stop code, or restarts with no blue screen:&lt;/strong> a &lt;a href="https://techfuelhq.com/articles/page-fault-in-nonpaged-area-2026/">PAGE_FAULT_IN_NONPAGED_AREA&lt;/a> code has its own guide, and restarts without a code belong with &lt;a href="https://techfuelhq.com/articles/pc-randomly-restarts-2026/">random restarts&lt;/a> and &lt;a href="https://techfuelhq.com/articles/psu-failure-symptoms-2026/">PSU failure symptoms&lt;/a>.&lt;/li>
&lt;/ul>
&lt;h2 id="1-read-the-crash-in-event-viewer">1. Read the crash in Event Viewer&lt;/h2>
&lt;p>This needs nothing but Windows.&lt;/p>
&lt;ol>
&lt;li>Open &lt;strong>Event Viewer&lt;/strong> and go to &lt;strong>Windows Logs &amp;gt; System&lt;/strong>.&lt;/li>
&lt;li>Find the &lt;strong>Kernel-Power&lt;/strong> event with ID &lt;strong>41&lt;/strong> logged when the PC came back up. On its &lt;strong>Details&lt;/strong> tab, &lt;code>BugcheckCode&lt;/code> is the stop code in decimal: &lt;code>239&lt;/code> is &lt;code>0xEF&lt;/code>. &lt;code>BugcheckParameter2&lt;/code> is Parameter 2, which Microsoft defines as &lt;code>0&lt;/code> when a process terminated and &lt;code>1&lt;/code> when a thread did.&lt;/li>
&lt;li>Look at the System log entries from the minutes before that restart. &lt;code>disk&lt;/code>, &lt;code>stornvme&lt;/code>, &lt;code>storahci&lt;/code> or &lt;code>WHEA-Logger&lt;/code> errors there send you to Step 2 before anything else.&lt;/li>
&lt;/ol>
&lt;p>&lt;a href="https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/event-id-41-restart" rel="noopener">Microsoft&amp;rsquo;s Event ID 41 page&lt;/a> documents those fields and the decimal format. If &lt;code>BugcheckCode&lt;/code> reads &lt;code>0&lt;/code>, Windows couldn&amp;rsquo;t record the stop code. Microsoft points to interrupted power or an underpowered or faulty power supply, or to a missing dump file: a &lt;code>volmgr&lt;/code> event 46 means the page file configuration needs checking. An empty &lt;code>C:\Windows\Minidump&lt;/code> folder is not a drive verdict by itself either: Windows needs a paging file on the boot volume to write a dump, and the dump type is chosen under Startup and Recovery &amp;gt; Write debugging information.&lt;/p>
&lt;p>Copy any &lt;code>.dmp&lt;/code> files from &lt;code>C:\Windows\Minidump&lt;/code> to your backup drive while you&amp;rsquo;re there, so later repairs can&amp;rsquo;t remove them. If you want the logs too, an elevated Terminal exports them:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>wevtutil epl System &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$HOME&lt;span style="color:#e6db74">\Desktop\0xef-system.evtx&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>wevtutil epl Application &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$HOME&lt;span style="color:#e6db74">\Desktop\0xef-application.evtx&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="2-check-the-drive-the-two-minute-test-the-checklists-bury">2. Check the drive: the two-minute test the checklists bury&lt;/h2>
&lt;p>Once your files and crash clues are safe off the machine, my own two-minute screen is reading the system drive&amp;rsquo;s health report and matching it against the System log. I run this read-only screen on every blue-screening PC as my own habit because it takes two minutes, though a clean SMART screen is never a standalone diagnosis.&lt;/p>
&lt;p>Open &lt;strong>CrystalDiskInfo&lt;/strong> (from Crystal Dew World), or, for an NVMe SSD, the built-in Windows route in the &lt;a href="https://techfuelhq.com/articles/ssd-health-check-2026/">SSD health check&lt;/a>, and select the system drive. Record its model, serial, and the time of the reading alongside three checks:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>The health banner.&lt;/strong> Caution or Bad on the boot drive means back up and go to Step 7. A Good banner cannot rule out a controller reset, loose M.2 slot, or silent firmware stall.&lt;/li>
&lt;li>&lt;strong>SATA SSDs and hard drives:&lt;/strong> record raw counts for Reallocated (&lt;code>05&lt;/code>), Current Pending (&lt;code>C5&lt;/code>), and Uncorrectable (&lt;code>C6&lt;/code>) sectors. Climbing numbers alongside read stalls matter far more than a static old non-zero value. The &lt;a href="https://techfuelhq.com/articles/hard-drive-health-check-2026/">hard drive health check&lt;/a> explains each attribute.&lt;/li>
&lt;li>&lt;strong>NVMe SSDs:&lt;/strong> check &lt;code>Media and Data Integrity Errors&lt;/code>, &lt;code>Error Information Log Entries&lt;/code>, and &lt;code>Available Spare&lt;/code>. &lt;a href="https://learn.microsoft.com/en-us/windows/win32/api/nvme/ns-nvme-nvme_health_info_log" rel="noopener">Microsoft&amp;rsquo;s NVMe field reference&lt;/a> says a &lt;code>Percentage Used&lt;/code> value of 100 means the estimated endurance has been consumed, but may not indicate a failure, so it&amp;rsquo;s not proof the SSD caused today&amp;rsquo;s &lt;code>0xEF&lt;/code>.&lt;/li>
&lt;/ol>
&lt;p>Then match the reading against the System log from Step 1:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What precedes the &lt;code>0xEF&lt;/code> crash&lt;/th>
&lt;th scope="col">Next move&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What precedes the 0xEF crash">&lt;code>disk&lt;/code> Event ID &lt;code>7&lt;/code>, &lt;code>51&lt;/code> or &lt;code>153&lt;/code> (bad block, paging error or retried I/O), &lt;code>stornvme&lt;/code> or &lt;code>storahci&lt;/code> Event ID &lt;code>129&lt;/code> (controller reset), &lt;code>WHEA-Logger&lt;/code> Event ID &lt;code>17&lt;/code> on the NVMe root port, or the drive dropping out of BIOS or Explorer&lt;/td>
&lt;td data-label="Next move">&lt;strong>Back up before any repair.&lt;/strong> If SMART media or sector errors are climbing, go to Step 7. If the counters stay at zero, power down, unplug, reseat the M.2 drive or swap the SATA cable and port, and watch whether the resets stop. A &lt;a href="https://techfuelhq.com/articles/whea-uncorrectable-error-2026/">WHEA_UNCORRECTABLE_ERROR&lt;/a> alongside &lt;code>0xEF&lt;/code> has its own hardware-record guide.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What precedes the 0xEF crash">Storage logs quiet, files copied cleanly, and the Application log or Reliability Monitor shows &lt;code>csrss.exe&lt;/code>, &lt;code>services.exe&lt;/code>, &lt;code>svchost.exe&lt;/code>, &lt;code>winlogon.exe&lt;/code> or a third-party service faulting after an update or driver install&lt;/td>
&lt;td data-label="Next move">&lt;strong>Go to Step 3.&lt;/strong> The drive passed its read-only check for now; the software half is next.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Keep &lt;code>chkdsk C: /r&lt;/code> off any suspect boot drive. &lt;a href="https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk" rel="noopener">Microsoft documents that &lt;code>/r&lt;/code>&lt;/a> locates bad sectors, includes everything &lt;code>/f&lt;/code> does, and checks every sector&amp;rsquo;s physical integrity. That&amp;rsquo;s a heavy job for a drive that&amp;rsquo;s already struggling. DISM and sfc are different: they check Windows system files, not every sector.&lt;/p>
&lt;h2 id="3-undo-the-last-update-driver-or-app">3. Undo the last update, driver or app&lt;/h2>
&lt;p>Microsoft&amp;rsquo;s 0xEF tips start with what changed: remove hardware you added recently, and remove or update device drivers or system services that were added just before the crashes began.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>A Windows update?&lt;/strong> If Reliability Monitor (press Start, type &lt;code>reliability&lt;/code>) shows the first red X within days of an update, remove it from &lt;strong>Settings &amp;gt; Windows Update &amp;gt; Update history &amp;gt; Uninstall updates&lt;/strong>, per &lt;a href="https://support.microsoft.com/en-us/windows/deployment/updates-lifecycle/how-to-uninstall-a-windows-update" rel="noopener">Microsoft&amp;rsquo;s uninstall steps&lt;/a>. Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/experience/backup-recovery/recovery-options-in-windows" rel="noopener">recovery options page&lt;/a> says this leaves your files and apps alone. Some updates can&amp;rsquo;t be uninstalled.&lt;/li>
&lt;li>&lt;strong>A driver?&lt;/strong> If a GPU, chipset, storage or security driver landed right before the crashes, open Device Manager, right-click the device, then &lt;strong>Properties &amp;gt; Driver &amp;gt; Roll Back Driver&lt;/strong>. While you&amp;rsquo;re there, look for devices marked with an exclamation point, which Microsoft&amp;rsquo;s tips also name.&lt;/li>
&lt;li>&lt;strong>Third-party software?&lt;/strong> A &lt;a href="https://support.microsoft.com/en-us/windows/experience/startup-boot/how-to-perform-a-clean-boot-in-windows" rel="noopener">clean boot&lt;/a> starts Windows with only essential drivers and startup programs: in System Configuration (&lt;code>msconfig&lt;/code>), select &lt;strong>Hide all Microsoft services&lt;/strong>, then &lt;strong>Disable all&lt;/strong>, and disable the startup apps in Task Manager. If the crashes stop, turn things back on half at a time to find the one responsible. Microsoft also documents a case where a developer&amp;rsquo;s service is set to restart the computer when it fails; removing that software is the fix there.&lt;/li>
&lt;/ul>
&lt;h2 id="4-repair-windows-files-and-scan-for-malware">4. Repair Windows files and scan for malware&lt;/h2>
&lt;ol>
&lt;li>&lt;strong>Install pending updates&lt;/strong> (Settings &amp;gt; Windows Update &amp;gt; Check for updates) and restart, as Microsoft&amp;rsquo;s SFC instructions ask before the repair.&lt;/li>
&lt;li>&lt;strong>Run DISM, then sfc&lt;/strong>, from an administrator Command Prompt, in the order &lt;a href="https://support.microsoft.com/en-us/windows/experience/backup-recovery/using-system-file-checker-in-windows" rel="noopener">Microsoft&amp;rsquo;s System File Checker instructions&lt;/a> give:&lt;/li>
&lt;/ol>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>DISM.exe /Online /Cleanup-image /Restorehealth
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sfc /scannow
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Wait for &amp;ldquo;The operation completed successfully&amp;rdquo; before starting &lt;code>sfc&lt;/code>, then reboot. These repair corrupted Microsoft system files; they cannot fix a buggy third-party &lt;code>.sys&lt;/code> driver or unstable hardware. If either stalls or new &lt;code>disk&lt;/code> or &lt;code>stornvme&lt;/code> events appear while it runs, stop and go back to Step 2.&lt;/p>
&lt;ol start="3">
&lt;li>&lt;strong>Scan for malware.&lt;/strong> Microsoft&amp;rsquo;s 0xEF page includes a virus scan that checks the Master Boot Record, because infection can corrupt a disk badly enough to cause bug checks. In Windows Security, open &lt;strong>Virus &amp;amp; threat protection &amp;gt; Scan options&lt;/strong> and run &lt;strong>Microsoft Defender Antivirus (offline scan)&lt;/strong>, which &lt;a href="https://support.microsoft.com/en-us/windows/security/threat-malware-protection/virus-and-threat-protection-in-the-windows-security-app" rel="noopener">Microsoft says&lt;/a> restarts and scans without loading Windows.&lt;/li>
&lt;/ol>
&lt;h2 id="5-reinstall-windows-and-keep-your-files">5. Reinstall Windows and keep your files&lt;/h2>
&lt;p>If the crashes survive the file repair, reinstall Windows in place. Both of Microsoft&amp;rsquo;s routes can keep your files and your apps.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Fix problems using Windows Update&lt;/strong> (Windows 11): &lt;strong>Settings &amp;gt; System &amp;gt; Recovery&lt;/strong>, then &lt;strong>Reinstall now&lt;/strong> under Fix problems using Windows Update. &lt;a href="https://support.microsoft.com/en-us/windows/deployment/install-upgrade/fix-issues-by-reinstalling-the-current-version-of-windows" rel="noopener">Microsoft says&lt;/a> it reinstalls the version you already have, repairs system files and components, and preserves your apps, files and settings. Keep the PC on power and online. It can be missing on PCs managed by work or school, and it needs Windows 11 with the 2022 update or later plus the February 2024 optional update or a later one.&lt;/li>
&lt;li>&lt;strong>In-place upgrade from installation media&lt;/strong> (Windows 11 or 10): create the installation media, open &lt;code>setup.exe&lt;/code> from the USB drive while signed in to Windows, choose &lt;strong>Change what to keep&lt;/strong>, and pick &lt;strong>Keep personal files and apps&lt;/strong>. That&amp;rsquo;s Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/deployment/install-upgrade/reinstall-windows-with-the-installation-media" rel="noopener">in-place upgrade&lt;/a> route.&lt;/li>
&lt;/ul>
&lt;p>Leave &lt;strong>Reset this PC&lt;/strong> for later. Microsoft&amp;rsquo;s recovery page calls it the most disruptive option: you can keep personal files, but apps and settings are removed. And if the cause is the drive or the memory, a fresh install fails the same way.&lt;/p>
&lt;h2 id="6-test-memory-and-firmware-settings">6. Test memory and firmware settings&lt;/h2>
&lt;p>Memory is the other part that kills critical processes: a protected process corrupted &lt;em>in RAM&lt;/em> dies just like one fed bad data from disk. The tests are free; the parts aren&amp;rsquo;t.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Running XMP or EXPO?&lt;/strong> Set memory back to its default profile and use the PC normally for about 48 hours, including whatever used to trigger the crash. That&amp;rsquo;s this site&amp;rsquo;s rule of thumb, not a pass mark: a quiet two days makes the profile worth investigating and doesn&amp;rsquo;t prove the memory or Windows is intact. PassMark&amp;rsquo;s &lt;a href="https://www.memtest86.com/troubleshooting.htm" rel="noopener">MemTest86 troubleshooting page&lt;/a> says some memory errors only appear when RAM timings are set too aggressively in the BIOS. The &lt;a href="https://techfuelhq.com/tutorials/how-to-enable-xmp-expo-2026/">XMP and EXPO guide&lt;/a> shows where the setting is.&lt;/li>
&lt;li>&lt;strong>Update the BIOS.&lt;/strong> Microsoft&amp;rsquo;s 0xEF tips include checking with the maker for an updated BIOS or firmware and running the maker&amp;rsquo;s hardware diagnostics. The &lt;a href="https://techfuelhq.com/tutorials/how-to-update-bios-2026/">BIOS update guide&lt;/a> covers the flash.&lt;/li>
&lt;li>&lt;strong>Intel Core 13th or 14th Gen desktop chip?&lt;/strong> Follow Intel&amp;rsquo;s &lt;a href="https://www.intel.com/content/www/us/en/support/articles/000102331/processors.html" rel="noopener">guidance for the Vmin Shift Instability issue&lt;/a>, which affects some of those processors: the relevant Intel Default Settings in the BIOS and the latest BIOS with microcode &lt;code>0x12F&lt;/code> or later. Intel has extended the warranty by two years for eligible affected processors, to up to five years from purchase.&lt;/li>
&lt;li>&lt;strong>Run MemTest86&lt;/strong> from a USB stick overnight (or &lt;code>mdsched.exe&lt;/code>, the built-in Windows Memory Diagnostic, for a faster first pass). PassMark notes that not every reported error is the RAM, because the test also exercises the CPU, caches and motherboard, and that some errors are temperature sensitive.&lt;/li>
&lt;li>&lt;strong>Keep the slot fixed.&lt;/strong> On a desktop with removable RAM, shut down and unplug it before each swap. Use the board manual&amp;rsquo;s single-module slot and default memory settings. Run the same test on each stick and label the results. If an error repeats on stick A while stick B passes, A is suspect. Failures that appear only with both sticks installed don&amp;rsquo;t identify either one. The &lt;a href="https://techfuelhq.com/articles/memory-management-bsod-2026/">MEMORY_MANAGEMENT guide&lt;/a> has the full slot matrix.&lt;/li>
&lt;li>&lt;strong>Power sits at the bottom of the ladder.&lt;/strong> If the machine also hard-restarts with no blue screen, shuts off under load, or needs several tries to cold-boot, check &lt;a href="https://techfuelhq.com/articles/psu-failure-symptoms-2026/">PSU failure symptoms&lt;/a>.&lt;/li>
&lt;/ul>
&lt;p>If you also saw &lt;a href="https://techfuelhq.com/articles/kernel-security-check-failure-2026/">KERNEL_SECURITY_CHECK_FAILURE&lt;/a>, that guide shows how to compare a profile change with what the crash dump recorded. Run the free tests before buying anything: current RAM and SSD prices are on the &lt;a href="https://techfuelhq.com/data/ram-price-index/">RAM price index&lt;/a> and the &lt;a href="https://techfuelhq.com/data/ssd-price-index/">SSD price index&lt;/a>, and a guessed-wrong purchase is an expensive mistake.&lt;/p>
&lt;p>&lt;strong>Stop here&lt;/strong> if the PC still crashes with stock memory settings, a current BIOS, repaired or reinstalled Windows and a drive that reads cleanly. Take the dumps, the exported logs and the drive reading to the PC or motherboard maker. Microsoft&amp;rsquo;s own resolution for 0xEF is debugger work across multiple dump files and the events before each crash, which is where support takes over.&lt;/p>
&lt;h2 id="7-if-the-drive-is-the-verdict-rescue-then-replace">7. If the drive is the verdict: rescue, then replace&lt;/h2>
&lt;p>A fresh Windows install that also crashes does not establish a failing drive. First protect the files. Look for independent storage evidence: repeated read failures on the system drive, increasing media errors, or a drive that disappears across known-good connections. A worn drive deserves attention, but a wear estimate or a stop code by itself does not explain the crash.&lt;/p>
&lt;p>The order is fixed. &lt;strong>Data off first, then replace.&lt;/strong> Copy files out from Windows or Safe Mode if they still open, or move the drive into a USB enclosure on another PC if they don&amp;rsquo;t. If copying fails or read errors climb, shut the machine down: image the drive sector by sector to a healthy target with a tool such as &lt;code>ddrescue&lt;/code> and work only on the copy, or use a professional recovery lab if this is the sole copy of irreplaceable data.&lt;/p>
&lt;p>Then swap it. Check your board&amp;rsquo;s manual for the slot type first: an M.2 slot takes an NVMe SSD, and a SATA-only machine needs a 2.5-inch SATA SSD instead. If you want one named drive, the &lt;a href="https://techfuelhq.com/articles/ssd-tier-list/">SSD tier list&lt;/a> suggests starting Tier A with the Samsung 990 PRO 1TB. On November 17, 2026, Newegg listed the 2TB 990 PRO at $389.99, the figure the &lt;a href="https://techfuelhq.com/data/ssd-price-index/">SSD price index&lt;/a> recorded that day; check the index for the latest reading. I would not reuse a drive with climbing reallocated sectors for anything — not as a game drive, not as scratch space. Its next failure has your data on it.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Samsung&amp;#43;990&amp;#43;PRO&amp;#43;1TB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/critical-process-died-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DSamsung%2B990%2BPRO%2B1TB" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/critical-process-died-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>If &lt;code>0xEF&lt;/code> returns on the replacement drive, save the new crash dump. Compare it with the earlier dump. Note which driver versions and hardware were present in both installations. Check which updates were reapplied. Microsoft recommends examining multiple dump files and the event log leading up to each crash. The repeat alone does not identify RAM, power or another drive to buy.&lt;/p>
&lt;h2 id="if-windows-wont-start-the-winre-route">If Windows won&amp;rsquo;t start: the WinRE route&lt;/h2>
&lt;p>A PC in a boot loop runs the same fixes from the Windows Recovery Environment. Before you start, get your BitLocker recovery key from another device at aka.ms/myrecoverykey, signed in to your Microsoft account, because &lt;a href="https://support.microsoft.com/en-us/windows/security/encryption/find-your-bitlocker-recovery-key" rel="noopener">Microsoft says&lt;/a> a startup prompt for it can follow a hardware change, and its support staff can&amp;rsquo;t retrieve a lost key.&lt;/p>
&lt;p>Windows opens WinRE itself: Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference" rel="noopener">WinRE documentation&lt;/a> lists two consecutive failed attempts to start Windows as a trigger. If it doesn&amp;rsquo;t appear, hold the power button to turn the PC off as the Windows logo shows, twice, then let the third start load &amp;ldquo;Preparing Automatic Repair&amp;rdquo; and choose &lt;strong>Advanced options&lt;/strong>. From &lt;strong>Troubleshoot &amp;gt; Advanced options&lt;/strong>, work in this order:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Copy files and logs out first if they aren&amp;rsquo;t backed up.&lt;/strong> Plug in a USB drive, open &lt;strong>Command Prompt&lt;/strong>, find the volume letters with &lt;code>diskpart&lt;/code> → &lt;code>list volume&lt;/code> → &lt;code>exit&lt;/code>, and copy irreplaceable folders plus &lt;code>C:\Windows\Minidump&lt;/code> and &lt;code>C:\Windows\System32\winevt\Logs\System.evtx&lt;/code> with &lt;code>robocopy&lt;/code>. Stop if read or CRC errors appear.&lt;/li>
&lt;li>&lt;strong>Uninstall Updates &amp;gt; Uninstall latest quality update&lt;/strong>, when the loop began right after an update. Microsoft&amp;rsquo;s recovery page says your files and apps aren&amp;rsquo;t affected.&lt;/li>
&lt;li>&lt;strong>Startup Settings &amp;gt; Restart &amp;gt; 4 (Safe Mode)&lt;/strong> or &lt;strong>5 (Safe Mode with Networking)&lt;/strong>. Microsoft describes Safe Mode as a basic state with a limited set of files and drivers. From there you can run Steps 2 to 4, roll back drivers and uninstall recent software. A machine stable in Safe Mode that crashes in normal startup points toward a third-party driver or startup service.&lt;/li>
&lt;li>&lt;strong>Startup Repair&lt;/strong>, once files and logs are safe and read cleanly.&lt;/li>
&lt;li>&lt;strong>System Restore&lt;/strong>, if you have a restore point from before the crashes. Microsoft says it rolls back system files and settings, not personal files.&lt;/li>
&lt;li>&lt;strong>Command Prompt for an offline file repair&lt;/strong>, only after files are safe and the drive shows no read errors: &lt;code>sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows&lt;/code>, substituting whichever letter &lt;code>diskpart&lt;/code> → &lt;code>list volume&lt;/code> shows for your Windows partition. Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc" rel="noopener">sfc reference&lt;/a> documents both offline switches.&lt;/li>
&lt;/ol>
&lt;p>The one tile I would leave alone for now is &lt;strong>Reset this PC&lt;/strong>. It forfeits your files-first sequencing if you haven&amp;rsquo;t copied anything out yet, and if the underlying cause is the drive, you&amp;rsquo;ll watch the fresh install fail the same way in a week. Reset is a fine last software step once the drive has been cleared and the files are safe.&lt;/p>
&lt;p>If even WinRE won&amp;rsquo;t load: reseat the drive and its cable (or the M.2 screw and slot), try the other SATA port, and test the drive in another machine through a USB enclosure. At that point you are diagnosing hardware, not Windows. If BIOS or Explorer keeps losing the drive after a reseat, a &lt;a href="https://techfuelhq.com/tutorials/how-to-update-bios-2026/">BIOS update&lt;/a> is worth trying before you replace it.&lt;/p>
&lt;h2 id="keeping-it-from-coming-back">Keeping it from coming back&lt;/h2>
&lt;p>A machine that has thrown &lt;code>0xEF&lt;/code> once earns two habits. Recheck the drive&amp;rsquo;s health in a month; sector counts that moved again settle any lingering doubt about a drive that squeaked by. And watch the pattern: a rebuilt machine that starts throwing &lt;em>different&lt;/em> stop codes has only reshuffled the problem, so test memory and power before buying parts.&lt;/p>
&lt;p>Domain-managed and BitLocker-locked corporate machines belong to your IT department, which holds keys and imaging tools you don&amp;rsquo;t. Everything else above works on any Windows 10 or 11 PC with a USB stick and a screwdriver.&lt;/p></description></item><item><title>Kernel Security Check Failure (0x139): What to Check First</title><link>https://techfuelhq.com/articles/kernel-security-check-failure-2026/</link><pubDate>Mon, 13 Jul 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/kernel-security-check-failure-2026/</guid><atom:updated>2026-11-18T05:05:11Z</atom:updated><description>&lt;p>One desktop starts throwing &lt;code>KERNEL_SECURITY_CHECK_FAILURE&lt;/code> (&lt;code>0x00000139&lt;/code>) the night a Realtek audio or Wi-Fi driver updates. Another hits the exact same blue screen twenty minutes after enabling DDR5-6400 EXPO in UEFI.&lt;/p>
&lt;p>Same stop screen. Completely different causes.&lt;/p>
&lt;p>Before pulling sticks or wiping Windows, I ask one question first. What changed right before the first &lt;code>0x139&lt;/code>? Write that answer down while the timeline is fresh, then read the first crash parameter so Windows tells you which security check tripped.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139--kernel-security-check-failure" rel="noopener">0x139 reference&lt;/a> says the bug check &amp;ldquo;indicates that the kernel detects the corruption of a critical data structure.&amp;rdquo; It doesn&amp;rsquo;t say who corrupted it. The odds favor software: Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/stop-error-or-blue-screen-error-troubleshooting" rel="noopener">advanced stop-error guide&lt;/a> attributes 70% of the crashes it analyzed to third-party driver code and 10% to hardware. So the steps below run from the free, reversible software checks to the memory test, and WinDbg comes last.&lt;/p>
&lt;h2 id="1-read-the-stop-code-and-parameter-1-in-event-viewer">1. Read the stop code and Parameter 1 in Event Viewer&lt;/h2>
&lt;p>Windows already recorded the crash, and reading it needs no download.&lt;/p>
&lt;ol>
&lt;li>Open &lt;strong>Event Viewer&lt;/strong> from Start search and go to &lt;strong>Windows Logs &amp;gt; System&lt;/strong>.&lt;/li>
&lt;li>Find the &lt;strong>Kernel-Power&lt;/strong> event with ID &lt;strong>41&lt;/strong> logged when the PC came back up after the crash.&lt;/li>
&lt;li>On its &lt;strong>Details&lt;/strong> tab, &lt;code>BugcheckCode&lt;/code> is the stop code in decimal: &lt;code>313&lt;/code> is &lt;code>0x139&lt;/code>. &lt;code>BugcheckParameter1&lt;/code> is Parameter 1, already written in hex (for example &lt;code>0x3&lt;/code>).&lt;/li>
&lt;li>Look at the System log entries from the minutes before that restart for driver or service errors, and note the time and what you were doing.&lt;/li>
&lt;/ol>
&lt;p>&lt;a href="https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/event-id-41-restart" rel="noopener">Microsoft&amp;rsquo;s Event ID 41 page&lt;/a> documents those fields and says the code is stored in decimal, while most bug check documentation uses hex. If &lt;code>BugcheckCode&lt;/code> reads &lt;code>0&lt;/code>, Windows didn&amp;rsquo;t record a stop code for that restart. Microsoft lists two things to check then: interrupted power or an underpowered or faulty power supply, and a missing dump file (a &lt;code>volmgr&lt;/code> event 46 points at the page file configuration). The &lt;a href="https://techfuelhq.com/articles/pc-randomly-restarts-2026/">random restarts guide&lt;/a> covers that route.&lt;/p>
&lt;p>Also copy the newest &lt;code>.dmp&lt;/code> file out of &lt;code>C:\Windows\Minidump&lt;/code> into a folder on your desktop so automatic cleanup never deletes it, for Step 5 or for support. Empty folder? Check &lt;code>System Properties &amp;gt; Advanced &amp;gt; Startup and Recovery &amp;gt; Settings&lt;/code> and confirm Small memory dump (256 KB) is selected per &lt;a href="https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file" rel="noopener">Microsoft&amp;rsquo;s small-dump guide&lt;/a>. Never force-crash your PC to manufacture a dump.&lt;/p>
&lt;h3 id="match-parameter-1-to-microsofts-table">Match Parameter 1 to Microsoft&amp;rsquo;s table&lt;/h3>
&lt;p>Watch out for one classic trap here. Event Viewer and WinDbg show Parameter 1 in hexadecimal, but &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139--kernel-security-check-failure" rel="noopener">Microsoft&amp;rsquo;s 0x139 parameter table&lt;/a> lists it in decimal. Hex &lt;code>0x14&lt;/code> is decimal 20, so don&amp;rsquo;t read it as row 14; hex &lt;code>0x1d&lt;/code> is decimal 29.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Parameter 1 (hex, as Event Viewer and WinDbg show it)&lt;/th>
&lt;th scope="col">Microsoft&amp;rsquo;s table (decimal)&lt;/th>
&lt;th scope="col">Microsoft&amp;rsquo;s description&lt;/th>
&lt;th scope="col">Where to go next&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Parameter 1 (hex, as Event Viewer and WinDbg show it)">&lt;code>0x0&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s table (decimal)">&lt;code>0&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s description">A stack-based buffer is overrun (legacy /GS violation).&lt;/td>
&lt;td data-label="Where to go next">Recent driver changes (Step 2), then the module on the stack (Step 5)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Parameter 1 (hex, as Event Viewer and WinDbg show it)">&lt;code>0x2&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s table (decimal)">&lt;code>2&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s description">Stack cookie instrumentation code detected a stack-based buffer overrun (/GS violation).&lt;/td>
&lt;td data-label="Where to go next">Same as &lt;code>0x0&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Parameter 1 (hex, as Event Viewer and WinDbg show it)">&lt;code>0x3&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s table (decimal)">&lt;code>3&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s description">A LIST_ENTRY is corrupted (for example, a double remove).&lt;/td>
&lt;td data-label="Where to go next">Step 2; Microsoft&amp;rsquo;s listed causes are driver mistakes, and the damage can predate the crash (Step 5)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Parameter 1 (hex, as Event Viewer and WinDbg show it)">&lt;code>0x5&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s table (decimal)">&lt;code>5&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s description">An invalid parameter was passed to a function that considers invalid parameters fatal.&lt;/td>
&lt;td data-label="Where to go next">Steps 2 and 3, keep the dump for Step 5&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Parameter 1 (hex, as Event Viewer and WinDbg show it)">&lt;code>0xe&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s table (decimal)">&lt;code>14&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s description">The reference count for an object is invalid.&lt;/td>
&lt;td data-label="Where to go next">Steps 2 and 3&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Parameter 1 (hex, as Event Viewer and WinDbg show it)">&lt;code>0x14&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s table (decimal)">&lt;code>20&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s description">A cryptographic self-test failed.&lt;/td>
&lt;td data-label="Where to go next">Steps 3 and 4 (Windows and firmware updates)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Parameter 1 (hex, as Event Viewer and WinDbg show it)">&lt;code>0x1d&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s table (decimal)">&lt;code>29&lt;/code>&lt;/td>
&lt;td data-label="Microsoft&amp;rsquo;s description">An RTL_BALANCED_NODE RBTree entry is corrupted.&lt;/td>
&lt;td data-label="Where to go next">Same as &lt;code>0x3&lt;/code>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Any other value: convert it to decimal and read its line in Microsoft&amp;rsquo;s table. The value matters most when you compare several crashes, and when you hand them to support.&lt;/p>
&lt;h2 id="2-undo-the-last-driver-app-or-hardware-change">2. Undo the last driver, app or hardware change&lt;/h2>
&lt;p>Microsoft&amp;rsquo;s tips for 0x139 start here: if you recently added hardware, remove or replace it; if new device drivers or system services were added, remove or update them; and look in Device Manager for devices marked with an exclamation point.&lt;/p>
&lt;p>If &lt;code>0x139&lt;/code> started right after an audio, LAN/Wi-Fi, RGB utility, or game anti-cheat update, roll that change back. If crashes loop before you reach the desktop, use &lt;a href="https://support.microsoft.com/en-us/windows/windows-startup-settings-1af6ec8c-4d4a-4b23-adb7-e76eef0b847f" rel="noopener">Windows Startup Settings&lt;/a> to step back in Safe Mode.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Confirm your BitLocker key first.&lt;/strong> Microsoft notes you need it to change startup settings on an encrypted device. Look up your &lt;a href="https://support.microsoft.com/en-us/windows/security/encryption/find-your-bitlocker-recovery-key" rel="noopener">BitLocker recovery key&lt;/a> at aka.ms/myrecoverykey on a phone or second computer.&lt;/li>
&lt;li>&lt;strong>Boot into Safe Mode if you need it.&lt;/strong> Hold &lt;code>Shift&lt;/code> while clicking Restart (or let WinRE open &lt;code>Troubleshoot &amp;gt; Advanced options &amp;gt; Startup Settings &amp;gt; Restart&lt;/code>), then press &lt;code>4&lt;/code> or &lt;code>F4&lt;/code> for Enable Safe Mode. Microsoft describes Safe Mode as a basic state with a limited set of files and drivers, so a problem that doesn&amp;rsquo;t happen there isn&amp;rsquo;t coming from the default settings and basic device drivers.&lt;/li>
&lt;li>&lt;strong>Roll back the changed driver.&lt;/strong> Open Device Manager, right-click the recently updated audio, network, or display adapter, open &lt;code>Properties &amp;gt; Driver&lt;/code>, and select Roll Back Driver (&lt;a href="https://support.microsoft.com/en-us/windows/update-drivers-through-device-manager-in-windows-ec62f46c-ff14-c91d-eead-d7126dc1f7b6" rel="noopener">Microsoft&amp;rsquo;s Device Manager steps&lt;/a> need an administrator account). For a GPU crash lead (&lt;code>nvlddmkm.sys&lt;/code> or &lt;code>amdkmdag.sys&lt;/code>), follow my &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/">GPU driver crash guide&lt;/a>. If an outdated motherboard RGB or hardware-monitoring utility installed &lt;code>WinRing0x64.sys&lt;/code> or &lt;code>ene.sys&lt;/code>, uninstall that utility cleanly from Installed apps.&lt;/li>
&lt;li>&lt;strong>Test one change at a time.&lt;/strong> Reboot normally and run the exact game or workload that triggered &lt;code>0x139&lt;/code> before touching any second driver or BIOS setting.&lt;/li>
&lt;/ol>
&lt;p>If the crashes start with one game and its anti-cheat, the &lt;a href="https://techfuelhq.com/gaming/easy-anti-cheat-fix-guide-2026/">Easy Anti-Cheat fix guide&lt;/a> covers that case.&lt;/p>
&lt;h2 id="3-install-windows-updates-then-repair-system-files">3. Install Windows updates, then repair system files&lt;/h2>
&lt;ol>
&lt;li>&lt;strong>Check for updates:&lt;/strong> Start &amp;gt; Settings &amp;gt; Windows Update &amp;gt; Check for updates. Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/resolving-blue-screen-errors-in-windows-60b01860-58f2-be66-7516-5c45a66ae3c6" rel="noopener">basic stop-code steps&lt;/a> include it.&lt;/li>
&lt;li>&lt;strong>Did the crashes start with an update?&lt;/strong> Remove it from Settings &amp;gt; Windows Update &amp;gt; Update history &amp;gt; Uninstall updates, per &lt;a href="https://support.microsoft.com/en-us/Windows/Deployment/Updates-Lifecycle/how-to-uninstall-a-windows-update" rel="noopener">Microsoft&amp;rsquo;s uninstall steps&lt;/a>. Microsoft notes that some updates can&amp;rsquo;t be uninstalled.&lt;/li>
&lt;li>&lt;strong>Repair Windows files&lt;/strong>, DISM first and SFC second, from an administrator Command Prompt, as &lt;a href="https://support.microsoft.com/en-us/windows/using-system-file-checker-in-windows-365e0031-36b1-6031-f804-8fd86e0ef4ca" rel="noopener">Microsoft&amp;rsquo;s System File Checker instructions&lt;/a> order them:&lt;/li>
&lt;/ol>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>DISM.exe /Online /Cleanup-image /Restorehealth
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sfc /scannow
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Wait for &amp;ldquo;The operation completed successfully&amp;rdquo; before starting &lt;code>sfc&lt;/code>, then reboot. These repair Windows&amp;rsquo; own files. They don&amp;rsquo;t replace a third-party driver or undo a memory overclock, so a repaired file count is not the end of the story if the crashes continue.&lt;/p>
&lt;ol start="4">
&lt;li>&lt;strong>Scan for malware.&lt;/strong> Microsoft&amp;rsquo;s 0x139 page includes a virus scan that checks the Master Boot Record, because infection can corrupt a disk badly enough to cause bug checks.&lt;/li>
&lt;/ol>
&lt;h2 id="4-update-the-bios-and-test-memory-at-default-settings">4. Update the BIOS and test memory at default settings&lt;/h2>
&lt;p>Microsoft&amp;rsquo;s general stop-error steps include making sure the BIOS and firmware are up to date. The &lt;a href="https://techfuelhq.com/tutorials/how-to-update-bios-2026/">BIOS update guide&lt;/a> covers doing that safely; an interrupted flash can leave a board unable to boot.&lt;/p>
&lt;p>Did &lt;code>0x139&lt;/code> appear on a newly built PC or after turning on XMP/EXPO? Test default memory settings next.&lt;/p>
&lt;ol>
&lt;li>Reboot into UEFI and set &lt;code>XMP / EXPO&lt;/code> to &lt;code>Disabled / Auto&lt;/code> without manually altering voltages. The &lt;a href="https://techfuelhq.com/tutorials/how-to-enable-xmp-expo-2026/">XMP and EXPO guide&lt;/a> shows where the profile setting sits.&lt;/li>
&lt;li>Use the PC normally for about 48 hours, including whatever load used to trigger the crash. That&amp;rsquo;s this site&amp;rsquo;s rule of thumb, not a pass mark: a quiet two days makes the profile worth investigating, and it doesn&amp;rsquo;t prove the memory or Windows is intact.&lt;/li>
&lt;li>Look at our &lt;a href="https://techfuelhq.com/articles/ddr5-ram-buying-guide-2025/">DDR5 RAM guide&lt;/a> if four populated DDR5 slots or tight secondary timings match your build. PassMark&amp;rsquo;s &lt;a href="https://www.memtest86.com/troubleshooting.htm" rel="noopener">MemTest86 troubleshooting page&lt;/a> says some memory errors only show when RAM timings are set too aggressively in the BIOS, and suggests standard, non-XMP timings for modules that support XMP.&lt;/li>
&lt;/ol>
&lt;p>On an Intel Core 13th or 14th Gen desktop processor, also follow Intel&amp;rsquo;s &lt;a href="https://www.intel.com/content/www/us/en/support/articles/000102331/processors.html" rel="noopener">guidance for the Vmin Shift Instability issue&lt;/a>, which affects some of those chips: use the relevant Intel Default Settings in the BIOS and the latest BIOS containing microcode &lt;code>0x12F&lt;/code> or later. Intel has extended warranty coverage by two years for eligible affected processors, to up to five years from the original purchase date.&lt;/p>
&lt;p>When crashes continue at default settings, boot MemTest86 from USB and save the HTML report. PassMark notes that not every error MemTest86 reports is the RAM itself, because the test also exercises the CPU, its caches and the motherboard, and that some errors are temperature sensitive. So test one stick at a time, with the PC powered off for each swap, in the slot your board manual names for a single module, before ordering replacement RAM. The &lt;a href="https://techfuelhq.com/articles/memory-management-bsod-2026/">MEMORY_MANAGEMENT guide&lt;/a> has the full slot-by-slot matrix.&lt;/p>
&lt;h2 id="5-read-the-dump-in-windbg">5. Read the dump in WinDbg&lt;/h2>
&lt;p>If the steps above haven&amp;rsquo;t settled it, the dump you saved in Step 1 shows what was running when the check tripped.&lt;/p>
&lt;ol>
&lt;li>Open your copied &lt;code>.dmp&lt;/code> in WinDbg (&lt;code>File &amp;gt; Open crash dump&lt;/code>) and run &lt;code>!analyze -v&lt;/code> (or &lt;code>.bugcheck&lt;/code>). &lt;code>Arg1&lt;/code> is Parameter 1 from the table above.&lt;/li>
&lt;li>Microsoft&amp;rsquo;s table defines Parameter 2 as the address of the trap frame for the exception. Load it with &lt;code>.trap &amp;lt;Arg2&amp;gt;&lt;/code>, then run &lt;code>kn&lt;/code> for the call stack, and note &lt;code>IMAGE_NAME&lt;/code>. &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/analyzing-a-kernel-mode-dump-file-with-windbg" rel="noopener">Microsoft&amp;rsquo;s kernel-dump walkthrough&lt;/a> covers setup and symbols.&lt;/li>
&lt;/ol>
&lt;p>Why does &lt;code>Arg1 = 0x3&lt;/code> (&lt;code>LIST_ENTRY&lt;/code> corruption) fool so many people? Microsoft explains that the inconsistency is detected when an entry is added to or removed from the list, not necessarily at the time the corruption occurred. The driver on the stack may only be the one that tripped over the damage. Microsoft&amp;rsquo;s resolution is to examine multiple dump files for similar characteristics, and to use the event log to look for higher-level events leading up to the stop code.&lt;/p>
&lt;p>A &lt;a href="https://community.osr.com/t/bsods-on-dpc-or-stack-related-system-memory-corruption-with-a-filter-storage-driver/57920" rel="noopener">filter-driver developer&amp;rsquo;s published traces&lt;/a> show multiple &lt;code>Arg1 = 3&lt;/code> dumps landing in graphics, WDF, and windowing stacks from one underlying bug, so I compare two or three &lt;code>.dmp&lt;/code> files before convicting the first &lt;code>.sys&lt;/code> name I see.&lt;/p>
&lt;p>When other stop codes appear alongside &lt;code>0x139&lt;/code>, log them separately: &lt;a href="https://techfuelhq.com/articles/memory-management-bsod-2026/">0x1A MEMORY_MANAGEMENT&lt;/a> and &lt;a href="https://techfuelhq.com/articles/page-fault-in-nonpaged-area-2026/">0x50 PAGE_FAULT_IN_NONPAGED_AREA&lt;/a> carry their own subcode tables. A &lt;a href="https://techfuelhq.com/articles/whea-uncorrectable-error-2026/">WHEA_UNCORRECTABLE_ERROR (0x124)&lt;/a> alongside 0x139 has its own hardware-record guide, and &lt;a href="https://techfuelhq.com/articles/critical-process-died-2026/">CRITICAL_PROCESS_DIED (0xEF)&lt;/a> starts with the drive.&lt;/p>
&lt;h2 id="leave-driver-verifier-off-an-everyday-pc">Leave Driver Verifier off an everyday PC&lt;/h2>
&lt;p>Forum copy-pastes routinely tell &lt;code>0x139&lt;/code> readers to open &lt;code>verifier.exe&lt;/code> and select every installed driver. Don&amp;rsquo;t.&lt;/p>
&lt;p>&lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier" rel="noopener">Microsoft&amp;rsquo;s Driver Verifier documentation&lt;/a> says running it could cause the computer to crash and to run it only on computers you use for testing and debugging. Microsoft&amp;rsquo;s advanced stop-error guide adds: &amp;ldquo;Don&amp;rsquo;t try to verify all the drivers at one time. This action can degrade performance and make the system unusable.&amp;rdquo;&lt;/p>
&lt;p>If a technician does enable it for one suspect driver, have the way back ready before the restart: a fresh System Restore point, your BitLocker recovery key, and the undo command. The undo is &lt;code>verifier /reset&lt;/code> from an administrator Command Prompt, then a restart. If Windows can&amp;rsquo;t reach the desktop with Verifier on, start in Safe Mode, where Microsoft says the tool can&amp;rsquo;t run, and run &lt;code>verifier /reset&lt;/code> there.&lt;/p>
&lt;h2 id="what-to-give-support">What to give support&lt;/h2>
&lt;p>Stop when the PC still crashes at default BIOS and memory settings with current Windows updates, repaired system files and the last driver change undone. That&amp;rsquo;s the point to hand it to the PC, motherboard or component maker.&lt;/p>
&lt;p>Save one structured note per crash. Two dumps showing the identical &lt;code>Arg1&lt;/code> subcode and trigger tell a board vendor far more than ten blind reinstalls, though you should keep raw &lt;code>.dmp&lt;/code> files private because kernel memory fragments can sit inside them.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>Crash date, time and activity:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Stop code and Parameter 1 in hex (or &amp;#34;no dump found&amp;#34;):
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Faulting IMAGE_NAME / stack lead in WinDbg:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Windows build; recent audio/network/GPU/anti-cheat driver version:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Memory config (2x or 4x DIMMs, EXPO/XMP on vs default):
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>Single change tested and how long it ran:
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div></description></item><item><title>Keyboard Not Working? Fix It by What Actually Broke (2026)</title><link>https://techfuelhq.com/articles/keyboard-not-working-2026/</link><pubDate>Sun, 05 Jul 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/keyboard-not-working-2026/</guid><atom:updated>2026-11-18T05:05:11Z</atom:updated><description>&lt;p>&amp;ldquo;Keyboard not working&amp;rdquo; covers several different failures, and the fix depends on which one you have. Find your symptom, then start at the step it names.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Symptom&lt;/th>
&lt;th scope="col">Start at&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Symptom">Nothing types on a desktop keyboard&lt;/td>
&lt;td data-label="Start at">Steps 1 and 2, then 6 to 8&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">Keys type the wrong characters, or ignore quick taps&lt;/td>
&lt;td data-label="Start at">Steps 3 and 4&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">One key or a few nearby keys stopped working&lt;/td>
&lt;td data-label="Start at">Steps 2 and 9&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">A wireless keyboard won&amp;rsquo;t respond, or the keyboard and mouse stopped together&lt;/td>
&lt;td data-label="Start at">Step 5&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">The laptop keyboard stopped but a USB keyboard types&lt;/td>
&lt;td data-label="Start at">&lt;a href="#laptop-keyboard-not-working-what-is-different">The laptop section&lt;/a>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/hardware/input-devices/mouse-and-keyboard-problems-in-windows" rel="noopener">mouse and keyboard procedure&lt;/a> starts with power, cables, direct USB ports, fresh batteries, and a second-PC test. Those checks separate a broken keyboard from a port or Windows problem without guessing.&lt;/p>
&lt;h2 id="1-give-yourself-a-way-to-type">1. Give yourself a way to type&lt;/h2>
&lt;p>Skip this if your keys still type. Otherwise you can&amp;rsquo;t do most fixes without input, so open the on-screen keyboard first. Press &lt;code>Windows key + Ctrl + O&lt;/code>, which Microsoft lists among its &lt;a href="https://support.microsoft.com/en-us/windows/keyboard-shortcuts-for-accessibility-021bcb62-45c8-e4ef-1e4f-41b8c1fc87fd" rel="noopener">accessibility shortcuts&lt;/a>, or click Start, type &lt;code>osk&lt;/code>, and open On-Screen Keyboard with your mouse. Now you can click keys and work through the menus below.&lt;/p>
&lt;p>If the shortcut does nothing, use the mouse: &lt;strong>Start &amp;gt; Settings &amp;gt; Accessibility &amp;gt; Keyboard&lt;/strong>, then turn on &lt;strong>On-Screen Keyboard&lt;/strong>. Windows 10 calls the category &lt;strong>Ease of Access&lt;/strong>. At sign-in, use the accessibility button in the lower-right corner instead. These are Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/accessibility/windows/use-the-on-screen-keyboard-osk-to-type" rel="noopener">documented launch paths&lt;/a>.&lt;/p>
&lt;p>If OSK opens with only navigation keys, choose &lt;strong>General&lt;/strong> to restore letters; Microsoft notes that closing it does not reset the saved layout. If keys appear but don&amp;rsquo;t type when clicked, open &lt;strong>Options&lt;/strong> and select &lt;strong>Click on keys&lt;/strong>. If OSK won&amp;rsquo;t open at all, restart and install pending Windows updates, then run Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/experience/backup-recovery/using-system-file-checker-in-windows" rel="noopener">system-file repair&lt;/a>, DISM first and SFC after it, from an administrator Command Prompt. A borrowed working USB keyboard is the easiest input for that.&lt;/p>
&lt;h2 id="2-try-another-port-then-another-pc">2. Try another port, then another PC&lt;/h2>
&lt;p>Plug a wired keyboard directly into a rear USB port on a desktop, rather than a front-panel port or hub, and try another cable if it&amp;rsquo;s detachable. Microsoft&amp;rsquo;s steps are to unplug the device and wait a little while, try a different USB port, give a USB hub power or remove it, and check the cable for damage.&lt;/p>
&lt;p>Then the one test that settles the biggest question: plug the keyboard into another computer. Microsoft says that if the device doesn&amp;rsquo;t work on the other PC, you might need to replace it. If it works there, the fault is your PC&amp;rsquo;s software or ports, not the keyboard. For a laptop&amp;rsquo;s built-in keyboard, run it the other way and plug any USB keyboard into the laptop; the &lt;a href="#laptop-keyboard-not-working-what-is-different">laptop section&lt;/a> covers what that tells you.&lt;/p>
&lt;h2 id="3-turn-off-filter-keys-sticky-keys-and-toggle-keys">3. Turn off Filter Keys, Sticky Keys and Toggle Keys&lt;/h2>
&lt;p>If quick taps get ignored and you have to hold keys down for them to register, Filter Keys is on. Microsoft&amp;rsquo;s accessibility shortcut list says holding right Shift for eight seconds turns Filter Keys on and off, so it&amp;rsquo;s easy to trigger by leaning on Shift. Filter Keys tells Windows to ignore brief or repeated key presses, which makes normal typing feel laggy or dead. The same list has two more: pressing Shift five times toggles Sticky Keys, and holding Num Lock for five seconds toggles Toggle Keys.&lt;/p>
&lt;p>Open &lt;code>Settings &amp;gt; Accessibility &amp;gt; Keyboard&lt;/code>. Turn Sticky keys, Filter keys, and Toggle keys off. Also disable the keyboard shortcut for each one so leaning on Shift can&amp;rsquo;t trigger it again.&lt;/p>
&lt;h2 id="4-fix-the-layout-and-num-lock">4. Fix the layout and Num Lock&lt;/h2>
&lt;p>If @ and &amp;quot; are swapped, or £ appears where # should be, your keyboard language changed. Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/keyboard-shortcuts-in-windows-dcc61a57-8ff0-cffe-9796-cb9706c75eec" rel="noopener">shortcut list&lt;/a> says &lt;code>Windows key + Spacebar&lt;/code> switches the input language and keyboard layout, so one stray press does it. Press it again to cycle back to your layout, then remove the extra one under &lt;code>Settings &amp;gt; Time &amp;amp; language &amp;gt; Language &amp;amp; region&lt;/code> so it can&amp;rsquo;t come back.&lt;/p>
&lt;p>On laptops without a separate number pad, &lt;strong>Num Lock&lt;/strong> overlays a number pad onto part of the letter keys. Press &lt;strong>Fn + Num Lock&lt;/strong> (sometimes labeled &lt;strong>NumLk&lt;/strong>) to switch it off and the letters return.&lt;/p>
&lt;h2 id="5-wireless-keyboards-power-and-pairing">5. Wireless keyboards: power and pairing&lt;/h2>
&lt;p>Swap or charge the batteries. For a keyboard on a USB receiver, Microsoft&amp;rsquo;s first step is to unplug the receiver, wait about 10 seconds, and plug it back in; look for a Reset button on the keyboard or the receiver too. That&amp;rsquo;s also the first check when the keyboard and mouse stopped together on one receiver. For Bluetooth, remove the keyboard under Settings &amp;gt; Bluetooth &amp;amp; devices and pair it again.&lt;/p>
&lt;h2 id="6-reinstall-the-keyboard-driver">6. Reinstall the keyboard driver&lt;/h2>
&lt;p>Open Device Manager with &lt;code>Windows key + X &amp;gt; Device Manager&lt;/code>. Expand Keyboards, right-click your keyboard, choose Uninstall device, and restart. Windows reinstalls the driver on boot. Use this after the port and second-PC tests, especially when the keyboard stopped after a Windows update. Microsoft&amp;rsquo;s procedure also has you check Windows Update for a driver.&lt;/p>
&lt;h2 id="7-test-with-fast-startup-off-when-a-restart-fixes-it">7. Test with Fast Startup off when a restart fixes it&lt;/h2>
&lt;p>If the keyboard is dead after you shut down and start up, but works after a Restart, test with Fast Startup off. With Fast Startup on, Microsoft explains that shutting down saves the kernel memory image, including the loaded kernel-mode drivers, to the hibernation file, and the next start loads that file; a cold start enumerates the attached devices and loads their drivers fresh. Go to &lt;code>Control Panel &amp;gt; Power Options &amp;gt; Choose what the power buttons do &amp;gt; Change settings that are currently unavailable&lt;/code>, uncheck Turn on fast startup, and save.&lt;/p>
&lt;p>The old Keyboard troubleshooter won&amp;rsquo;t help here: Microsoft lists it among the legacy troubleshooters it is &lt;a href="https://support.microsoft.com/windows/0c5ac9a2-1600-4539-b9d0-069e71f9040a" rel="noopener">removing from Windows 11&lt;/a>. The steps on this page cover the same ground.&lt;/p>
&lt;h2 id="8-undo-the-windows-update-that-broke-it">8. Undo the Windows update that broke it&lt;/h2>
&lt;p>If the problem started with a specific update, use the on-screen keyboard to remove it: &lt;strong>Settings &amp;gt; Windows Update &amp;gt; Update history &amp;gt; Uninstall updates&lt;/strong>, per &lt;a href="https://support.microsoft.com/en-us/windows/deployment/updates-lifecycle/how-to-uninstall-a-windows-update" rel="noopener">Microsoft&amp;rsquo;s uninstall steps&lt;/a>. Some updates can&amp;rsquo;t be uninstalled.&lt;/p>
&lt;h2 id="9-clean-or-check-the-dead-keys">9. Clean or check the dead keys&lt;/h2>
&lt;p>Isolated dead keys after the settings above are usually physical. Microsoft&amp;rsquo;s checklist includes making sure no dirt is blocking keys. Power off, tip the keyboard, and clean under and around the stuck keys with a can of compressed air; the &lt;a href="https://techfuelhq.com/tutorials/how-to-clean-pc-2026/">PC cleaning guide&lt;/a> explains why the can stays upright and the bursts stay short. If a cluster of keys died after a spill, that&amp;rsquo;s liquid damage to the membrane or switches, and the keyboard usually needs replacing.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=compressed&amp;#43;air&amp;#43;duster&amp;#43;can&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/keyboard-not-working-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3Dcompressed%2Bair%2Bduster%2Bcan" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/keyboard-not-working-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="laptop-keyboard-not-working-what-is-different">Laptop keyboard not working: what is different&lt;/h2>
&lt;p>A built-in keyboard can&amp;rsquo;t go to another PC, so plug a USB keyboard into the laptop. If that one types, Dell says the issue is limited to the laptop&amp;rsquo;s own keyboard. Windows can still be the cause.&lt;/p>
&lt;p>&lt;strong>Test the keys before Windows loads.&lt;/strong> On a Dell, power on and tap F12; Dell says reaching the boot menu means the keyboard is working, and its &lt;a href="https://www.dell.com/support/kbdoc/en-us/000131432/keyboard-usage-and-troubleshooting-guide" rel="noopener">built-in diagnostics&lt;/a> check whether the keyboard is detected below the operating system. Dead keys there rule out Windows. Other makers have their own pre-boot menus and diagnostics; your model&amp;rsquo;s support page names them.&lt;/p>
&lt;p>&lt;strong>If the keys work there, fix Windows.&lt;/strong> Dell&amp;rsquo;s procedure is to uninstall each entry under Keyboards in Device Manager and restart so Windows reinstalls the drivers. Then update the BIOS and drivers; Dell calls outdated ones a common cause of keyboard trouble, and ASUS puts that update first. The &lt;a href="https://techfuelhq.com/tutorials/how-to-update-bios-2026/">BIOS update guide&lt;/a> covers the flash.&lt;/p>
&lt;p>&lt;strong>Function keys doing the wrong job&lt;/strong> (volume or brightness instead of F1 to F12, or the reverse) are in the other mode. On a Dell, Fn+Esc toggles the function-key lock. ASUS uses the same shortcut on models with an LED on the Fn key.&lt;/p>
&lt;p>&lt;strong>Drain the power before you call it hardware.&lt;/strong> ASUS documents an &lt;a href="https://www.asus.com/support/faq/1050239/" rel="noopener">embedded controller reset&lt;/a> for keyboard problems: remove external devices, connect the power adapter and hold the power button for 40 seconds. Dell&amp;rsquo;s hard reset for a removable battery differs: adapter and battery out, then 15 to 20 seconds on the power button.&lt;/p>
&lt;p>&lt;strong>Three faults are service jobs.&lt;/strong> A keyboard or trackpad that feels raised or won&amp;rsquo;t click properly is on Dell&amp;rsquo;s list of swollen-battery signs; stop using the laptop, and never puncture, compress or disassemble the battery. After a spill, Dell says to power off at once, tilt the laptop to drain it and let it dry for at least 24 to 48 hours before contacting support. And an internal cable that has come loose means opening the case. All three belong with the maker or a repair shop.&lt;/p>
&lt;p>For one dead laptop key, Dell&amp;rsquo;s first step is to power off and blow compressed air around it, keeping the can upright. A keycap that came off can be reseated by aligning it and pressing gently, provided the plastic scissor spring under it looks intact. Dell says its keys cannot be replaced individually, so a key that still fails needs a new keyboard.&lt;/p>
&lt;h2 id="when-it-really-is-the-keyboard">When it really is the keyboard&lt;/h2>
&lt;p>If it failed on another PC, cleaning didn&amp;rsquo;t help, and the settings above are all clear, the keyboard (or its cable) is the fault. A dead laptop keyboard is also the one case where you need an external one to keep working, and a cheap wired backup is worth having regardless: it plugs in with no pairing, which makes it the tool for doing the Device Manager fixes above when your main keyboard is dead. Newegg&amp;rsquo;s catalogue lists the Logitech K120 as a full-size, plug-and-play wired keyboard, and it was in stock there on November 17, 2026.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Logitech&amp;#43;K120&amp;#43;wired&amp;#43;keyboard&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/keyboard-not-working-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DLogitech%2BK120%2Bwired%2Bkeyboard" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/keyboard-not-working-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>Still fighting Windows peripherals? See our fixes for &lt;a href="https://techfuelhq.com/gaming/xbox-controller-not-connecting-to-pc-fix-2026/">an Xbox controller that won&amp;rsquo;t connect&lt;/a> and &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/">GPU driver crashes&lt;/a>.&lt;/p></description></item><item><title>Proxmox Upgrade 8 to 9: Preflight Checks and Gotchas</title><link>https://techfuelhq.com/tutorials/proxmox-ve-8-to-9-upgrade-2026/</link><pubDate>Wed, 17 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/proxmox-ve-8-to-9-upgrade-2026/</guid><atom:updated>2026-11-18T04:54:38Z</atom:updated><description>&lt;p>This takes a Proxmox VE 8 host, or a cluster one node at a time, to Proxmox VE 9 in place. Every command and file below follows Proxmox&amp;rsquo;s official &lt;a href="https://pve.proxmox.com/wiki/Upgrade_from_8_to_9" rel="noopener">Upgrade from 8 to 9&lt;/a> guide (revision last edited September 17, 2026), rechecked on November 18, 2026. On that date the trixie repositories deliver &lt;strong>Proxmox VE 9.2&lt;/strong> (released May 21, 2026, kernel 7.0), and 9.2 is still the current installer.&lt;/p>
&lt;p>You have a reason to do it now: Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/wiki/FAQ" rel="noopener">lifecycle table&lt;/a> puts the end of Proxmox VE 8 support at &lt;strong>2026-08&lt;/strong>. The upgrade is routine when you prepare for it. Skip the preparation and it can leave a node with no network or no boot.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Back up first, always.&lt;/strong> Proxmox&amp;rsquo;s guide is blunt: &lt;em>&amp;ldquo;A valid and tested backup is always required before starting the upgrade process.&amp;rdquo;&lt;/em>&lt;/p>&lt;/blockquote>
&lt;h2 id="before-you-touch-anything">Before you touch anything&lt;/h2>
&lt;p>Tick every line before you touch a repository:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Every node on PVE 8.4.1 or later.&lt;/strong> The &lt;code>pve8to9&lt;/code> checker ships in the latest 8.4 packages.&lt;/li>
&lt;li>&lt;strong>Tested backups of every VM and container on external storage&lt;/strong>, plus a copy of &lt;code>/etc/pve&lt;/code>, &lt;code>/etc/passwd&lt;/code>, &lt;code>/etc/network/interfaces&lt;/code>, &lt;code>/etc/resolv.conf&lt;/code> and anything you changed from a default install. Restore one guest to prove the backups work.&lt;/li>
&lt;li>&lt;strong>Console access that isn&amp;rsquo;t the web GUI.&lt;/strong> Use IPMI/iKVM or a physical console. If you only have SSH, Proxmox recommends testing the upgrade on an identical, non-production machine first, and running the upgrade inside &lt;code>tmux&lt;/code> or &lt;code>screen&lt;/code>. The GUI&amp;rsquo;s virtual console is interrupted during the upgrade.&lt;/li>
&lt;li>&lt;strong>At least 5 GB free on the root filesystem&lt;/strong>, ideally more than 10 GB.&lt;/li>
&lt;li>&lt;strong>A healthy cluster&lt;/strong>, if you run one.&lt;/li>
&lt;li>&lt;strong>Hyperconverged Ceph on 19.2 Squid&lt;/strong> before you start. Upgrade Quincy or Reef first.&lt;/li>
&lt;li>&lt;strong>Proxmox Backup Server on the same host:&lt;/strong> bring PBS to the latest 3.4, run &lt;code>pbs3to4 --full&lt;/code> and follow the &lt;a href="https://pbs.proxmox.com/wiki/Upgrade_from_3_to_4" rel="noopener">PBS 3-to-4 guide&lt;/a>, switching its repository in the same stage as PVE&amp;rsquo;s.&lt;/li>
&lt;li>&lt;strong>Third-party repositories, packages and storage plugins&lt;/strong> that work on Debian 13 Trixie and Proxmox VE 9. A storage plugin has to be adapted by its author first.&lt;/li>
&lt;li>&lt;strong>The known upgrade issues read.&lt;/strong> Proxmox&amp;rsquo;s guide lists them and the &lt;a href="#gotchas-the-checker-wont-fix-for-you">Gotchas&lt;/a> section below covers the main ones; the 9.0 &lt;a href="https://pve.proxmox.com/wiki/Roadmap#9.0-known-issues" rel="noopener">known issues&lt;/a> in the roadmap are the other list it points to.&lt;/li>
&lt;li>&lt;strong>A rehearsal if you can.&lt;/strong> Proxmox suggests installing PVE 8.4 on test hardware or in a VM, copying the relevant configuration over and upgrading that first. On hardware ten or more years old, Proxmox recommends testing on identical or similar hardware before production; it notes Ceph &amp;ldquo;illegal instruction&amp;rdquo; errors reported on AMD Opteron 2427 and Turion II Neo N54L CPUs.&lt;/li>
&lt;/ul>
&lt;p>Put the host on a UPS you&amp;rsquo;ve actually tested before you start, because a power loss mid-upgrade is an avoidable risk; the &lt;a href="https://techfuelhq.com/homelab/ups-testing-reality-2026/">UPS testing guide&lt;/a> covers what a real test looks like.&lt;/p>
&lt;p>Then bring every node to the latest 8.4 and confirm the version. Run these, and everything below, from the console or SSH inside &lt;code>tmux&lt;/code>:&lt;/p>
&lt;pre tabindex="0">&lt;code>apt update
apt dist-upgrade
pveversion
&lt;/code>&lt;/pre>&lt;p>&lt;code>pveversion&lt;/code> has to report 8.4.1 or newer. If it doesn&amp;rsquo;t, check the node&amp;rsquo;s repositories (web UI, Node &amp;gt; Repositories); they must still point at Proxmox VE 8 on Bookworm at this stage. With hyperconverged Ceph, &lt;code>ceph --version&lt;/code> must report Squid (19). If it doesn&amp;rsquo;t, stop and upgrade Ceph first.&lt;/p>
&lt;h2 id="run-the-checklist-pve8to9---full">Run the checklist: &lt;code>pve8to9 --full&lt;/code>&lt;/h2>
&lt;pre tabindex="0">&lt;code>pve8to9 --full
&lt;/code>&lt;/pre>&lt;p>The script only checks and reports; it changes nothing. Resolve every failure, act on each warning that applies to the node, and rerun it after every fix to confirm the fix worked. Proxmox warns that the script can&amp;rsquo;t recognize every problem on a heavily customized host. The two findings Proxmox documents:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>&lt;code>proxmox-ve&lt;/code> package is too old.&lt;/strong> Run the 8.4 update above again.&lt;/li>
&lt;li>&lt;strong>LVM or LVM-thin guest volumes with autoactivation enabled.&lt;/strong> From PVE 9, new logical volumes are created with autoactivation off and Proxmox activates them when needed. For existing volumes, run the migration script the checker suggests, &lt;code>/usr/share/pve-manager/migrations/pve-lvm-disable-autoactivation&lt;/code>. Proxmox strongly recommends it for guest volumes on shared LVM (iSCSI or Fibre Channel LUNs) and calls it optional for local-only LVM.&lt;/li>
&lt;/ul>
&lt;p>It can also tell you to remove the &lt;code>systemd-boot&lt;/code> meta-package. On Trixie that package carries hooks that install systemd-boot as the bootloader, and Proxmox says it is safe to remove when &lt;code>pve8to9&lt;/code> suggests it, unless you set up systemd-boot yourself. The checker&amp;rsquo;s output changes as the upgrade progresses, which is why you run it again in step 6.&lt;/p>
&lt;h2 id="the-upgrade-itself">The upgrade itself&lt;/h2>
&lt;p>On a cluster, finish every step on one node before you start the next.&lt;/p>
&lt;h3 id="1-pin-network-interface-names-and-move-sysctlconf-settings">1. Pin network interface names and move &lt;code>sysctl.conf&lt;/code> settings&lt;/h3>
&lt;p>Two things break at the first reboot on 9, so fix them now, on 8.&lt;/p>
&lt;p>&lt;strong>NIC names.&lt;/strong> The new kernel recognizes more features of some hardware, and because names often derive from the PCI address, a NIC can come up under a new name. If &lt;code>vmbr0&lt;/code> points at the old one, the host boots with no network. Give the NIC a stable name of your own with a systemd &lt;code>.link&lt;/code> file, following Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#network_override_device_names" rel="noopener">manual method&lt;/a>. Create &lt;code>/etc/systemd/network/10-enwan0.link&lt;/code>, using your NIC&amp;rsquo;s MAC address:&lt;/p>
&lt;pre tabindex="0">&lt;code>[Match]
MACAddress=aa:bb:cc:dd:ee:ff
Type=ether
[Link]
Name=enwan0
&lt;/code>&lt;/pre>&lt;p>Proxmox recommends a name that starts with &lt;code>en&lt;/code> or &lt;code>eth&lt;/code> (so the GUI treats it as a physical NIC) and won&amp;rsquo;t clash with names systemd generates, which is why the example uses &lt;code>enwan0&lt;/code>. Change &lt;code>/etc/network/interfaces&lt;/code> to the new name, then refresh the initramfs, because link files are copied into it:&lt;/p>
&lt;pre tabindex="0">&lt;code>update-initramfs -u -k all
&lt;/code>&lt;/pre>&lt;p>Then reboot and confirm the network works before you go further. If guests must keep running through that reboot, migrate them first (step 2). Proxmox VE 9 also ships &lt;code>pve-network-interface-pinning generate&lt;/code>, which writes &lt;code>.link&lt;/code> files for every physical NIC that doesn&amp;rsquo;t have one yet, with &lt;code>nic1&lt;/code>, &lt;code>nic2&lt;/code>-style names, leaves &lt;code>.new&lt;/code> copies of the edited configuration files for you to diff, and doesn&amp;rsquo;t update interface names in &lt;code>/etc/pve/firewall/cluster.fw&lt;/code>. Use it only if it is installed on the node and you want those new names.&lt;/p>
&lt;p>&lt;strong>&lt;code>/etc/sysctl.conf&lt;/code>.&lt;/strong> The systemd-sysctl in Proxmox VE 9 no longer reads it, and Debian 13&amp;rsquo;s &lt;a href="https://www.debian.org/releases/trixie/release-notes/issues.en.html" rel="noopener">release notes&lt;/a> say the same. Check it now (&lt;code>cat /etc/sysctl.conf&lt;/code>) and move anything you set there, IP forwarding included, into a file such as &lt;code>/etc/sysctl.d/99-local.conf&lt;/code>. EVPN exit nodes that set &lt;code>rp_filter&lt;/code> there are affected too.&lt;/p>
&lt;p>&lt;strong>Ceph Full Mesh setups&lt;/strong> with &lt;code>post-up /usr/bin/systemctl restart frr.service&lt;/code> in &lt;code>/etc/network/interfaces&lt;/code> deadlock at boot on 9, because FRR now depends on the networking service. Change the line before you reboot:&lt;/p>
&lt;pre tabindex="0">&lt;code>post-up /usr/bin/systemctl is-active --quiet frr.service &amp;amp;&amp;amp; /usr/bin/systemctl restart frr.service || true
&lt;/code>&lt;/pre>&lt;h3 id="2-move-guests-off-the-node">2. Move guests off the node&lt;/h3>
&lt;p>On a cluster, migrate any VM or container that has to keep running to another node. Migrating from an older Proxmox VE version to a newer one always works; newer to older may work but isn&amp;rsquo;t supported. If a migration away from a node still on 8 throws errors while you&amp;rsquo;re logged into an upgraded node&amp;rsquo;s GUI, log into the old node&amp;rsquo;s GUI and retry.&lt;/p>
&lt;h3 id="3-switch-the-repositories-to-trixie">3. Switch the repositories to Trixie&lt;/h3>
&lt;p>Change the Debian base and the old enterprise list to trixie:&lt;/p>
&lt;pre tabindex="0">&lt;code>sed -i &amp;#39;s/bookworm/trixie/g&amp;#39; /etc/apt/sources.list
sed -i &amp;#39;s/bookworm/trixie/g&amp;#39; /etc/apt/sources.list.d/pve-enterprise.list
&lt;/code>&lt;/pre>&lt;p>Comment out (&lt;code>#&lt;/code>) any Bookworm-specific line that remains. Then add the Proxmox VE 9 repository in the deb822 format. Without a subscription:&lt;/p>
&lt;pre tabindex="0">&lt;code>cat &amp;gt; /etc/apt/sources.list.d/proxmox.sources &amp;lt;&amp;lt; EOF
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF
&lt;/code>&lt;/pre>&lt;p>With a subscription, create &lt;code>/etc/apt/sources.list.d/pve-enterprise.sources&lt;/code> the same way with &lt;code>URIs: https://enterprise.proxmox.com/debian/pve&lt;/code> and &lt;code>Components: pve-enterprise&lt;/code>.&lt;/p>
&lt;p>For hyperconverged Ceph, create &lt;code>/etc/apt/sources.list.d/ceph.sources&lt;/code> with &lt;code>Suites: trixie&lt;/code> and either &lt;code>URIs: http://download.proxmox.com/debian/ceph-squid&lt;/code> with &lt;code>Components: no-subscription&lt;/code>, or &lt;code>URIs: https://enterprise.proxmox.com/debian/ceph-squid&lt;/code> with &lt;code>Components: enterprise&lt;/code>. Replace any ceph.com repository with Proxmox&amp;rsquo;s. A 401 error on an enterprise repository means the subscription needs a refresh, in the web UI or with &lt;code>pvesubscription update --force&lt;/code>. Remove any backports line; Proxmox hasn&amp;rsquo;t tested the upgrade with backports packages installed.&lt;/p>
&lt;h3 id="4-check-the-repositories-before-you-upgrade">4. Check the repositories before you upgrade&lt;/h3>
&lt;pre tabindex="0">&lt;code>apt update
apt policy
&lt;/code>&lt;/pre>&lt;p>Continue only when &lt;code>apt update&lt;/code> shows no errors and &lt;code>apt policy&lt;/code> lists only the repositories you intend. Then remove what the new files replace: the PVE 8 no-subscription line (in &lt;code>sources.list&lt;/code>, &lt;code>pve-install-repo.list&lt;/code> or another &lt;code>.list&lt;/code> file), &lt;code>pve-enterprise.list&lt;/code> once &lt;code>pve-enterprise.sources&lt;/code> works, and &lt;code>ceph.list&lt;/code> once &lt;code>ceph.sources&lt;/code> works. Run both commands again to confirm the old entries are gone.&lt;/p>
&lt;h3 id="5-run-the-upgrade">5. Run the upgrade&lt;/h3>
&lt;p>Proxmox&amp;rsquo;s guide documents no rollback from here. If this goes wrong, the fallback is the recovery table below or a fresh install and restore.&lt;/p>
&lt;pre tabindex="0">&lt;code>apt dist-upgrade
&lt;/code>&lt;/pre>&lt;p>The guide&amp;rsquo;s time estimate: under 5 minutes on a fast SSD, 60 minutes or more on a slow spinning disk. Read every configuration-file prompt and check the diff. Proxmox&amp;rsquo;s recommended answers:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">File&lt;/th>
&lt;th scope="col">Choice&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="File">&lt;code>/etc/issue&lt;/code>&lt;/td>
&lt;td data-label="Choice">Keep your current version (the default &amp;ldquo;No&amp;rdquo;)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="File">&lt;code>/etc/lvm/lvm.conf&lt;/code>&lt;/td>
&lt;td data-label="Choice">Install the maintainer&amp;rsquo;s version if you made no changes yourself&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="File">&lt;code>/etc/ssh/sshd_config&lt;/code>&lt;/td>
&lt;td data-label="Choice">Maintainer&amp;rsquo;s version, if the only change replaces &lt;code>ChallengeResponseAuthentication&lt;/code>; inspect anything else&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="File">&lt;code>/etc/default/grub&lt;/code>&lt;/td>
&lt;td data-label="Choice">Keep your version if unsure; this usually only asks because you added a kernel option&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="File">&lt;code>/etc/chrony/chrony.conf&lt;/code>&lt;/td>
&lt;td data-label="Choice">Maintainer&amp;rsquo;s version if unchanged; move local changes into &lt;code>conf.d&lt;/code> or &lt;code>sources.d&lt;/code>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Press &lt;code>q&lt;/code> to leave an apt-listchanges screen, pick your keyboard layout if asked, and take the default on service-restart questions. If you&amp;rsquo;d rather not see kernel audit messages flood the journal during the upgrade, run &lt;code>systemctl disable --now systemd-journald-audit.socket&lt;/code> beforehand; otherwise they stop after the reboot.&lt;/p>
&lt;h3 id="6-rerun-the-checker-reboot-and-verify">6. Rerun the checker, reboot and verify&lt;/h3>
&lt;pre tabindex="0">&lt;code>pve8to9
&lt;/code>&lt;/pre>&lt;p>Read what it reports first. When it is clean or only shows warnings that don&amp;rsquo;t apply, reboot:&lt;/p>
&lt;pre tabindex="0">&lt;code>reboot
&lt;/code>&lt;/pre>&lt;p>Reboot even if you were already on the opt-in 6.14 kernel under 8, because the 9 kernel is rebuilt with the new compiler and ABI. Afterwards:&lt;/p>
&lt;pre tabindex="0">&lt;code>pveversion
&lt;/code>&lt;/pre>&lt;p>It should report 9.x. Hard-refresh the web UI (Ctrl+Shift+R) so you aren&amp;rsquo;t looking at a cached 8.x interface, then check storage, networking, services and guests before you touch the next node.&lt;/p>
&lt;p>On a cluster, confirm every node runs the latest packages; if one doesn&amp;rsquo;t, go back to &lt;a href="#before-you-touch-anything">Before you touch anything&lt;/a> for it. Once every node is on 9, HA groups migrate to HA rules on their own. If HA misbehaves after that, read &lt;code>journalctl -eu pve-ha-crm&lt;/code> on the active CRM node. You can then convert old &lt;code>.list&lt;/code> files with &lt;code>apt modernize-sources&lt;/code>: answer &lt;code>n&lt;/code> first to preview, run it again and answer &lt;code>Y&lt;/code> to apply, and delete the &lt;code>.list.bak&lt;/code> files it leaves once everything works.&lt;/p>
&lt;h2 id="gotchas-the-checker-wont-fix-for-you">Gotchas the checker won&amp;rsquo;t fix for you&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>ZFS pools.&lt;/strong> Proxmox VE 9.2 ships ZFS 2.4. Leave &lt;code>zpool upgrade&lt;/code> alone unless you need a new pool feature: Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">ZFS guide&lt;/a> says a new feature active on &lt;code>rpool&lt;/code> makes a GRUB-booted system unbootable, and an upgraded pool can&amp;rsquo;t be imported by an older kernel or an older Proxmox ISO. The &lt;a href="https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/">ZFS on Proxmox tutorial&lt;/a> covers the rest of pool care.&lt;/li>
&lt;li>&lt;strong>&lt;code>/tmp&lt;/code> is now a tmpfs&lt;/strong> of up to 50% of RAM, and files in &lt;code>/tmp&lt;/code> and &lt;code>/var/tmp&lt;/code> are cleaned regularly. Don&amp;rsquo;t keep anything there.&lt;/li>
&lt;li>&lt;strong>GRUB on LVM in UEFI mode&lt;/strong> can fail with &lt;code>disk lvmid/... not found&lt;/code>. On those systems run &lt;code>[ -d /sys/firmware/efi ] &amp;amp;&amp;amp; apt install grub-efi-amd64&lt;/code>. Root on ZFS and legacy-boot systems aren&amp;rsquo;t affected.&lt;/li>
&lt;li>&lt;strong>cgroup v1 is gone.&lt;/strong> Containers with systemd 230 or older (CentOS 7, Ubuntu 16.04) won&amp;rsquo;t start; move them to a newer OS first.&lt;/li>
&lt;li>&lt;strong>PCI passthrough&lt;/strong> has failed to start VMs for some users on the new kernel. The documented workaround is booting an older kernel and pinning it. The &lt;a href="https://techfuelhq.com/tutorials/gpu-passthrough-proxmox-vm-2026/">GPU passthrough guide&lt;/a> covers the setup side.&lt;/li>
&lt;li>&lt;strong>Live migration between different CPU models or vendors&lt;/strong> can leave VMs unresponsive. Test with a non-production VM first.&lt;/li>
&lt;li>&lt;strong>VM memory can read above 100%,&lt;/strong> because PVE 9 counts the VM&amp;rsquo;s overhead when the guest reports no detailed usage. Compare it with the new Host memory usage field.&lt;/li>
&lt;li>&lt;strong>NVIDIA vGPU&lt;/strong> needs a driver matched to the kernel; use Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE" rel="noopener">compatibility table&lt;/a>. &lt;strong>Veeam&lt;/strong> doesn&amp;rsquo;t work with VMs on QEMU machine version 10.0 or newer; pin affected VMs to &lt;code>9.2+pve1&lt;/code> or wait.&lt;/li>
&lt;li>&lt;strong>Ceph &amp;ldquo;insecure key types&amp;rdquo; health errors&lt;/strong> can appear after the first upgraded node with a monitor reboots. If nothing else is wrong, keep going and run the key migration once every node is on 9.&lt;/li>
&lt;li>&lt;strong>Custom OpenFabric or OSPF FRR configs&lt;/strong> in &lt;code>/etc/frr/frr.conf.local&lt;/code> stop working once an SDN config is applied. Create &lt;code>/etc/default/frr&lt;/code> with &lt;code>ospfd=yes&lt;/code> or &lt;code>fabricd=yes&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Proxmox on top of plain Debian&lt;/strong> with &lt;code>linux-image-amd64&lt;/code> installed: remove that package before the dist-upgrade, because it conflicts with 9.x.&lt;/li>
&lt;/ul>
&lt;blockquote>
&lt;p>&lt;strong>A Windows VM that won&amp;rsquo;t boot after the upgrade.&lt;/strong> Since the kernel 7.0 rollout on 9.2, Windows guests on SeaBIOS with MBR disks have been reported failing with &lt;code>0xc0000001&lt;/code>, and OVMF guests dropping to the UEFI boot menu. Don&amp;rsquo;t reinstall anything yet: the fixes are in &lt;a href="https://techfuelhq.com/articles/proxmox-9-windows-vm-not-booting-2026/">Windows VM won&amp;rsquo;t boot after the Proxmox 9 upgrade&lt;/a>.&lt;/p>&lt;/blockquote>
&lt;h2 id="stop-continue-or-recover">Stop, continue, or recover&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Signal&lt;/th>
&lt;th scope="col">What to do&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Signal">Node below 8.4.1, or &lt;code>pve8to9 --full&lt;/code> reports a failure&lt;/td>
&lt;td data-label="What to do">Stop. Update PVE 8, fix the failure, rerun the checker.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Signal">A warning or notice&lt;/td>
&lt;td data-label="What to do">Read it, decide whether it applies, do the documented fix if it does, rerun.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Signal">&lt;code>apt update&lt;/code> errors, or &lt;code>apt policy&lt;/code> shows the wrong repositories&lt;/td>
&lt;td data-label="What to do">Stop. Fix the Debian, Proxmox and Ceph/PBS repository files, remove stale Bookworm entries, check again.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Signal">&lt;code>W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!&lt;/code>&lt;/td>
&lt;td data-label="What to do">Stop. A trixie repository is missing or misconfigured. Fix it; don&amp;rsquo;t remove or bypass the hook. If a repository has no trixie version, restore the old repository files, run &lt;code>apt update&lt;/code>, remove the packages from that repository and start the upgrade again.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Signal">A network failure left the upgrade half done&lt;/td>
&lt;td data-label="What to do">Fix the connection and the repositories, then run &lt;code>apt -f install&lt;/code>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Signal">Boot reports &lt;code>Check of pool pve/data failed (status:64). Manual repair required!&lt;/code>&lt;/td>
&lt;td data-label="What to do">Run the repair below. Only for that exact message.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Signal">The upgraded host doesn&amp;rsquo;t boot&lt;/td>
&lt;td data-label="What to do">Use &lt;a href="https://pve.proxmox.com/wiki/Recover_From_Grub_Failure" rel="noopener">Recover From Grub Failure&lt;/a> if it matches. A Ceph Full Mesh host stuck at boot: boot the PVE ISO&amp;rsquo;s Rescue Boot (Advanced menu) and edit &lt;code>/etc/network/interfaces&lt;/code>. Otherwise, fresh-install 9 and restore. A system installed on ZFS with legacy BIOS boot before the 6.4 ISO can also hit a broken boot: Proxmox points to its &lt;a href="https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool" rel="noopener">switch to proxmox-boot-tool&lt;/a> article.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Destructive: this repairs an LVM thin pool in place. Run it only for the &lt;code>status:64&lt;/code> message above, with your backups in hand:&lt;/p>
&lt;pre tabindex="0">&lt;code>lvconvert --repair pve/data
&lt;/code>&lt;/pre>&lt;h2 id="the-other-path-fresh-install-and-restore">The other path: fresh install and restore&lt;/h2>
&lt;p>Proxmox also documents a new installation, the path it describes for new hardware: back up every guest to external storage, save &lt;code>/etc&lt;/code> (at least &lt;code>/etc/pve&lt;/code>, &lt;code>/etc/passwd&lt;/code>, &lt;code>/etc/network/interfaces&lt;/code>, &lt;code>/etc/resolv.conf&lt;/code>), install the latest 9.x from the ISO, force-reload the web UI (Ctrl+Shift+R), rebuild the cluster if you had one, restore &lt;code>/etc/pve/storage.cfg&lt;/code> and the firewall files (&lt;code>/etc/pve/firewall/&lt;/code> and &lt;code>/etc/pve/nodes/&amp;lt;node&amp;gt;/host.fw&lt;/code>), then restore the guests.&lt;/p>
&lt;p>Destructive: the ISO install erases all data on the host&amp;rsquo;s target disks. The &lt;a href="https://techfuelhq.com/articles/how-to-install-proxmox-ve-2026/">install reference&lt;/a> walks through a fresh 9.x install, and &lt;a href="https://techfuelhq.com/tutorials/proxmox-migrate-vm-without-cluster-2026/">moving a VM to a new host without a cluster&lt;/a> covers getting guests across.&lt;/p>
&lt;h2 id="what-you-land-on">What you land on&lt;/h2>
&lt;p>Proxmox VE 9.2, per the &lt;a href="https://pve.proxmox.com/wiki/Roadmap" rel="noopener">roadmap&lt;/a>: Debian 13 Trixie, kernel 7.0 as the stable default, QEMU 11.0, LXC 7.0, ZFS 2.4, Ceph Squid 19.2 with Ceph Tentacle 20.2 as a stable option. The 9.2 additions over 9.0 include dynamic load balancing of HA-managed guests by the Cluster Resource Scheduler (working with your &lt;a href="https://techfuelhq.com/tutorials/proxmox-clustering-ha-2026/">HA rules&lt;/a>), WireGuard and BGP fabrics in the SDN stack, custom CPU models in the web UI, and a cluster-wide HA disarm for maintenance.&lt;/p>
&lt;p>None of this changes the procedure. You simply land on the current release, not 9.0.&lt;/p>
&lt;p>If you lean on community automation for cluster nodes, read the &lt;a href="https://techfuelhq.com/homelab/proxmox-helper-scripts-safe-2026/">helper-scripts safety guide&lt;/a> before you run anything as root mid-upgrade.&lt;/p>
&lt;h2 id="the-sequence-as-a-68-second-animation">The sequence as a 68-second animation&lt;/h2>
&lt;p>This original animation walks the same preparation and upgrade sequence from Proxmox&amp;rsquo;s guide.&lt;/p>
&lt;figure class="post-video">
&lt;video controls preload="none" playsinline poster="/videos/tutorials/proxmox-ve-8-to-9-upgrade-2026/proxmox-8-to-9-planning-overview-poster.jpg" width="1280" height="720" aria-describedby="proxmox-upgrade-video-caption">
&lt;source src="https://techfuelhq.com/videos/tutorials/proxmox-ve-8-to-9-upgrade-2026/proxmox-8-to-9-planning-overview-720p.webm" type="video/webm">
&lt;track kind="captions" srclang="en" label="English" src="https://techfuelhq.com/videos/tutorials/proxmox-ve-8-to-9-upgrade-2026/proxmox-8-to-9-planning-overview.en.vtt" default>
Your browser does not support embedded video. &lt;a href="https://techfuelhq.com/videos/tutorials/proxmox-ve-8-to-9-upgrade-2026/proxmox-8-to-9-planning-overview-720p.webm" download type="video/webm">Download the WebM video&lt;/a>.
&lt;/video>
&lt;figcaption id="proxmox-upgrade-video-caption">Original animated planning overview based on Proxmox's official upgrade documentation. It explains the sequence; it is not a recording of an upgrade.&lt;/figcaption>
&lt;/figure>
&lt;details>
&lt;summary>Video transcript&lt;/summary>
&lt;ol>
&lt;li>0:00–0:05. Plan the upgrade. Proxmox VE 8 to 9 upgrade planning overview. This original animation explains the preparation sequence.&lt;/li>
&lt;li>0:05–0:13. Start current. Start with every node fully updated to Proxmox VE 8.4, with &lt;code>pve-manager&lt;/code> version 8.4.1 or later.&lt;/li>
&lt;li>0:13–0:21. Make recovery possible. Verify external guest backups. Keep IPMI or physical console access, or use SSH inside &lt;code>tmux&lt;/code> or &lt;code>screen&lt;/code>. Do not rely on the web interface console.&lt;/li>
&lt;li>0:21–0:30. Run the full preflight. Run &lt;code>pve8to9 --full&lt;/code>. Stop on failures, act on every warning that applies, and rerun the checker after each fix. The checker reports; it does not perform the upgrade.&lt;/li>
&lt;li>0:30–0:38. Protect cluster state. On a cluster, move guests away, upgrade one node at a time, and keep quorum. Hyperconverged Ceph must be on Squid 19 before the Proxmox upgrade.&lt;/li>
&lt;li>0:38–0:47. Switch repositories deliberately. Change the Debian and Proxmox repositories from Bookworm to Trixie. Run &lt;code>apt update&lt;/code> and &lt;code>apt policy&lt;/code>, then continue only when there are no errors and only the intended repositories appear.&lt;/li>
&lt;li>0:47–0:54. Stop on a removal conflict. Stop if APT wants to remove the &lt;code>proxmox-ve&lt;/code> package. Repair the repository or package conflict before continuing.&lt;/li>
&lt;li>0:54–1:01. Upgrade with the prompts in view. Run &lt;code>apt dist-upgrade&lt;/code>. Read each configuration-file prompt and choose deliberately instead of accepting every default.&lt;/li>
&lt;li>1:01–1:08. Check, reboot, verify. Rerun &lt;code>pve8to9&lt;/code>, reboot, then verify the Proxmox version, storage, network, services, and guests. The full guide covers the gotchas and recovery paths.&lt;/li>
&lt;/ol>
&lt;/details></description></item><item><title>VLANs for the Homelab: Network Segmentation Guide (2026)</title><link>https://techfuelhq.com/tutorials/vlans-homelab-2026/</link><pubDate>Sun, 31 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/vlans-homelab-2026/</guid><atom:updated>2026-11-18T04:54:38Z</atom:updated><description>&lt;p>A flat network — every device sharing one &lt;code>/24&lt;/code> subnet — is fine right up until it isn&amp;rsquo;t. It stays fine while everything on it is trusted. It stops being fine the day you plug in a smart TV whose firmware stopped getting patches in 2022, or a doorbell camera phoning home to a cloud you&amp;rsquo;ve never audited, or you want a guest to have Wi-Fi without also having a clear path to your NAS. On a flat network, every device can talk to every other device. Segmentation is how you take that away without unplugging anything.&lt;/p>
&lt;p>VLANs are the tool. One managed switch, one router that can route between the segments, and you can carve that single flat network into as many isolated lanes as you want — IoT that can reach the internet but not your Proxmox host, a guest network walled off from everything local, a management VLAN only your admin laptop can touch. This guide walks the whole thing end to end for the most common homelab stack: &lt;strong>OPNsense doing the routing and firewalling, a MikroTik managed switch doing the tagging, and Proxmox carrying VLANs to VMs and containers over a single cable.&lt;/strong> The concepts transfer to UniFi, pfSense, or a cheap Netgear or TP-Link smart switch — only the menus change. The menu paths and commands follow the current OPNsense manual, MikroTik&amp;rsquo;s RouterOS bridge VLAN documentation and Proxmox VE 9.2, checked November 18, 2026.&lt;/p>
&lt;p>Before the menus, though, one diagram earns its keep more than any other. Almost every VLAN problem I&amp;rsquo;ve helped someone debug came down to not having a mental model of what physically happens to a frame on the wire — specifically, why some ports are &amp;ldquo;tagged&amp;rdquo; and some are &amp;ldquo;untagged,&amp;rdquo; and why mixing that up quietly breaks everything. So we start there.&lt;/p>
&lt;!-- ========== SIGNATURE VISUAL A: HOW A VLAN TAG LIVES AND DIES ========== -->
&lt;div class="visual-block">
&lt;div style="background:#0a0a23;border:1px solid rgba(255,255,255,0.07);border-radius:10px;padding:26px 22px 20px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',sans-serif;">
&lt;div style="margin-bottom:18px;">
&lt;div style="font-size:19px;font-weight:700;color:#e8e8f0;letter-spacing:-0.3px;">How a VLAN tag lives and dies&lt;/div>
&lt;div style="font-size:0.875rem;color:#9a9ab5;margin-top:5px;line-height:1.5;">A frame is born untagged, gets stamped at the access port, rides the trunk alongside other VLANs, and is stripped bare again on the way out. Devices never see the tag &amp;mdash; the switch does all the work.&lt;/div>
&lt;/div>
&lt;!-- three-zone flow -->
&lt;div style="display:flex;gap:8px;align-items:stretch;flex-wrap:wrap;">
&lt;!-- zone 1: access in -->
&lt;div style="flex:1;min-width:170px;background:rgba(255,255,255,0.02);border:1px solid rgba(255,255,255,0.07);border-radius:8px;padding:14px;">
&lt;div style="font-size:0.8125rem;color:#5dca7a;font-weight:700;">Access port &amp;middot; in&lt;/div>
&lt;div style="font-size:0.875rem;color:#c8c8d8;margin-top:8px;line-height:1.5;">Your laptop sends an ordinary frame. It has no idea VLANs exist.&lt;/div>
&lt;div style="margin-top:12px;display:inline-block;background:#1a1a3a;border:1px dashed #5a5a7a;border-radius:5px;padding:6px 10px;font-size:0.875rem;color:#9a9ab5;font-family:ui-monospace,monospace;">untagged frame&lt;/div>
&lt;div style="margin-top:10px;font-size:0.875rem;color:#9a9ab5;line-height:1.5;">Switch stamps it with the port's &lt;strong style="color:#e8e8f0;">PVID = 10&lt;/strong> on ingress.&lt;/div>
&lt;/div>
&lt;!-- arrow -->
&lt;div style="display:flex;align-items:center;color:#5090e0;font-size:22px;font-weight:700;">&amp;rarr;&lt;/div>
&lt;!-- zone 2: trunk -->
&lt;div style="flex:1.4;min-width:210px;background:rgba(80,144,224,0.06);border:1px solid rgba(80,144,224,0.3);border-radius:8px;padding:14px;">
&lt;div style="font-size:0.8125rem;color:#5090e0;font-weight:700;">Trunk &amp;middot; one cable, many VLANs&lt;/div>
&lt;div style="font-size:0.875rem;color:#c8c8d8;margin-top:8px;line-height:1.5;">Every frame here carries a tag. Three VLANs share the wire and never mix.&lt;/div>
&lt;div style="margin-top:12px;display:flex;flex-direction:column;gap:5px;">
&lt;div style="background:#1a2a1a;border-left:1px solid #5dca7a;border-radius:4px;padding:5px 9px;font-size:0.875rem;color:#c8e8c8;font-family:ui-monospace,monospace;">[VID 10] homelab &amp;rarr;&lt;/div>
&lt;div style="background:#2a2416;border-left:1px solid #ffa040;border-radius:4px;padding:5px 9px;font-size:0.875rem;color:#e8d8b8;font-family:ui-monospace,monospace;">[VID 20] iot &amp;rarr;&lt;/div>
&lt;div style="background:#2a1a2a;border-left:1px solid #b070e0;border-radius:4px;padding:5px 9px;font-size:0.875rem;color:#e0c8e8;font-family:ui-monospace,monospace;">[VID 30] guest &amp;rarr;&lt;/div>
&lt;/div>
&lt;/div>
&lt;!-- arrow -->
&lt;div style="display:flex;align-items:center;color:#5090e0;font-size:22px;font-weight:700;">&amp;rarr;&lt;/div>
&lt;!-- zone 3: access out -->
&lt;div style="flex:1;min-width:170px;background:rgba(255,255,255,0.02);border:1px solid rgba(255,255,255,0.07);border-radius:8px;padding:14px;">
&lt;div style="font-size:0.8125rem;color:#5dca7a;font-weight:700;">Access port &amp;middot; out&lt;/div>
&lt;div style="font-size:0.875rem;color:#c8c8d8;margin-top:8px;line-height:1.5;">The VID-10 frame reaches an end device's access port. The switch strips the tag. A Proxmox guest trunk keeps it tagged until the host delivers it to the guest.&lt;/div>
&lt;div style="margin-top:12px;display:inline-block;background:#1a1a3a;border:1px dashed #5a5a7a;border-radius:5px;padding:6px 10px;font-size:0.875rem;color:#9a9ab5;font-family:ui-monospace,monospace;">untagged frame&lt;/div>
&lt;div style="margin-top:10px;font-size:0.875rem;color:#9a9ab5;line-height:1.5;">The server receives clean traffic. It never knew it was on VLAN 10.&lt;/div>
&lt;/div>
&lt;/div>
&lt;!-- 802.1Q tag anatomy -->
&lt;div style="margin-top:20px;padding-top:16px;border-top:1px solid rgba(255,255,255,0.06);">
&lt;div style="font-size:0.875rem;color:#9a9ab5;margin-bottom:9px;">The 4 bytes that make it work &amp;mdash; the &lt;strong style="color:#e8e8f0;">802.1Q tag&lt;/strong>, slipped in right after the source MAC address:&lt;/div>
&lt;div style="display:flex;gap:3px;flex-wrap:wrap;font-family:ui-monospace,monospace;">
&lt;div style="flex:3;min-width:110px;background:#151533;border:1px solid #2a2a4a;border-radius:4px 0 0 4px;padding:8px 6px;text-align:center;">&lt;div style="font-size:13px;color:var(--text-bright);font-weight:700;">0x8100&lt;/div>&lt;div style="font-size:0.8125rem;color:#7a7a96;margin-top:2px;">TPID &amp;middot; 16 bits&lt;/div>&lt;/div>
&lt;div style="flex:1;min-width:52px;background:#151533;border:1px solid #2a2a4a;padding:8px 6px;text-align:center;">&lt;div style="font-size:13px;color:#e8e8f0;font-weight:700;">PCP&lt;/div>&lt;div style="font-size:0.8125rem;color:#7a7a96;margin-top:2px;">3 bits&lt;/div>&lt;/div>
&lt;div style="flex:1;min-width:44px;background:#151533;border:1px solid #2a2a4a;padding:8px 6px;text-align:center;">&lt;div style="font-size:13px;color:#e8e8f0;font-weight:700;">DEI&lt;/div>&lt;div style="font-size:0.8125rem;color:#7a7a96;margin-top:2px;">1 bit&lt;/div>&lt;/div>
&lt;div style="flex:3;min-width:110px;background:#1a2a1a;border:1px solid #3a5a3a;border-radius:0 4px 4px 0;padding:8px 6px;text-align:center;">&lt;div style="font-size:13px;color:#5dca7a;font-weight:700;">VID = 10&lt;/div>&lt;div style="font-size:0.8125rem;color:#7a9a7a;margin-top:2px;">12 bits &amp;middot; the VLAN number&lt;/div>&lt;/div>
&lt;/div>
&lt;div style="margin-top:9px;font-size:0.875rem;color:#6a6a86;line-height:1.5;">The VID is only 12 bits, so valid VLAN IDs run &lt;strong style="color:#9a9ab5;">1&amp;ndash;4094&lt;/strong> (0 and 4095 are reserved). Everything a homelab needs fits in that range many times over.&lt;/div>
&lt;/div>
&lt;div style="margin-top:16px;padding-top:12px;border-top:1px solid rgba(255,255,255,0.06);font-size:0.8125rem;color:#55556e;display:flex;justify-content:space-between;">
&lt;span>Get tagged vs untagged right before anything else.&lt;/span>
&lt;span>techfuelhq.com&lt;/span>
&lt;/div>
&lt;/div>
&lt;/div>
&lt;p>Read that diagram twice if you need to. The single most common VLAN mistake is treating a device port as &amp;ldquo;tagged&amp;rdquo; — it isn&amp;rsquo;t. &lt;strong>End devices connect to untagged (access) ports; only links between network gear are tagged (trunk) ports.&lt;/strong> A Proxmox host is the exception that proves the rule: because it hosts guests on many VLANs, its uplink is a trunk, and Proxmox itself handles the per-guest tagging internally. Wi-Fi access points are the other one: their uplink carries every VLAN their SSIDs use.&lt;/p>
&lt;h2 id="why-segment-your-network">Why segment your network&lt;/h2>
&lt;p>&lt;strong>IoT isolation is the reason most people start.&lt;/strong> Smart TVs, cameras, speakers, robot vacuums — cheap devices with firmware that stops getting security updates the moment the next model ships. Put them on their own VLAN with a firewall rule that blocks them from reaching your trusted network, and a compromised camera can still phone home to its cloud, but it can&amp;rsquo;t pivot to your NAS or scan your Proxmox management interface. If you&amp;rsquo;re properly paranoid, you also block IoT devices from reaching &lt;em>each other&lt;/em>, so one bad device can&amp;rsquo;t recruit the others. Zigbee and Z-Wave hubs belong here too; the &lt;a href="https://techfuelhq.com/tutorials/home-assistant-zigbee-zwave-2026/">Home Assistant Zigbee and Z-Wave guide&lt;/a> covers the gateways themselves.&lt;/p>
&lt;p>&lt;strong>A guest network that&amp;rsquo;s actually isolated.&lt;/strong> Visitors get internet, full stop — no visibility into your file shares, your Home Assistant, or your admin panels. A guest VLAN with a block-all-local rule does this cleanly, and you never have to hand out (or later change) your real Wi-Fi password.&lt;/p>
&lt;p>&lt;strong>A management VLAN for the things that run everything.&lt;/strong> Proxmox web UIs, switch management IPs, IPMI/iKVM, UPS network cards — the interfaces that, if reached by the wrong device, hand an attacker the keys. Lock them to a VLAN only your admin machine can enter.&lt;/p>
&lt;p>&lt;strong>Separation of services.&lt;/strong> Production VMs and lab/dev VMs on different VLANs, with outbound rules per segment: production can only reach the specific destinations it needs; the dev VLAN can go anywhere but can&amp;rsquo;t touch production. This is where a homelab starts behaving like a real network, and it&amp;rsquo;s genuinely good practice to learn on hardware you own.&lt;/p>
&lt;h2 id="plan-the-vlans-before-you-touch-a-menu">Plan the VLANs before you touch a menu&lt;/h2>
&lt;p>Ten minutes on paper saves an hour of &amp;ldquo;why can&amp;rsquo;t this ping that.&amp;rdquo; Decide your VLAN IDs, subnets, and the one-line purpose of each before you log into anything:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">VLAN ID&lt;/th>
&lt;th scope="col">Name&lt;/th>
&lt;th scope="col">Subnet&lt;/th>
&lt;th scope="col">Purpose&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="VLAN ID">1&lt;/td>
&lt;td data-label="Name">Default&lt;/td>
&lt;td data-label="Subnet">none&lt;/td>
&lt;td data-label="Purpose">The switch&amp;rsquo;s default VLAN. No devices; kept off the trunk to OPNsense&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="VLAN ID">10&lt;/td>
&lt;td data-label="Name">Homelab&lt;/td>
&lt;td data-label="Subnet">192.168.10.0/24&lt;/td>
&lt;td data-label="Purpose">Proxmox guests, NAS, homelab infrastructure&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="VLAN ID">20&lt;/td>
&lt;td data-label="Name">IoT&lt;/td>
&lt;td data-label="Subnet">192.168.20.0/24&lt;/td>
&lt;td data-label="Purpose">Smart devices, cameras, Zigbee/Z-Wave gateways&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="VLAN ID">30&lt;/td>
&lt;td data-label="Name">Guest&lt;/td>
&lt;td data-label="Subnet">192.168.30.0/24&lt;/td>
&lt;td data-label="Purpose">Visitor devices, fully isolated&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="VLAN ID">40&lt;/td>
&lt;td data-label="Name">Trusted&lt;/td>
&lt;td data-label="Subnet">192.168.40.0/24&lt;/td>
&lt;td data-label="Purpose">Your own laptops, phones and desktops&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="VLAN ID">99&lt;/td>
&lt;td data-label="Name">Management&lt;/td>
&lt;td data-label="Subnet">192.168.99.0/24&lt;/td>
&lt;td data-label="Purpose">Switch mgmt IPs, OPNsense admin, IPMI, your admin laptop&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The IDs are arbitrary but conventions help future-you: 10/20/30/40 for user VLANs, 99 for management, and VLAN 1 left alone. &lt;strong>Don&amp;rsquo;t put anything important on VLAN 1.&lt;/strong> It&amp;rsquo;s the default native VLAN, it carries untagged traffic that lands on it by accident, and every switch treats it specially — using it for real devices is how &amp;ldquo;untagged frames leaked between segments&amp;rdquo; bugs happen. OPNsense&amp;rsquo;s own VLAN guide says the trunk port facing the firewall should carry no native or default VLAN at all.&lt;/p>
&lt;p>Your current flat network keeps running on the firewall&amp;rsquo;s existing LAN port while you build this. Move devices onto Trusted once its tests pass, and keep that old LAN as your way back in until everything works.&lt;/p>
&lt;p>Each VLAN above gets a full &lt;code>/24&lt;/code>, which is 254 usable hosts — far more than a home segment will ever need, and the simplicity is worth the wasted address space. If you&amp;rsquo;d rather carve a block into tidier segments or check the usable host range for a given prefix, the &lt;a href="https://techfuelhq.com/tools/subnet-cidr-calculator/">subnet &amp;amp; CIDR calculator&lt;/a> works out the network, broadcast, and host ranges for any CIDR.&lt;/p>
&lt;p>The switch has to understand 802.1Q tags; an unmanaged switch can&amp;rsquo;t do any of this. If you&amp;rsquo;re buying one, an 8-port smart switch is enough for a first build, and a model with PoE+ ports can also power your access point. The &lt;a href="https://techfuelhq.com/articles/best-homelab-networking-gear-under-200/">homelab networking gear guide&lt;/a> compares more switches, and the &lt;a href="https://techfuelhq.com/tools/poe-budget-calculator/">PoE budget calculator&lt;/a> checks that a switch can feed everything you plug into it.&lt;/p>
&lt;p>With the plan on paper, the next question is the one that trips people up: once every VLAN is isolated, &lt;em>what is actually allowed to talk to what?&lt;/em> Draw that as a grid and the entire firewall policy becomes obvious.&lt;/p>
&lt;!-- ========== SIGNATURE VISUAL B: THE ISOLATION MATRIX ========== -->
&lt;div class="visual-block">
&lt;div style="background:#0a0a23;border:1px solid rgba(255,255,255,0.07);border-radius:10px;padding:26px 22px 20px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',sans-serif;">
&lt;div style="margin-bottom:16px;">
&lt;div style="font-size:19px;font-weight:700;color:#e8e8f0;letter-spacing:-0.3px;">The isolation matrix&lt;/div>
&lt;div style="font-size:0.875rem;color:#9a9ab5;margin-top:5px;line-height:1.5;">Read a row as &amp;ldquo;traffic starting &lt;em>from&lt;/em> this VLAN, going &lt;em>to&lt;/em>&amp;hellip;&amp;rdquo;. This grid &lt;em>is&lt;/em> the firewall policy &amp;mdash; every green cell is a pass rule, every red cell a block rule. Build this before you write a single rule.&lt;/div>
&lt;/div>
&lt;div style="overflow-x:auto;">
&lt;table style="border-collapse:collapse;width:100%;min-width:520px;font-size:0.875rem;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',sans-serif;">
&lt;thead>
&lt;tr>
&lt;th style="text-align:left;padding:8px 10px;color:#6b6b8a;font-size:0.8125rem;font-weight:700;border-bottom:1px solid #2a2a4a;">FROM &amp;darr; / TO &amp;rarr;&lt;/th>
&lt;th style="padding:8px 6px;color:#c8c8d8;border-bottom:1px solid #2a2a4a;">Trusted&lt;/th>
&lt;th style="padding:8px 6px;color:#c8c8d8;border-bottom:1px solid #2a2a4a;">Homelab&lt;/th>
&lt;th style="padding:8px 6px;color:#c8c8d8;border-bottom:1px solid #2a2a4a;">IoT&lt;/th>
&lt;th style="padding:8px 6px;color:#c8c8d8;border-bottom:1px solid #2a2a4a;">Guest&lt;/th>
&lt;th style="padding:8px 6px;color:#c8c8d8;border-bottom:1px solid #2a2a4a;">Mgmt&lt;/th>
&lt;th style="padding:8px 6px;color:#c8c8d8;border-bottom:1px solid #2a2a4a;">Internet&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td style="padding:7px 10px;color:#e8e8f0;font-weight:600;border-bottom:1px solid #16162e;">Trusted&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;border-bottom:1px solid #16162e;">self&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;border-bottom:1px solid #16162e;">allow&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;border-bottom:1px solid #16162e;">allow&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#14243a;color:#8ab8e8;border-bottom:1px solid #16162e;">allow&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="padding:7px 10px;color:#e8e8f0;font-weight:600;border-bottom:1px solid #16162e;">Homelab&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;border-bottom:1px solid #16162e;">allow&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;border-bottom:1px solid #16162e;">self&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;border-bottom:1px solid #16162e;">allow&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#14243a;color:#8ab8e8;border-bottom:1px solid #16162e;">allow&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="padding:7px 10px;color:#e8e8f0;font-weight:600;border-bottom:1px solid #16162e;">IoT&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#2a2416;color:#e8c87a;border-bottom:1px solid #16162e;">self*&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#14243a;color:#8ab8e8;border-bottom:1px solid #16162e;">allow&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="padding:7px 10px;color:#e8e8f0;font-weight:600;border-bottom:1px solid #16162e;">Guest&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#301616;color:#e88a8a;border-bottom:1px solid #16162e;">block&lt;/td>
&lt;td style="text-align:center;background:#14243a;color:#8ab8e8;border-bottom:1px solid #16162e;">allow&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="padding:7px 10px;color:#e8e8f0;font-weight:600;">Mgmt&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;">allow&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;">allow&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;">allow&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;">allow&lt;/td>
&lt;td style="text-align:center;background:#16301a;color:#7ee89a;">self&lt;/td>
&lt;td style="text-align:center;background:#14243a;color:#8ab8e8;">allow&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;div style="margin-top:14px;display:flex;gap:16px;flex-wrap:wrap;font-size:0.875rem;color:#9a9ab5;">
&lt;span>&lt;span style="display:inline-block;width:10px;height:10px;background:#16301a;border:1px solid #7ee89a;border-radius:2px;vertical-align:middle;">&lt;/span> pass rule&lt;/span>
&lt;span>&lt;span style="display:inline-block;width:10px;height:10px;background:#301616;border:1px solid #e88a8a;border-radius:2px;vertical-align:middle;">&lt;/span> block rule&lt;/span>
&lt;span>&lt;span style="display:inline-block;width:10px;height:10px;background:#14243a;border:1px solid #8ab8e8;border-radius:2px;vertical-align:middle;">&lt;/span> internet only&lt;/span>
&lt;/div>
&lt;div style="margin-top:11px;font-size:0.875rem;color:#6a6a86;line-height:1.55;">*IoT-to-IoT is a judgment call: block it too if you want one compromised device unable to reach the others. Note the deliberate one-way arrows &amp;mdash; Trusted reaches Homelab, but Homelab-to-Trusted stays open here because you trust your own infrastructure; tighten that if you don't.&lt;/div>
&lt;div style="margin-top:14px;padding-top:12px;border-top:1px solid rgba(255,255,255,0.06);font-size:0.8125rem;color:#55556e;display:flex;justify-content:space-between;">
&lt;span>Default-deny between VLANs; open exactly the cells you need.&lt;/span>
&lt;span>techfuelhq.com&lt;/span>
&lt;/div>
&lt;/div>
&lt;/div>
&lt;p>The rest of this guide is just teaching your three boxes to enforce that grid. OPNsense routes and filters (the colored cells above). The MikroTik switch tags and untags (the frame lifecycle up top). Proxmox carries the whole set of VLANs to your VMs over one cable.&lt;/p>
&lt;h2 id="back-up-both-boxes-first">Back up both boxes first&lt;/h2>
&lt;p>Before you change anything, take a copy you can restore:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>OPNsense:&lt;/strong> &lt;code>System ‣ Configuration ‣ Backups&lt;/code>, then download the configuration file.&lt;/li>
&lt;li>&lt;strong>MikroTik:&lt;/strong> export the whole configuration as a text script, then copy the file off the switch:&lt;/li>
&lt;/ul>
&lt;pre tabindex="0">&lt;code>/export file=before-vlans
&lt;/code>&lt;/pre>&lt;p>RouterOS saves it as &lt;code>before-vlans.rsc&lt;/code>. MikroTik notes that an export leaves out user passwords, certificates and SSH keys, so keep those separately.&lt;/p>
&lt;h2 id="opnsense-routing-and-the-firewall-rules">OPNsense: routing and the firewall rules&lt;/h2>
&lt;p>OPNsense is where the isolation matrix becomes real. It terminates every VLAN, hands out DHCP on each, and enforces the pass/block rules.&lt;/p>
&lt;h3 id="create-the-vlan-interfaces">Create the VLAN interfaces&lt;/h3>
&lt;p>Open &lt;code>Interfaces ‣ Devices ‣ VLAN&lt;/code> (older OPNsense releases called this menu &amp;ldquo;Other Types&amp;rdquo;). For each VLAN:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Parent:&lt;/strong> the port cabled to the switch trunk (&lt;code>ether1&lt;/code>). OPNsense&amp;rsquo;s VLAN guide says the parent interface should stay unassigned, so use a spare port such as &lt;code>igc2&lt;/code> rather than the port your current LAN runs on. On a two-port firewall the LAN itself has to move onto a VLAN; do that from the console with your backup in hand.&lt;/li>
&lt;li>&lt;strong>VLAN tag:&lt;/strong> the VLAN ID (e.g., &lt;code>10&lt;/code>)&lt;/li>
&lt;li>&lt;strong>Description:&lt;/strong> Homelab, IoT, Guest, Trusted, Management&lt;/li>
&lt;/ul>
&lt;p>Then assign them under &lt;code>Interfaces ‣ Assignments&lt;/code>: add each new VLAN device (OPNsense names them like &lt;code>vlan0.10&lt;/code>) as an interface and rename it to something legible — &lt;code>HOMELAB&lt;/code>, &lt;code>IOT&lt;/code>, &lt;code>GUEST&lt;/code>, &lt;code>TRUSTED&lt;/code>, &lt;code>MGMT&lt;/code>. This assignment step is easy to forget, and until you do it the interface has no IP and routes nothing.&lt;/p>
&lt;h3 id="give-each-vlan-an-ip-and-dhcp">Give each VLAN an IP and DHCP&lt;/h3>
&lt;p>For each assigned interface (e.g., &lt;code>Interfaces ‣ HOMELAB&lt;/code>): &lt;strong>Enable&lt;/strong>, IPv4 Configuration Type &lt;strong>Static IPv4&lt;/strong>, address &lt;code>192.168.10.1/24&lt;/code>. That &lt;code>.1&lt;/code> is the VLAN&amp;rsquo;s gateway. Repeat per VLAN. Each VLAN needs its own subnet, or inter-VLAN routing won&amp;rsquo;t work.&lt;/p>
&lt;p>DHCP comes from Dnsmasq, which the current setup wizard configures for DHCP (ISC DHCP is end-of-life in OPNsense). In &lt;code>Services ‣ Dnsmasq DNS &amp;amp; DHCP ‣ General&lt;/code>, add the VLAN interfaces under &lt;strong>Interface&lt;/strong> and tick &lt;strong>DHCP register firewall rules&lt;/strong>, so OPNsense adds the rules that let DHCP through. Then in &lt;code>Services ‣ Dnsmasq DNS &amp;amp; DHCP ‣ DHCP ranges&lt;/code>, add one range per interface, such as &lt;code>192.168.10.100&lt;/code> to &lt;code>192.168.10.199&lt;/code> for Homelab and the same pattern for IoT, Guest and Trusted. The Management VLAN can stay static-only if you prefer to hand-assign admin addresses; then give your admin laptop a fixed address such as &lt;code>192.168.99.10/24&lt;/code>.&lt;/p>
&lt;h3 id="write-the-firewall-rules">Write the firewall rules&lt;/h3>
&lt;p>&lt;code>Firewall ‣ Rules&lt;/code>, per interface tab. Put a rule on the interface where the traffic enters the firewall. A connection from Homelab to Management enters on Homelab, so a block placed only on the Management tab does not protect that destination. For ordinary quick interface rules, the first match wins; blocks must precede broad passes. See the &lt;a href="https://docs.opnsense.org/manual/firewall.html" rel="noopener">OPNsense firewall rule documentation&lt;/a> for processing order, including automatic and floating rules.&lt;/p>
&lt;p>&lt;code>RFC1918&lt;/code> below means an alias you create under &lt;code>Firewall ‣ Aliases&lt;/code> holding &lt;code>10.0.0.0/8&lt;/code>, &lt;code>172.16.0.0/12&lt;/code> and &lt;code>192.168.0.0/16&lt;/code>. It includes the firewall&amp;rsquo;s own addresses, which is why IoT and Guest need a DNS pass above the block: devices there use their VLAN gateway as their DNS server, and, per OPNsense&amp;rsquo;s &lt;a href="https://docs.opnsense.org/manual/unbound.html" rel="noopener">Unbound documentation&lt;/a>, Unbound answers queries on every available interface address by default.&lt;/p>
&lt;pre tabindex="0">&lt;code># IoT tab
Pass IoT net -&amp;gt; 192.168.20.1 TCP/UDP 53 # DNS on the firewall&amp;#39;s IoT address
Block IoT net -&amp;gt; RFC1918 # no other local network, firewall included
Pass IoT net -&amp;gt; any # internet is fine
&lt;/code>&lt;/pre>&lt;pre tabindex="0">&lt;code># Guest tab
Pass Guest net -&amp;gt; 192.168.30.1 TCP/UDP 53 # DNS on the firewall&amp;#39;s Guest address
Block Guest net -&amp;gt; RFC1918 # no local anything
Pass Guest net -&amp;gt; any # internet only
&lt;/code>&lt;/pre>&lt;pre tabindex="0">&lt;code># Homelab tab: block the management destination before the broad pass
Block Homelab net -&amp;gt; MGMT net
Block Homelab net -&amp;gt; Guest net # matches the matrix
Pass Homelab net -&amp;gt; any
&lt;/code>&lt;/pre>&lt;pre tabindex="0">&lt;code># Trusted tab: management is reserved for the admin segment
Block Trusted net -&amp;gt; MGMT net
Block Trusted net -&amp;gt; Guest net # matches the matrix
Pass Trusted net -&amp;gt; any
&lt;/code>&lt;/pre>&lt;pre tabindex="0">&lt;code># Management tab: traffic originating from the admin segment
Pass MGMT net -&amp;gt; any
&lt;/code>&lt;/pre>&lt;p>DHCP needs no rule of its own here because Dnsmasq registered it. IoT and Guest already block the management subnet through their private-address blocks. Any additional source VLAN needs its own management deny before a broad pass. The broad passes on Homelab and Trusted also reach the firewall&amp;rsquo;s own address on that VLAN, web interface included; if only Management should administer the firewall, add a block for that address above the pass and test it from the console. Check automatic, floating and anti-lockout rules as well; preserve console access before changing administration rules. These examples cover IPv4. Add equivalent IPv6 policy before enabling routed IPv6.&lt;/p>
&lt;p>Test the boundary with a known management service. First confirm its address and port work from an authorized Management host. Then attempt a new connection to the same address and port from Homelab, Trusted, IoT and Guest; those attempts should be blocked in the firewall log. Use a fresh connection because an existing state can survive a rule edit. A service that was already unreachable is not evidence that your deny rule works.&lt;/p>
&lt;h2 id="mikrotik-bridge-vlan-filtering-do-this-the-modern-way">MikroTik: bridge VLAN filtering (do this the modern way)&lt;/h2>
&lt;p>Here is where a lot of older guides will steer you wrong, so read this section carefully. On a CRS3xx-class MikroTik switch, VLANs are &lt;strong>not&lt;/strong> configured by creating &lt;code>/interface vlan&lt;/code> objects on a physical port. That approach is exactly the misconfiguration MikroTik&amp;rsquo;s own documentation warns against; it produces switches that &amp;ldquo;work&amp;rdquo; until they mysteriously don&amp;rsquo;t, because traffic is being software-switched through the CPU instead of hardware-offloaded in the switch chip. The correct modern method is &lt;strong>bridge VLAN filtering&lt;/strong>: one bridge, a VLAN table that says which ports are tagged and untagged for each VLAN, and a single switch to turn filtering on.&lt;/p>
&lt;p>&lt;strong>One hard warning first:&lt;/strong> enabling &lt;code>vlan-filtering=yes&lt;/code> is the last step, and doing it wrong locks you out of the switch. Configure everything else, make sure your own access port and management VLAN are in the table, and ideally have serial/console access before you flip that switch. If you enable filtering over the very connection you&amp;rsquo;re configuring and the management VLAN isn&amp;rsquo;t set up correctly, the session dies mid-command.&lt;/p>
&lt;p>The example below uses &lt;code>ether1&lt;/code> for the trunk to OPNsense, &lt;code>ether2&lt;/code> for a tagged Proxmox guest uplink, &lt;code>ether3&lt;/code> for an untagged IoT device, &lt;code>ether4&lt;/code> for a trusted desktop, &lt;code>ether5&lt;/code> for your admin laptop on Management, and &lt;code>ether6&lt;/code> for a Wi-Fi access point. These are example port names; map them to the physical interfaces on your model. Keep the Proxmox host&amp;rsquo;s existing management cable and bridge separate while configuring the guest uplink. A host with only one NIC needs a planned management migration and console access before using a tagged-only port.&lt;/p>
&lt;p>&lt;strong>Build the bridge with filtering off, add the ports:&lt;/strong>&lt;/p>
&lt;pre tabindex="0">&lt;code>/interface bridge
add name=bridge1 vlan-filtering=no
/interface bridge port
# ether1 = trunk to OPNsense: tagged frames only, no native VLAN
add bridge=bridge1 interface=ether1 ingress-filtering=yes frame-types=admit-only-vlan-tagged
# ether2 = tagged trunk to the Proxmox guest bridge
add bridge=bridge1 interface=ether2 ingress-filtering=yes frame-types=admit-only-vlan-tagged
# ether3 = access port for an IoT hub on VLAN 20
add bridge=bridge1 interface=ether3 pvid=20 ingress-filtering=yes frame-types=admit-only-untagged-and-priority-tagged
# ether4 = access port for a trusted desktop on VLAN 40
add bridge=bridge1 interface=ether4 pvid=40 ingress-filtering=yes frame-types=admit-only-untagged-and-priority-tagged
# ether5 = access port for your admin laptop on VLAN 99
add bridge=bridge1 interface=ether5 pvid=99 ingress-filtering=yes frame-types=admit-only-untagged-and-priority-tagged
# ether6 = access point: tagged SSID VLANs plus untagged management (see the Wi-Fi section)
add bridge=bridge1 interface=ether6 pvid=99 ingress-filtering=yes
&lt;/code>&lt;/pre>&lt;p>The &lt;code>pvid&lt;/code> on an access port is what stamps incoming untagged frames onto the right VLAN — it&amp;rsquo;s the &amp;ldquo;IN&amp;rdquo; step from the frame-lifecycle diagram. &lt;code>frame-types=admit-only-untagged-and-priority-tagged&lt;/code> tells that port to reject already-tagged frames, so a device can&amp;rsquo;t lie about its VLAN. On the trunks, &lt;code>admit-only-vlan-tagged&lt;/code> drops untagged frames, which keeps VLAN 1 off them. MikroTik&amp;rsquo;s guide says to use &lt;code>ingress-filtering&lt;/code> wherever possible; without it, a port can still inject traffic for a VLAN it isn&amp;rsquo;t a member of.&lt;/p>
&lt;p>&lt;strong>Fill in the VLAN table — which ports are tagged vs untagged per VLAN:&lt;/strong>&lt;/p>
&lt;pre tabindex="0">&lt;code>/interface bridge vlan
add bridge=bridge1 tagged=ether1,ether2 vlan-ids=10
add bridge=bridge1 tagged=ether1,ether2,ether6 untagged=ether3 vlan-ids=20
add bridge=bridge1 tagged=ether1,ether2,ether6 vlan-ids=30
add bridge=bridge1 tagged=ether1,ether6 untagged=ether4 vlan-ids=40
# Only VLAN 99 includes bridge1 (the switch itself), so management lives there alone
add bridge=bridge1 tagged=bridge1,ether1,ether2 untagged=ether5,ether6 vlan-ids=99
&lt;/code>&lt;/pre>&lt;p>&lt;code>bridge1&lt;/code> in a &lt;code>tagged&lt;/code> list is the switch&amp;rsquo;s own CPU. MikroTik&amp;rsquo;s examples add it only to the management VLAN, so the switch has no address on the others.&lt;/p>
&lt;p>&lt;strong>Put the switch&amp;rsquo;s own management IP on VLAN 99, then enable filtering last:&lt;/strong>&lt;/p>
&lt;pre tabindex="0">&lt;code>/interface vlan
add interface=bridge1 name=vlan99 vlan-id=99
# this /interface vlan is correct - it is on the BRIDGE, giving the switch itself an L3 presence on VLAN 99
/ip address
add address=192.168.99.2/24 interface=vlan99
/ip route
add dst-address=0.0.0.0/0 gateway=192.168.99.1
&lt;/code>&lt;/pre>&lt;p>Plug your admin laptop into &lt;code>ether5&lt;/code> with its &lt;code>192.168.99.x&lt;/code> address. Then turn on Safe Mode (&lt;code>Ctrl+X&lt;/code> in the terminal, or the Safe Mode button in WinBox) and enable filtering, with the CPU port accepting tagged frames only:&lt;/p>
&lt;pre tabindex="0">&lt;code>/interface bridge
set bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes vlan-filtering=yes
&lt;/code>&lt;/pre>&lt;p>If that cuts your session, RouterOS undoes every change made in Safe Mode once the connection times out (MikroTik gives the TCP timeout as 9 minutes). If you can still reach &lt;code>192.168.99.2&lt;/code> from a new session, end the Safe Mode session with &lt;code>/quit&lt;/code>, which keeps the changes; &lt;code>Ctrl+D&lt;/code> would undo them.&lt;/p>
&lt;p>Note the distinction that trips everyone up: &lt;code>/interface vlan&lt;/code> is wrong on a &lt;em>physical ether port&lt;/em> (that&amp;rsquo;s the software-switching trap) but &lt;strong>right on the bridge itself&lt;/strong>, where it gives the switch a routable management address on VLAN 99. Same command, completely different meaning depending on where you point it.&lt;/p>
&lt;h2 id="wi-fi-one-ssid-per-vlan">Wi-Fi: one SSID per VLAN&lt;/h2>
&lt;p>Most IoT and guest devices arrive over Wi-Fi, so the access point does the same job as an access port, once per SSID. In the AP&amp;rsquo;s settings, map each SSID to a single VLAN: an IoT SSID on 20, a guest SSID on 30, your own SSID on 40. Ubiquiti&amp;rsquo;s UniFi guide describes exactly this, and MikroTik&amp;rsquo;s Wi-Fi docs do the same with a VLAN ID per wireless interface. The switch port feeding the AP then carries those VLANs tagged, which is what &lt;code>ether6&lt;/code> does in the table above.&lt;/p>
&lt;p>If the AP&amp;rsquo;s own management address is untagged, give its port &lt;code>pvid=99&lt;/code>, as above, so management lands on the Management VLAN, and leave its &lt;code>frame-types&lt;/code> at the default so it accepts both tagged SSID traffic and untagged management (the hybrid-port case in MikroTik&amp;rsquo;s guide). Check that a phone joining each SSID gets an address from that VLAN&amp;rsquo;s DHCP range. For picking the AP or router itself, see the &lt;a href="https://techfuelhq.com/networking/best-wifi-7-router-2026/">Wi-Fi 7 router guide&lt;/a>.&lt;/p>
&lt;h2 id="proxmox-one-vlan-aware-bridge-every-vlan">Proxmox: one VLAN-aware bridge, every VLAN&lt;/h2>
&lt;p>One VLAN-aware bridge can carry the guest VLANs. This example creates &lt;code>vmbr1&lt;/code> on a spare physical NIC such as &lt;code>eno2&lt;/code>, retaining the existing management bridge and its IP configuration. Check that both example names are free and that the NIC is the one cabled to switch port &lt;code>ether2&lt;/code>.&lt;/p>
&lt;p>&lt;code>Datacenter → pve01 → System → Network&lt;/code>:&lt;/p>
&lt;ul>
&lt;li>Choose Create → Linux Bridge, name it &lt;code>vmbr1&lt;/code>, and set Bridge ports to the spare NIC (&lt;code>eno2&lt;/code> in this example).&lt;/li>
&lt;li>Tick VLAN aware. Leave the new bridge&amp;rsquo;s host IP addresses and gateway empty; do not move the existing management address or default route.&lt;/li>
&lt;li>Save, review the pending change from the console, then Apply Configuration.&lt;/li>
&lt;/ul>
&lt;p>The new bridge&amp;rsquo;s physical NIC plugs into the tagged &lt;code>ether2&lt;/code> trunk configured above. That port admits VLAN-tagged frames and carries VLANs 10, 20, 30 and 99. Then, when creating or editing a VM/LXC, in the network tab:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Bridge:&lt;/strong> &lt;code>vmbr1&lt;/code>&lt;/li>
&lt;li>&lt;strong>VLAN Tag:&lt;/strong> &lt;code>10&lt;/code> (for the Homelab VLAN)&lt;/li>
&lt;/ul>
&lt;p>The guest gets an untagged interface that Proxmox silently places on VLAN 10. The VM has no idea — it&amp;rsquo;s the frame-lifecycle &amp;ldquo;OUT&amp;rdquo; step happening inside the host. Want a guest reachable from two VLANs? Home Assistant is the classic case: user access from one VLAN, device discovery on IoT. Add a second network device with a different VLAN Tag; the &lt;a href="https://techfuelhq.com/tutorials/home-assistant-proxmox-2026/">Home Assistant on Proxmox guide&lt;/a> sets up that VM. To reach it from Trusted with this table, add VLAN 40 to &lt;code>ether2&lt;/code>&amp;rsquo;s tagged list as well. One caveat worth burning into memory: &lt;strong>don&amp;rsquo;t put the Proxmox management interface itself on a VLAN unless you&amp;rsquo;re sure the config is right and you have console/iKVM access.&lt;/strong> A VLAN typo on the management interface locks you out of the very web UI you&amp;rsquo;d use to fix it.&lt;/p>
&lt;h2 id="the-thing-that-quietly-breaks-mdns-and-multicast">The thing that quietly breaks: mDNS and multicast&lt;/h2>
&lt;p>You will finish all of the above, test it, watch IoT get blocked from your LAN, feel great — and then discover you can no longer cast to the living-room TV, AirPlay to a HomePod, or print from your laptop. Nothing is broken. This is VLANs working &lt;em>exactly&lt;/em> as designed, and it&amp;rsquo;s the single most common &amp;ldquo;why did I even do this&amp;rdquo; moment.&lt;/p>
&lt;p>Many casting, AirPlay, HomeKit and AirPrint devices advertise services through &lt;strong>mDNS on UDP port 5353&lt;/strong>. Link-local mDNS does not normally cross routed VLAN boundaries. Your phone can therefore fail to discover a device even when a routed connection to its address would be allowed. Some products also use other discovery methods; mDNS is not a universal fix for every device.&lt;/p>
&lt;p>The fix is an &lt;strong>mDNS reflector&lt;/strong> (also called a repeater): a service that listens for those multicast announcements on one VLAN and rebroadcasts them onto the others, so devices on different segments can discover each other. On OPNsense:&lt;/p>
&lt;ol>
&lt;li>&lt;code>System ‣ Firmware ‣ Plugins&lt;/code> — install &lt;strong>&lt;code>os-mdns-repeater&lt;/code>&lt;/strong>, then reload the page.&lt;/li>
&lt;li>&lt;code>Services ‣ MDNS Repeater&lt;/code> — enable it and select the VLANs that need to see each other (typically Trusted and IoT). It needs at least two and at most five interfaces.&lt;/li>
&lt;li>Check &lt;code>Firewall ‣ Rules&lt;/code> and the firewall log for discovery traffic on each participating interface. Where the rules block it, allow UDP 5353 from that VLAN to the mDNS multicast destination for the address family in use. This permits discovery traffic; it does not permit the subsequent application session.&lt;/li>
&lt;/ol>
&lt;p>Discovery provides an address and service port, as described in &lt;a href="https://www.rfc-editor.org/rfc/rfc6763.html#section-5" rel="noopener">DNS-SD&lt;/a>. The client then connects to that service over a separately allowed routed path. In this guide, the Trusted tab&amp;rsquo;s &lt;code>Pass Trusted net -&amp;gt; any&lt;/code> rule allows Trusted clients to initiate connections to IoT devices, with replies allowed by firewall state. If you tighten that rule, add the required device addresses and application TCP/UDP ports explicitly. Device-initiated connections may need their own exception; a reflector does not authorize them.&lt;/p>
&lt;p>Test from every VLAN intended to use the service: first confirm discovery, then complete a cast/playback session, HomeKit operation or print job and inspect denied traffic. A device appearing in a picker proves discovery only. Keep Guest out of the reflector and restrict participation to the segments that need it. If you&amp;rsquo;d rather resolve names centrally, &lt;a href="https://techfuelhq.com/tutorials/adguard-home-local-dns-proxmox-2026/">AdGuard Home as local DNS&lt;/a> covers serving DNS across VLANs.&lt;/p>
&lt;h2 id="test-that-isolation-is-real">Test that isolation is real&lt;/h2>
&lt;p>Configuration that isn&amp;rsquo;t verified is a guess. Prove each cell of the matrix:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># From an IoT device (or a VM tagged onto VLAN 20)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ping 1.1.1.1 &lt;span style="color:#75715e"># PASS - internet allowed&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>nslookup example.com 192.168.20.1 &lt;span style="color:#75715e"># PASS - DNS on its own gateway&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ping 192.168.40.1 &lt;span style="color:#75715e"># FAIL - blocked from the Trusted VLAN&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ping 192.168.10.10 &lt;span style="color:#75715e"># FAIL - blocked from homelab&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># From a laptop on the Trusted VLAN&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ping 192.168.10.10 &lt;span style="color:#75715e"># PASS - Trusted can reach the test Homelab guest&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ping 192.168.99.2 &lt;span style="color:#75715e"># FAIL - switch management is reserved for Management&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># From the admin laptop on ether5 (Management)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ping 192.168.99.2 &lt;span style="color:#75715e"># PASS - the switch answers on its management address&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If an inter-VLAN test fails when it should pass (or passes when it should fail), work down this list in order:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>OPNsense rule order&lt;/strong> — block before pass, first match wins.&lt;/li>
&lt;li>&lt;strong>DNS on IoT or Guest&lt;/strong> — if devices get an address but no names resolve, the DNS pass rule is missing or sits below the RFC1918 block.&lt;/li>
&lt;li>&lt;strong>DHCP scope&lt;/strong> — is the device actually getting an address in the right VLAN&amp;rsquo;s range? Wrong subnet means wrong VLAN, upstream of any rule.&lt;/li>
&lt;li>&lt;strong>Switch VLAN table&lt;/strong> — does the untagged port assignment match the VLAN ID? And did you remember &lt;code>vlan-filtering=yes&lt;/code>?&lt;/li>
&lt;/ol>
&lt;h2 id="the-mistakes-that-cost-the-most-time">The mistakes that cost the most time&lt;/h2>
&lt;p>&lt;strong>&lt;code>vlan-filtering=yes&lt;/code> never got set.&lt;/strong> You built the entire bridge VLAN table, everything looks configured, and no segmentation is enforced — because filtering is still off and the table is inert. This is a silent failure: nothing errors, it just doesn&amp;rsquo;t work. It&amp;rsquo;s the first thing to check on a MikroTik that &amp;ldquo;isn&amp;rsquo;t segmenting.&amp;rdquo;&lt;/p>
&lt;p>&lt;strong>A pass-any rule sitting above the block rule.&lt;/strong> OPNsense reads top to bottom and stops at the first match. If IoT can still reach your LAN, a broad pass rule is almost certainly shadowing your block. Reorder it.&lt;/p>
&lt;p>&lt;strong>Forgetting to assign the VLAN interface in OPNsense.&lt;/strong> Creating the device under &lt;code>Interfaces ‣ Devices ‣ VLAN&lt;/code> is only half the job — it does nothing until you also add it under &lt;code>Interfaces ‣ Assignments&lt;/code> and give it an IP.&lt;/p>
&lt;p>&lt;strong>The trunk isn&amp;rsquo;t tagged for a VLAN that needs it.&lt;/strong> If VLAN 20 traffic never reaches OPNsense, the trunk port probably isn&amp;rsquo;t in VLAN 20&amp;rsquo;s tagged list. Every VLAN that has to reach the router must be tagged on the uplink, and every SSID&amp;rsquo;s VLAN must be tagged on the AP&amp;rsquo;s port.&lt;/p>
&lt;p>&lt;strong>Management on a VLAN with no escape hatch.&lt;/strong> Putting a switch or Proxmox host&amp;rsquo;s management interface on a VLAN is good practice — right up until a VLAN typo locks you out of the only interface you could fix it from. Always keep a console path: serial for the switch, iKVM or a directly attached keyboard/monitor for Proxmox.&lt;/p>
&lt;p>&lt;strong>Treating discovery as proof of connectivity.&lt;/strong> If a device is missing, check mDNS and any other discovery protocol it uses. If it appears but playback or printing fails, check routing and the application&amp;rsquo;s service ports in the firewall log. The repeater only handles discovery.&lt;/p>
&lt;hr>
&lt;p>&lt;em>VLANs need a capable router to enforce inter-VLAN firewall rules — the segmentation lives at the switch, but the policy lives at the firewall. The &lt;a href="https://techfuelhq.com/tutorials/opnsense-mini-pc-setup-2026/">OPNsense setup guide&lt;/a> covers building that firewall from scratch, &lt;a href="https://techfuelhq.com/networking/opnsense-vs-pfsense-2026/">OPNsense vs pfSense&lt;/a> helps pick between the two for the routing role, and &lt;a href="https://techfuelhq.com/networking/unifi-vs-opnsense-build-2026/">UniFi vs an OPNsense build&lt;/a> covers the all-UniFi alternative. For the physical layer — managed switches and cabling — the &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE home networking guide&lt;/a> covers hardware selection.&lt;/em>&lt;/p>
&lt;p>For a beginner-first VLAN plan covering subnets, Wi-Fi mapping and isolation checks, see Obelinf&amp;rsquo;s &lt;a href="https://obelinf.com/blog/how-to-set-up-vlans-in-a-homelab/" rel="nofollow">homelab VLAN setup guide&lt;/a>. This is a reciprocal editorial link; TechFuel HQ chose the reference and wording.&lt;/p></description></item><item><title>Self-Hosted Password Manager: Vaultwarden on Proxmox (2026)</title><link>https://techfuelhq.com/tutorials/vaultwarden-proxmox-2026/</link><pubDate>Fri, 29 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/vaultwarden-proxmox-2026/</guid><atom:updated>2026-11-18T04:54:38Z</atom:updated><description>&lt;img src="https://techfuelhq.com/images/tutorials/vaultwarden-proxmox-2026.svg" alt="Architecture diagram of Vaultwarden on Proxmox: a Debian 12 LXC inside a Proxmox VE host runs the Rust Vaultwarden binary on 127.0.0.1:8080 behind a Caddy reverse proxy that terminates Let's Encrypt HTTPS; browser, mobile, and desktop Bitwarden clients sync in over HTTPS, access is via public Let's Encrypt or Tailscale-only, and a daily 2 AM job backs up the SQLite database, attachments, and RSA keys to a NAS — about 100MB total RAM." width="1200" height="630" loading="eager" fetchpriority="high" style="display:block;margin:1.5rem auto;max-width:100%;height:auto;border:1px solid #1e1e3a;border-radius:8px;" />
&lt;p>Password managers that live in someone else&amp;rsquo;s cloud have one failure mode that self-hosted doesn&amp;rsquo;t: the company goes under, gets acquired, or changes pricing. Vaultwarden on Proxmox solves this. Your vault lives on hardware you own, all Bitwarden official clients work against it without modification, and the whole setup runs in one lightweight LXC container.&lt;/p>
&lt;p>This guide goes from an empty Proxmox node to a working Vaultwarden 1.37.5 install with HTTPS, closed signups, a hashed admin token, daily backups and every device connected. It is written against Vaultwarden 1.37.5 (released November 1, 2026), a Debian 13 container and Proxmox VE 9.2.&lt;/p>
&lt;h2 id="what-vaultwarden-is">What Vaultwarden is&lt;/h2>
&lt;p>Vaultwarden is an open-source reimplementation of the Bitwarden server written in Rust. It is not affiliated with Bitwarden, Inc., but it is compatible with all official Bitwarden clients — browser extensions, mobile apps, desktop apps — without any modification to those clients.&lt;/p>
&lt;p>What you get versus bitwarden.com paid plans: organizations, collections, TOTP authenticator codes, and Bitwarden Send — all for free, running on your own hardware. What you don&amp;rsquo;t get: Bitwarden&amp;rsquo;s enterprise compliance features and their guaranteed uptime. For a homelab password manager, the trade is worth it.&lt;/p>
&lt;p>(Bitwarden&amp;rsquo;s &lt;a href="https://bitwarden.com/help/install-on-premise-linux/" rel="noopener">standard self-hosted deployment&lt;/a> runs eleven containers, and its &lt;a href="https://bitwarden.com/help/install-and-deploy-lite/" rel="noopener">lite deployment&lt;/a> one Docker image; Vaultwarden is a single Rust binary.)&lt;/p>
&lt;h2 id="prerequisites">Prerequisites&lt;/h2>
&lt;ul>
&lt;li>Proxmox VE 9.x (Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/wiki/FAQ" rel="noopener">lifecycle table&lt;/a> ended VE 8 support in August 2026)&lt;/li>
&lt;li>A domain name you control with the ability to add a DNS record (even a subdomain works), or &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale&lt;/a> with HTTPS enabled for a tailnet-only vault&lt;/li>
&lt;li>Basic comfort with SSH and running commands&lt;/li>
&lt;/ul>
&lt;p>This guide uses Caddy as the reverse proxy because it obtains and renews certificates on its own. If you already run nginx or Traefik, adapt the proxy block; the &lt;a href="https://techfuelhq.com/homelab/caddy-vs-nginx-proxy-manager-vs-traefik-2026/">Caddy vs Nginx Proxy Manager vs Traefik comparison&lt;/a> covers the trade-offs. If you&amp;rsquo;d rather use a community install script for the container, read &lt;a href="https://techfuelhq.com/homelab/proxmox-helper-scripts-safe-2026/">how to run Proxmox helper scripts safely&lt;/a> first; this guide builds it by hand so you can see every part.&lt;/p>
&lt;h2 id="step-1-create-a-debian-13-lxc">Step 1: Create a Debian 13 LXC&lt;/h2>
&lt;p>In the Proxmox web UI:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Create CT&lt;/strong> with the Debian 13 template (&lt;code>debian-13-standard&lt;/code>). If it isn&amp;rsquo;t downloaded yet, &lt;code>pveam update&lt;/code> and &lt;code>pveam available --section system&lt;/code> list it, and &lt;code>pveam download local &amp;lt;template-name&amp;gt;&lt;/code> fetches it&lt;/li>
&lt;li>&lt;strong>Hostname:&lt;/strong> &lt;code>vaultwarden&lt;/code>&lt;/li>
&lt;li>&lt;strong>Storage:&lt;/strong> 8GB is plenty for the server and OS; increase it if you&amp;rsquo;ll store file attachments&lt;/li>
&lt;li>&lt;strong>RAM:&lt;/strong> 256MB minimum, 512MB comfortable&lt;/li>
&lt;li>&lt;strong>CPU:&lt;/strong> 1 core is sufficient&lt;/li>
&lt;li>&lt;strong>Network:&lt;/strong> a static IP on your LAN (the router will forward to it in Step 3)&lt;/li>
&lt;li>&lt;strong>Unprivileged:&lt;/strong> leave it on. Option A below needs no extra features. Option B (Docker) needs &lt;strong>Nesting&lt;/strong> and &lt;strong>keyctl&lt;/strong>, covered there.&lt;/li>
&lt;/ol>
&lt;p>Start the container and open its console, or SSH in as root. Update it:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>apt update &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span> apt upgrade -y
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>apt install -y curl wget ca-certificates sqlite3
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-2-install-vaultwarden">Step 2: Install Vaultwarden&lt;/h2>
&lt;p>Vaultwarden publishes no standalone binary downloads. Its &lt;a href="https://github.com/dani-garcia/vaultwarden/wiki/Pre-built-binaries" rel="noopener">pre-built binaries&lt;/a> page says the supported way to get one is to extract the statically linked binary from the official Alpine image, along with the matching &lt;code>web-vault&lt;/code> (the binary alone serves no UI). Option A does that without installing Docker. Option B runs the image under Docker instead.&lt;/p>
&lt;h3 id="option-a-binary-in-the-lxc-no-docker-recommended-here">Option A: binary in the LXC, no Docker (recommended here)&lt;/h3>
&lt;p>The project points at &lt;a href="https://github.com/jjlin/docker-image-extract" rel="noopener">docker-image-extract&lt;/a>, a shell script that pulls and unpacks an image from Docker Hub with &lt;code>curl&lt;/code> or &lt;code>wget&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>mkdir -p /root/vw-image /opt/vaultwarden/data
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cd /root/vw-image
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>wget https://raw.githubusercontent.com/jjlin/docker-image-extract/main/docker-image-extract
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>chmod +x docker-image-extract
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>./docker-image-extract vaultwarden/server:1.37.5-alpine
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>install -m &lt;span style="color:#ae81ff">0755&lt;/span> output/vaultwarden /usr/local/bin/vaultwarden
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cp -a output/web-vault /opt/vaultwarden/
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The script extracts the image into &lt;code>./output&lt;/code>. Pin the release tag as above rather than &lt;code>latest&lt;/code>, so you choose when to update.&lt;/p>
&lt;p>&lt;strong>Hash the admin token.&lt;/strong> The admin page&amp;rsquo;s password is &lt;code>ADMIN_TOKEN&lt;/code>, and the config sits in plain text, so store an Argon2 hash instead of the password itself. Vaultwarden has a generator built in; it asks for the password twice and prints a PHC string starting with &lt;code>$argon2id$&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>/usr/local/bin/vaultwarden hash
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Add &lt;code>--preset owasp&lt;/code> for OWASP&amp;rsquo;s minimum settings instead of the Bitwarden defaults. Then create &lt;code>/opt/vaultwarden/.env&lt;/code> and paste the PHC string inside single quotes, so the &lt;code>$&lt;/code> signs are kept as written:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># /opt/vaultwarden/.env&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>DATA_FOLDER&lt;span style="color:#f92672">=&lt;/span>/opt/vaultwarden/data
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>WEB_VAULT_FOLDER&lt;span style="color:#f92672">=&lt;/span>/opt/vaultwarden/web-vault
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>DOMAIN&lt;span style="color:#f92672">=&lt;/span>https://vault.yourdomain.com
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>SIGNUPS_ALLOWED&lt;span style="color:#f92672">=&lt;/span>false
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ADMIN_TOKEN&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;$argon2id$v=19$m=65540,t=3,p=4$...paste-yours...&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ROCKET_ADDRESS&lt;span style="color:#f92672">=&lt;/span>127.0.0.1
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ROCKET_PORT&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">8080&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>chmod &lt;span style="color:#ae81ff">600&lt;/span> /opt/vaultwarden/.env
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>DOMAIN&lt;/code> must be the exact address you&amp;rsquo;ll open the vault at; Vaultwarden&amp;rsquo;s config notes say attachment downloads, email links and U2F depend on it. Create a systemd service:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-ini" data-lang="ini">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># /etc/systemd/system/vaultwarden.service&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">[Unit]&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">Description&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">Vaultwarden password server&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">After&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">network.target&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">[Service]&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">User&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">root&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">EnvironmentFile&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">/opt/vaultwarden/.env&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">ExecStart&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">/usr/local/bin/vaultwarden&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">Restart&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">on-failure&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">WorkingDirectory&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">/opt/vaultwarden&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">[Install]&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">WantedBy&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">multi-user.target&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>systemctl enable --now vaultwarden
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>systemctl status vaultwarden
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Vaultwarden now listens on &lt;code>127.0.0.1:8080&lt;/code>, reachable only from inside the container. Caddy exposes it in the next step.&lt;/p>
&lt;h3 id="option-b-docker-compose">Option B: Docker Compose&lt;/h3>
&lt;p>Docker inside an unprivileged LXC needs two container features. From the Proxmox host shell, run &lt;code>pct set &amp;lt;CTID&amp;gt; --features nesting=1,keyctl=1&lt;/code> and restart the container. Proxmox&amp;rsquo;s container docs say nesting exposes what nested containers need and keyctl is required to use Docker inside a container, and that for maximum isolation, running application containers inside a Proxmox VM remains the recommended practice. If you&amp;rsquo;d rather follow that advice, run these commands in a small Debian VM instead; the &lt;a href="https://techfuelhq.com/homelab/lxc-vs-vm-proxmox-2026/">LXC vs VM guide&lt;/a> covers the choice.&lt;/p>
&lt;p>Install Docker and create the directory:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>curl -fsSL https://get.docker.com | sh
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>mkdir -p /opt/vaultwarden/data
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cd /opt/vaultwarden
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Generate the admin token hash with a throwaway container:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker run --rm -it vaultwarden/server:1.37.5 /vaultwarden hash
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Put the PHC string in &lt;code>/opt/vaultwarden/.env&lt;/code> next to the compose file, inside single quotes:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># /opt/vaultwarden/.env (read by docker compose)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>VAULTWARDEN_ADMIN_TOKEN&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;$argon2id$v=19$m=65540,t=3,p=4$...paste-yours...&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># /opt/vaultwarden/docker-compose.yml&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">vaultwarden&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">vaultwarden/server:1.37.5 &lt;/span> &lt;span style="color:#75715e"># pin the release; 1.37.5 shipped 2026-11-01&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">container_name&lt;/span>: &lt;span style="color:#ae81ff">vaultwarden&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">restart&lt;/span>: &lt;span style="color:#ae81ff">unless-stopped&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">volumes&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./data:/data&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">DOMAIN&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;https://vault.yourdomain.com&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">SIGNUPS_ALLOWED&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;false&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ADMIN_TOKEN&lt;/span>: &lt;span style="color:#ae81ff">${VAULTWARDEN_ADMIN_TOKEN}&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ports&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#e6db74">&amp;#34;127.0.0.1:8080:80&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Passing the token through &lt;code>.env&lt;/code> avoids Compose&amp;rsquo;s variable interpolation of the &lt;code>$&lt;/code> signs. If you paste the PHC string straight into &lt;code>docker-compose.yml&lt;/code> instead, Vaultwarden&amp;rsquo;s wiki says to write every dollar sign twice. &lt;code>docker compose config&lt;/code> shows what Compose will actually pass. Start it:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>chmod &lt;span style="color:#ae81ff">600&lt;/span> /opt/vaultwarden/.env
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose up -d
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose logs -f
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If the log warns that you&amp;rsquo;re using a plain text &lt;code>ADMIN_TOKEN&lt;/code>, the PHC string didn&amp;rsquo;t arrive intact; the &lt;a href="https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page" rel="noopener">admin page wiki&lt;/a> lists the checks.&lt;/p>
&lt;h2 id="step-3-https-with-caddy">Step 3: HTTPS with Caddy&lt;/h2>
&lt;p>Install Caddy from its official repository:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>apt install -y debian-keyring debian-archive-keyring apt-transport-https curl
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>curl -1sLf &lt;span style="color:#e6db74">&amp;#39;https://dl.cloudsmith.io/public/caddy/stable/gpg.key&amp;#39;&lt;/span> | gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>curl -1sLf &lt;span style="color:#e6db74">&amp;#39;https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt&amp;#39;&lt;/span> | tee /etc/apt/sources.list.d/caddy-stable.list
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>chmod o+r /usr/share/keyrings/caddy-stable-archive-keyring.gpg
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>chmod o+r /etc/apt/sources.list.d/caddy-stable.list
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>apt update
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>apt install -y caddy
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The package runs Caddy as a systemd service named &lt;code>caddy&lt;/code>. Replace &lt;code>/etc/caddy/Caddyfile&lt;/code> with:&lt;/p>
&lt;pre tabindex="0">&lt;code># /etc/caddy/Caddyfile
vault.yourdomain.com {
# Only LAN addresses may open the admin page
@admin {
path /admin*
not remote_ip private_ranges
}
redir @admin /
reverse_proxy 127.0.0.1:8080 {
# Pass the real client IP so rate limits and fail2ban see it
header_up X-Real-IP {remote_host}
}
}
&lt;/code>&lt;/pre>&lt;p>Replace &lt;code>vault.yourdomain.com&lt;/code> with your domain and point its DNS record at your home IP. Caddy obtains and renews the Let&amp;rsquo;s Encrypt certificate itself. For that, ports 80 and 443 on your router must forward to this container&amp;rsquo;s LAN IP. The &lt;code>@admin&lt;/code> block is from Vaultwarden&amp;rsquo;s proxy examples and keeps &lt;code>/admin&lt;/code> off the internet. The &lt;code>X-Real-IP&lt;/code> line matters because Vaultwarden&amp;rsquo;s login rate limits and its log lines use that header for the client address.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>systemctl reload caddy
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>systemctl status caddy
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Once the certificate is issued, &lt;code>https://vault.yourdomain.com&lt;/code> shows the Bitwarden login screen. Vaultwarden&amp;rsquo;s &lt;a href="https://github.com/dani-garcia/vaultwarden/wiki/Enabling-HTTPS" rel="noopener">HTTPS wiki&lt;/a> calls HTTPS pretty much required, because the web vault uses web crypto APIs that most browsers only make available in HTTPS contexts.&lt;/p>
&lt;p>Keeping the vault off the internet entirely? Skip the port forward and use Step 7&amp;rsquo;s Tailscale address in place of this one.&lt;/p>
&lt;h2 id="step-4-create-your-account-and-close-signups">Step 4: Create your account and close signups&lt;/h2>
&lt;p>Both config blocks above ship &lt;code>SIGNUPS_ALLOWED=false&lt;/code>, which is the right resting state, but it also hides the &lt;strong>Create account&lt;/strong> link in the web vault, so you can&amp;rsquo;t register your own first account while it is set. Bootstrap in three moves: set &lt;code>SIGNUPS_ALLOWED=true&lt;/code>, restart, and register straight away.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Option A: edit /opt/vaultwarden/.env, then&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>systemctl restart vaultwarden
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Option B: edit docker-compose.yml, then&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose up -d
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Open &lt;code>https://vault.yourdomain.com&lt;/code>, create your account, then put &lt;code>SIGNUPS_ALLOWED=false&lt;/code> back and restart the same way. Do it in the same sitting — an instance reachable from the internet with signups open is a stranger&amp;rsquo;s free vault host. After that, invite new users from the admin panel at &lt;code>https://vault.yourdomain.com/admin&lt;/code>, which works from your LAN and takes the password you hashed in Step 2.&lt;/p>
&lt;p>Settings you save in the admin panel go into &lt;code>config.json&lt;/code> in the data folder and override the environment from then on, so pick one place to manage each setting.&lt;/p>
&lt;p>&lt;strong>Enable two-step login.&lt;/strong> In your account settings, Security, Two-step login, turn on an authenticator app. Store the recovery codes somewhere safe: not in Vaultwarden itself, not in your email, somewhere physically separate.&lt;/p>
&lt;h2 id="step-5-connect-your-devices">Step 5: Connect your devices&lt;/h2>
&lt;p>Bitwarden&amp;rsquo;s apps choose the server on the login screen:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Browser extension and mobile apps:&lt;/strong> on the login screen, open the &lt;strong>Logging in on&lt;/strong> menu, choose &lt;strong>Self-hosted&lt;/strong>, and enter &lt;code>https://vault.yourdomain.com&lt;/code> as the Server URL. On iOS, turn on Bitwarden under the system&amp;rsquo;s AutoFill settings.&lt;/li>
&lt;li>&lt;strong>Desktop app:&lt;/strong> on the login screen, open the &lt;strong>Accessing&lt;/strong> menu, choose &lt;strong>Self-hosted&lt;/strong>, and enter the same URL.&lt;/li>
&lt;/ul>
&lt;p>Log in on each one and let it sync.&lt;/p>
&lt;h2 id="step-6-automated-backups">Step 6: Automated backups&lt;/h2>
&lt;p>Vaultwarden stores everything in &lt;code>/opt/vaultwarden/data/&lt;/code> for both options. The critical files:&lt;/p>
&lt;ul>
&lt;li>&lt;code>db.sqlite3&lt;/code> — your entire vault database&lt;/li>
&lt;li>&lt;code>attachments/&lt;/code> — any file attachments&lt;/li>
&lt;li>&lt;code>config.json&lt;/code> — settings saved from the admin panel&lt;/li>
&lt;li>&lt;code>rsa_key*&lt;/code> — RSA keys for JWT signing (back these up or sessions will invalidate after a restore)&lt;/li>
&lt;/ul>
&lt;p>&lt;code>sqlite3&lt;/code> went on in Step 1. &lt;a href="https://github.com/dani-garcia/vaultwarden/wiki/Backing-up-your-vault" rel="noopener">Vaultwarden&amp;rsquo;s backup guide&lt;/a> recommends SQLite&amp;rsquo;s &lt;code>.backup&lt;/code> command and identifies the separate attachments, configuration and signing-key files. Keep these backups private; configuration can contain credentials.&lt;/p>
&lt;p>Create &lt;code>/opt/vaultwarden/backup.sh&lt;/code> with the following contents. This example requires &lt;code>/mnt/nas-backups&lt;/code> to be an actual mounted filesystem so a missing NAS does not silently turn into a local backup. Set &lt;code>BACKUP_MOUNT&lt;/code> to your real mount point. The script leaves failed attempts under &lt;code>.vw-pending.*&lt;/code> for inspection and exits before retention. It does not stop Vaultwarden: use a maintenance window with application writes stopped when you need the database and attachments captured together.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e">#!/bin/bash
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e">&lt;/span>&lt;span style="color:#75715e"># /opt/vaultwarden/backup.sh&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>set -euo pipefail
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>umask &lt;span style="color:#ae81ff">077&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>DATA_DIR&lt;span style="color:#f92672">=&lt;/span>/opt/vaultwarden/data
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>BACKUP_MOUNT&lt;span style="color:#f92672">=&lt;/span>/mnt/nas-backups
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>BACKUP_DIR&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>$BACKUP_MOUNT&lt;span style="color:#e6db74">/vaultwarden&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>TIMESTAMP&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>date +%Y%m%d-%H%M%S&lt;span style="color:#66d9ef">)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>DEST&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>$BACKUP_DIR&lt;span style="color:#e6db74">/vw-backup-&lt;/span>$TIMESTAMP&lt;span style="color:#e6db74">-&lt;/span>$$&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>trap &lt;span style="color:#e6db74">&amp;#39;printf &amp;#34;Backup failed. Check this run before treating it as complete.\n&amp;#34; &amp;gt;&amp;amp;2&amp;#39;&lt;/span> ERR
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>command -v sqlite3 &amp;gt; /dev/null
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>mountpoint -q &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$BACKUP_MOUNT&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>test -s &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$DATA_DIR&lt;span style="color:#e6db74">/db.sqlite3&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>mkdir -p &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$BACKUP_DIR&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>PENDING&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>mktemp -d &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$BACKUP_DIR&lt;span style="color:#e6db74">/.vw-pending.XXXXXX&amp;#34;&lt;/span>&lt;span style="color:#66d9ef">)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sqlite3 &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$DATA_DIR&lt;span style="color:#e6db74">/db.sqlite3&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;.backup &amp;#39;&lt;/span>$PENDING&lt;span style="color:#e6db74">/db.sqlite3&amp;#39;&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>test &lt;span style="color:#e6db74">&amp;#34;&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>sqlite3 &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$PENDING&lt;span style="color:#e6db74">/db.sqlite3&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#39;PRAGMA integrity_check;&amp;#39;&lt;/span>&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#f92672">=&lt;/span> ok
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># These paths are absent on installations that have never used the features.&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">for&lt;/span> item in attachments sends config.json; &lt;span style="color:#66d9ef">do&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#66d9ef">if&lt;/span> &lt;span style="color:#f92672">[&lt;/span> -e &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$DATA_DIR&lt;span style="color:#e6db74">/&lt;/span>$item&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#f92672">]&lt;/span>; &lt;span style="color:#66d9ef">then&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> cp -a -- &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$DATA_DIR&lt;span style="color:#e6db74">/&lt;/span>$item&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$PENDING&lt;span style="color:#e6db74">/&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#66d9ef">fi&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">done&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>shopt -s nullglob
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>keys&lt;span style="color:#f92672">=(&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>$DATA_DIR&lt;span style="color:#e6db74">&amp;#34;&lt;/span>/rsa_key*&lt;span style="color:#f92672">)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>test &lt;span style="color:#e6db74">&amp;#34;&lt;/span>&lt;span style="color:#e6db74">${#&lt;/span>keys[@]&lt;span style="color:#e6db74">}&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span> -gt &lt;span style="color:#ae81ff">0&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cp -a -- &lt;span style="color:#e6db74">&amp;#34;&lt;/span>&lt;span style="color:#e6db74">${&lt;/span>keys[@]&lt;span style="color:#e6db74">}&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$PENDING&lt;span style="color:#e6db74">/&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Only promote a complete copy. Never prune in a failure handler.&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>test ! -e &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$DEST&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>mv -T -- &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$PENDING&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$DEST&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>find &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$BACKUP_DIR&lt;span style="color:#e6db74">&amp;#34;&lt;/span> -mindepth &lt;span style="color:#ae81ff">1&lt;/span> -maxdepth &lt;span style="color:#ae81ff">1&lt;/span> -type d &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -name &lt;span style="color:#e6db74">&amp;#39;vw-backup-*&amp;#39;&lt;/span> -mtime +30 -exec rm -rf -- &lt;span style="color:#f92672">{}&lt;/span> +
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>printf &lt;span style="color:#e6db74">&amp;#39;Backup complete: %s\n&amp;#39;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$DEST&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>chmod &lt;span style="color:#ae81ff">700&lt;/span> /opt/vaultwarden/backup.sh
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Add one daily entry at 2am; do not duplicate an existing entry.&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>echo &lt;span style="color:#e6db74">&amp;#34;0 2 * * * root /opt/vaultwarden/backup.sh &amp;gt;&amp;gt; /var/log/vw-backup.log 2&amp;gt;&amp;amp;1&amp;#34;&lt;/span> &amp;gt;&amp;gt; /etc/crontab
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Alert on a nonzero job exit and on a missed run. Inspect partial attempts separately; they are excluded from this script&amp;rsquo;s retention names. Also back up &lt;code>/opt/vaultwarden/.env&lt;/code> securely, since settings supplied outside the data directory are not captured by this script. For a local destination swept by Proxmox Backup Server, adapt and verify the destination check deliberately before scheduling it. For a copy that leaves the house, the &lt;a href="https://techfuelhq.com/homelab/restic-vs-borg-vs-kopia-2026/">Restic vs Borg vs Kopia comparison&lt;/a> covers encrypted off-site tools.&lt;/p>
&lt;p>Test recovery in a separate instance with outbound mail disabled and a separate hostname. Keep production data untouched. With the test instance stopped, restore the database and related files into its empty data directory, retaining ownership appropriate to that instance. Do not pair the restored database with an old &lt;code>db.sqlite3-wal&lt;/code>: Vaultwarden&amp;rsquo;s documentation warns that a mismatched WAL can corrupt it. Start the test instance and check login, a known vault item and an attachment. The script&amp;rsquo;s integrity check verifies SQLite structure. Application recovery still needs this separate test.&lt;/p>
&lt;h2 id="step-7-tailscale-only-access-optional">Step 7: Tailscale-only access (optional)&lt;/h2>
&lt;p>If you don&amp;rsquo;t want Vaultwarden reachable from the public internet, serve it only on your tailnet. Skip Step 3&amp;rsquo;s port forward and let Caddy fetch a certificate from Tailscale, which also renews it for you.&lt;/p>
&lt;ol>
&lt;li>Install Tailscale in the container. An unprivileged LXC needs &lt;code>/dev/net/tun&lt;/code> passed through first; the &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale guide&lt;/a> covers it.&lt;/li>
&lt;li>In the Tailscale admin console&amp;rsquo;s DNS page, turn on MagicDNS if it&amp;rsquo;s off, then &lt;strong>Enable HTTPS&lt;/strong> under HTTPS Certificates. Tailscale warns that your machine names and tailnet name are published in the public Certificate Transparency log, so rename the machine first if its name gives anything away.&lt;/li>
&lt;li>Caddy runs as the &lt;code>caddy&lt;/code> user on Debian, so let it fetch certificates: add &lt;code>TS_PERMIT_CERT_UID=caddy&lt;/code> to &lt;code>/etc/default/tailscaled&lt;/code>, then &lt;code>systemctl restart tailscaled&lt;/code>.&lt;/li>
&lt;li>Use the tailnet name as the site address, with no &lt;code>tls&lt;/code> line:&lt;/li>
&lt;/ol>
&lt;pre tabindex="0">&lt;code>vaultwarden.your-tailnet.ts.net {
reverse_proxy 127.0.0.1:8080 {
header_up X-Real-IP {remote_host}
}
}
&lt;/code>&lt;/pre>&lt;ol start="5">
&lt;li>Set &lt;code>DOMAIN=https://vaultwarden.your-tailnet.ts.net&lt;/code>, restart Vaultwarden, and &lt;code>systemctl reload caddy&lt;/code>.&lt;/li>
&lt;/ol>
&lt;p>Caddy gets &lt;code>.ts.net&lt;/code> certificates from the local Tailscale daemon at handshake time and renews them without help. Don&amp;rsquo;t use &lt;code>tailscale cert&lt;/code> with certificate files pasted into the Caddyfile: those Let&amp;rsquo;s Encrypt certificates expire after 90 days, and Tailscale says you are responsible for renewing certificates created that way.&lt;/p>
&lt;p>Clients now sync whenever they&amp;rsquo;re on your tailnet, at home or away. Nothing is exposed to the internet.&lt;/p>
&lt;h2 id="harden-an-internet-facing-vault">Harden an internet-facing vault&lt;/h2>
&lt;p>With signups closed and two-step login on, finish these before you leave port 443 open:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Limit or remove the admin page.&lt;/strong> The Caddyfile in Step 3 already keeps &lt;code>/admin&lt;/code> to LAN addresses. Once setup is done you can turn the page off: remove &lt;code>ADMIN_TOKEN&lt;/code>, make sure &lt;code>DISABLE_ADMIN_TOKEN&lt;/code> isn&amp;rsquo;t set and no &lt;code>admin_token&lt;/code> is in &lt;code>config.json&lt;/code>, then restart.&lt;/li>
&lt;li>&lt;strong>Know the built-in rate limits.&lt;/strong> Vaultwarden 1.37.5 limits logins (&lt;code>LOGIN_RATELIMIT_SECONDS=60&lt;/code>, &lt;code>LOGIN_RATELIMIT_MAX_BURST=10&lt;/code>) and admin logins (&lt;code>ADMIN_RATELIMIT_SECONDS=300&lt;/code>, &lt;code>ADMIN_RATELIMIT_MAX_BURST=3&lt;/code>) per client IP by default. That&amp;rsquo;s why Caddy passes &lt;code>X-Real-IP&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Add fail2ban&lt;/strong> if you want repeat offenders banned at the firewall. Vaultwarden&amp;rsquo;s &lt;a href="https://github.com/dani-garcia/vaultwarden/wiki/Fail2Ban-Setup" rel="noopener">Fail2Ban guide&lt;/a> has the filter for its failed-login log line and a separate jail for the admin page.&lt;/li>
&lt;li>&lt;strong>Leave password hints off the login page.&lt;/strong> &lt;code>SHOW_PASSWORD_HINT&lt;/code> defaults to &lt;code>false&lt;/code>; Vaultwarden&amp;rsquo;s notes advise against turning it on for a public instance.&lt;/li>
&lt;li>&lt;strong>Set up SMTP&lt;/strong> (&lt;code>SMTP_HOST&lt;/code>, &lt;code>SMTP_FROM&lt;/code>, &lt;code>SMTP_PORT&lt;/code>, &lt;code>SMTP_SECURITY&lt;/code>, &lt;code>SMTP_USERNAME&lt;/code>, &lt;code>SMTP_PASSWORD&lt;/code>) so invitations and account emails reach people.&lt;/li>
&lt;li>&lt;strong>Keep it current.&lt;/strong> Security fixes arrive in point releases; 1.37.5 shipped two.&lt;/li>
&lt;/ul>
&lt;h2 id="updating-vaultwarden">Updating Vaultwarden&lt;/h2>
&lt;p>Back up first: Vaultwarden runs automatic database migrations on startup.&lt;/p>
&lt;p>For Option A, extract the new tag, then swap the binary and web vault:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>cd /root/vw-image
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>rm -rf output
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>./docker-image-extract vaultwarden/server:NEW-VERSION-alpine
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>systemctl stop vaultwarden
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Replaces the program files only; /opt/vaultwarden/data is not touched&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>install -m &lt;span style="color:#ae81ff">0755&lt;/span> output/vaultwarden /usr/local/bin/vaultwarden
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>rm -rf /opt/vaultwarden/web-vault
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cp -a output/web-vault /opt/vaultwarden/
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>systemctl start vaultwarden
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>For Option B, change the image tag in &lt;code>docker-compose.yml&lt;/code>, then:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>cd /opt/vaultwarden
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose pull
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose up -d
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Read each release&amp;rsquo;s notes first; 1.37.5&amp;rsquo;s notes say invalid configuration values now stop startup with an error.&lt;/p>
&lt;h2 id="when-bitwarden-says-sync-failed">When Bitwarden says sync failed&lt;/h2>
&lt;p>Work through these in order:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Server URL and &lt;code>DOMAIN&lt;/code> must match.&lt;/strong> The app&amp;rsquo;s Server URL, the browser address and &lt;code>DOMAIN&lt;/code> should be the same &lt;code>https://&lt;/code> address, character for character.&lt;/li>
&lt;li>&lt;strong>The certificate must be valid for that name.&lt;/strong> Open the URL in a browser on the same device. A certificate warning there means the app will fail too. Caddy&amp;rsquo;s certificate or Tailscale HTTPS fixes it; a self-signed certificate has to be trusted on every device.&lt;/li>
&lt;li>&lt;strong>Is the server current?&lt;/strong> New client releases can depend on server changes: Vaultwarden 1.37.5&amp;rsquo;s notes say it is required for web vault 2026.7.1 or newer to switch two-step login methods on or off.&lt;/li>
&lt;li>&lt;strong>Changes reach the browser but not the phone.&lt;/strong> Browser, desktop and extension clients get live updates over WebSockets, which Vaultwarden enables by default on its normal port; a browser&amp;rsquo;s network tab should show a &lt;code>101&lt;/code> response on &lt;code>/notifications/hub&lt;/code>. Mobile apps use Apple&amp;rsquo;s and Google&amp;rsquo;s push services instead, and Vaultwarden&amp;rsquo;s push (&lt;code>PUSH_ENABLED&lt;/code>) is off until you configure it with push credentials from Bitwarden; without it, the phone picks up changes on its next sync.&lt;/li>
&lt;li>&lt;strong>Still failing?&lt;/strong> Vaultwarden&amp;rsquo;s &lt;a href="https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting" rel="noopener">client troubleshooting page&lt;/a> suggests reproducing the problem against a free Bitwarden cloud account to tell a client bug from a server one, and Bitwarden&amp;rsquo;s mobile Flight Recorder logs what the app expected.&lt;/li>
&lt;/ol>
&lt;hr>
&lt;p>&lt;em>Running Vaultwarden and other self-hosted services on Proxmox? The &lt;a href="https://techfuelhq.com/homelab/lxc-vs-vm-proxmox-2026/">LXC vs VM guide&lt;/a> covers when to use each. &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale setup&lt;/a> handles the remote access piece. If you want &lt;code>vault.yourdomain.com&lt;/code> to resolve to the container&amp;rsquo;s LAN address at home, a local DNS server such as &lt;a href="https://techfuelhq.com/tutorials/adguard-home-local-dns-proxmox-2026/">AdGuard Home&lt;/a> can answer for it. The &lt;a href="https://techfuelhq.com/tools/power-cost-calculator/">Power &amp;amp; Cost Calculator&lt;/a> shows what the always-on host costs to run, and the &lt;a href="https://techfuelhq.com/homelab/ups-testing-reality-2026/">UPS testing guide&lt;/a> covers keeping it up through an outage.&lt;/em>&lt;/p></description></item><item><title>Proxmox WireGuard in an LXC: Self-Hosted VPN Setup Guide (2026)</title><link>https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/</link><pubDate>Wed, 27 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/</guid><atom:updated>2026-11-18T04:54:38Z</atom:updated><description>&lt;p>Tailscale is easier. If you want remote access with no server to run, the &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale tutorial&lt;/a> is the right read. WireGuard is for when you want no coordinator at all: your server, your key pairs, no third party knowing which clients are connected.&lt;/p>
&lt;p>This guide sets up a WireGuard server in a Proxmox LXC, adds phone and laptop clients by QR code, and covers the split vs full tunnel decision. It is written against Proxmox VE 9.2 with a Debian 13 container, checked against the WireGuard and Proxmox documentation on November 18, 2026.&lt;/p>
&lt;p>&lt;strong>Already run OPNsense?&lt;/strong> Then you may not need a container at all. OPNsense runs a WireGuard server itself, under VPN ‣ WireGuard, with a peer generator for clients; you allow the WireGuard port with a rule on the WAN interface instead of forwarding it to another host. Follow OPNsense&amp;rsquo;s &lt;a href="https://docs.opnsense.org/manual/how-tos/wireguard-client.html" rel="noopener">road warrior guide&lt;/a> instead of this one.&lt;/p>
&lt;h2 id="what-youll-have-at-the-end">What you&amp;rsquo;ll have at the end&lt;/h2>
&lt;ul>
&lt;li>WireGuard server running in a Proxmox LXC, listening on UDP port 51820&lt;/li>
&lt;li>Clients (phone, laptop) that can reach your homelab from anywhere&lt;/li>
&lt;li>Your choice of split tunnel (access homelab only) or IPv4 full tunnel (IPv4 traffic through home)&lt;/li>
&lt;li>Dynamic DNS hostname so it works when your home IP changes&lt;/li>
&lt;/ul>
&lt;h2 id="prerequisites">Prerequisites&lt;/h2>
&lt;ul>
&lt;li>A Proxmox VE 9 host on a home network with internet access&lt;/li>
&lt;li>A port forward on your router: UDP 51820 to the WireGuard container&amp;rsquo;s IP (Step 6)&lt;/li>
&lt;li>Optionally: a DuckDNS or Cloudflare DNS hostname for your home IP (Step 5)&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Check inbound IPv4 reachability first.&lt;/strong> Compare the router&amp;rsquo;s WAN IPv4 address with the public IPv4 shown by an external IP-check service. A WAN address in &lt;code>100.64.0.0/10&lt;/code> or a private range, or a mismatch, indicates upstream NAT that needs investigation. With your own upstream router, forward UDP 51820 at both layers. With ISP carrier-grade NAT, request a reachable public IPv4 or use an outbound mesh/relay design such as Tailscale. DDNS updates a name; it cannot open an ISP&amp;rsquo;s NAT. Test from cellular data or another external network, because a LAN test may depend on NAT loopback. The &lt;a href="https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/">dynamic DNS guide&lt;/a> covers the CGNAT check in more depth, and &lt;a href="https://techfuelhq.com/networking/port-forwarding-2026/">port forwarding&lt;/a> explains what has to line up for a forward to work.&lt;/p>
&lt;p>&lt;strong>Make sure the WireGuard module is loaded on the host.&lt;/strong> A container uses the host&amp;rsquo;s kernel and can&amp;rsquo;t load modules itself:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># On the Proxmox host (not inside an LXC)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>lsmod | grep wireguard
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># If nothing prints, load it now and at every boot:&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>modprobe wireguard
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>echo wireguard &amp;gt; /etc/modules-load.d/wireguard.conf
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>WireGuard&amp;rsquo;s &lt;a href="https://www.wireguard.com/quickstart/" rel="noopener">quick start&lt;/a> has a side-by-side demonstration of two peers if you want to see the bare commands before you start.&lt;/p>
&lt;h2 id="step-1-create-the-lxc-container">Step 1: Create the LXC container&lt;/h2>
&lt;p>In the Proxmox web UI, Create CT:&lt;/p>
&lt;pre tabindex="0">&lt;code>Hostname: wireguard
Template: Debian 13 (debian-13-standard)
Storage: 4GB disk
RAM: 256MB
vCPU: 1
Network: Static IP (e.g., 192.168.1.7/24)
Unprivileged container: unticked (privileged; see below)
&lt;/code>&lt;/pre>&lt;p>In a privileged LXC, root inside the container maps to root on the host. A container escape can therefore compromise the Proxmox host and its guests. Keep this container dedicated and patched, retain the default AppArmor restrictions, and expose only the VPN port. Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pct.html#_unprivileged_containers" rel="noopener">container security documentation&lt;/a> recommends unprivileged containers for better isolation. If the required network operations fail in an unprivileged container on your host, use a VM rather than removing host security controls. This guide does not validate a separate unprivileged configuration. The &lt;a href="https://techfuelhq.com/homelab/lxc-vs-vm-proxmox-2026/">LXC vs VM guide&lt;/a> covers that trade-off.&lt;/p>
&lt;p>Start the container, then inside it install the tools. The server config&amp;rsquo;s &lt;code>PostUp&lt;/code> lines call &lt;code>iptables&lt;/code>, so install it too:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>apt update &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span> apt install -y wireguard qrencode iptables
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-2-generate-the-server-key-pair">Step 2: Generate the server key pair&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Inside the WireGuard LXC&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cd /etc/wireguard
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>umask &lt;span style="color:#ae81ff">077&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>wg genkey | tee server_private.key | wg pubkey &amp;gt; server_public.key
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>umask 077&lt;/code> makes both files readable by root only. Keep &lt;code>server_private.key&lt;/code> and &lt;code>wg0.conf&lt;/code> that way. A stolen private key lets an attacker impersonate that peer in new connections; rotate the key and update its peers. WireGuard&amp;rsquo;s &lt;a href="https://www.wireguard.com/protocol/" rel="noopener">forward secrecy&lt;/a> means disclosure of a long-term private key alone does not decrypt previously recorded sessions. A compromised endpoint can still expose plaintext and active session secrets.&lt;/p>
&lt;h2 id="step-3-create-the-server-config">Step 3: Create the server config&lt;/h2>
&lt;p>This writes &lt;code>wg0.conf&lt;/code> and pulls the private key in directly, so it never has to appear on screen:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>umask &lt;span style="color:#ae81ff">077&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; /etc/wireguard/wg0.conf &lt;span style="color:#e6db74">&amp;lt;&amp;lt; EOF
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">[Interface]
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"># The WireGuard server&amp;#39;s IP on the VPN subnet
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Address = 10.10.0.1/24
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">ListenPort = 51820
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">PrivateKey = $(cat /etc/wireguard/server_private.key)
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"># Forward and NAT client traffic out of the container&amp;#39;s eth0
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -D FORWARD -o wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"># Clients are added below as [Peer] blocks
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The &lt;code>Address = 10.10.0.1/24&lt;/code> line defines the VPN subnet, and every client&amp;rsquo;s &lt;code>AllowedIPs&lt;/code> (your LAN such as &lt;code>192.168.1.0/24&lt;/code>, or &lt;code>0.0.0.0/0&lt;/code> for full-tunnel) is also a CIDR block. The &lt;a href="https://techfuelhq.com/tools/subnet-cidr-calculator/">subnet &amp;amp; CIDR calculator&lt;/a> makes it easy to get those masks and host ranges right. It also helps you pick a VPN subnet that won&amp;rsquo;t overlap the LAN you&amp;rsquo;re routing to.&lt;/p>
&lt;p>The &lt;code>10.10.0.0/24&lt;/code> subnet is the WireGuard VPN subnet. It is separate from your home LAN (&lt;code>192.168.1.0/24&lt;/code>). The server gets &lt;code>10.10.0.1&lt;/code>; clients get &lt;code>10.10.0.2&lt;/code>, &lt;code>10.10.0.3&lt;/code>, etc.&lt;/p>
&lt;p>&lt;strong>Enable IP forwarding&lt;/strong> in a file under &lt;code>/etc/sysctl.d&lt;/code>. Debian 13&amp;rsquo;s systemd-sysctl no longer reads &lt;code>/etc/sysctl.conf&lt;/code>, so a line there would be lost at the next reboot:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>echo &lt;span style="color:#e6db74">&amp;#39;net.ipv4.ip_forward = 1&amp;#39;&lt;/span> &amp;gt; /etc/sysctl.d/99-wireguard.conf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sysctl -p /etc/sysctl.d/99-wireguard.conf
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;strong>Start and enable WireGuard:&lt;/strong>&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>systemctl enable --now wg-quick@wg0
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Verify&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>wg show
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-4-add-clients">Step 4: Add clients&lt;/h2>
&lt;p>Each client (phone, laptop) needs its own key pair and config. Generating them on the server is convenient, but the client&amp;rsquo;s private key and its config file then exist on the server until you delete them, so work in a root-only directory rather than &lt;code>/tmp&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>install -d -m &lt;span style="color:#ae81ff">0700&lt;/span> /root/wg-clients
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cd /root/wg-clients
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>umask &lt;span style="color:#ae81ff">077&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>wg genkey | tee client1_private.key | wg pubkey &amp;gt; client1_public.key
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;strong>Write the client config:&lt;/strong>&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>cat &amp;gt; /root/wg-clients/client1.conf &lt;span style="color:#e6db74">&amp;lt;&amp;lt; EOF
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">[Interface]
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Address = 10.10.0.2/32
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">PrivateKey = $(cat /root/wg-clients/client1_private.key)
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"># Your AdGuard Home IP, or 1.1.1.1 if you don&amp;#39;t run one
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">DNS = 192.168.1.5
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">[Peer]
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"># The WireGuard server
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">PublicKey = $(cat /etc/wireguard/server_public.key)
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Endpoint = your-home.duckdns.org:51820
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"># Split tunnel: homelab only. For IPv4 full tunnel use 0.0.0.0/0 (see the IPv6 caveat below)
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">AllowedIPs = 192.168.1.0/24, 10.10.0.0/24
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">PersistentKeepalive = 25
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>PersistentKeepalive = 25&lt;/code> keeps the connection alive through NAT, the address translation your router does. Without it, an idle connection behind NAT may drop after a few minutes.&lt;/p>
&lt;p>&lt;strong>Add the client to the server&lt;/strong> and reload without dropping other clients:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>cat &amp;gt;&amp;gt; /etc/wireguard/wg0.conf &lt;span style="color:#e6db74">&amp;lt;&amp;lt; EOF
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">[Peer]
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"># Client 1 (phone)
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">PublicKey = $(cat /root/wg-clients/client1_public.key)
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">AllowedIPs = 10.10.0.2/32
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>wg syncconf wg0 &amp;lt;&lt;span style="color:#f92672">(&lt;/span>wg-quick strip wg0&lt;span style="color:#f92672">)&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;strong>Show the config as a QR code&lt;/strong> and scan it with the WireGuard app on iOS or Android. Print it to the terminal rather than saving an image, because the QR code contains the private key:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>qrencode -t ansiutf8 &amp;lt; /root/wg-clients/client1.conf
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>For a laptop, copy &lt;code>client1.conf&lt;/code> over a secure channel (SSH) and import it in the WireGuard app.&lt;/p>
&lt;p>Destructive: once the client has imported its config, delete the client&amp;rsquo;s private key and config from the server. They should only exist on the client:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>rm -f /root/wg-clients/client1_private.key /root/wg-clients/client1.conf
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Keep &lt;code>client1_public.key&lt;/code> if you like; it&amp;rsquo;s already in &lt;code>wg0.conf&lt;/code>. Repeat the step for each client with the next address (&lt;code>10.10.0.3/32&lt;/code>, and so on).&lt;/p>
&lt;h2 id="step-5-set-up-dynamic-dns">Step 5: Set up dynamic DNS&lt;/h2>
&lt;p>If your home IP changes (most residential ISPs assign dynamic IPs), use a free DDNS service:&lt;/p>
&lt;p>&lt;strong>DuckDNS (free, simple):&lt;/strong>&lt;/p>
&lt;ol>
&lt;li>Go to duckdns.org, create an account, create a domain: &lt;code>yourname.duckdns.org&lt;/code>&lt;/li>
&lt;li>Create an update script:&lt;/li>
&lt;/ol>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>install -d -o root -g root -m &lt;span style="color:#ae81ff">0700&lt;/span> /opt/duckdns
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>umask &lt;span style="color:#ae81ff">077&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Keep the token out of command arguments and in a root-only curl config.&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; /opt/duckdns/update.conf &lt;span style="color:#e6db74">&amp;lt;&amp;lt; &amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">url = &amp;#34;https://www.duckdns.org/update?domains=yourname&amp;amp;token=YOUR-TOKEN&amp;amp;ip=&amp;#34;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; /opt/duckdns/duck.sh &lt;span style="color:#e6db74">&amp;lt;&amp;lt; &amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">#!/bin/bash
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">set -euo pipefail
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">response=$(curl --fail --silent --show-error --max-time 30 \
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> --proto &amp;#39;=https&amp;#39; --config /opt/duckdns/update.conf)
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">if [[ &amp;#34;$response&amp;#34; != &amp;#34;OK&amp;#34; ]]; then
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> logger -p user.err -t duckdns &amp;#39;DuckDNS update failed; check the protected config&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> exit 1
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">fi
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>chown root:root /opt/duckdns/update.conf /opt/duckdns/duck.sh
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>chmod &lt;span style="color:#ae81ff">0600&lt;/span> /opt/duckdns/update.conf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>chmod &lt;span style="color:#ae81ff">0700&lt;/span> /opt/duckdns/duck.sh
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>/opt/duckdns/duck.sh &lt;span style="color:#75715e"># test once; curl verifies the HTTPS certificate&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Add to cron — update every 5 minutes&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>printf &lt;span style="color:#e6db74">&amp;#39;%s\n&amp;#39;&lt;/span> &lt;span style="color:#e6db74">&amp;#39;*/5 * * * * root /opt/duckdns/duck.sh&amp;#39;&lt;/span> &amp;gt; /etc/cron.d/duckdns
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>chown root:root /etc/cron.d/duckdns
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>chmod &lt;span style="color:#ae81ff">0644&lt;/span> /etc/cron.d/duckdns
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;ol start="3">
&lt;li>Use &lt;code>yourname.duckdns.org:51820&lt;/code> as the Endpoint in all your client configs.&lt;/li>
&lt;/ol>
&lt;p>Prefer a domain on Cloudflare? The &lt;a href="https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/">dynamic DNS guide&lt;/a> covers a scoped Cloudflare token instead.&lt;/p>
&lt;h2 id="step-6-set-up-the-port-forward">Step 6: Set up the port forward&lt;/h2>
&lt;p>On your router (OPNsense, pfSense, or consumer firmware):&lt;/p>
&lt;ul>
&lt;li>Forward &lt;strong>UDP port 51820&lt;/strong> to your WireGuard LXC IP (&lt;code>192.168.1.7&lt;/code>)&lt;/li>
&lt;/ul>
&lt;p>In OPNsense: Firewall → NAT → Port Forward → Add:&lt;/p>
&lt;ul>
&lt;li>Interface: WAN&lt;/li>
&lt;li>Protocol: UDP&lt;/li>
&lt;li>Destination port: 51820&lt;/li>
&lt;li>Redirect target: 192.168.1.7, port 51820&lt;/li>
&lt;/ul>
&lt;h2 id="step-7-verify-the-connection">Step 7: Verify the connection&lt;/h2>
&lt;p>On a client on cellular data, after importing the config:&lt;/p>
&lt;ol>
&lt;li>Enable the WireGuard tunnel&lt;/li>
&lt;li>Check that you can reach the server: &lt;code>ping 10.10.0.1&lt;/code>&lt;/li>
&lt;li>For split tunnel: verify you can reach homelab devices: &lt;code>ping 192.168.1.2&lt;/code> (Proxmox host)&lt;/li>
&lt;li>For IPv4 full tunnel: verify an IPv4 IP-check service shows your home IPv4, then separately check IPv6. An IPv6 result from the remote network is a bypass of this IPv4-only tunnel.&lt;/li>
&lt;/ol>
&lt;p>On the server, &lt;code>wg show&lt;/code> displays connected peers, their last handshake time, and transfer stats. A handshake within the last 3 minutes means the client is actively connected.&lt;/p>
&lt;h2 id="troubleshooting">Troubleshooting&lt;/h2>
&lt;p>&lt;strong>No handshake at all.&lt;/strong> &lt;code>wg show wg0 latest-handshakes&lt;/code> stays at zero for the peer. Work outward from the server:&lt;/p>
&lt;ol>
&lt;li>The server is listening: &lt;code>wg show wg0 listen-port&lt;/code> prints &lt;code>51820&lt;/code>.&lt;/li>
&lt;li>The keys are crossed correctly: the server&amp;rsquo;s &lt;code>[Peer]&lt;/code> holds the client&amp;rsquo;s public key, and the client&amp;rsquo;s &lt;code>[Peer]&lt;/code> holds the server&amp;rsquo;s.&lt;/li>
&lt;li>The endpoint name resolves to your current public IP: compare &lt;code>getent hosts yourname.duckdns.org&lt;/code> with your router&amp;rsquo;s WAN address.&lt;/li>
&lt;li>The forward reaches the container: UDP 51820 to &lt;code>192.168.1.7&lt;/code> on the router, and no CGNAT upstream (see Prerequisites). Test from outside your network.&lt;/li>
&lt;/ol>
&lt;p>&lt;strong>Handshake, but no LAN access.&lt;/strong> Check that &lt;code>sysctl net.ipv4.ip_forward&lt;/code> prints &lt;code>1&lt;/code> after a reboot, that the NAT rule is in place (&lt;code>iptables -t nat -S POSTROUTING&lt;/code> should list the &lt;code>MASQUERADE&lt;/code> rule), and that the client&amp;rsquo;s &lt;code>AllowedIPs&lt;/code> includes the LAN range you&amp;rsquo;re trying to reach.&lt;/p>
&lt;p>&lt;strong>Names don&amp;rsquo;t resolve over the tunnel.&lt;/strong> The client&amp;rsquo;s &lt;code>DNS =&lt;/code> server has to be reachable through the tunnel, so its address must fall inside the client&amp;rsquo;s &lt;code>AllowedIPs&lt;/code> (here &lt;code>192.168.1.5&lt;/code> is inside &lt;code>192.168.1.0/24&lt;/code>). On a Linux client, wg-quick sets DNS through &lt;code>resolvconf&lt;/code>, so that has to be installed.&lt;/p>
&lt;p>&lt;strong>It worked until the home IP changed.&lt;/strong> Check that the DuckDNS job is logging no errors, then bring the client tunnel down and up so it resolves the name again.&lt;/p>
&lt;h2 id="adding-adguard-home-as-vpn-dns">Adding AdGuard Home as VPN DNS&lt;/h2>
&lt;p>If you&amp;rsquo;re running &lt;a href="https://techfuelhq.com/tutorials/adguard-home-local-dns-proxmox-2026/">AdGuard Home for DNS filtering and local hostname resolution&lt;/a>, set it as the DNS in client configs:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-ini" data-lang="ini">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">[Interface]&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">DNS&lt;/span> &lt;span style="color:#f92672">=&lt;/span> &lt;span style="color:#e6db74">192.168.1.5 # AdGuard Home IP&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This lets VPN clients:&lt;/p>
&lt;ul>
&lt;li>Resolve &lt;code>pve.lan&lt;/code>, &lt;code>nas.lan&lt;/code>, and other local hostnames&lt;/li>
&lt;li>Get DNS-level ad blocking while connected to the VPN&lt;/li>
&lt;li>Use AdGuard&amp;rsquo;s split DNS without a separate Tailscale configuration&lt;/li>
&lt;/ul>
&lt;h2 id="split-tunnel-vs-full-tunnel">Split tunnel vs full tunnel&lt;/h2>
&lt;p>&lt;strong>Split tunnel&lt;/strong> (&lt;code>AllowedIPs = 192.168.1.0/24, 10.10.0.0/24&lt;/code>):&lt;/p>
&lt;ul>
&lt;li>Only homelab traffic goes through the VPN&lt;/li>
&lt;li>Internet traffic uses the local connection at the client&amp;rsquo;s location&lt;/li>
&lt;li>Faster for general browsing; no impact on video streaming&lt;/li>
&lt;li>Can&amp;rsquo;t browse the web through your home IP&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>IPv4 full tunnel&lt;/strong> (&lt;code>AllowedIPs = 0.0.0.0/0&lt;/code>):&lt;/p>
&lt;ul>
&lt;li>IPv4 traffic routes through the WireGuard server and your home network&lt;/li>
&lt;li>Use your home IPv4 as the exit node&lt;/li>
&lt;li>Useful on untrusted networks (airports, hotels) or for geo-unlocking&lt;/li>
&lt;li>Your home upload bandwidth becomes the internet speed limit for clients&lt;/li>
&lt;/ul>
&lt;p>The server config enables IPv4 forwarding and IPv4 NAT only. IPv6 is outside this recipe. If the client has IPv6 connectivity, it can bypass the tunnel unless you block it on that client. Verify both address families on each intended client; do not add &lt;code>::/0&lt;/code> without a tested IPv6 address, forwarding, routing and firewall setup.&lt;/p>
&lt;p>For a homelab VPN where the goal is remote access to services, split tunnel is usually the right choice. It&amp;rsquo;s faster and doesn&amp;rsquo;t load your home upload connection with all internet traffic.&lt;/p>
&lt;h2 id="wireguard-vs-tailscale-the-comparison">WireGuard vs Tailscale: the comparison&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">WireGuard (self-hosted)&lt;/th>
&lt;th scope="col">Tailscale&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Third-party dependency&lt;/td>
&lt;td data-label="WireGuard (self-hosted)">None&lt;/td>
&lt;td data-label="Tailscale">Tailscale coordinator&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Works behind double NAT&lt;/td>
&lt;td data-label="WireGuard (self-hosted)">Requires port forward on one side&lt;/td>
&lt;td data-label="Tailscale">Yes, fully automatic&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Users and devices&lt;/td>
&lt;td data-label="WireGuard (self-hosted)">As many peers as you configure&lt;/td>
&lt;td data-label="Tailscale">Free Personal plan: 6 users, unlimited user devices&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Key management&lt;/td>
&lt;td data-label="WireGuard (self-hosted)">Manual&lt;/td>
&lt;td data-label="Tailscale">Automatic&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">ACLs / per-client rules&lt;/td>
&lt;td data-label="WireGuard (self-hosted)">Manual iptables&lt;/td>
&lt;td data-label="Tailscale">Tailscale grants policy&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Mobile app&lt;/td>
&lt;td data-label="WireGuard (self-hosted)">Official WireGuard app&lt;/td>
&lt;td data-label="Tailscale">Tailscale app&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Local DNS integration&lt;/td>
&lt;td data-label="WireGuard (self-hosted)">Manual (set DNS per client)&lt;/td>
&lt;td data-label="Tailscale">MagicDNS, automatic&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Tailscale&amp;rsquo;s plan terms are from its pricing page on November 18, 2026. Tailscale wins on simplicity and NAT traversal. WireGuard wins on control, privacy (no coordinator logs), and flexibility (full tunnel, custom DNS, any subnet routing). For the full decision framework, including which one to pick behind carrier-grade NAT (CGNAT), see &lt;a href="https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/">Tailscale vs WireGuard: which one should you actually run?&lt;/a>. Want a mesh without running your own server? &lt;a href="https://techfuelhq.com/networking/netbird-vs-tailscale-2026/">NetBird vs Tailscale&lt;/a> and &lt;a href="https://techfuelhq.com/networking/zerotier-vs-tailscale-2026/">ZeroTier vs Tailscale&lt;/a> cover the alternatives.&lt;/p>
&lt;hr>
&lt;p>&lt;em>Running VLANs? See the &lt;a href="https://techfuelhq.com/tutorials/vlans-homelab-2026/">VLAN homelab guide&lt;/a> for segmenting your WireGuard clients from IoT and trusted LAN traffic. Building the firewall itself? The &lt;a href="https://techfuelhq.com/tutorials/opnsense-mini-pc-setup-2026/">OPNsense mini PC setup guide&lt;/a> covers the install, and OPNsense&amp;rsquo;s own road warrior guide covers its WireGuard server under VPN ‣ WireGuard.&lt;/em>&lt;/p></description></item><item><title>ZFS on Proxmox: Pool Setup, ARC Cap, and SSD Wear (2026)</title><link>https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/</link><pubDate>Tue, 26 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/</guid><atom:updated>2026-11-18T04:54:38Z</atom:updated><description>&lt;p>The &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">ZFS storage backend comparison&lt;/a> covers when ZFS beats LVM-thin, TrueNAS, or Unraid, and &lt;a href="https://techfuelhq.com/homelab/zfs-vs-btrfs-2026/">ZFS vs Btrfs&lt;/a> covers the filesystem choice. This guide covers the Proxmox commands: creating an &lt;code>ashift=12&lt;/code> pool safely, tuning the ARC cap, picking &lt;code>lz4&lt;/code> vs &lt;code>zstd&lt;/code>, replacing a failed disk, and avoiding consumer SSDs that wear out. It is written against Proxmox VE 9.2, which ships OpenZFS 2.4; the commands also apply to Proxmox VE 8.1 and later.&lt;/p>
&lt;p>Pick your starting point before running a single command:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Already have a running ZFS pool and only want to check or tune RAM / SSD wear?&lt;/strong> Jump straight to &lt;a href="#tune-zfs-arc-for-a-shared-host">Tune ZFS ARC&lt;/a> or &lt;a href="#why-consumer-qlc-and-dram-less-nvme-ssds-burn-out-on-proxmox-zfs">Why consumer SSDs wear out&lt;/a>. Do not touch &lt;code>zpool create&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Adding brand-new or wiped drives for a fresh pool?&lt;/strong> Start right below at &lt;a href="#identify-your-drives">Identify your drives&lt;/a> and verify serial numbers before previewing with &lt;code>zpool create -n&lt;/code>.&lt;/li>
&lt;li>&lt;strong>A disk just failed?&lt;/strong> Go to &lt;a href="#replace-a-failed-disk">Replace a failed disk&lt;/a>.&lt;/li>
&lt;/ul>
&lt;h2 id="identify-your-drives">Identify your drives&lt;/h2>
&lt;p>Pool creation erases every target disk. Never run &lt;code>zpool create&lt;/code> on a Proxmox boot drive, a mounted filesystem, or a drive holding unbacked-up data. Stop immediately if a serial looks ambiguous. Double-check every serial twice.&lt;/p>
&lt;p>Match every physical drive&amp;rsquo;s model, capacity, and serial number before touching ZFS:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS,MODEL,SERIAL,WWN
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ls -la /dev/disk/by-id/ | grep -v part
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Always pass &lt;code>/dev/disk/by-id/&lt;/code> paths (never &lt;code>/dev/sda&lt;/code> or &lt;code>/dev/nvme0n1&lt;/code>) to &lt;code>zpool create&lt;/code>. Kernel enumeration shifts whenever PCIe cards move. While ZFS reads on-disk labels once a pool exists, passing &lt;code>/dev/sdX&lt;/code> during creation or &lt;code>zpool replace&lt;/code> is still the classic way admins wipe the wrong disk by mistake.&lt;/p>
&lt;p>Example inventory you want in front of you:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>ata-ST16000NM001G-2_ZR507B3X -&amp;gt; 16TB Seagate IronWolf (empty)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ata-ST16000NM001G-2_ZR507B3Y -&amp;gt; 16TB Seagate IronWolf (empty)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>nvme-Micron_7450_MTFDKBA960TFR_2319X1 -&amp;gt; 960GB Enterprise PLP NVMe (empty)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>nvme-Micron_7450_MTFDKBA960TFR_2319X2 -&amp;gt; 960GB Enterprise PLP NVMe (empty)
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="why-consumer-qlc-and-dram-less-nvme-ssds-burn-out-on-proxmox-zfs">Why consumer QLC and DRAM-less NVMe SSDs burn out on Proxmox ZFS&lt;/h2>
&lt;p>Before you build an SSD pool on whatever 2 TB M.2 stick was on sale last week, look at what Proxmox asks for. I learned this lesson watching a budget consumer drive chew through wear percentage on an otherwise quiet test node.&lt;/p>
&lt;p>Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pve-installation.html" rel="noopener">system requirements&lt;/a> say it plainly for VM storage: SSDs with power-loss protection (PLP) are recommended, and consumer SSDs are discouraged. The host and ZFS both write synchronously. The &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pmxcfs.html" rel="noopener">Proxmox Cluster File System (&lt;code>pmxcfs&lt;/code>)&lt;/a> keeps &lt;code>/etc/pve&lt;/code> in a SQLite database on disk (&lt;code>/var/lib/pve-cluster/config.db&lt;/code>) with a copy in RAM, and ZFS commits synchronous writes through its intent log (ZIL), which lives in the pool unless you add a separate log device. Proxmox&amp;rsquo;s ZFS guide recommends PLP SSDs for log devices because they have much smaller commit latencies.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">SSD class&lt;/th>
&lt;th scope="col">Power-loss protection (PLP) &amp;amp; DRAM&lt;/th>
&lt;th scope="col">Under Proxmox + ZFS sync writes&lt;/th>
&lt;th scope="col">Homelab suitability&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="SSD class">&lt;strong>Consumer QLC / DRAM-less NVMe&lt;/strong>&lt;/td>
&lt;td data-label="Power-loss protection (PLP) &amp;amp; DRAM">No PLP; host-memory buffer or small SLC cache over dense QLC cells&lt;/td>
&lt;td data-label="Under Proxmox &amp;#43; ZFS sync writes">Higher sync-write commit latency than PLP drives; the class Proxmox discourages for VM storage&lt;/td>
&lt;td data-label="Homelab suitability">&lt;strong>Avoid for ZFS pools or &lt;code>rpool&lt;/code>&lt;/strong> (fine for read-heavy scratch/game libraries, bad for ZFS)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="SSD class">&lt;strong>Prosumer TLC NVMe with DRAM&lt;/strong>&lt;/td>
&lt;td data-label="Power-loss protection (PLP) &amp;amp; DRAM">DRAM cache, TLC NAND, no PLP&lt;/td>
&lt;td data-label="Under Proxmox &amp;#43; ZFS sync writes">Better than QLC for light VM duty, but sync commits stay slower than on PLP drives; monitor SMART &lt;code>Percentage Used&lt;/code> monthly&lt;/td>
&lt;td data-label="Homelab suitability">Acceptable for non-critical single-node labs when mirrored and monitored&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="SSD class">&lt;strong>Enterprise SSD / NVMe with PLP&lt;/strong> (e.g., Samsung PM893, Micron 7450; check the datasheet of any model you consider)&lt;/td>
&lt;td data-label="Power-loss protection (PLP) &amp;amp; DRAM">Power-loss protection for data in flight&lt;/td>
&lt;td data-label="Under Proxmox &amp;#43; ZFS sync writes">Much smaller commit latencies, per Proxmox&amp;rsquo;s ZFS guide&lt;/td>
&lt;td data-label="Homelab suitability">&lt;strong>Recommended by Proxmox&lt;/strong> for VM storage and log devices&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Newegg&amp;rsquo;s catalogue listed both the Micron 7450 and Samsung PM893 families on November 17, 2026, in M.2, U.3 and SATA forms. Check the exact model, capacity, form factor and seller on the listing before you buy. This page has no buy buttons because the right drive depends on the slot you have.&lt;/p>
&lt;p>Check your existing NVMe wear right now with &lt;code>smartctl -a /dev/nvme0n1 | grep -E &amp;quot;Percentage Used|Data Units Written&amp;quot;&lt;/code>. The &lt;a href="https://techfuelhq.com/articles/ssd-health-check-2026/">SSD health check guide&lt;/a> explains how to read those numbers, the &lt;a href="https://techfuelhq.com/tools/ssd-endurance-calculator/">SSD endurance calculator&lt;/a> turns your write rate into a TBW budget, and the &lt;a href="https://techfuelhq.com/articles/best-nvme-ssd-homelab-2026/">homelab NVMe guide by role&lt;/a> covers which drives suit boot, VM storage, cache and bulk.&lt;/p>
&lt;h2 id="create-a-pool-common-topologies-ashift12">Create a pool: common topologies (&lt;code>ashift=12&lt;/code>)&lt;/h2>
&lt;p>Never force a pool wipe. Replace every disk placeholder below with a verified &lt;code>/dev/disk/by-id/&lt;/code> whole-disk symlink, and keep &lt;code>-n&lt;/code> on the first run because &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/8/zpool-create.8.html" rel="noopener">OpenZFS &lt;code>zpool-create(8)&lt;/code>&lt;/a> treats &lt;code>-n&lt;/code> as a non-destructive dry-run preview that prints the exact vdev layout without writing a byte to disk. Only remove &lt;code>-n&lt;/code> once every serial matches your checklist, and never pass &lt;code>-f&lt;/code> to silence an active-filesystem warning.&lt;/p>
&lt;p>Destructive: each command below, run without &lt;code>-n&lt;/code>, erases every disk it names.&lt;/p>
&lt;h3 id="two-disks-mirror-recommended-starting-vm-pool">Two disks: mirror (recommended starting VM pool)&lt;/h3>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>zpool create -n -o ashift&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">12&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O compression&lt;span style="color:#f92672">=&lt;/span>lz4 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O atime&lt;span style="color:#f92672">=&lt;/span>off &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O xattr&lt;span style="color:#f92672">=&lt;/span>sa &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O dnodesize&lt;span style="color:#f92672">=&lt;/span>auto &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> datapool mirror &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/nvme-EnterpriseDisk1 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/nvme-EnterpriseDisk2
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="four-disks-striped-mirrors-raid10--best-vm-random-iops">Four disks: striped mirrors (RAID10 — best VM random IOPS)&lt;/h3>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>zpool create -n -o ashift&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">12&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O compression&lt;span style="color:#f92672">=&lt;/span>lz4 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O atime&lt;span style="color:#f92672">=&lt;/span>off &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O xattr&lt;span style="color:#f92672">=&lt;/span>sa &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O dnodesize&lt;span style="color:#f92672">=&lt;/span>auto &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> datapool &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> mirror /dev/disk/by-id/ata-Disk1 /dev/disk/by-id/ata-Disk2 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> mirror /dev/disk/by-id/ata-Disk3 /dev/disk/by-id/ata-Disk4
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="five-or-more-disks-raidz2-bulk-media--backups-not-iops-heavy-vms">Five or more disks: RAIDZ2 (bulk media &amp;amp; backups, not IOPS-heavy VMs)&lt;/h3>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>zpool create -n -o ashift&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">12&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O compression&lt;span style="color:#f92672">=&lt;/span>lz4 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O atime&lt;span style="color:#f92672">=&lt;/span>off &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O xattr&lt;span style="color:#f92672">=&lt;/span>sa &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O dnodesize&lt;span style="color:#f92672">=&lt;/span>auto &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> datapool raidz2 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/ata-Disk1 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/ata-Disk2 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/ata-Disk3 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/ata-Disk4 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/ata-Disk5
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>RAIDZ1 needs at least 3 disks and RAIDZ2 at least 4. With exactly four disks, Proxmox&amp;rsquo;s ZFS guide says two mirrors are usually the better choice: the usable space is the same and the performance is better. For a bulk pool on spinning disks, the &lt;a href="https://techfuelhq.com/homelab/best-nas-hard-drives-2026/">NAS hard drive guide&lt;/a> compares drives by use.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Pool / dataset flag&lt;/th>
&lt;th scope="col">Why it belongs on Proxmox&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Pool / dataset flag">&lt;code>-o ashift=12&lt;/code>&lt;/td>
&lt;td data-label="Why it belongs on Proxmox">Locks vdev physical sector alignment to &lt;code>2^12 = 4,096 bytes&lt;/code> (4K). &lt;strong>Immutable per vdev after creation.&lt;/strong> Proxmox&amp;rsquo;s guide says the ashift must match the disk&amp;rsquo;s sector size or be larger; check the drive&amp;rsquo;s datasheet.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Pool / dataset flag">&lt;code>-O compression=lz4&lt;/code>&lt;/td>
&lt;td data-label="Why it belongs on Proxmox">Fast stream compression with early-abort on incompressible blocks; essentially free CPU overhead on modern x86 while shrinking OS blocks, logs, and sparse VM extents.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Pool / dataset flag">&lt;code>-O atime=off&lt;/code>&lt;/td>
&lt;td data-label="Why it belongs on Proxmox">Stops ZFS from writing a new metadata block every time a file is read.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Pool / dataset flag">&lt;code>-O xattr=sa&lt;/code> + &lt;code>-O dnodesize=auto&lt;/code>&lt;/td>
&lt;td data-label="Why it belongs on Proxmox">Stores Linux extended attributes directly inside system-attribute bonus buffers rather than hidden directory trees — major IOPS win for LXC containers and Samba shares.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Verify the created pool with &lt;code>zpool status datapool&lt;/code> and &lt;code>zpool get ashift datapool&lt;/code>.&lt;/p>
&lt;p>&lt;strong>Or use the web interface.&lt;/strong> The node&amp;rsquo;s &lt;strong>Disks&lt;/strong> panel manages attached disks, and its ZFS pool creation runs the same API call, &lt;code>POST /nodes/{node}/disks/zfs&lt;/code>. That call takes the RAID level, the devices, &lt;code>ashift&lt;/code> (default 12), the compression algorithm, and an option to add the new pool as Proxmox storage in the same step, which saves you the next section.&lt;/p>
&lt;h2 id="add-the-pool-to-proxmox-storage">Add the pool to Proxmox storage&lt;/h2>
&lt;p>Register the pool with Proxmox (&lt;code>--sparse 1&lt;/code> enables thin provisioning so a 64 GiB virtual disk only consumes blocks actually written):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>pvesm add zfspool datapool-storage &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --pool datapool &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --content rootdir,images &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --sparse &lt;span style="color:#ae81ff">1&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Or add it in the GUI under &lt;strong>Datacenter → Storage → Add → ZFS&lt;/strong> and tick &lt;strong>Thin provision&lt;/strong>.&lt;/p>
&lt;h2 id="tune-zfs-arc-for-a-shared-host">Tune ZFS ARC for a shared host&lt;/h2>
&lt;p>ARC (Adaptive Replacement Cache) is ZFS&amp;rsquo;s RAM read cache. Outdated forum posts still repeat &amp;ldquo;ZFS eats 50% of your RAM by default on Proxmox&amp;rdquo; as an unconditional fact. What your host actually caps ARC at depends on &lt;strong>how and when Proxmox was installed&lt;/strong>. Check which case you&amp;rsquo;re in before editing anything:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Host installation history&lt;/th>
&lt;th scope="col">Default &lt;code>zfs_arc_max&lt;/code> ceiling&lt;/th>
&lt;th scope="col">Effective cap on a &lt;code>64 GiB&lt;/code> host&lt;/th>
&lt;th scope="col">Where it comes from&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Host installation history">&lt;strong>Fresh Proxmox VE 8.1+ or VE 9 ISO install&lt;/strong>&lt;/td>
&lt;td data-label="Default zfs_arc_max ceiling">&lt;strong>10% of physical RAM&lt;/strong>, capped at &lt;code>16 GiB&lt;/code>&lt;/td>
&lt;td data-label="Effective cap on a 64 GiB host">&lt;strong>&lt;code>6.4 GiB&lt;/code>&lt;/strong> (or &lt;code>16 GiB&lt;/code> on a &lt;code>256 GiB&lt;/code> host)&lt;/td>
&lt;td data-label="Where it comes from">Written to &lt;code>/etc/modprobe.d/zfs.conf&lt;/code> during installation (&lt;a href="https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_zfs_limit_memory_usage" rel="noopener">Proxmox ZFS docs&lt;/a>)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Host installation history">&lt;strong>No &lt;code>zfs_arc_max&lt;/code> set&lt;/strong> (installed before 8.1, or Proxmox installed over Debian, with no &lt;code>zfs.conf&lt;/code> line) on &lt;strong>OpenZFS 2.3 or later&lt;/strong>&lt;/td>
&lt;td data-label="Default zfs_arc_max ceiling">Larger of &lt;code>RAM - 1 GiB&lt;/code> and &lt;code>5/8 × RAM&lt;/code>&lt;/td>
&lt;td data-label="Effective cap on a 64 GiB host">&lt;strong>&lt;code>63 GiB&lt;/code>&lt;/strong> (&lt;code>64 - 1 GiB&lt;/code>)&lt;/td>
&lt;td data-label="Where it comes from">ZFS&amp;rsquo;s own default (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/4/zfs.4.html" rel="noopener">OpenZFS &lt;code>zfs(4)&lt;/code>&lt;/a>); Proxmox VE 9.2 ships ZFS 2.4&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Host installation history">&lt;strong>No &lt;code>zfs_arc_max&lt;/code> set&lt;/strong> on a ZFS release older than 2.3&lt;/td>
&lt;td data-label="Default zfs_arc_max ceiling">&lt;strong>50% of physical RAM&lt;/strong>&lt;/td>
&lt;td data-label="Effective cap on a 64 GiB host">&lt;strong>&lt;code>32 GiB&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Where it comes from">ZFS&amp;rsquo;s default before 2.3, per Proxmox&amp;rsquo;s docs&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>An in-place upgrade keeps whatever &lt;code>/etc/modprobe.d/zfs.conf&lt;/code> you had, so a host installed before 8.1 with no line there moves to the 2.3+ default when it reaches Proxmox VE 9.&lt;/p>
&lt;p>Never guess which row applies. Read the active kernel parameter directly:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># 0 means uncapped upstream default; non-zero is bytes&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat /sys/module/zfs/parameters/zfs_arc_max
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat /sys/module/zfs/parameters/zfs_arc_min
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>arc_summary | head -n &lt;span style="color:#ae81ff">35&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>grep -RnsE &lt;span style="color:#e6db74">&amp;#39;^[[:space:]]*options[[:space:]]+zfs[[:space:]]&amp;#39;&lt;/span> /etc/modprobe.d/
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Leave working caps alone. If a fresh install already capped your &lt;code>64 GiB&lt;/code> box at &lt;code>~6.4 GiB&lt;/code> and your guests have plenty of free memory, leave it unchanged. Proxmox&amp;rsquo;s rule of thumb for sizing ARC is at least 2 GiB plus 1 GiB per TiB of storage (10 GiB for an 8 TiB pool), and it warns that ARC size is crucial for I/O performance, so reduce it with caution. If an uncapped host (&lt;code>0&lt;/code>) or a legacy 50% host is leaving your VMs short of memory, set an explicit byte ceiling in &lt;code>/etc/modprobe.d/zfs.conf&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Example: 64 GiB host running 44 GiB of VMs + 6 GiB OS headroom -&amp;gt; 12 GiB ARC&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># 12 * 1024^3 = 12884901888 bytes&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">if&lt;/span> &lt;span style="color:#f92672">[&lt;/span> -f /etc/modprobe.d/zfs.conf &lt;span style="color:#f92672">]&lt;/span>; &lt;span style="color:#66d9ef">then&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> cp -a /etc/modprobe.d/zfs.conf &lt;span style="color:#e6db74">&amp;#34;/etc/modprobe.d/zfs.conf.bak.&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>date -u +%Y%m%dT%H%M%SZ&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">fi&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; /etc/modprobe.d/zfs.conf &lt;span style="color:#e6db74">&amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">options zfs zfs_arc_max=12884901888
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># MANDATORY when Proxmox boots from ZFS (rpool), because zfs.ko loads inside initramfs!&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>update-initramfs -u -k all
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Two rules from &lt;a href="https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_zfs_limit_memory_usage" rel="noopener">Proxmox&amp;rsquo;s ZFS administration guide&lt;/a> prevent silent ignores:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>&lt;code>zfs_arc_min&lt;/code> trap on high-RAM servers:&lt;/strong> &lt;code>zfs_arc_min&lt;/code> defaults to &lt;code>1/32&lt;/code> of system RAM (&lt;code>8 GiB&lt;/code> on a &lt;code>256 GiB&lt;/code> server, &lt;code>16 GiB&lt;/code> on &lt;code>512 GiB&lt;/code>). If you set &lt;code>zfs_arc_max&lt;/code> &lt;em>equal to or below&lt;/em> &lt;code>zfs_arc_min&lt;/code>, &lt;code>zfs_arc_max&lt;/code> is ignored. Set &lt;code>zfs_arc_min&lt;/code> to at most &lt;code>zfs_arc_max - 1&lt;/code> when capping large-memory hosts tightly.&lt;/li>
&lt;li>&lt;strong>Apply live now, persist via &lt;code>initramfs&lt;/code>:&lt;/strong> Writing bytes straight to &lt;code>/sys/module/zfs/parameters/zfs_arc_max&lt;/code> (&lt;code>echo 12884901888 &amp;gt; /sys/module/zfs/parameters/zfs_arc_max&lt;/code>) changes the cap for the current boot, while the &lt;code>zfs.conf&lt;/code> line plus &lt;code>update-initramfs -u -k all&lt;/code> (on a ZFS root) and a reboot make it permanent. Model your exact VM + ARC split interactively in the &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">Proxmox VM Capacity Planner&lt;/a>.&lt;/li>
&lt;/ol>
&lt;h2 id="create-datasets-with-lz4-vs-zstd-compression">Create datasets with &lt;code>lz4&lt;/code> vs &lt;code>zstd&lt;/code> compression&lt;/h2>
&lt;p>Never dump backups, ISOs, and media directly into the pool&amp;rsquo;s root dataset. Create child datasets so each workload gets the right &lt;code>compression&lt;/code> and &lt;code>recordsize&lt;/code>:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Dataset workload&lt;/th>
&lt;th scope="col">Recommended &lt;code>compression&lt;/code>&lt;/th>
&lt;th scope="col">Recommended &lt;code>recordsize&lt;/code>&lt;/th>
&lt;th scope="col">Why&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Dataset workload">VM zvols &amp;amp; LXC rootfs (&lt;code>datapool/vm-disks&lt;/code>)&lt;/td>
&lt;td data-label="Recommended compression">&lt;code>lz4&lt;/code>&lt;/td>
&lt;td data-label="Recommended recordsize">Pool default (&lt;code>8K&lt;/code>/&lt;code>16K&lt;/code> zvols, &lt;code>128K&lt;/code> LXC)&lt;/td>
&lt;td data-label="Why">Minimal latency and CPU cost; skips uncompressible blocks immediately&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dataset workload">Proxmox / PBS backups &amp;amp; logs (&lt;code>datapool/backups&lt;/code>)&lt;/td>
&lt;td data-label="Recommended compression">&lt;code>zstd-3&lt;/code>&lt;/td>
&lt;td data-label="Recommended recordsize">&lt;code>1M&lt;/code>&lt;/td>
&lt;td data-label="Why">Higher compression ratio on &lt;code>.vma&lt;/code>, &lt;code>.tar&lt;/code>, and structured text at modest CPU cost&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dataset workload">PostgreSQL / MariaDB bind mounts (&lt;code>datapool/db&lt;/code>)&lt;/td>
&lt;td data-label="Recommended compression">&lt;code>lz4&lt;/code> or &lt;code>zstd-3&lt;/code>&lt;/td>
&lt;td data-label="Recommended recordsize">&lt;code>16K&lt;/code> (match Postgres &lt;code>8K&lt;/code>/&lt;code>16K&lt;/code> page size)&lt;/td>
&lt;td data-label="Why">Prevents 128K read-modify-write amplification on random database commits&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dataset workload">Movies, TV, &amp;amp; Lossless/HEVC media (&lt;code>datapool/media&lt;/code>)&lt;/td>
&lt;td data-label="Recommended compression">&lt;code>lz4&lt;/code> or &lt;code>off&lt;/code>&lt;/td>
&lt;td data-label="Recommended recordsize">&lt;code>1M&lt;/code>&lt;/td>
&lt;td data-label="Why">&lt;code>1M&lt;/code> blocks cut metadata overhead on multi-gigabyte MKVs; &lt;code>lz4&lt;/code> early-aborts cleanly on H.265 while still compressing &lt;code>.srt&lt;/code> subtitles and &lt;code>.nfo&lt;/code> sidecars&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>zfs create -o compression&lt;span style="color:#f92672">=&lt;/span>lz4 datapool/vm-disks
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zfs create -o compression&lt;span style="color:#f92672">=&lt;/span>zstd-3 -o recordsize&lt;span style="color:#f92672">=&lt;/span>1M datapool/backups
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zfs create -o compression&lt;span style="color:#f92672">=&lt;/span>lz4 -o recordsize&lt;span style="color:#f92672">=&lt;/span>1M datapool/media
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zfs get compression,compressratio,recordsize,used,available datapool/vm-disks datapool/backups datapool/media
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Leave &lt;code>dedup&lt;/code> off on a homelab host; &lt;code>lz4&lt;/code> and &lt;code>zstd-3&lt;/code> give you real space savings without it.&lt;/p>
&lt;h2 id="confirm-automatic-scrubs">Confirm automatic scrubs&lt;/h2>
&lt;p>Scrubs catch silent bit rot early. Proxmox&amp;rsquo;s &lt;code>zfsutils-linux&lt;/code> package ships &lt;code>/etc/cron.d/zfsutils-linux&lt;/code>, which runs &lt;code>/usr/lib/zfs-linux/scrub&lt;/code> at &lt;code>00:24&lt;/code> on the second Sunday of every month across all healthy (&lt;code>ONLINE&lt;/code>) pools that aren&amp;rsquo;t already scrubbing, and a TRIM job at the same time on the first Sunday. Verify that cron file on your host rather than assuming a custom timer is active:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>cat /etc/cron.d/zfsutils-linux
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zpool status datapool | grep scan
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Avoid running duplicate scrub schedules. If you prefer per-pool systemd timers (&lt;code>systemctl enable --now zfs-scrub-monthly@datapool.timer&lt;/code>), comment out the &lt;code>/etc/cron.d/zfsutils-linux&lt;/code> entry so both schedules never collide on the same Sunday night, and remember you can pause a long HDD scrub during daytime work with &lt;code>zpool scrub -p datapool&lt;/code> before resuming it later with &lt;code>zpool scrub datapool&lt;/code>.&lt;/p>
&lt;h2 id="snapshot-policy-and-off-host-replication">Snapshot policy and off-host replication&lt;/h2>
&lt;p>Local snapshots are not backups. While &lt;code>zfs snapshot datapool/vm-disks@$(date +%Y-%m-%d)&lt;/code> gives instant rollback before risky updates and &lt;a href="https://github.com/jimsalterjrs/sanoid" rel="noopener">&lt;code>sanoid&lt;/code>&lt;/a> (&lt;code>apt install sanoid&lt;/code>) automates hourly and daily retention pruning cleanly, local snapshots still live on the exact same physical pool and exclude &lt;code>/etc/pve/qemu-server/&amp;lt;vmid&amp;gt;.conf&lt;/code>.&lt;/p>
&lt;p>For full Proxmox guest recovery (VM disks + config + deduplication), run &lt;a href="https://pbs.proxmox.com/docs/introduction.html" rel="noopener">Proxmox Backup Server&lt;/a> on separate hardware. For raw dataset replication (&lt;code>datapool/media&lt;/code> to a remote ZFS NAS), use &lt;code>zfs send&lt;/code> / &lt;code>zfs receive&lt;/code> with &lt;code>set -o pipefail&lt;/code> (or &lt;code>syncoid&lt;/code>):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>set -o pipefail
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>snapshot&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;replication-&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>date -u +%Y%m%dT%H%M%SZ&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zfs snapshot &lt;span style="color:#e6db74">&amp;#34;datapool/media@&lt;/span>$snapshot&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Initial full send to an empty remote target dataset&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zfs send &lt;span style="color:#e6db74">&amp;#34;datapool/media@&lt;/span>$snapshot&lt;span style="color:#e6db74">&amp;#34;&lt;/span> | &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> ssh root@192.168.1.20 &lt;span style="color:#e6db74">&amp;#34;zfs receive backuppool/media-from-proxmox&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Subsequent runs send incrementals (&lt;code>zfs send -i &amp;quot;datapool/media@$previous&amp;quot; &amp;quot;datapool/media@$snapshot&amp;quot;&lt;/code>) per &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-send.8.html" rel="noopener">OpenZFS &lt;code>zfs-send(8)&lt;/code>&lt;/a> and &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-receive.8.html" rel="noopener">&lt;code>zfs-receive(8)&lt;/code>&lt;/a>, and you should never slap &lt;code>zfs receive -F&lt;/code> onto an unattended replication script to silence a snapshot mismatch before inspecting both datasets with &lt;code>zfs list -t snapshot&lt;/code>. Force flags destroy diverging snapshots.&lt;/p>
&lt;h2 id="get-an-email-when-a-pool-degrades">Get an email when a pool degrades&lt;/h2>
&lt;p>ZFS&amp;rsquo;s event daemon, ZED, watches the kernel module&amp;rsquo;s events and can email you on pool errors. Proxmox installs it by default (the &lt;code>zfs-zed&lt;/code> package). Set the address in &lt;code>/etc/zfs/zed.d/zed.rc&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ZED_EMAIL_ADDR&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;root&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>root&lt;/code> is the default, and Proxmox forwards mail for root to the email address configured for the root user, so make sure that address is set and that mail from the host actually arrives.&lt;/p>
&lt;h2 id="replace-a-failed-disk">Replace a failed disk&lt;/h2>
&lt;p>Find the failed device and the new disk&amp;rsquo;s by-id path first:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>zpool status -v datapool
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ls -la /dev/disk/by-id/ | grep -v part
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Destructive: &lt;code>zpool replace&lt;/code> writes ZFS onto the new disk and erases whatever is on it. Double-check the new disk&amp;rsquo;s serial:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>zpool replace -f datapool &amp;lt;old-device&amp;gt; /dev/disk/by-id/&amp;lt;new-device&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Watch the resilver with &lt;code>zpool status -v&lt;/code> until it finishes.&lt;/p>
&lt;p>&lt;strong>A bootable disk (&lt;code>rpool&lt;/code>) needs more steps,&lt;/strong> because the new disk also needs the boot partitions. Proxmox&amp;rsquo;s guide copies the partition table from a healthy boot disk, gives the new disk fresh GUIDs, then replaces the ZFS partition. Destructive: the first command overwrites the new disk&amp;rsquo;s partition table:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sgdisk &amp;lt;healthy bootable device&amp;gt; -R &amp;lt;new device&amp;gt;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sgdisk -G &amp;lt;new device&amp;gt;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zpool replace -f rpool &amp;lt;old zfs partition&amp;gt; &amp;lt;new zfs partition&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Then make it bootable. Check which bootloader you have with &lt;code>proxmox-boot-tool status&lt;/code>. With proxmox-boot-tool:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>proxmox-boot-tool format &amp;lt;new disk&lt;span style="color:#e6db74">&amp;#39;s ESP&amp;gt;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">proxmox-boot-tool init &amp;lt;new disk&amp;#39;&lt;/span>s ESP&amp;gt; &lt;span style="color:#f92672">[&lt;/span>grub&lt;span style="color:#f92672">]&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Pass &lt;code>grub&lt;/code> to &lt;code>init&lt;/code> if &lt;code>proxmox-boot-tool status&lt;/code> says your disks use GRUB, especially with Secure Boot. The ESP is partition 2 on disks set up by the Proxmox installer since 5.4. Systems still on plain GRUB (installed with 6.3 or earlier and never migrated) use &lt;code>grub-install &amp;lt;new disk&amp;gt;&lt;/code> instead.&lt;/p>
&lt;h2 id="leave-zpool-upgrade-alone">Leave &lt;code>zpool upgrade&lt;/code> alone&lt;/h2>
&lt;p>After a Proxmox upgrade, &lt;code>zpool upgrade&lt;/code> would enable the newer ZFS release&amp;rsquo;s pool features, and Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">ZFS guide&lt;/a> says there&amp;rsquo;s no upside unless you need one. The downsides it lists: a system that still boots &lt;code>rpool&lt;/code> with GRUB becomes unbootable once a new feature is active, an older kernel with older ZFS modules can&amp;rsquo;t import the upgraded pool, and neither can an older Proxmox ISO you might boot to repair it. Never upgrade &lt;code>rpool&lt;/code> on a GRUB-booted system. The &lt;a href="https://techfuelhq.com/tutorials/proxmox-ve-8-to-9-upgrade-2026/">Proxmox 8 to 9 upgrade guide&lt;/a> covers the rest of that upgrade.&lt;/p>
&lt;h2 id="monitor-pool-health-and-avoid-common-mistakes">Monitor pool health and avoid common mistakes&lt;/h2>
&lt;p>Check &lt;code>zpool status -v&lt;/code>, &lt;code>zpool list&lt;/code> (keep pool occupancy under 80% so ZFS copy-on-write block allocation never fragments into slow metaslab searches), and &lt;code>smartctl&lt;/code> SSD wear every month. Full pools crawl. Four mistakes worth avoiding:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Passing &lt;code>/dev/sdX&lt;/code> instead of &lt;code>/dev/disk/by-id/&lt;/code>.&lt;/strong> Verify model + serial every single time.&lt;/li>
&lt;li>&lt;strong>Building ZFS on consumer QLC NVMe sticks.&lt;/strong> Proxmox discourages consumer SSDs for VM storage; buy used or new enterprise PLP SSDs instead.&lt;/li>
&lt;li>&lt;strong>Creating datasets per VM by hand.&lt;/strong> Register the parent dataset via &lt;code>pvesm&lt;/code> and let Proxmox manage &lt;code>vm-100-disk-0&lt;/code> zvols automatically.&lt;/li>
&lt;li>&lt;strong>Editing &lt;code>/etc/modprobe.d/zfs.conf&lt;/code> without &lt;code>update-initramfs -u -k all&lt;/code>.&lt;/strong> On a ZFS boot pool (&lt;code>rpool&lt;/code>), skipping initramfs regeneration means your next reboot silently reverts to the old ARC ceiling.&lt;/li>
&lt;/ul>
&lt;hr>
&lt;p>&lt;em>For topology math (mirrors vs RAIDZ, when a PLP SLOG or special vdev actually helps), read the &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">ZFS storage backend comparison&lt;/a>. To model guest RAM alongside your exact ARC cap, open the &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">Proxmox VM Capacity Planner&lt;/a>.&lt;/em>&lt;/p></description></item><item><title>Tailscale Remote Access for the Homelab (2026 Setup Guide)</title><link>https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/</link><pubDate>Mon, 25 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/</guid><atom:updated>2026-11-18T04:54:38Z</atom:updated><description>&lt;p>Port forwarding, dynamic DNS and a hand-built VPN server are the traditional way into a homelab, and each is one more thing to break. Tailscale replaces that with one node on your LAN that advertises the whole network to your tailnet, handles NAT traversal itself, and gives you a web console to manage devices.&lt;/p>
&lt;p>This guide sets that node up on a Proxmox VE host (or a dedicated LXC), checked against Tailscale&amp;rsquo;s documentation and Proxmox VE 9.2 on November 18, 2026.&lt;/p>
&lt;h2 id="what-tailscale-is-and-isnt">What Tailscale is (and isn&amp;rsquo;t)&lt;/h2>
&lt;p>Tailscale is a mesh VPN built on WireGuard. Each device you install it on gets a stable IP address in the &lt;code>100.x.x.x&lt;/code> range (the Tailscale IP space, also called a tailnet). Devices try to reach one another directly. If the networks prevent that, they can use an encrypted relay connection.&lt;/p>
&lt;p>What it is not: a traditional VPN that routes all your traffic through a central server. By default, only traffic to other tailnet devices goes through Tailscale. Your normal internet traffic goes direct. You can enable exit nodes if you want full traffic routing, but that&amp;rsquo;s optional.&lt;/p>
&lt;p>This guide keeps services private to your tailnet. If you want someone without a Tailscale client to reach a service, that&amp;rsquo;s a separate choice: &lt;a href="https://tailscale.com/docs/features/tailscale-funnel" rel="noopener">Tailscale Funnel&lt;/a> can make it public. &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">Tailscale vs Cloudflare Tunnel&lt;/a> compares the paths. For a family TV, start with the actual client: Tailscale has apps for Android TV, Fire TV and Apple TV, but not Roku or webOS. The &lt;a href="https://techfuelhq.com/tutorials/jellyfin-remote-access-2026/">Jellyfin remote access guide&lt;/a> works through those cases.&lt;/p>
&lt;p>The plan:&lt;/p>
&lt;ol>
&lt;li>Install Tailscale on the Proxmox host (or a dedicated LXC).&lt;/li>
&lt;li>Advertise your home LAN as a subnet route and approve it.&lt;/li>
&lt;li>Install Tailscale on your laptop and phone.&lt;/li>
&lt;li>Reach every device on the home network from anywhere.&lt;/li>
&lt;/ol>
&lt;p>Subnet routing advertises your LAN&amp;rsquo;s exact CIDR (for example &lt;code>192.168.1.0/24&lt;/code>). If you&amp;rsquo;re not sure of the network address or range to advertise, the &lt;a href="https://techfuelhq.com/tools/subnet-cidr-calculator/">subnet &amp;amp; CIDR calculator&lt;/a> confirms it from any IP and prefix so you don&amp;rsquo;t accidentally route the wrong block.&lt;/p>
&lt;h2 id="step-1-install-tailscale-on-your-proxmox-host">Step 1: Install Tailscale on your Proxmox host&lt;/h2>
&lt;p>SSH into your Proxmox host and run Tailscale&amp;rsquo;s install script:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>curl -fsSL https://tailscale.com/install.sh | sh
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Then connect the node:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>tailscale up
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>You&amp;rsquo;ll get a URL. Open it in a browser, log in with your Tailscale account (Google, GitHub, or Microsoft SSO, or email), and authorize the device. Then run:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>tailscale status
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>You should see your Proxmox host listed with a &lt;code>100.x.x.x&lt;/code> IP. The host is now in your tailnet and reachable from any other Tailscale device. Only the host, though: not your NAS, your router&amp;rsquo;s admin page or anything else on the LAN. That&amp;rsquo;s the next step.&lt;/p>
&lt;h2 id="step-2-advertise-your-lan-as-a-subnet-route">Step 2: Advertise your LAN as a subnet route&lt;/h2>
&lt;p>A subnet router forwards tailnet traffic to devices that don&amp;rsquo;t run Tailscale. Linux needs IP forwarding for that. Put the setting in &lt;code>/etc/sysctl.d&lt;/code>, the location Tailscale&amp;rsquo;s subnet router guide uses when that directory exists:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>echo &lt;span style="color:#e6db74">&amp;#39;net.ipv4.ip_forward = 1&amp;#39;&lt;/span> | tee -a /etc/sysctl.d/99-tailscale.conf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>echo &lt;span style="color:#e6db74">&amp;#39;net.ipv6.conf.all.forwarding = 1&amp;#39;&lt;/span> | tee -a /etc/sysctl.d/99-tailscale.conf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sysctl -p /etc/sysctl.d/99-tailscale.conf
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Don&amp;rsquo;t use &lt;code>/etc/sysctl.conf&lt;/code> on Proxmox VE 9: its systemd-sysctl no longer reads that file (see Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/wiki/Upgrade_from_8_to_9" rel="noopener">upgrade guide&lt;/a> and the Debian 13 &lt;a href="https://www.debian.org/releases/trixie/release-notes/issues.en.html" rel="noopener">release notes&lt;/a>), so forwarding would switch off at the next reboot and remote access would quietly stop. If you set it there on Proxmox 8, move it before you &lt;a href="https://techfuelhq.com/tutorials/proxmox-ve-8-to-9-upgrade-2026/">upgrade to 9&lt;/a>. Tailscale also asks that your firewall deny forwarding by default when forwarding is on.&lt;/p>
&lt;p>Find your LAN range if you&amp;rsquo;re unsure:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ip route show | grep -v tailscale
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Look for a line like &lt;code>192.168.1.0/24 dev vmbr0&lt;/code>. Then advertise it, replacing the example range with yours:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>tailscale set --advertise-routes&lt;span style="color:#f92672">=&lt;/span>192.168.1.0/24
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;strong>Approve the route.&lt;/strong> An advertised route does nothing until an admin approves it (unless you use &lt;code>autoApprovers&lt;/code> in the policy file):&lt;/p>
&lt;ol>
&lt;li>Open the &lt;a href="https://login.tailscale.com/admin/machines" rel="noopener">Machines page&lt;/a> of the admin console.&lt;/li>
&lt;li>Find the host by its &lt;strong>Subnets&lt;/strong> badge, select it, and go to its &lt;strong>Subnets&lt;/strong> section.&lt;/li>
&lt;li>Select &lt;code>192.168.1.0/24&lt;/code> and choose &lt;strong>Save&lt;/strong>.&lt;/li>
&lt;/ol>
&lt;p>&lt;strong>Disable key expiry on this node.&lt;/strong> Tailscale keys expire after 180 days by default, and when this node&amp;rsquo;s key expires every connection through it stops, which is exactly when you&amp;rsquo;re away from home. On the Machines page, open the menu at the far right of the host&amp;rsquo;s row and choose &lt;strong>Disable Key Expiry&lt;/strong>. Tailscale lists subnet routers as a case for doing this. A node you tag gets key expiry disabled by default.&lt;/p>
&lt;p>&lt;strong>On client devices.&lt;/strong> Android, iOS, macOS, tvOS and Windows pick up approved subnet routes automatically. Linux clients only see Tailscale IPs until you run:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>tailscale set --accept-routes
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Test from your phone on cellular data, not Wi-Fi, by opening or pinging a LAN address such as your router:&lt;/p>
&lt;pre tabindex="0">&lt;code>ping 192.168.1.1
&lt;/code>&lt;/pre>&lt;p>If it answers, subnet routing works. On a laptop, &lt;code>tailscale status&lt;/code> shows whether each peer connection is &lt;code>direct&lt;/code>, &lt;code>relay&lt;/code> or &lt;code>peer-relay&lt;/code>.&lt;/p>
&lt;p>Tailscale&amp;rsquo;s &lt;a href="https://tailscale.com/docs/reference/best-practices/performance" rel="noopener">performance guide&lt;/a> also recommends turning on UDP GRO forwarding on the internet-facing NIC of a Linux subnet router (Tailscale 1.54 or later on kernel 6.2 or later). Its &lt;code>ethtool&lt;/code> commands don&amp;rsquo;t persist across a reboot on their own, and the guide&amp;rsquo;s persistence steps cover networkd-dispatcher and NetworkManager, so treat it as an optional speed tweak.&lt;/p>
&lt;h2 id="step-3-use-magicdns-and-your-local-dns">Step 3: Use MagicDNS and your local DNS&lt;/h2>
&lt;p>MagicDNS lets you reach devices by name instead of IP. Tailnets created on or after October 20, 2022 have it on by default; on an older tailnet, turn it on in the &lt;a href="https://login.tailscale.com/admin/dns" rel="noopener">DNS page&lt;/a> of the admin console.&lt;/p>
&lt;p>Each device&amp;rsquo;s machine name then works on its own (&lt;code>ssh root@proxmox&lt;/code>, &lt;code>https://proxmox:8006&lt;/code>) and as a full name like &lt;code>proxmox.your-tailnet.ts.net&lt;/code>. Rename the machine in the admin console if you want a different name.&lt;/p>
&lt;p>&lt;strong>Add your local DNS server.&lt;/strong> If you run Pi-hole or &lt;a href="https://techfuelhq.com/tutorials/adguard-home-local-dns-proxmox-2026/">AdGuard Home&lt;/a> on the LAN, push it to your tailnet clients:&lt;/p>
&lt;ol>
&lt;li>Admin console, DNS page, &lt;strong>Add nameserver&lt;/strong>.&lt;/li>
&lt;li>Enter the server&amp;rsquo;s Tailscale IP, or its LAN IP if it sits behind your subnet router.&lt;/li>
&lt;li>Turn on &lt;strong>Override DNS servers&lt;/strong> if you want clients to use it even when they&amp;rsquo;re away from home. Without it, devices keep their local DNS settings.&lt;/li>
&lt;/ol>
&lt;p>To send only your local domain to that server, add it as a restricted nameserver for that domain instead (split DNS).&lt;/p>
&lt;h2 id="step-4-run-tailscale-in-an-lxc-instead-optional">Step 4: Run Tailscale in an LXC instead (optional)&lt;/h2>
&lt;p>To keep the Proxmox host itself clean, run the subnet router in a dedicated container.&lt;/p>
&lt;ol>
&lt;li>Create a Debian 13 LXC.&lt;/li>
&lt;li>Give it the TUN device: open the container&amp;rsquo;s &lt;strong>Resources&lt;/strong> tab, choose &lt;strong>Add&lt;/strong>, then &lt;strong>Device Passthrough&lt;/strong>, enter &lt;code>/dev/net/tun&lt;/code>, and add it. From the host shell, Tailscale&amp;rsquo;s guide gives &lt;code>pct set &amp;lt;CTID&amp;gt; --dev0 /dev/net/tun&lt;/code> and &lt;code>pct set &amp;lt;CTID&amp;gt; --features keyctl=1,nesting=1&lt;/code> as the alternative. Unprivileged containers usually don&amp;rsquo;t provide &lt;code>/dev/net/tun&lt;/code> on their own.&lt;/li>
&lt;li>If the container is running, shut it down and start it again.&lt;/li>
&lt;/ol>
&lt;p>Then inside the container:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>apt update &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span> apt install -y curl
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>curl -fsSL https://tailscale.com/install.sh | sh
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Enable forwarding inside the container the same way:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>echo &lt;span style="color:#e6db74">&amp;#39;net.ipv4.ip_forward = 1&amp;#39;&lt;/span> | tee -a /etc/sysctl.d/99-tailscale.conf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>echo &lt;span style="color:#e6db74">&amp;#39;net.ipv6.conf.all.forwarding = 1&amp;#39;&lt;/span> | tee -a /etc/sysctl.d/99-tailscale.conf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sysctl -p /etc/sysctl.d/99-tailscale.conf
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Then connect and advertise:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>tailscale up
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>tailscale set --advertise-routes&lt;span style="color:#f92672">=&lt;/span>192.168.1.0/24
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Approve the route and disable key expiry for this node as in Step 2. The container is now the gateway for the whole LAN.&lt;/p>
&lt;h2 id="step-5-ssh-key-setup-for-password-free-access">Step 5: SSH key setup for password-free access&lt;/h2>
&lt;p>Once Tailscale is running, you can SSH into your Proxmox host via its Tailscale IP. To make this keyless:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># On your laptop — generate a key if you don&amp;#39;t have one&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ssh-keygen -t ed25519 -C &lt;span style="color:#e6db74">&amp;#34;homelab-access&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Copy to Proxmox host&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ssh-copy-id root@100.x.x.x &lt;span style="color:#75715e"># use Proxmox&amp;#39;s Tailscale IP&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Add an entry to &lt;code>~/.ssh/config&lt;/code> on your laptop:&lt;/p>
&lt;pre tabindex="0">&lt;code>Host proxmox
HostName 100.x.x.x
User root
IdentityFile ~/.ssh/id_ed25519
&lt;/code>&lt;/pre>&lt;p>Now &lt;code>ssh proxmox&lt;/code> from anywhere connects through Tailscale. Works on cellular, works through hotel WiFi, works through CGNAT — no port forwarding, no exposed SSH port on the internet.&lt;/p>
&lt;h2 id="limiting-access-with-grants">Limiting access with grants&lt;/h2>
&lt;p>By default, every device in your tailnet can reach every other device. For a personal homelab this is fine. If you share the tailnet, say a family member who should reach Jellyfin but not the Proxmox UI, write a policy in the admin console under &lt;strong>Access controls&lt;/strong>. Tailscale now recommends grants over the older &lt;code>acls&lt;/code> section. Access is denied unless a grant allows it, and a destination is a device, tag, IP, CIDR or a named host, never a placeholder like &lt;code>100.x.x.x&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-json" data-lang="json">&lt;span style="display:flex;">&lt;span>{
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;groups&amp;#34;&lt;/span>: {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;group:family&amp;#34;&lt;/span>: [&lt;span style="color:#e6db74">&amp;#34;partner@example.com&amp;#34;&lt;/span>]
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> },
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;hosts&amp;#34;&lt;/span>: {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;jellyfin&amp;#34;&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;192.168.1.50&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> },
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;grants&amp;#34;&lt;/span>: [
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;src&amp;#34;&lt;/span>: [&lt;span style="color:#e6db74">&amp;#34;autogroup:owner&amp;#34;&lt;/span>],
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;dst&amp;#34;&lt;/span>: [&lt;span style="color:#e6db74">&amp;#34;*&amp;#34;&lt;/span>],
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;ip&amp;#34;&lt;/span>: [&lt;span style="color:#e6db74">&amp;#34;*&amp;#34;&lt;/span>]
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> },
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;src&amp;#34;&lt;/span>: [&lt;span style="color:#e6db74">&amp;#34;group:family&amp;#34;&lt;/span>],
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;dst&amp;#34;&lt;/span>: [&lt;span style="color:#e6db74">&amp;#34;jellyfin&amp;#34;&lt;/span>],
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;ip&amp;#34;&lt;/span>: [&lt;span style="color:#e6db74">&amp;#34;tcp:8096&amp;#34;&lt;/span>]
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> }
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> ]
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>}
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The owner keeps access to everything. The family group reaches only TCP 8096, Jellyfin&amp;rsquo;s default HTTP port, on the LAN address behind your subnet router. Replace the email and IP with yours. A grant permits traffic; it doesn&amp;rsquo;t create routes, so the subnet route from Step 2 still has to be approved. The &lt;a href="https://tailscale.com/docs/reference/syntax/grants" rel="noopener">grants reference&lt;/a> lists every selector.&lt;/p>
&lt;h2 id="troubleshooting">Troubleshooting&lt;/h2>
&lt;p>&lt;strong>Connection goes through a relay (DERP).&lt;/strong> &lt;code>tailscale status&lt;/code> shows &lt;code>relay&lt;/code> and a relay city code instead of &lt;code>direct&lt;/code>. Direct tunnels use UDP, from source port 41641 by default, so a firewall that blocks outbound UDP forces relaying. Tailscale&amp;rsquo;s &lt;a href="https://tailscale.com/docs/reference/device-connectivity" rel="noopener">device connectivity guide&lt;/a> walks through the causes.&lt;/p>
&lt;p>&lt;strong>Subnet routes not working.&lt;/strong> Check that:&lt;/p>
&lt;ol>
&lt;li>The route was advertised with the right CIDR (&lt;code>tailscale set --advertise-routes=...&lt;/code>).&lt;/li>
&lt;li>It is approved on the Machines page.&lt;/li>
&lt;li>Linux clients ran &lt;code>tailscale set --accept-routes&lt;/code>.&lt;/li>
&lt;li>Forwarding is still on after a reboot: &lt;code>sysctl net.ipv4.ip_forward&lt;/code> should print &lt;code>1&lt;/code>.&lt;/li>
&lt;/ol>
&lt;p>&lt;strong>Can&amp;rsquo;t reach one device on the subnet.&lt;/strong> By default a subnet router uses source NAT, so LAN devices see the traffic coming from the router&amp;rsquo;s own LAN address and reply to it. If that device has its own firewall, allow that address. If you turned SNAT off with &lt;code>--snat-subnet-routes=false&lt;/code>, LAN devices need a return route for Tailscale addresses through the subnet router.&lt;/p>
&lt;p>&lt;strong>Remote access stopped after months.&lt;/strong> The node&amp;rsquo;s key probably expired. On the Machines page choose &lt;strong>Temporarily extend key&lt;/strong> (30 minutes), then disable key expiry, or reauthenticate with &lt;code>tailscale up --force-reauth&lt;/code> from a console that doesn&amp;rsquo;t depend on Tailscale.&lt;/p>
&lt;p>&lt;strong>Tailscale down after a host upgrade.&lt;/strong> Check &lt;code>systemctl status tailscaled&lt;/code> and &lt;code>journalctl -u tailscaled&lt;/code>, and &lt;code>systemctl enable --now tailscaled&lt;/code> if the service isn&amp;rsquo;t enabled.&lt;/p>
&lt;h2 id="what-about-headscale">What about Headscale?&lt;/h2>
&lt;p>&lt;a href="https://headscale.net/" rel="noopener">Headscale&lt;/a> lets you run the coordination server yourself. Its &lt;a href="https://github.com/juanfont/headscale/blob/v0.29.7/docs/about/features.md" rel="noopener">v0.29.7 feature list&lt;/a> marks MagicDNS, subnet routers, exit nodes and Taildrop as supported; &lt;strong>Funnel and Serve are not&lt;/strong>. If a public URL depends on Funnel, keep that service where it is until you&amp;rsquo;ve tested an alternative from outside the tailnet. Self-hosting the control server also means keeping another way in if the host running it loses power. In &lt;a href="https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/">my Headscale guide&lt;/a>, I explain how to weigh a working private route against the cost of maintaining your own control server and what I have not tested.&lt;/p>
&lt;hr>
&lt;p>&lt;em>Accessing your homelab remotely is step one. Protecting it with a &lt;a href="https://techfuelhq.com/tools/ups-runtime-calculator/">UPS&lt;/a> is step two — Tailscale can&amp;rsquo;t help you if the power cuts out while you&amp;rsquo;re away. The &lt;a href="https://techfuelhq.com/tools/power-cost-calculator/">Power &amp;amp; Cost Calculator&lt;/a> shows what running an always-on Tailscale gateway node costs per year. Prefer to run your own server with no coordinator at all? The &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">WireGuard self-hosted VPN guide&lt;/a> sets one up in a Proxmox LXC. Want the mesh without Tailscale&amp;rsquo;s control plane? &lt;a href="https://techfuelhq.com/networking/netbird-vs-tailscale-2026/">NetBird vs Tailscale&lt;/a> weighs the open, self-hostable option, and &lt;a href="https://techfuelhq.com/networking/zerotier-vs-tailscale-2026/">ZeroTier vs Tailscale&lt;/a> covers the other common alternative.&lt;/em>&lt;/p></description></item><item><title>UniFi vs an OPNsense Build: The IDS/IPS Ceiling</title><link>https://techfuelhq.com/networking/unifi-vs-opnsense-build-2026/</link><pubDate>Mon, 07 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/unifi-vs-opnsense-build-2026/</guid><atom:updated>2026-11-18T04:54:19Z</atom:updated><description>&lt;p>Turning on threat management costs you throughput. Ubiquiti publishes how much. You just have to look elsewhere.&lt;/p>
&lt;p>I have run both a UniFi gateway appliance and an x86 OPNsense box I built myself. Before comparing gateway spec sheets or pricing out mini PCs, draw one architectural line across your homelab diagram: what stays inside your Layer 2 switch ASIC versus what hits your Layer 3 firewall CPU. Getting that boundary wrong makes people overspend on 10GbE routers they never saturate, or choke local NAS backups through a 2.3 Gbps firewall inspection queue.&lt;/p>
&lt;h2 id="draw-the-l2-switch-vs-l3-firewall-traffic-boundary-first">Draw the L2 switch vs L3 firewall traffic boundary first&lt;/h2>
&lt;p>Switches move local packets. Routers cross subnets. Ethernet frames between two machines in the same subnet and VLAN are forwarded in silicon by your switch chip at full wire speed, whereas packets only climb up to your UniFi gateway or OPNsense CPU when they cross a Layer 3 subnet boundary, hit NAT/PPPoE toward your ISP, or enter a VPN tunnel:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Traffic flow in your homelab&lt;/th>
&lt;th scope="col">Where packets flow&lt;/th>
&lt;th scope="col">Touches router / firewall CPU?&lt;/th>
&lt;th scope="col">Sizing impact&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>Same-VLAN 10GbE PC → NAS SMB/iSCSI&lt;/strong> (&lt;code>192.168.10.20&lt;/code> → &lt;code>192.168.10.50&lt;/code>)&lt;/td>
&lt;td data-label="Where packets flow">&lt;strong>Layer 2 switch ASIC only&lt;/strong>&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>No&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">A &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE switch&lt;/a> delivers full 10 Gbps local transfers even if your router only has 1 GbE or 2.5 GbE ports.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>Inter-VLAN East-West routing&lt;/strong> (VLAN 10 workstation → VLAN 20 NAS or VLAN 30 IoT)&lt;/td>
&lt;td data-label="Where packets flow">Hairpins up the 802.1Q trunk into the &lt;strong>L3 firewall&lt;/strong> and back down&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>Yes — every packet&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">Putting your workstation on VLAN 10 and your 10GbE NAS on VLAN 20 forces every backup through the firewall&amp;rsquo;s routing + IPS ceiling (unless you give the PC a second direct storage-VLAN NIC).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>Fiber / cable WAN (DHCP vs PPPoE)&lt;/strong>&lt;/td>
&lt;td data-label="Where packets flow">&lt;strong>L3 firewall NAT + WAN interface&lt;/strong>&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>Yes — every packet&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">Standard DHCP WAN scales easily; multi-gig &lt;strong>PPPoE&lt;/strong> adds per-packet encapsulation overhead that taxes weak ARM cores and single-queue FreeBSD NICs unless hardware-offloaded or paired with fast x86 cores and Intel RSS queues.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>Suricata IDS (alert) / inline IPS (block)&lt;/strong>&lt;/td>
&lt;td data-label="Where packets flow">&lt;strong>L3 firewall CPU + RAM&lt;/strong> (netmap / packet engine)&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>Yes — heavy CPU &amp;amp; RAM&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">Scales with active signature count and packet rate. Over TLS 1.3 (HTTPS), IDS/IPS inspects IP reputation, DNS, TLS SNI/JA4 metadata, and unencrypted flows rather than decrypting payloads.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>SQM / Smart Queues (FQ-CoDel)&lt;/strong>&lt;/td>
&lt;td data-label="Where packets flow">&lt;strong>L3 firewall CPU&lt;/strong> (traffic shaper)&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>Yes&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">Ubiquiti doesn&amp;rsquo;t recommend Smart Queues on connections of 300 Mbps or faster. OPNsense&amp;rsquo;s FQ-CoDel shaper has no published speed cutoff; your CPU is the limit.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>WireGuard / OpenVPN remote access &amp;amp; site-to-site&lt;/strong>&lt;/td>
&lt;td data-label="Where packets flow">&lt;strong>L3 firewall CPU&lt;/strong> (unless terminated on an internal host)&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>Yes — ChaCha20-Poly1305 crypto&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">Terminating multi-gigabit WireGuard on the gateway favors x86 AES/SIMD clock speed over entry ARM appliances.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Keep high-bandwidth storage clients and your NAS on the same storage subnet (or add a dedicated untagged storage NIC) so bulk 10GbE traffic stays on your switch ASIC. Size the firewall strictly for &lt;strong>WAN speed + inter-VLAN east-west traffic + VPN/IPS&lt;/strong>.&lt;/p>
&lt;h2 id="the-unifi-idsips-ceiling-is-published-one-page-away">The UniFi IDS/IPS ceiling is published, one page away&lt;/h2>
&lt;p>Ubiquiti&amp;rsquo;s help documentation on &lt;a href="https://help.ui.com/hc/en-us/articles/360006893234-UniFi-Gateway-Intrusion-Detection-and-Prevention-IDS-IPS" rel="noopener">Gateway Intrusion Detection and Prevention (IDS/IPS)&lt;/a> states plainly that enabling inspection &amp;ldquo;increases CPU and memory utilization&amp;rdquo; and that &amp;ldquo;maximum routing performance may be reduced,&amp;rdquo; directing buyers to &lt;a href="https://techspecs.ui.com/unifi/cloud-gateways" rel="noopener">techspecs.ui.com&lt;/a>. Inside the UniFi controller (&lt;strong>Settings → CyberSecure → Protection&lt;/strong>), the switch sits there with no throughput warning beside it.&lt;/p>
&lt;p>Here is Ubiquiti&amp;rsquo;s cloud-gateway lineup with physical WAN ports next to published IDS/IPS throughput. Specifications are from each model&amp;rsquo;s page on techspecs.ui.com and prices from &lt;a href="https://store.ui.com/us/en/category/all-cloud-gateways" rel="noopener">Ubiquiti&amp;rsquo;s US store&lt;/a>, both read November 18, 2026. The store shows a base price and a higher price with its surcharge included; both are below.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Gateway&lt;/th>
&lt;th scope="col">Default WAN ports&lt;/th>
&lt;th scope="col" style="text-align: right">IDS/IPS throughput&lt;/th>
&lt;th scope="col" style="text-align: right">Store price&lt;/th>
&lt;th scope="col" style="text-align: right">With surcharge&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Gateway">Cloud Gateway Ultra (UCG-Ultra)&lt;/td>
&lt;td data-label="Default WAN ports">2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>1 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price">$129&lt;/td>
&lt;td style="text-align: right" data-label="With surcharge">$142&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Cloud Gateway Max (UCG-Max)&lt;/td>
&lt;td data-label="Default WAN ports">2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>2.3 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price">from $199&lt;/td>
&lt;td style="text-align: right" data-label="With surcharge">from $219&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">UniFi Express 7 (UX7)&lt;/td>
&lt;td data-label="Default WAN ports">10 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>2.3 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price">from $199&lt;/td>
&lt;td style="text-align: right" data-label="With surcharge">from $219&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Dream Router 7 (UDR7)&lt;/td>
&lt;td data-label="Default WAN ports">10G SFP+, 2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>2.3 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price">$279&lt;/td>
&lt;td style="text-align: right" data-label="With surcharge">$307&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Cloud Gateway Fiber (UCG-Fiber)&lt;/td>
&lt;td data-label="Default WAN ports">10G SFP+, 10 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>5 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price">$279&lt;/td>
&lt;td style="text-align: right" data-label="With surcharge">$307&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Dream Machine Pro (UDM-Pro)&lt;/td>
&lt;td data-label="Default WAN ports">10G SFP+, 1 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>3.5 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price">$379&lt;/td>
&lt;td style="text-align: right" data-label="With surcharge">$417&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Dream Machine SE (UDM-SE)&lt;/td>
&lt;td data-label="Default WAN ports">10G SFP+, 2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>3.5 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price">$499&lt;/td>
&lt;td style="text-align: right" data-label="With surcharge">$549&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Dream Machine Pro Max (UDM-Pro-Max)&lt;/td>
&lt;td data-label="Default WAN ports">10G SFP+, 2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>5 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price">$599&lt;/td>
&lt;td style="text-align: right" data-label="With surcharge">$660&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Dream Machine Beast (UDM-Beast)&lt;/td>
&lt;td data-label="Default WAN ports">25G SFP28, 10 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>25 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price">$1,499&lt;/td>
&lt;td style="text-align: right" data-label="With surcharge">$1,651&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Enterprise Firewall (EFG)&lt;/td>
&lt;td data-label="Default WAN ports">25G SFP28, 2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>12.5 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price">$1,999&lt;/td>
&lt;td style="text-align: right" data-label="With surcharge">$2,202&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Read the first two columns against each other. &lt;strong>A UniFi Express 7 exposes a 10 GbE WAN port and inspects at 2.3 Gbps.&lt;/strong> A Cloud Gateway Ultra exposes a 2.5 GbE WAN port and inspects at 1 Gbps. The RJ45 or SFP+ port tells you the physical link speed negotiated with your ONT. The inspection column tells you the ceiling once Threat Management goes on.&lt;/p>
&lt;p>Price order does not match inspection order either. &lt;strong>The $279 Cloud Gateway Fiber (UCG-Fiber) inspects at 5 Gbps&lt;/strong>, beating the $379 rackmount Dream Machine Pro (3.5 Gbps) and matching the $599 Dream Machine Pro Max, as independent hardware testing in &lt;a href="https://www.servethehome.com/ubiquiti-unifi-cloud-gateway-fiber-ucg-fiber-review/3/" rel="noopener">ServeTheHome&amp;rsquo;s UCG-Fiber review&lt;/a> also highlights alongside its newer quad-core Cortex-A73 platform.&lt;/p>
&lt;p>On November 18 the only Black Friday offer on that store page was the ruggedized UCG-Industrial (5 Gbps IPS), listed at $399, down from $579. None of the models in the table above was marked down that day.&lt;/p>
&lt;h2 id="multi-gig-fiber--bufferbloat-are-where-appliances-bite-silently">Multi-gig fiber &amp;amp; bufferbloat are where appliances bite silently&lt;/h2>
&lt;p>On a symmetric 500 Mbps or 1 Gbps fiber plan, almost every modern gateway feels effortless. Threat management turns on, speed tests read 940 Mbps, and nothing complains.&lt;/p>
&lt;p>The trap springs when you upgrade to 2 Gbps or 5 Gbps fiber, or route NAS traffic across VLANs. Nothing throws an error banner. Your 2.5 Gbps or 5 Gbps line simply plateaus at the gateway&amp;rsquo;s inspection cap while you blame the ISP.&lt;/p>
&lt;p>Latency under load hits an even lower ceiling on UniFi. Ubiquiti&amp;rsquo;s &lt;a href="https://help.ui.com/hc/en-us/articles/12648661321367-UniFi-Gateway-Smart-Queues" rel="noopener">Smart Queues documentation&lt;/a> says Smart Queues is designed for low-bandwidth connections under 300 Mbps and that Ubiquiti does &amp;ldquo;not recommend enabling Smart Queues for ISP connections that provide 300 Mbps or higher speeds.&amp;rdquo; On an x86 OPNsense box, &lt;a href="https://docs.opnsense.org/manual/how-tos/shaper_bufferbloat.html" rel="noopener">FQ-CoDel traffic shaping&lt;/a> has no firmware cutoff like that; the ceiling is your CPU.&lt;/p>
&lt;h2 id="ucg-max-and-ucg-fiber-vs-an-x86-opnsense-box">UCG-Max and UCG-Fiber vs an x86 OPNsense box&lt;/h2>
&lt;p>Do not compare &amp;ldquo;UniFi&amp;rdquo; in the abstract against &amp;ldquo;some old PC.&amp;rdquo; Compare the two compact UniFi sweet spots (UCG-Max and UCG-Fiber) directly against the two common x86 OPNsense hardware tiers (an Intel N100/N150 fanless box with i226-V ports, and a Core i3 / N305 box with SFP+):&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Dimension&lt;/th>
&lt;th scope="col">UniFi Cloud Gateway Max (UCG-Max)&lt;/th>
&lt;th scope="col">UniFi Cloud Gateway Fiber (UCG-Fiber)&lt;/th>
&lt;th scope="col">Fanless N100 / N150 (4× Intel i226-V 2.5GbE) + OPNsense&lt;/th>
&lt;th scope="col">Core i3 / N305 SFF (10G SFP+ Intel X550/X710) + OPNsense&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Physical ports&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">5× 2.5 GbE RJ45 (1 WAN + 4 LAN)&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">2× 10G SFP+, 1× 10 GbE RJ45, 4× 2.5 GbE (1 PoE+)&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">4–6× 2.5 GbE RJ45 (Intel i226-V)&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">2× 10G SFP+ + 2× 2.5 GbE Intel NICs&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Routed / IPS ceiling&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">2.5 Gbps line / &lt;strong>2.3 Gbps&lt;/strong> published IPS&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">10 Gbps line / &lt;strong>5 Gbps&lt;/strong> published IPS&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">2.5 Gbps NAT/VLAN port limit; Suricata inline IPS scales with ruleset and CPU&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">10 Gbps inter-VLAN &amp;amp; NAT; most headroom for multi-gig PPPoE, FQ-CoDel, WireGuard &amp;amp; Suricata&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Suricata IDS/IPS control&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">Pre-packaged CyberSecure category toggles&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">Pre-packaged CyberSecure category toggles&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">Granular per-interface &lt;a href="https://docs.opnsense.org/manual/ips.html" rel="noopener">OPNsense Suricata netmap IPS&lt;/a>, custom ET Open/Pro rules, per-SID drop/bypass&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">Same full Suricata netmap control + RAM/CPU headroom for multi-VLAN inspection&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Switch &amp;amp; Wi-Fi pane&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">&lt;strong>Built-in UniFi Network&lt;/strong> adopts switches &amp;amp; APs in one UI&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">&lt;strong>Built-in UniFi Network&lt;/strong> adopts switches &amp;amp; APs in one UI&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">Separate: run the UniFi Network controller in Docker/LXC for APs/switches while OPNsense owns L3&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">Separate: OPNsense owns L3; switches/APs managed independently&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Upgrade &amp;amp; rollback safety&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">Appliance firmware updates (cloud/local backup restore)&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">Appliance firmware updates (cloud/local backup restore)&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">&lt;strong>ZFS boot environments&lt;/strong>: snapshot before major upgrades and roll back from the boot menu&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">&lt;strong>ZFS boot environments&lt;/strong> + portable &lt;code>config.xml&lt;/code> restore onto any spare x86 box&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Ubiquiti rates the UCG-Max at 16.1 W maximum and the UCG-Fiber at 29.4 W maximum excluding PoE output (&lt;a href="https://techspecs.ui.com/unifi/cloud-gateways/ucg-max" rel="noopener">UCG-Max&lt;/a>, &lt;a href="https://techspecs.ui.com/unifi/cloud-gateways/ucg-fiber" rel="noopener">UCG-Fiber&lt;/a> spec pages); for a mini PC, check its maker&amp;rsquo;s power figure.&lt;/p>
&lt;p>Notice the operational trade-off honestly. With UniFi, creating VLAN 30 automatically provisions the gateway subnet, DHCP server, 802.1Q switch trunk profiles, and Wi-Fi SSID mapping from one screen. With OPNsense + UniFi switches/APs, you create VLAN 30 once in OPNsense (&lt;strong>Interfaces → Assignments → VLANs&lt;/strong> + DHCP) and create a matching &lt;strong>Third-Party Gateway&lt;/strong> VLAN 30 network in the UniFi controller. That is one extra step per VLAN, and in exchange you own every firewall state, NAT outbound rule, DNS Unbound override, and boot snapshot outright. The &lt;a href="https://techfuelhq.com/tutorials/vlans-homelab-2026/">homelab VLAN guide&lt;/a> walks the whole VLAN layout.&lt;/p>
&lt;h2 id="rule-granularity--why-new-diy-builds-start-on-opnsense">Rule granularity &amp;amp; why new DIY builds start on OPNsense&lt;/h2>
&lt;p>UniFi Network 9.0 narrowed the gap with &lt;a href="https://help.ui.com/hc/en-us/articles/115003173168-Zone-Based-Firewalls-in-UniFi" rel="noopener">Zone-Based Firewalls&lt;/a>, offering custom zones up to thirty total alongside protocol, port, IP, MAC, and application matching. What remains fixed is the appliance floor underneath: UniFi&amp;rsquo;s six default zones and built-in system policies carry lock icons and cannot be edited or deleted (you place override rules above them), and each network maps to a single zone. On OPNsense&amp;rsquo;s &lt;code>pf&lt;/code> engine, nothing is hidden: floating rules, interface groups, policy-based multi-WAN / VPN gateway routing, live firewall log filtering (&lt;strong>Firewall → Log Files → Live View&lt;/strong>), and NAT reflection are completely explicit.&lt;/p>
&lt;p>If you choose the DIY route, my &lt;a href="https://techfuelhq.com/networking/opnsense-vs-pfsense-2026/">OPNsense vs pfSense comparison&lt;/a> covers why I start every new box on OPNsense rather than pfSense. The short version is licensing: Netgate stopped offering the free Home+Lab download of pfSense Plus on &lt;a href="https://www.netgate.com/blog/addressing-changes-to-pfsense-plus-homelab" rel="noopener">October 26, 2023&lt;/a>, and Plus on third-party hardware now starts at &lt;a href="https://www.netgate.com/pfsense-plus-software/software-types" rel="noopener">$129 per year&lt;/a>, while pfSense CE stays free.&lt;/p>
&lt;h2 id="use-intel-nics-on-opnsense-skip-realtek">Use Intel NICs on OPNsense (skip Realtek)&lt;/h2>
&lt;p>OPNsense runs on FreeBSD, and FreeBSD is where the NIC choice bites. Both &lt;a href="https://docs.opnsense.org/manual/hardware.html" rel="noopener">OPNsense&amp;rsquo;s hardware guide&lt;/a> and &lt;a href="https://docs.netgate.com/pfsense/en/latest/hardware/index.html" rel="noopener">Netgate&amp;rsquo;s hardware docs&lt;/a> give the same guidance: use &lt;strong>Intel NICs&lt;/strong>. OPNsense says Intel NICs are &amp;ldquo;reliable, fast and not error-prone&amp;rdquo; and deliver higher throughput at a reduced CPU load; Netgate calls them best practice because they have solid FreeBSD drivers, and warns that other chipsets with FreeBSD drivers can still suffer from instability or poor performance. In practice that means an Intel i226-V for 2.5GbE or an X550 or X710 for 10GbE rather than a Realtek RTL8111 or RTL8125. This is FreeBSD advice: a Linux host such as Proxmox is a different driver stack, which is why the &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE budget guide&lt;/a> can treat Realtek 10G cards differently. Check exact Ethernet controller silicon before ordering in our &lt;a href="https://techfuelhq.com/homelab/n150-mini-pc-2026/">N150 mini PC guide&lt;/a>.&lt;/p>
&lt;h2 id="bottom-line-which-box-belongs-at-your-edge">Bottom line: which box belongs at your edge?&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Buy the UniFi Cloud Gateway Fiber (UCG-Fiber) or UCG-Max&lt;/strong> if you already run UniFi switches and Wi-Fi access points, want single-screen VLAN provisioning, and its published IDS/IPS ceiling (5 Gbps on UCG-Fiber, 2.3 Gbps on UCG-Max) clears your WAN speed with room to spare.&lt;/li>
&lt;li>&lt;strong>Build OPNsense on an Intel i226-V N100/N150 mini PC (for 1–2.5 Gbps) or a Core i3 SFP+ SFF box (for 5–10 Gbps)&lt;/strong> if you want live &lt;code>pf&lt;/code> packet logs, policy-based WireGuard/Tailscale routing, FQ-CoDel bufferbloat control above 300 Mbps, ZFS boot-environment rollbacks, and no vendor-imposed inspection cap. Start with &lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">the best mini PCs for a homelab&lt;/a> for the box and the &lt;a href="https://techfuelhq.com/tutorials/opnsense-mini-pc-setup-2026/">OPNsense mini-PC setup guide&lt;/a> for the install.&lt;/li>
&lt;li>&lt;strong>Keep 10GbE NAS traffic on Layer 2 either way:&lt;/strong> put high-speed storage transfers on a dedicated switch VLAN/subnet so your workstation and NAS talk at 10 Gbps across the switch ASIC without turning your firewall into an expensive bottleneck.&lt;/li>
&lt;/ul>
&lt;p>If you don&amp;rsquo;t need a separate firewall at all and just want better Wi-Fi with a built-in router, the &lt;a href="https://techfuelhq.com/networking/best-wifi-7-router-2026/">Wi-Fi 7 router picks&lt;/a> cover that route.&lt;/p>
&lt;h3 id="where-to-buy-the-cloud-gateway-fiber">Where to buy the Cloud Gateway Fiber&lt;/h3>
&lt;p>Newegg listed the UCG-Fiber at $446.45 on November 17, 2026, well above the $279 ($307 with surcharge) on Ubiquiti&amp;rsquo;s own store the next day, so compare the seller and the total before you pay. Newegg&amp;rsquo;s catalogue had no UCG-Max listing that day; Ubiquiti&amp;rsquo;s store lists it from $199 ($219 with surcharge).&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Ubiquiti&amp;#43;UniFi&amp;#43;Cloud&amp;#43;Gateway&amp;#43;Fiber&amp;#43;UCG-Fiber&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/unifi-vs-opnsense-build-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2F0E6-003V-005X4%3Fitem%3D9SIAD6HKHD0879" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/networking/unifi-vs-opnsense-build-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-18&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>The Newegg button opens the UCG-Fiber listing from that day&amp;rsquo;s catalogue; the Amazon button searches the exact model name, so check the model code (UCG-Fiber) before you pay.&lt;/p></description></item><item><title>ZeroTier vs Tailscale (2026): Layer 2 Switch or Plug-and-Play Mesh?</title><link>https://techfuelhq.com/networking/zerotier-vs-tailscale-2026/</link><pubDate>Sun, 05 Jul 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/zerotier-vs-tailscale-2026/</guid><atom:updated>2026-11-18T04:54:19Z</atom:updated><description>&lt;p>If you want your devices to reach each other from anywhere in 2026 - your NAS from a coffee shop, your desktop from your phone, a friend&amp;rsquo;s server across the country - &lt;strong>Tailscale&lt;/strong> and &lt;strong>ZeroTier&lt;/strong> are the two mesh networks you keep running into. Both create a private overlay where every device gets a fixed address and can talk to every other device without port forwarding, even behind carrier-grade NAT.&lt;/p>
&lt;p>They look interchangeable from the outside. They are not. The difference sits one layer down in the network stack, and it decides which one is right for you. This is the focused two-way version of that decision, written for homelabbers rather than enterprise network teams.&lt;/p>
&lt;h2 id="the-20-second-answer">The 20-second answer&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>You want the simplest possible secure remote access across a pile of roaming devices, with as little setup as possible:&lt;/strong> &lt;strong>Tailscale.&lt;/strong> It is the right default for most people in 2026, and its free tier stretches further than ZeroTier&amp;rsquo;s.&lt;/li>
&lt;li>&lt;strong>You need a real flat LAN across the internet - broadcasts, multicast, Wake-on-LAN, legacy LAN apps, or bridging - or you run MikroTik gear:&lt;/strong> &lt;strong>ZeroTier.&lt;/strong> Its Layer 2 design does things Tailscale structurally cannot.&lt;/li>
&lt;li>&lt;strong>You want to own the entire control plane on your own hardware:&lt;/strong> lean toward &lt;strong>&lt;a href="https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/">Headscale&lt;/a>&lt;/strong> (self-hosted Tailscale control server) or &lt;strong>&lt;a href="https://techfuelhq.com/networking/netbird-vs-tailscale-2026/">NetBird&lt;/a>&lt;/strong> rather than either default, because ZeroTier&amp;rsquo;s own controller has needed a separate commercial license for any business use since version 1.16.0.&lt;/li>
&lt;li>&lt;strong>Running a UniFi gateway?&lt;/strong> &lt;a href="#zerotier-or-tailscale-on-a-unifi-gateway">ZeroTier or Tailscale on a UniFi gateway&lt;/a> covers both installs.&lt;/li>
&lt;/ul>
&lt;p>Neither is a mistake. What follows is where they actually diverge.&lt;/p>
&lt;h2 id="the-one-thing-that-explains-every-other-difference-layer-3-vs-layer-2">The one thing that explains every other difference: Layer 3 vs Layer 2&lt;/h2>
&lt;p>This is the root of the whole comparison, so it is worth getting right.&lt;/p>
&lt;p>&lt;strong>Tailscale is a Layer 3 (IP-level) VPN.&lt;/strong> It is built on the WireGuard protocol and adds a coordination layer on top: it distributes keys between your devices automatically, punches through NAT so they find each other, hands every device a stable &lt;code>100.x.x.x&lt;/code> address plus a MagicDNS name, and enforces access policy. It moves &lt;strong>IP packets&lt;/strong> between devices that now know how to reach each other. It does not stretch your local network across the internet - each device is its own island that can route to the others.&lt;/p>
&lt;p>&lt;strong>ZeroTier is a Layer 2 (Ethernet-level) virtual switch.&lt;/strong> Instead of routing IP packets, it emulates a physical network switch in software: every device you join to a ZeroTier network behaves as if it were plugged into the same switch, on the same flat LAN, even when the machines are in different countries. Because it works at the Ethernet layer, it carries the things a real switch carries - broadcasts, multicast, ARP, and non-IP protocols - not just IP traffic. That also means a ZeroTier network is one flat segment unless you split it yourself; if you already separate your lab into &lt;a href="https://techfuelhq.com/tutorials/vlans-homelab-2026/">VLANs&lt;/a>, decide which segment a ZeroTier member should land in before you bridge it.&lt;/p>
&lt;p>That single architectural choice cascades into everything else:&lt;/p>
&lt;ul>
&lt;li>Need broadcast or multicast (LAN game discovery, some IoT protocols, Wake-on-LAN across sites, legacy software that assumes one subnet)? That is Layer 2 - &lt;strong>ZeroTier&lt;/strong>.&lt;/li>
&lt;li>Just need &amp;ldquo;my devices can reach each other by IP or name, securely, from anywhere&amp;rdquo;? That is Layer 3, and it is simpler - &lt;strong>Tailscale&lt;/strong>.&lt;/li>
&lt;/ul>
&lt;p>Everything below is a consequence of this.&lt;/p>
&lt;h2 id="zerotier-or-tailscale-on-a-unifi-gateway">ZeroTier or Tailscale on a UniFi gateway&lt;/h2>
&lt;p>ZeroTier documents its own install on Ubiquiti hardware. The Tailscale route covered here comes from a community project instead.&lt;/p>
&lt;p>ZeroTier&amp;rsquo;s &lt;a href="https://docs.zerotier.com/ubiquiti/" rel="noopener">Ubiquiti guide&lt;/a> lists separate .deb packages by hardware family. ARM64 builds cover UniFi Dream Machine variants, the UXG-Pro, Cloud Key Gen2 and UDR, and MIPS64 builds cover EdgeRouter models and the USG line. You download the package for your model into &lt;code>/config/data/firstboot/install-packages/&lt;/code>, install it with &lt;code>dpkg&lt;/code>, and manage it as the &lt;code>zerotier-one&lt;/code> service. The guide says to keep the package in that folder so the device can reinstall ZeroTier after a firmware upgrade. It also points to a separate guide on routing between physical and virtual ZeroTier networks.&lt;/p>
&lt;p>One user report on ZeroTier&amp;rsquo;s GitHub tracker, &lt;a href="https://github.com/zerotier/ZeroTierOne/issues/2488" rel="noopener">issue 2488&lt;/a>, which was still open on November 18, 2026, says UniFi Cloud Gateway models do not reinstall packages from that folder after a firmware upgrade the way UDM models do. The reporter says the ZeroTier config survives, so reinstalling the package brings the gateway back, and describes a script and boot service that automate the reinstall. Treat it as one user&amp;rsquo;s account. Check that ZeroTier is still installed after an upgrade.&lt;/p>
&lt;p>For Tailscale, the &lt;a href="https://github.com/SierraSoftworks/tailscale-unifi" rel="noopener">SierraSoftworks/tailscale-unifi&lt;/a> project on GitHub is a community install for UniFi OS. It is MIT-licensed. Tailscale and Ubiquiti do not publish it. Its README describes scripts that install Tailscale on UniFi Cloud Gateways with a persistent service and automatic updates. It needs UniFi OS 2.x or later. The README lists the USG, Cloud Key Gen 1 and UniFi Travel Router among incompatible devices. It also documents slow TCP throughput on the Cloud Gateway Max when the gateway acts as a Tailscale subnet router, and gives a workaround. Tailscale&amp;rsquo;s own docs describe a &lt;a href="https://tailscale.com/docs/features/subnet-routers" rel="noopener">subnet router&lt;/a> as a way to reach devices that cannot run the Tailscale client.&lt;/p>
&lt;p>If Tailscale runs on your devices behind a UniFi gateway instead, Tailscale&amp;rsquo;s &lt;a href="https://tailscale.com/docs/integrations/firewalls" rel="noopener">firewall page&lt;/a> says to expect traffic relayed through DERP or a peer relay rather than a direct connection. Its workaround is to allow peer-to-peer traffic: on a gateway with threat detection enabled, uncheck the P2P category. In UniFi Network 9.0.108 and later that lives under &lt;strong>Network → Security → Protection → Peer to Peer and Dark Web&lt;/strong>; in 9.0.107 and earlier it is &lt;strong>Settings → Firewall &amp;amp; Security → Edit threat categories&lt;/strong>.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Warning:&lt;/strong> unchecking P2P turns off threat detection for that whole category, not just for Tailscale. To undo, check P2P again in the same place.&lt;/p>&lt;/blockquote>
&lt;p>Layer 2 versus Layer 3 still decides which one belongs on the gateway.&lt;/p>
&lt;h2 id="setup-and-day-to-day-ease-tailscale-wins-clearly">Setup and day-to-day ease: Tailscale wins clearly&lt;/h2>
&lt;p>This is the widest gap between the two products, and it shows up in the step count rather than in anyone&amp;rsquo;s testimonial, so compare what each one asks of a first-time user. Everything below is our own walkthrough of both onboarding flows, not a poll of anybody.&lt;/p>
&lt;p>Tailscale&amp;rsquo;s onboarding is: install the client, sign in with an existing identity provider (Google, Microsoft, GitHub, and others), and the device is on your tailnet. NAT traversal, key exchange, and DNS are handled for you. There is very little to misconfigure.&lt;/p>
&lt;p>ZeroTier is more hands-on. You create a network, get a 16-digit network ID, join devices with that ID, and then &lt;strong>manually authorize&lt;/strong> each device in the controller. Its power lives in a flow-rules engine and managed IP assignment that give you fine control - but that control is also more to learn and more to get wrong, and the complexity is what buys the flexibility.&lt;/p>
&lt;p>If your priority is minimal friction, Tailscale is the easier tool by a wide margin. If you enjoy - or need - to shape the network by hand, ZeroTier gives you more surface to work with.&lt;/p>
&lt;h2 id="speed-close-enough-that-it-rarely-decides-anything">Speed: close enough that it rarely decides anything&lt;/h2>
&lt;p>Both establish direct peer-to-peer links when they can and fall back to relays when they cannot. &lt;a href="https://tailscale.com/compare/zerotier" rel="noopener">Tailscale&amp;rsquo;s own comparison&lt;/a> says its throughput &amp;ldquo;is similar to ZeroTier&amp;rsquo;s in most environments&amp;rdquo;, and that WireGuard&amp;rsquo;s somewhat lower overhead is rarely noticeable in practice. ZeroTier&amp;rsquo;s README describes its fallback as &amp;ldquo;free (but slow) relaying&amp;rdquo; for peers that cannot connect directly, so whether you get a direct path matters more than which tool you picked.&lt;/p>
&lt;p>ZeroTier also has an edge for specific situations: its &lt;a href="https://docs.zerotier.com/multipath/" rel="noopener">multipath&lt;/a> feature can aggregate several physical links into one bond for more total throughput or failover.&lt;/p>
&lt;p>Bottom line: on an established tunnel over a normal home connection, treat them as a tie. Do not pick on speed alone.&lt;/p>
&lt;h2 id="the-free-tier-where-the-two-differ-most">The free tier: where the two differ most&lt;/h2>
&lt;p>Plan figures below are from &lt;a href="https://www.zerotier.com/pricing/" rel="noopener">ZeroTier&amp;rsquo;s pricing page&lt;/a> and &lt;a href="https://tailscale.com/pricing" rel="noopener">Tailscale&amp;rsquo;s pricing page&lt;/a>, both read November 18, 2026.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Tailscale Personal (free):&lt;/strong> up to &lt;strong>6 users&lt;/strong> with &lt;strong>unlimited user devices&lt;/strong>, up to 3 ACL groups and up to 50 tagged resources to start. For a solo homelab that keeps adding machines, this is effectively uncapped.&lt;/li>
&lt;li>&lt;strong>ZeroTier Personal (free):&lt;/strong> &lt;strong>10 devices&lt;/strong>, &lt;strong>1 network&lt;/strong>, &lt;strong>1 network admin&lt;/strong>, for personal, non-commercial use. Its paid &lt;strong>Essential&lt;/strong> plan is &lt;strong>$18 per month&lt;/strong> with a commercial license (10 devices included, then $2 per extra device), and &lt;strong>Scale&lt;/strong> is &lt;strong>$179 per month&lt;/strong> for 100 included devices, then $1.80 each.&lt;/li>
&lt;/ul>
&lt;p>For comparison, Tailscale&amp;rsquo;s paid plans are &lt;strong>Standard&lt;/strong> at $8 per user per month and &lt;strong>Premium&lt;/strong> at $18 per user per month - but most homelabbers never leave the free Personal plan.&lt;/p>
&lt;p>The practical takeaway: if you are a single person adding your eleventh device, ZeroTier&amp;rsquo;s free tier stops you and Tailscale&amp;rsquo;s does not. Check each vendor&amp;rsquo;s pricing page before you commit, since this is exactly the kind of limit that changes.&lt;/p>
&lt;h2 id="self-hosting-and-the-licensing-change">Self-hosting and the licensing change&lt;/h2>
&lt;p>If you like to own your infrastructure, read this section carefully, because the ground shifted under ZeroTier.&lt;/p>
&lt;p>Historically, ZeroTier&amp;rsquo;s appeal for the self-hosting crowd was that you could run your own controller and even your own root nodes (moons) and depend on nobody. ZeroTier 1.16.0, released August 21, 2025, changed that (&lt;a href="https://github.com/zerotier/ZeroTierOne/blob/dev/RELEASE-NOTES.md" rel="noopener">release notes&lt;/a>):&lt;/p>
&lt;ul>
&lt;li>The client core and service moved to the Mozilla Public License.&lt;/li>
&lt;li>The network controller moved to a commercial source-available license, the ZeroTier Source-Available License 1.0, which also covers the other components in the repository&amp;rsquo;s &lt;code>nonfree&lt;/code> directory. Its &lt;a href="https://github.com/zerotier/ZeroTierOne/blob/dev/nonfree/LICENSE.md" rel="noopener">license text&lt;/a> allows personal, non-commercial use free of charge and requires a separate commercial license for any business, government or non-profit use.&lt;/li>
&lt;li>Default binary builds no longer contain the controller; you build it yourself with &lt;code>make ZT_NONFREE=1&lt;/code>.&lt;/li>
&lt;li>Moons are &amp;ldquo;even more extra &lt;em>deprecated&lt;/em>&amp;rdquo; and should not be used in new deployments.&lt;/li>
&lt;/ul>
&lt;p>So a personal homelab can still run its own ZeroTier controller, but the reason a homelab picked ZeroTier in the first place, that the whole stack could live on hardware you own under an open license, has thinned. The WireGuard-based projects that answer the same want are NetBird and Netmaker.&lt;/p>
&lt;p>Tailscale&amp;rsquo;s control plane is proprietary as a service, but the escape hatch is healthier: &lt;strong>&lt;a href="https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/">Headscale&lt;/a>&lt;/strong> is a mature open-source implementation of the Tailscale coordination server, so you can keep the polished Tailscale clients and run the brains on your own box. If self-hosting the whole stack matters to you, that combination - or a fully open project like &lt;a href="https://techfuelhq.com/networking/netbird-vs-tailscale-2026/">NetBird&lt;/a> - is currently the more predictable bet than pinning your future to ZeroTier&amp;rsquo;s controller licensing.&lt;/p>
&lt;h2 id="where-zerotier-still-genuinely-wins">Where ZeroTier still genuinely wins&lt;/h2>
&lt;p>Do not read the above as &amp;ldquo;just use Tailscale.&amp;rdquo; ZeroTier holds real, structural advantages that Tailscale cannot match by design:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>True Layer 2 features:&lt;/strong> broadcast, multicast, and non-IP traffic ride the ZeroTier network as if every device were on one switch. Wake-on-LAN across sites, LAN-discovery-dependent apps, and bridging a remote device onto your home subnet are ZeroTier&amp;rsquo;s home turf.&lt;/li>
&lt;li>&lt;strong>MikroTik native support:&lt;/strong> MikroTik ships ZeroTier as a RouterOS 7 package for ARM and ARM64 routers, and RouterOS can host its own ZeroTier controller on the router (&lt;a href="https://help.mikrotik.com/docs/spaces/ROS/pages/83755083/ZeroTier" rel="noopener">MikroTik&amp;rsquo;s ZeroTier docs&lt;/a>). If that is your gear, it is a real reason to choose ZeroTier. If you are pricing MikroTik switching anyway, &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE on a budget&lt;/a> covers its CRS305.&lt;/li>
&lt;li>&lt;strong>No forced identity provider:&lt;/strong> ZeroTier does not require linking machines to a Google, Microsoft, or Apple account - a genuine privacy and independence angle that Tailscale&amp;rsquo;s SSO-first model does not offer out of the box.&lt;/li>
&lt;li>&lt;strong>Simultaneous multi-network membership:&lt;/strong> a device can belong to several ZeroTier networks at once natively; doing the equivalent on Tailscale takes more work.&lt;/li>
&lt;li>&lt;strong>CGNAT resilience:&lt;/strong> ZeroTier is reliable behind carrier-grade NAT, and multipath can bond a second uplink for failover.&lt;/li>
&lt;/ul>
&lt;p>If any of those describe your situation - especially the Layer 2 requirements or MikroTik hardware - ZeroTier is not just viable, it is the correct answer.&lt;/p>
&lt;h2 id="side-by-side">Side-by-side&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Factor&lt;/th>
&lt;th scope="col">Tailscale&lt;/th>
&lt;th scope="col">ZeroTier&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Factor">Network layer&lt;/td>
&lt;td data-label="Tailscale">Layer 3 (IP VPN)&lt;/td>
&lt;td data-label="ZeroTier">Layer 2 (virtual Ethernet switch)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">Protocol&lt;/td>
&lt;td data-label="Tailscale">WireGuard&lt;/td>
&lt;td data-label="ZeroTier">Custom ZeroTier protocol&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">Setup ease&lt;/td>
&lt;td data-label="Tailscale">Very easy, SSO, zero-config&lt;/td>
&lt;td data-label="ZeroTier">More technical, manual authorization + rules&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">Free tier (Nov 2026)&lt;/td>
&lt;td data-label="Tailscale">6 users, unlimited user devices&lt;/td>
&lt;td data-label="ZeroTier">10 devices, 1 network, non-commercial&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">Paid entry&lt;/td>
&lt;td data-label="Tailscale">$8/user/mo (Standard)&lt;/td>
&lt;td data-label="ZeroTier">$18/mo (Essential)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">Broadcast / multicast / WoL&lt;/td>
&lt;td data-label="Tailscale">No (Layer 3)&lt;/td>
&lt;td data-label="ZeroTier">Yes (Layer 2)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">MikroTik native&lt;/td>
&lt;td data-label="Tailscale">No&lt;/td>
&lt;td data-label="ZeroTier">Yes (RouterOS 7, ARM/ARM64)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">Auth&lt;/td>
&lt;td data-label="Tailscale">Identity provider (SSO) required&lt;/td>
&lt;td data-label="ZeroTier">No identity provider required; machine keys&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">Self-host control plane&lt;/td>
&lt;td data-label="Tailscale">Headscale (open source)&lt;/td>
&lt;td data-label="ZeroTier">Controller source-available; free for non-commercial use only&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Factor">Best at&lt;/td>
&lt;td data-label="Tailscale">Simplest secure remote access&lt;/td>
&lt;td data-label="ZeroTier">Flexible flat-LAN emulation&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="who-should-pick-which">Who should pick which&lt;/h2>
&lt;p>&lt;strong>Choose Tailscale&lt;/strong> for &amp;ldquo;reach my stuff from anywhere, securely, without fuss,&amp;rdquo; especially if you keep adding devices. Our &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale remote-access homelab guide&lt;/a> walks the full setup.&lt;/p>
&lt;p>&lt;strong>Choose ZeroTier&lt;/strong> if you need Layer 2 behavior, run MikroTik gear or want to avoid a forced identity provider, knowing the free tier is smaller and the self-hosted controller now needs a separate commercial license for any business use.&lt;/p>
&lt;p>&lt;strong>Choose neither, and look at Headscale or &lt;a href="https://techfuelhq.com/networking/netbird-vs-tailscale-2026/">NetBird&lt;/a>,&lt;/strong> if owning the complete control plane on your own hardware is non-negotiable. If the people connecting won&amp;rsquo;t install any client at all, &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">Tailscale vs Cloudflare Tunnel&lt;/a> covers browser-only access.&lt;/p>
&lt;p>Still weighing the underlying options rather than these two managed meshes? Start with &lt;a href="https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/">Tailscale vs WireGuard&lt;/a> for the raw-protocol-versus-coordination-layer decision, or &lt;a href="https://techfuelhq.com/networking/unifi-vs-opnsense-build-2026/">UniFi vs an OPNsense build&lt;/a> if you are choosing the firewall at the edge.&lt;/p></description></item><item><title>OPNsense vs pfSense (2026): Which Firewall Should You Actually Run?</title><link>https://techfuelhq.com/networking/opnsense-vs-pfsense-2026/</link><pubDate>Wed, 01 Jul 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/opnsense-vs-pfsense-2026/</guid><atom:updated>2026-11-18T04:54:19Z</atom:updated><description>&lt;p>If you are standing up a real firewall for a home network or a homelab in 2026, the choice almost always comes down to two FreeBSD-based, open-source platforms: &lt;strong>OPNsense&lt;/strong> and &lt;strong>pfSense&lt;/strong>. They look similar on a feature checklist, they share a common ancestor, and both will happily route, filter, VPN, and inspect traffic for a small network. The interesting differences are not on the spec sheet - they are in licensing direction, interface philosophy, update cadence, and the plugin you happen to depend on.&lt;/p>
&lt;p>This is the focused two-way version of that decision. If you are trying to pick the &lt;em>hardware&lt;/em> to run either of these on - Netgate boxes, Protectli, MikroTik, or UniFi - that is a different question; for the UniFi half, &lt;a href="https://techfuelhq.com/networking/unifi-vs-opnsense-build-2026/">UniFi vs an OPNsense build&lt;/a> has Ubiquiti&amp;rsquo;s published IDS/IPS throughput per gateway.&lt;/p>
&lt;h2 id="the-20-second-answer">The 20-second answer&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>New build, commodity hardware, want a modern UI and fast updates:&lt;/strong> &lt;strong>OPNsense.&lt;/strong> It is the better default for most people starting fresh in 2026.&lt;/li>
&lt;li>&lt;strong>You already run pfSense and it works, or you depend on pfBlockerNG / a pfSense-specific package:&lt;/strong> &lt;strong>stay on pfSense CE.&lt;/strong> It is stable and there is no urgency to move.&lt;/li>
&lt;li>&lt;strong>You want a paid, vendor-backed appliance with US support and legendary uptime:&lt;/strong> &lt;strong>pfSense Plus on Netgate hardware.&lt;/strong>&lt;/li>
&lt;/ul>
&lt;p>Both are genuinely good. Nobody picking either one is making a mistake. What follows is where they actually diverge.&lt;/p>
&lt;h2 id="common-roots-a-decade-apart">Common roots, a decade apart&lt;/h2>
&lt;p>OPNsense began as a fork of pfSense and the older m0n0wall project in &lt;strong>2014&lt;/strong>, with its first official release in &lt;strong>January 2015&lt;/strong> (&lt;a href="https://opnsense.org/opnsense/" rel="noopener">OPNsense project history&lt;/a>). That shared lineage is why the two feel familiar - the same FreeBSD packet-filtering core (&lt;code>pf&lt;/code>), the same broad feature set, similar concepts for rules, NAT, and VPN.&lt;/p>
&lt;p>But a decade of separate development has pulled them apart. OPNsense is maintained by &lt;strong>Deciso&lt;/strong>, a Netherlands-based company, and follows a fixed cycle of two major releases a year. The current series is &lt;strong>26.7 (&amp;ldquo;Xenial Xenops&amp;rdquo;)&lt;/strong>, released July 15, 2026 on FreeBSD 15.1; minor updates have landed about every two weeks since, the latest being 26.7.9 on November 11, 2026 (&lt;a href="https://docs.opnsense.org/releases/CE_26.7.html" rel="noopener">OPNsense 26.7 release notes&lt;/a>). pfSense is developed by &lt;strong>Netgate&lt;/strong> in the US and ships as two editions: &lt;strong>pfSense CE&lt;/strong> (Community Edition, free and open source, now on the 2.9 line: 2.9.0 shipped August 20, 2026 and 2.9.1 on November 17, 2026, both on a FreeBSD 16.0-CURRENT base per &lt;a href="https://docs.netgate.com/pfsense/en/latest/releases/versions.html" rel="noopener">Netgate&amp;rsquo;s version table&lt;/a>) and &lt;strong>pfSense Plus&lt;/strong>, the commercial edition, which comes on Netgate appliances or runs on other hardware with a paid subscription.&lt;/p>
&lt;h3 id="where-each-one-stands-in-november-2026">Where each one stands in November 2026&lt;/h3>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">OPNsense&lt;/th>
&lt;th scope="col">pfSense CE&lt;/th>
&lt;th scope="col">pfSense Plus&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">License&lt;/td>
&lt;td data-label="OPNsense">2-Clause BSD&lt;/td>
&lt;td data-label="pfSense CE">Open source&lt;/td>
&lt;td data-label="pfSense Plus">Netgate EULA&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Cost&lt;/td>
&lt;td data-label="OPNsense">Free&lt;/td>
&lt;td data-label="pfSense CE">Free&lt;/td>
&lt;td data-label="pfSense Plus">Included on Netgate appliances; $129 per instance per year (TAC Lite) elsewhere&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Latest release&lt;/td>
&lt;td data-label="OPNsense">26.7.9 (Nov 11, 2026)&lt;/td>
&lt;td data-label="pfSense CE">2.9.1 (Nov 17, 2026)&lt;/td>
&lt;td data-label="pfSense Plus">26.07.1 (Nov 17, 2026)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">FreeBSD base&lt;/td>
&lt;td data-label="OPNsense">15.1&lt;/td>
&lt;td data-label="pfSense CE">16.0-CURRENT snapshot&lt;/td>
&lt;td data-label="pfSense Plus">16.0-CURRENT snapshot&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Releases, May 2025 to Nov 2026&lt;/td>
&lt;td data-label="OPNsense">Three major series (25.7, 26.1, 26.7) plus minor updates&lt;/td>
&lt;td data-label="pfSense CE">Four (2.8.0, 2.8.1, 2.9.0, 2.9.1)&lt;/td>
&lt;td data-label="pfSense Plus">Eight (25.07 through 26.07.1)&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Prices and versions are from &lt;a href="https://www.netgate.com/pfsense-plus-software/software-types" rel="noopener">Netgate&amp;rsquo;s subscription table&lt;/a>, Netgate&amp;rsquo;s version table and the OPNsense release notes, read November 18, 2026.&lt;/p>
&lt;h2 id="licensing-the-quiet-reason-a-lot-of-people-moved">Licensing: the quiet reason a lot of people moved&lt;/h2>
&lt;p>This is the single biggest non-technical driver of the 2026 conversation, and it is worth being clear-eyed about.&lt;/p>
&lt;p>OPNsense is fully open source under a &lt;strong>2-clause BSD license&lt;/strong>, with no paid tier gating firewall features. pfSense CE is also open source and free, but Netgate&amp;rsquo;s own version table lists eight pfSense Plus releases (25.07 through 26.07.1) against four CE releases (2.8.0 through 2.9.1) between May 2025 and November 2026. Netgate also stopped offering the free Home+Lab download of Plus on &lt;a href="https://www.netgate.com/blog/addressing-changes-to-pfsense-plus-homelab" rel="noopener">October 26, 2023&lt;/a>, so Plus on your own hardware is now a subscription. Unease about that CE-versus-Plus direction is a real part of why some long-time pfSense users switched. You will find this sentiment stated plainly across &lt;a href="https://www.reddit.com/r/homelab/comments/1ix85pw/pfsense_vs_opnsense/" rel="noopener">r/homelab&lt;/a> and &lt;a href="https://www.reddit.com/r/selfhosted/comments/1h1zvhq/pfsense_vs_opnsense/" rel="noopener">r/selfhosted&lt;/a> threads on the topic.&lt;/p>
&lt;p>None of that makes pfSense CE a bad firewall - it is still free, capable, and widely run. But if &amp;ldquo;will the free edition keep getting first-class attention&amp;rdquo; is a question you care about, OPNsense&amp;rsquo;s answer is simpler.&lt;/p>
&lt;h2 id="interface-and-daily-use">Interface and daily use&lt;/h2>
&lt;p>The most commonly cited difference, and the one you feel every time something breaks at 2 a.m., is the web UI.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>OPNsense&lt;/strong> uses a &lt;strong>collapsible left-side menu with a built-in search bar&lt;/strong>. Menus are grouped logically, inline help is current, and finding a setting you rarely touch is fast. It also ships &lt;strong>built-in two-factor authentication&lt;/strong> for the web UI and a &lt;strong>built-in REST API&lt;/strong>, which is a real advantage if you automate anything.&lt;/li>
&lt;li>&lt;strong>pfSense&lt;/strong> uses the &lt;strong>traditional top-drop menu&lt;/strong> layout. It is dense, it is what a lot of people learned on, and once you know where things live it is perfectly efficient - but there is no built-in search, and the learning curve is steeper for a newcomer.&lt;/li>
&lt;/ul>
&lt;p>If you are new to firewalls, OPNsense&amp;rsquo;s interface is the friendlier place to start. If you have muscle memory for pfSense&amp;rsquo;s menus, that familiarity is worth something real.&lt;/p>
&lt;h2 id="plugins-and-packages">Plugins and packages&lt;/h2>
&lt;p>pfSense&amp;rsquo;s &lt;strong>package library is larger and older&lt;/strong>, and its headline package is &lt;strong>pfBlockerNG&lt;/strong> for DNS and IP blocklisting - a genuinely excellent tool that many pfSense users consider load-bearing. Mature packages like HAProxy, ntopng, and ACME are well established.&lt;/p>
&lt;p>OPNsense takes a &lt;strong>more curated approach&lt;/strong>: a tighter, quality-controlled plugin set, with several things built in that pfSense treats as add-ons (reporting/NetFlow insight, for example). It does not have pfBlockerNG, but it covers the same ground with built-in Unbound DNS blocklists, native alias/GeoIP features, and optional plugins like Zenarmor for next-gen filtering.&lt;/p>
&lt;p>The practical read: if a specific pfSense package - especially pfBlockerNG - is central to your setup, that is a legitimate reason to stay on pfSense. If you want a clean, curated set that mostly works out of the box, OPNsense&amp;rsquo;s model is less likely to leave you running an abandoned package.&lt;/p>
&lt;h2 id="security-cadence---with-a-caveat">Security cadence - with a caveat&lt;/h2>
&lt;p>OPNsense&amp;rsquo;s two-week minor-release rhythm means new features and fixes generally land faster, and the project says it ships security updates weekly (&lt;a href="https://opnsense.org/opnsense/" rel="noopener">OPNsense&lt;/a>). That cadence is a real advantage.&lt;/p>
&lt;p>The caveat: a faster &lt;em>release&lt;/em> cadence is not automatically a faster &lt;em>patch-for-a-specific-CVE&lt;/em> cadence. There have been &lt;a href="https://forums.lawrencesystems.com/t/opnsense-vs-pfsense-security/19842" rel="noopener">documented community discussions&lt;/a> arguing pfSense has at times shipped certain upstream security fixes sooner, despite its slower release rhythm. Both projects take security seriously; neither is negligent. Do not pick a firewall on a blanket &amp;ldquo;one patches faster&amp;rdquo; claim - the reality is more nuanced than either camp&amp;rsquo;s marketing.&lt;/p>
&lt;h2 id="performance-effectively-a-tie-where-it-counts">Performance: effectively a tie where it counts&lt;/h2>
&lt;p>Raw throughput is a function of your CPU and NIC, not which firewall you install. Both OPNsense and pfSense now use &lt;strong>kernel-mode WireGuard&lt;/strong>, which closed the old user-space VPN ceiling.&lt;/p>
&lt;p>On our own bench, at a 1 Gbps WAN:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Firewall / hardware&lt;/th>
&lt;th scope="col">NAT throughput&lt;/th>
&lt;th scope="col">WireGuard (1 tunnel)&lt;/th>
&lt;th scope="col">Idle power&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Firewall / hardware">pfSense Plus, Netgate 4100&lt;/td>
&lt;td data-label="NAT throughput">~938 Mbps&lt;/td>
&lt;td data-label="WireGuard (1 tunnel)">~941 Mbps&lt;/td>
&lt;td data-label="Idle power">14 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Firewall / hardware">OPNsense, Protectli VP2420 (i3-N305)&lt;/td>
&lt;td data-label="NAT throughput">~941 Mbps&lt;/td>
&lt;td data-label="WireGuard (1 tunnel)">~938 Mbps&lt;/td>
&lt;td data-label="Idle power">11 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Firewall / hardware">OPNsense, N100 mini-PC&lt;/td>
&lt;td data-label="NAT throughput">~939 Mbps&lt;/td>
&lt;td data-label="WireGuard (1 tunnel)">~692 Mbps&lt;/td>
&lt;td data-label="Idle power">7 W&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>They are, for practical purposes, tied at line rate. The one place a gap opens is &lt;strong>Suricata IDS on underpowered hardware&lt;/strong>: a four-core N100 starts to bottleneck with IDS enabled, while an eight-core i3-N305-class box or better keeps up (core counts from Intel&amp;rsquo;s &lt;a href="https://www.intel.com/content/www/us/en/products/sku/231803/intel-processor-n100-6m-cache-up-to-3-40-ghz/specifications.html" rel="noopener">N100&lt;/a> and &lt;a href="https://www.intel.com/content/www/us/en/products/sku/231805/intel-core-i3n305-processor-6m-cache-up-to-3-80-ghz/specifications.html" rel="noopener">i3-N305&lt;/a> spec pages). That is a CPU story, not an OPNsense-versus-pfSense story. If you would rather terminate WireGuard on a server than on the firewall, the &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">WireGuard LXC guide for Proxmox&lt;/a> covers that layout, and for 2.5G or 10G links the NICs and switch matter more than either OS (&lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE on a budget&lt;/a>).&lt;/p>
&lt;p>On paper, both fix lag under load the same way. Each puts an FQ-CoDel shaper on the WAN. OPNsense&amp;rsquo;s &lt;a href="https://docs.opnsense.org/manual/how-tos/shaper_bufferbloat.html" rel="noopener">bufferbloat guide&lt;/a> starts the pipe at 85% of the ISP&amp;rsquo;s advertised rate and tunes from there, and Netgate&amp;rsquo;s &lt;a href="https://docs.netgate.com/pfsense/en/latest/recipes/codel-limiters.html" rel="noopener">CoDel limiter recipe&lt;/a> sets each limiter equal to the speed-tested WAN bandwidth.&lt;/p>
&lt;h2 id="how-to-actually-decide">How to actually decide&lt;/h2>
&lt;p>Skip the feature-checklist paralysis. Answer these instead:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Do you already run pfSense and is it working?&lt;/strong> Stay. There is no prize for switching.&lt;/li>
&lt;li>&lt;strong>Do you depend on pfBlockerNG or another pfSense-specific package?&lt;/strong> Stay on pfSense.&lt;/li>
&lt;li>&lt;strong>Starting fresh, on your own commodity hardware, want the nicer UI and faster updates?&lt;/strong> OPNsense.&lt;/li>
&lt;li>&lt;strong>Want a paid appliance with vendor support and set-and-forget uptime?&lt;/strong> pfSense Plus on a Netgate box.&lt;/li>
&lt;li>&lt;strong>Uneasy about the pfSense CE/Plus licensing direction?&lt;/strong> OPNsense removes that question entirely.&lt;/li>
&lt;/ol>
&lt;p>Once you have picked, the next step is hardware and setup. For a clean, quiet, low-power box to run either one, see &lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">the best mini PCs for a homelab&lt;/a> or the &lt;a href="https://techfuelhq.com/homelab/n150-mini-pc-2026/">N150 mini PC guide&lt;/a>, which compares boxes down to their network controllers; for a step-by-step OPNsense install on a mini PC, our &lt;a href="https://techfuelhq.com/tutorials/opnsense-mini-pc-setup-2026/">OPNsense mini-PC setup guide&lt;/a> walks the whole thing. If you are also planning VLANs behind the firewall, start with the &lt;a href="https://techfuelhq.com/tutorials/vlans-homelab-2026/">homelab VLAN guide&lt;/a>, and if your WAN address changes, the &lt;a href="https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/">dynamic DNS guide&lt;/a> covers OPNsense&amp;rsquo;s ddclient plugin.&lt;/p>
&lt;h2 id="bottom-line">Bottom line&lt;/h2>
&lt;p>In 2026, &lt;strong>OPNsense is the better default for a new homelab firewall&lt;/strong> - modern UI, fast updates, commodity-hardware friendly, and free of the licensing question hanging over pfSense CE. &lt;strong>pfSense remains an excellent choice&lt;/strong> if you already run it, value its maturity and stability, or depend on a pfSense-specific package. Both are FreeBSD-grade, both will serve a home network for years, and the &amp;ldquo;wrong&amp;rdquo; choice here is still a very good firewall.&lt;/p></description></item><item><title>SSH Port Forwarding: -L, -R, -D and Why Your Reverse Tunnel Only Works Locally (2026)</title><link>https://techfuelhq.com/networking/ssh-port-forwarding-tunneling-2026/</link><pubDate>Sat, 15 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/ssh-port-forwarding-tunneling-2026/</guid><atom:updated>2026-11-18T04:50:24Z</atom:updated><description>&lt;p>Three flags. The third is where the afternoon goes.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ssh -L 8080:internal-host:80 user@server &lt;span style="color:#75715e"># reach IN&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ssh -R 8080:localhost:80 user@server &lt;span style="color:#75715e"># expose OUT&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ssh -D &lt;span style="color:#ae81ff">1080&lt;/span> user@server &lt;span style="color:#75715e"># SOCKS proxy&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>-L&lt;/code> opens a listener on &lt;strong>your&lt;/strong> machine. &lt;code>-R&lt;/code> opens one on &lt;strong>the server&lt;/strong>. That is the entire difference. Inverting it is the beginner mistake, and it announces itself immediately, which makes it the cheap one.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">You want to&lt;/th>
&lt;th scope="col">Flag&lt;/th>
&lt;th scope="col">Listener opens on&lt;/th>
&lt;th scope="col">Example&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="You want to">Reach a service on the far network&lt;/td>
&lt;td data-label="Flag">&lt;code>-L&lt;/code>&lt;/td>
&lt;td data-label="Listener opens on">your machine&lt;/td>
&lt;td data-label="Example">&lt;code>ssh -L 8080:192.168.1.50:80 user@gateway&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You want to">Expose a service on your side through the server&lt;/td>
&lt;td data-label="Flag">&lt;code>-R&lt;/code>&lt;/td>
&lt;td data-label="Listener opens on">the server&lt;/td>
&lt;td data-label="Example">&lt;code>ssh -R 8080:localhost:80 user@vps&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You want to">Browse the far network through one proxy port&lt;/td>
&lt;td data-label="Flag">&lt;code>-D&lt;/code>&lt;/td>
&lt;td data-label="Listener opens on">your machine (SOCKS 4/5)&lt;/td>
&lt;td data-label="Example">&lt;code>ssh -D 1080 user@server&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You want to">Log in to a host only a bastion can reach&lt;/td>
&lt;td data-label="Flag">&lt;code>-J&lt;/code>&lt;/td>
&lt;td data-label="Listener opens on">nowhere (routing only)&lt;/td>
&lt;td data-label="Example">&lt;code>ssh -J bastion user@internal-host&lt;/code>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Everything here follows the OpenSSH manuals: &lt;a href="https://man.openbsd.org/ssh.1" rel="noopener">ssh(1)&lt;/a> for the flags, &lt;a href="https://man.openbsd.org/sshd_config.5" rel="noopener">sshd_config(5)&lt;/a> for the server side and &lt;a href="https://man.openbsd.org/ssh_config.5" rel="noopener">ssh_config(5)&lt;/a> for the client side. If you meant the rule in your router, that is &lt;a href="https://techfuelhq.com/networking/port-forwarding-2026/">router port forwarding&lt;/a>, a different tool with different failure modes.&lt;/p>
&lt;p>The expert mistake is different, and it is the reason this page exists: &lt;strong>&lt;code>-R&lt;/code> does not fail when it does not work.&lt;/strong> It succeeds into a state that is not the one you asked for.&lt;/p>
&lt;h2 id="the--r-trap">The -R trap&lt;/h2>
&lt;p>You run this on a home machine, against a VPS with a public IP:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ssh -R 8080:localhost:80 user@vps
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>You expect &lt;code>http://vps-public-ip:8080&lt;/code> to reach the web server at home. From the VPS itself, &lt;code>curl localhost:8080&lt;/code> works perfectly, which is the detail that sends people off debugging their home firewall, their router, and eventually their ISP, when none of those were ever in the path. From anywhere else: connection refused.&lt;/p>
&lt;p>Nothing errored. The tunnel is up. It is bound to &lt;code>127.0.0.1&lt;/code> on the VPS, which is a perfectly good place for a listener to be if that is what you asked for, and you did not.&lt;/p>
&lt;p>That is sshd&amp;rsquo;s documented default. Remote forwards bind loopback unless &lt;code>GatewayPorts&lt;/code> is enabled, and it defaults to &lt;code>no&lt;/code>.&lt;/p>
&lt;p>Then comes the second half, which is the part that costs the extra hour. You reasonably try to force it from the client:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ssh -R 0.0.0.0:8080:localhost:80 user@vps &lt;span style="color:#75715e"># still loopback-only&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>It does not help.&lt;/p>
&lt;p>&lt;a href="https://man.openbsd.org/ssh.1" rel="noopener">&lt;code>ssh(1)&lt;/code>&lt;/a> is explicit: specifying a remote bind_address will only succeed if the server&amp;rsquo;s GatewayPorts option is enabled. Your bind address is a request, not an instruction — the server is free to override it, and by default it does exactly that, binding loopback anyway rather than refusing the forward and saying why. A refusal would have cost you thirty seconds. The override costs you the evening.&lt;/p>
&lt;p>This is documented in OpenSSH&amp;rsquo;s own tracker as &lt;a href="https://web.archive.org/web/20230325121713/https://bugzilla.mindrot.org/show_bug.cgi?id=1297" rel="noopener">bug 1297&lt;/a>, filed in 2007 by someone who noticed the socket was always bound to &lt;code>127.0.0.1&lt;/code> and &lt;code>[::1]&lt;/code> and that &lt;code>-L&lt;/code> had no such problem. The reporter then recognized the behavior as by design and asked only for feedback; OpenSSH&amp;rsquo;s Damien Miller replied that there was no clean way for the server to tell the client, so the fix was a debug message, applied in 2013 for OpenSSH 6.4. That is the shape of the confusion: local forwards obey you, remote forwards negotiate with a server whose defaults you did not read.&lt;/p>
&lt;h2 id="fixing-it-on-the-correct-side">Fixing it, on the correct side&lt;/h2>
&lt;p>On the &lt;strong>server&lt;/strong>, in &lt;code>sshd_config&lt;/code>:&lt;/p>
&lt;pre tabindex="0">&lt;code>GatewayPorts clientspecified
&lt;/code>&lt;/pre>&lt;p>Then reload sshd. Not your session. The daemon.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Warning:&lt;/strong> this lets remote forwards listen on the server&amp;rsquo;s public address, so anything you forward with an explicit bind address like &lt;code>0.0.0.0&lt;/code> can be reached from the internet unless a firewall on the server blocks it. To undo it, delete the line (the default is &lt;code>no&lt;/code>, per &lt;a href="https://man.openbsd.org/sshd_config.5" rel="noopener">sshd_config(5)&lt;/a>) and reload sshd again.&lt;/p>&lt;/blockquote>
&lt;p>I recommend &lt;code>clientspecified&lt;/code> over &lt;code>yes&lt;/code> deliberately. &lt;code>yes&lt;/code> forces remote forwards to bind the wildcard address for &lt;strong>every&lt;/strong> client on that server — a blunt, global change that removes the option of a loopback-only forward from everyone. &lt;code>clientspecified&lt;/code> gives each client the choice, so &lt;code>-R 0.0.0.0:8080:...&lt;/code> binds wide and a plain &lt;code>-R 8080:...&lt;/code> stays local.&lt;/p>
&lt;h3 id="the-two-gatewayports">The two GatewayPorts&lt;/h3>
&lt;p>Here is the detail that turns a five-minute fix into a long one, and it is purely a naming accident.&lt;/p>
&lt;p>There are &lt;strong>two&lt;/strong> &lt;code>GatewayPorts&lt;/code> options with near-identical wording:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">File&lt;/th>
&lt;th scope="col">Governs&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="File">&lt;code>sshd_config&lt;/code> (server)&lt;/td>
&lt;td data-label="Governs">&lt;code>-R&lt;/code> listeners the server opens on your behalf&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="File">&lt;code>ssh_config&lt;/code> (client)&lt;/td>
&lt;td data-label="Governs">your own &lt;code>-L&lt;/code> and &lt;code>-D&lt;/code> listeners&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>They live in different files, on different machines, and do different jobs. Editing the client one, reloading nothing, and then wondering for forty minutes why the reverse tunnel is still loopback-only is an experience I would rather you skip.&lt;/p>
&lt;p>Debugging &lt;code>-R&lt;/code>? Server file. Every time.&lt;/p>
&lt;h2 id="-l-properly">-L, properly&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ssh -L &lt;span style="color:#f92672">[&lt;/span>bind_address:&lt;span style="color:#f92672">]&lt;/span>port:host:hostport destination
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>host:hostport&lt;/code> is resolved from the server&amp;rsquo;s perspective, and that is the entire point of the flag: you are borrowing the server&amp;rsquo;s view of the network for the duration of the session, which is why it reaches things your own machine has no route to. This reaches a NAS at &lt;code>192.168.1.50&lt;/code> that your laptop cannot route to:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ssh -L 8080:192.168.1.50:80 user@homelab-gateway
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Then browse &lt;code>localhost:8080&lt;/code>. That is it.&lt;/p>
&lt;p>By default that listener binds loopback on your machine, so nobody else on the coffee-shop wifi can use your tunnel. That default is correct. Leave it.&lt;/p>
&lt;p>&lt;code>-L&lt;/code> also accepts Unix sockets on either end, which is how you reach a socket-only service like a database or a Docker daemon without publishing a TCP port for it.&lt;/p>
&lt;h2 id="-d-the-one-people-underuse">-D, the one people underuse&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ssh -D &lt;span style="color:#ae81ff">1080&lt;/span> user@server
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>That is a local SOCKS 4/5 listener. Point a browser&amp;rsquo;s SOCKS proxy at &lt;code>localhost:1080&lt;/code> and its traffic emerges from the server, with DNS resolved there too if the client is configured for remote DNS.&lt;/p>
&lt;p>I reach for this more than &lt;code>-L&lt;/code> when I am poking at a homelab, because it needs no per-service forwards. One flag, and the whole network is reachable by its internal names for as long as the session lives.&lt;/p>
&lt;p>It is not a VPN. It carries only what an application deliberately sends through the proxy, so anything not SOCKS-aware ignores it completely and silently, which is a distinction people discover at the worst possible moment. If you want everything routed, you want &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">WireGuard&lt;/a> or &lt;a href="https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/">Tailscale&lt;/a>, not this.&lt;/p>
&lt;h2 id="-j-which-is-not-a-tunnel-at-all">-J, which is not a tunnel at all&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ssh -J bastion.example.com user@internal-host
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>ProxyJump reaches a final destination &lt;em>through&lt;/em> an intermediate. Nothing is published, no listener opens, and the bastion does not see your session in cleartext — your client negotiates end-to-end with the real target.&lt;/p>
&lt;p>Keep the distinction clean.&lt;/p>
&lt;ul>
&lt;li>Administrative access to a machine behind a bastion is a &lt;strong>&lt;code>-J&lt;/code>&lt;/strong> job.&lt;/li>
&lt;li>Exposing a service is a &lt;strong>&lt;code>-L&lt;/code>&lt;/strong> or &lt;strong>&lt;code>-R&lt;/code>&lt;/strong> job.&lt;/li>
&lt;/ul>
&lt;p>I have watched people build an elaborate &lt;code>-L&lt;/code> chain for something &lt;code>-J&lt;/code> does in one flag, in &lt;code>~/.ssh/config&lt;/code>, permanently:&lt;/p>
&lt;pre tabindex="0">&lt;code>Host internal-*
ProxyJump bastion.example.com
&lt;/code>&lt;/pre>&lt;h2 id="administratively-prohibited">&amp;ldquo;administratively prohibited&amp;rdquo;&lt;/h2>
&lt;pre tabindex="0">&lt;code>channel 3: open failed: administratively prohibited
&lt;/code>&lt;/pre>&lt;p>Two things about this message. The first one saves you a search.&lt;/p>
&lt;p>First: the &lt;code>3&lt;/code> is meaningless. It is OpenSSH&amp;rsquo;s local channel id from a format string. Searching the literal message &lt;em>with the number in it&lt;/em> is why people find nothing.&lt;/p>
&lt;p>Second: it means the server refused. Almost nothing more. There are at least three distinct causes, all server-side:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>&lt;code>AllowTcpForwarding&lt;/code>&lt;/strong> in &lt;code>sshd_config&lt;/code> disallowing that direction. It takes &lt;code>local&lt;/code> and &lt;code>remote&lt;/code> as values, not just yes and no, so a server can permit &lt;code>-L&lt;/code> and refuse &lt;code>-R&lt;/code> (&lt;a href="https://man.openbsd.org/sshd_config.5" rel="noopener">sshd_config(5)&lt;/a>).&lt;/li>
&lt;li>&lt;strong>A key option in &lt;code>authorized_keys&lt;/code>&lt;/strong> — &lt;code>no-port-forwarding&lt;/code>, or &lt;code>restrict&lt;/code>, which turns everything off and then re-enables only what you name after it (&lt;a href="https://man.openbsd.org/sshd.8" rel="noopener">sshd(8)&lt;/a>).&lt;/li>
&lt;li>&lt;strong>&lt;code>permitopen&lt;/code> / &lt;code>PermitOpen&lt;/code>&lt;/strong> restricting forwards to a specific host and port list that does not include the one you asked for.&lt;/li>
&lt;/ol>
&lt;p>Check them in that order. The &lt;code>authorized_keys&lt;/code> case catches people out most often, because the server&amp;rsquo;s global config reads permissive and the restriction is sitting on the key itself, which is not where anyone looks second.&lt;/p>
&lt;h2 id="privileged-ports-behave-differently-by-direction">Privileged ports behave differently by direction&lt;/h2>
&lt;p>&lt;code>ssh(1)&lt;/code> gives two different rules, and they are easy to conflate:&lt;/p>
&lt;ul>
&lt;li>For &lt;code>-L&lt;/code>: only the superuser can forward privileged ports. That is on &lt;strong>your&lt;/strong> side.&lt;/li>
&lt;li>For &lt;code>-R&lt;/code>: privileged ports can be forwarded only when logging in as root on the remote machine. That is on &lt;strong>the server&amp;rsquo;s&lt;/strong> side.&lt;/li>
&lt;/ul>
&lt;p>So &lt;code>-R 80:localhost:8080&lt;/code> to a VPS fails unless you are logging in as root there, which you should not be. Bind something above 1024 and put a reverse proxy in front of it.&lt;/p>
&lt;h2 id="keeping-a-tunnel-alive">Keeping a tunnel alive&lt;/h2>
&lt;p>An SSH tunnel is a process. Processes die. For anything you depend on, put it under supervision rather than in a terminal you will eventually close:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-ini" data-lang="ini">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># /etc/systemd/system/tunnel.service&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">[Service]&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">ExecStart&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">/usr/bin/ssh -N -T -o ServerAliveInterval=30 -o ExitOnForwardFailure=yes \
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> -R 8080:localhost:80 user@vps&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">Restart&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">always&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#a6e22e">RestartSec&lt;/span>&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">10&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>-N&lt;/code> runs no remote command, &lt;code>-T&lt;/code> allocates no TTY. For a quick one-off rather than a service, &lt;code>ssh -f -N -R 8080:localhost:80 user@vps&lt;/code> drops into the background once the session is up; with &lt;code>ExitOnForwardFailure=yes&lt;/code> it waits until the remote forwards are established first (&lt;a href="https://man.openbsd.org/ssh.1" rel="noopener">ssh(1)&lt;/a>). If you don&amp;rsquo;t care which port the server uses, &lt;code>-R 0:localhost:80&lt;/code> has the server allocate one and report it back to the client. &lt;code>ExitOnForwardFailure=yes&lt;/code> earns its place: without it, ssh happily stays connected when a forward could not be established, and systemd sees a healthy process fronting a tunnel that carries nothing.&lt;/p>
&lt;p>&lt;code>ServerAliveInterval&lt;/code> matters because an idle tunnel crossing a NAT gateway is exactly the kind of connection a middlebox reaps without telling either end, leaving you with a socket that looks established on both sides and moves nothing.&lt;/p>
&lt;h2 id="where-this-stops-being-the-right-tool">Where this stops being the right tool&lt;/h2>
&lt;p>Reverse tunnels are the classic answer to &amp;ldquo;my home connection has no public IP&amp;rdquo; (check that first with the CGNAT test in the &lt;a href="https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/">dynamic DNS guide&lt;/a>), and for one or two services they remain a genuinely good one, because the alternative is standing up infrastructure to solve a problem that a single flag already solves. They work. I still keep one for a couple of things.&lt;/p>
&lt;p>But if you find yourself maintaining several, plus a systemd unit for each, plus &lt;code>GatewayPorts&lt;/code> on a server whose config you now have to remember, you have hand-built a worse mesh VPN. That is the point to look at &lt;a href="https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/">Tailscale or WireGuard&lt;/a>, or at &lt;a href="https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/">running the control plane yourself&lt;/a>.&lt;/p>
&lt;p>The dividing line I use is this. One or two forwards, occasional, and &lt;code>-R&lt;/code> is fine.&lt;/p>
&lt;p>More than that, or anything a household depends on, and the tunnel collection has quietly become technical debt with a systemd unit attached to each piece.&lt;/p>
&lt;h2 id="what-i-have-not-tested">What I have not tested&lt;/h2>
&lt;p>I have not verified whether a current client surfaces the loopback downgrade under &lt;code>-v&lt;/code>. OpenSSH added a debug message for this case in the 6.4 era, and I could not establish from the sources I read whether that reliably reaches a modern user&amp;rsquo;s terminal. Assume it is silent and check the listener yourself with &lt;code>ss -tlnp&lt;/code> on the server.&lt;/p>
&lt;p>I have not tested any of the &lt;code>authorized_keys&lt;/code> restriction interactions on a live sshd during this write-up, so treat the ordering advice as a plan of attack rather than a measured result.&lt;/p>
&lt;h2 id="what-getting-it-wrong-costs">What getting it wrong costs&lt;/h2>
&lt;p>The &lt;code>-R&lt;/code> trap costs an evening. That is the good outcome: you conclude nothing works, and go read the docs.&lt;/p>
&lt;p>The bad outcome is &lt;code>GatewayPorts yes&lt;/code> set globally on a server, forgotten, on a box that also hosts something else. Now every remote forward any account opens binds the wildcard address by default. Somebody tunnels an admin panel out to test something, leaves it up, and there is a listener on a public IP that nobody remembers creating.&lt;/p>
&lt;p>&lt;code>clientspecified&lt;/code> costs nothing extra and does not accumulate that debt.&lt;/p>
&lt;p>&lt;strong>Where to buy the A small VPS to be the jump host:&lt;/strong> &lt;a href="https://www.jdoqocy.com/click-101825417-17082116" rel="nofollow sponsored">Check Contabo&lt;/a> &amp;middot; &lt;a href="https://www.dpbolvw.net/click-101825417-12892698" rel="nofollow sponsored">Check Namecheap&lt;/a>. Affiliate links.&lt;/p></description></item><item><title>Glance Dashboard Setup on Windows 11 Without Docker</title><link>https://techfuelhq.com/tutorials/glance-dashboard-setup-2026/</link><pubDate>Sat, 03 Oct 2026 11:47:22 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/glance-dashboard-setup-2026/</guid><atom:updated>2026-11-18T04:49:22Z</atom:updated><description>&lt;p>Glance is a self-hosted start page: one screen for links, feeds, service checks, calendars, server statistics, and other widgets. You do &lt;strong>not&lt;/strong> need Docker to run it on Windows. The project publishes a portable Windows executable, and the official README&amp;rsquo;s Windows path is simply the executable plus a &lt;code>glance.yml&lt;/code> file in the same folder.&lt;/p>
&lt;p>The name is easy to mix up with &lt;strong>Glances&lt;/strong>, the Python system monitor. They are different projects. If you wanted the monitoring tool, use the &lt;a href="https://techfuelhq.com/homelab/beszel-vs-netdata-vs-glances-2026/">Beszel vs Netdata vs Glances comparison&lt;/a>. This guide covers &lt;code>glanceapp/glance&lt;/code>, the dashboard.&lt;/p>
&lt;p>I tested Glance v0.8.6 natively on Windows 11 Home build 26200. I verified the downloaded archive against the SHA-256 published by GitHub before running it, bound it only to loopback, exercised good and bad config reloads, and sampled the process after ten minutes. The setup below is a reduced version of that tested configuration.&lt;/p>
&lt;p>No installer was involved.&lt;/p>
&lt;p>The current release on November 18, 2026 is v0.8.8 (November 7). v0.8.7 and v0.8.8 are fix releases, and v0.8.8&amp;rsquo;s notes list fixed vulnerabilities, so download the current release; the steps and config below still apply to it per the v0.8.8 README and configuration reference.&lt;/p>
&lt;h2 id="1-download-the-official-windows-build">1. Download the official Windows build&lt;/h2>
&lt;p>Open the &lt;a href="https://github.com/glanceapp/glance/releases/latest" rel="noopener">latest Glance release&lt;/a> and download the Windows archive that matches your CPU. For a typical 64-bit Intel or AMD Windows PC, that is &lt;code>glance-windows-amd64.zip&lt;/code>.&lt;/p>
&lt;p>Create a folder that you own, such as &lt;code>C:\Tools\Glance&lt;/code>, and extract the archive there. Keep the downloaded ZIP until you verify it.&lt;/p>
&lt;p>In PowerShell, move to the folder containing the ZIP and calculate its hash:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>Get-FileHash .\glance-windows-amd64.zip -Algorithm SHA256
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>GitHub lists a SHA-256 digest beside each release asset. For &lt;a href="https://github.com/glanceapp/glance/releases/tag/v0.8.8" rel="noopener">v0.8.8&lt;/a>, &lt;code>glance-windows-amd64.zip&lt;/code> is listed as:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>e14a9efccb845e9f6abce363302eafdc915a8cb348be1d8423269b75ef66bfe7
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>For v0.8.6, my downloaded archive and GitHub&amp;rsquo;s API both returned:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>e92ca602a1b807f00310b1b70c8271fe779001a5648bb4a13e0f50e81355076c
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Match the whole value, character for character. When a newer release replaces the one you downloaded, use the digest attached to that release rather than reusing one of these.&lt;/p>
&lt;p>After extraction, confirm the executable before configuring anything:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>Set-Location C:\Tools\Glance
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>.\glance.exe --version
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The tested binary printed &lt;code>v0.8.6&lt;/code>.&lt;/p>
&lt;h2 id="2-create-a-local-only-glanceyml">2. Create a local-only glance.yml&lt;/h2>
&lt;p>Create &lt;code>glance.yml&lt;/code> beside &lt;code>glance.exe&lt;/code> and paste this configuration:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">server&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">host&lt;/span>: &lt;span style="color:#ae81ff">127.0.0.1&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">port&lt;/span>: &lt;span style="color:#ae81ff">8080&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">branding&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">app-name&lt;/span>: &lt;span style="color:#ae81ff">Windows Glance&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">pages&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">name&lt;/span>: &lt;span style="color:#ae81ff">Home&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">width&lt;/span>: &lt;span style="color:#ae81ff">wide&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">columns&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">size&lt;/span>: &lt;span style="color:#ae81ff">small&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">widgets&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">type&lt;/span>: &lt;span style="color:#ae81ff">clock&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">hour-format&lt;/span>: &lt;span style="color:#ae81ff">12h&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">type&lt;/span>: &lt;span style="color:#ae81ff">calendar&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">first-day-of-week&lt;/span>: &lt;span style="color:#ae81ff">monday&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">size&lt;/span>: &lt;span style="color:#ae81ff">full&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">widgets&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">type&lt;/span>: &lt;span style="color:#ae81ff">monitor&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">title&lt;/span>: &lt;span style="color:#ae81ff">Local services&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">cache&lt;/span>: &lt;span style="color:#ae81ff">1m&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">sites&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">title&lt;/span>: &lt;span style="color:#ae81ff">Glance&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">url&lt;/span>: &lt;span style="color:#ae81ff">http://127.0.0.1:8080/&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">type&lt;/span>: &lt;span style="color:#ae81ff">server-stats&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">servers&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">type&lt;/span>: &lt;span style="color:#ae81ff">local&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">name&lt;/span>: &lt;span style="color:#ae81ff">Windows PC&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This is intentionally smaller than the project&amp;rsquo;s example dashboard. It gives you a clock, calendar, loopback health check, and Windows server statistics without credentials, outside feeds, or Docker.&lt;/p>
&lt;p>The &lt;code>host: 127.0.0.1&lt;/code> line is the safety boundary. Glance&amp;rsquo;s &lt;a href="https://github.com/glanceapp/glance/blob/v0.8.8/docs/configuration.md#server" rel="noopener">server configuration&lt;/a> says the host controls which address the server listens on and that its default is all interfaces. Loopback keeps this first run on your PC. Do not remove that line just to make another device connect; exposing a dashboard to the LAN is a separate access and firewall decision.&lt;/p>
&lt;p>If you later decide that phones, tablets, or another workstation should reach this page, choose the listening address and Windows Firewall scope together, test from the intended client, and confirm that the dashboard is still unreachable from networks that were never meant to see it. For access away from home without opening a router port, our &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale guide&lt;/a> covers the private-network route.&lt;/p>
&lt;p>Validate the file before starting the server:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>.\glance.exe --config .\glance.yml config&lt;span style="color:#960050;background-color:#1e0010">:&lt;/span>validate
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>A valid file returns to the prompt without an error. To inspect the fully resolved config, use:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>.\glance.exe --config .\glance.yml config&lt;span style="color:#960050;background-color:#1e0010">:&lt;/span>print
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="3-start-glance-and-open-the-dashboard">3. Start Glance and open the dashboard&lt;/h2>
&lt;p>Run the executable from the same folder:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>.\glance.exe
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The console should report that the server is starting on &lt;code>127.0.0.1:8080&lt;/code>. Leave that window open, then visit:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>http://127.0.0.1:8080/
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Keep the console visible; Glance reports bad edits there.&lt;/p>
&lt;p>The &lt;a href="https://github.com/glanceapp/glance/blob/v0.8.8/README.md#windows" rel="noopener">official Windows instructions&lt;/a> use the same executable-and-config arrangement and point the browser at port 8080. This guide keeps that arrangement but supplies a smaller config and explicitly binds the server to loopback.&lt;/p>
&lt;p>If you prefer to keep the config elsewhere, pass its path every time you start Glance:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>.\glance.exe --config D:\Dashboard\glance.yml
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This guide stops at a portable manual launch. I did not install Glance as a Windows service, create a scheduled task, or add an autostart entry during the capture, so I am not presenting any of those as tested steps.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s documented Startup-folder method for launching it at sign-in is in the FAQ below, marked untested.&lt;/p>
&lt;h2 id="what-the-native-windows-run-measured">What the native Windows run measured&lt;/h2>
&lt;p>These numbers describe one capture on one PC. They are useful for sizing this small dashboard, but they are not a cross-machine benchmark.&lt;/p>
&lt;p>The browser run used an isolated Playwright Chromium context that allowed only &lt;code>127.0.0.1&lt;/code> and &lt;code>localhost&lt;/code>, was configured to abort every other destination before request dispatch, and recorded zero external requests, failed requests, console errors, or page errors while the complete dashboard fit a 1440-pixel viewport without horizontal overflow.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Check&lt;/th>
&lt;th scope="col">Glance v0.8.6 result&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Check">Official archive&lt;/td>
&lt;td data-label="Glance v0.8.6 result">&lt;code>glance-windows-amd64.zip&lt;/code>, 6,518,780 bytes&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Check">SHA-256&lt;/td>
&lt;td data-label="Glance v0.8.6 result">&lt;code>e92ca602a1b807f00310b1b70c8271fe779001a5648bb4a13e0f50e81355076c&lt;/code>, matched GitHub&amp;rsquo;s release API&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Check">Process start to first HTTP 200&lt;/td>
&lt;td data-label="Glance v0.8.6 result">565.4 ms&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Check">Working set at 35.8 seconds&lt;/td>
&lt;td data-label="Glance v0.8.6 result">19.07 MiB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Check">Private memory at 35.8 seconds&lt;/td>
&lt;td data-label="Glance v0.8.6 result">53.24 MiB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Check">Working set at 603.2 seconds&lt;/td>
&lt;td data-label="Glance v0.8.6 result">25.64 MiB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Check">Private memory at 603.2 seconds&lt;/td>
&lt;td data-label="Glance v0.8.6 result">58.52 MiB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Check">CPU time at 603.2 seconds&lt;/td>
&lt;td data-label="Glance v0.8.6 result">2.234 seconds&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Check">Browser check&lt;/td>
&lt;td data-label="Glance v0.8.6 result">HTTP 200, no console or page errors, no external requests&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The dashboard rendered CPU, RAM, and disk use from the Windows host. It did not render a CPU temperature. The Docker widget failed because the native machine had no Docker socket. Both outcomes are covered below rather than hidden behind a perfect-looking screenshot.&lt;/p>
&lt;h2 id="4-edit-the-dashboard-while-it-is-running">4. Edit the dashboard while it is running&lt;/h2>
&lt;p>Glance watches the configuration file. Save a valid change and refresh the browser if the visible page has not already updated, then check the console.&lt;/p>
&lt;p>The official &lt;a href="https://github.com/glanceapp/glance/blob/v0.8.8/docs/configuration.md#auto-reload" rel="noopener">auto-reload documentation&lt;/a> says a valid save takes effect without restarting the process. It also says a bad live edit logs an error and leaves the old configuration running.&lt;/p>
&lt;p>That is what happened in the Windows capture:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Save operation&lt;/th>
&lt;th scope="col" style="text-align: right">New page visible after&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Save operation">In-place file write&lt;/td>
&lt;td style="text-align: right" data-label="New page visible after">606.6 ms&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Save operation">Atomic file replacement&lt;/td>
&lt;td style="text-align: right" data-label="New page visible after">638.8 ms&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Save operation">Invalid live config&lt;/td>
&lt;td style="text-align: right" data-label="New page visible after">Error logged after 632.5 ms; old page stayed HTTP 200&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Save operation">Valid config restored&lt;/td>
&lt;td style="text-align: right" data-label="New page visible after">Recovered after 657.9 ms&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The capture exercised an in-place write and an atomic file replacement. I did not drive Notepad or VS Code during the test, so the evidence supports Glance&amp;rsquo;s file reload behavior, not an editor-specific promise.&lt;/p>
&lt;p>Reloading also clears Glance&amp;rsquo;s cached widget data. The official configuration reference warns that frequent reloads can cause APIs to rate-limit repeated requests. Finish a group of edits before saving when a page pulls several outside feeds.&lt;/p>
&lt;h2 id="5-add-service-checks-without-mistaking-them-for-alerts">5. Add service checks without mistaking them for alerts&lt;/h2>
&lt;p>The monitor widget sends a GET request and treats HTTP 200 as healthy; its &lt;code>alt-status-codes&lt;/code> option lets other codes count as healthy too (the docs&amp;rsquo; example is &lt;code>403&lt;/code>). Add another entry under &lt;code>sites&lt;/code> when a local service is ready, such as the &lt;a href="https://techfuelhq.com/tutorials/jellyfin-setup-docker-homelab-2026/">Jellyfin server from our Docker guide&lt;/a> on port 8096 or an &lt;a href="https://techfuelhq.com/tutorials/audiobookshelf-docker-setup-2026/">Audiobookshelf&lt;/a> instance:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">title&lt;/span>: &lt;span style="color:#ae81ff">Jellyfin&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">url&lt;/span>: &lt;span style="color:#ae81ff">http://127.0.0.1:8096/&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Use an address reachable from the Glance process. A green result means that one request succeeded from this Windows PC. It does not prove that the service is reachable from outside your network, and Glance cannot report a whole-PC or whole-network outage while the machine running Glance is down.&lt;/p>
&lt;p>That is the same placement limit covered in the &lt;a href="https://techfuelhq.com/tutorials/uptime-kuma-docker-setup-2026/">Uptime Kuma setup guide&lt;/a>. Treat the Glance monitor as a convenient status panel. Use a separately placed monitor when you need alerts or an outside view.&lt;/p>
&lt;h2 id="6-understand-the-windows-widget-gaps">6. Understand the Windows widget gaps&lt;/h2>
&lt;h3 id="server-stats-has-no-temperature">Server stats has no temperature&lt;/h3>
&lt;p>The &lt;code>server-stats&lt;/code> widget rendered CPU, RAM, and disk percentages in the native test. Temperature was absent. Running the sensor command produced:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>.\glance.exe sensors&lt;span style="color:#960050;background-color:#1e0010">:&lt;/span>print
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>Failed to retrieve sensor information: Exception occurred. (Not supported )
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>That is expected on the tested host.&lt;/p>
&lt;p>Glance&amp;rsquo;s server-stats documentation says temperature is omitted when the widget cannot find a suitable sensor. The missing number did not stop the other Windows statistics from rendering.&lt;/p>
&lt;h3 id="docker-containers-shows-a-socket-error">Docker Containers shows a socket error&lt;/h3>
&lt;p>Do not add this widget to a no-Docker setup:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>- &lt;span style="color:#f92672">type&lt;/span>: &lt;span style="color:#ae81ff">docker-containers&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The &lt;a href="https://github.com/glanceapp/glance/blob/v0.8.8/docs/configuration.md#docker-containers" rel="noopener">Docker Containers reference&lt;/a> says the widget requires access to &lt;code>docker.sock&lt;/code> and defaults to &lt;code>/var/run/docker.sock&lt;/code>. On the native Windows machine, it tried that Unix path and returned a socket error. Removing the widget is the correct fix when you do not run Docker.&lt;/p>
&lt;p>If your goal is managing Compose stacks rather than displaying a home page, Glance is the wrong layer. &lt;a href="https://techfuelhq.com/tutorials/dockge-docker-compose-manager-2026/">Dockge manages Compose files&lt;/a>; Glance links to services and summarizes them.&lt;/p>
&lt;h2 id="fix-three-captured-startup-failures">Fix three captured startup failures&lt;/h2>
&lt;h3 id="glance-says-glanceyml-is-missing">Glance says glance.yml is missing&lt;/h3>
&lt;p>Running v0.8.6 from an empty folder returned exit code 1 and this exact message:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>parsing config: reading glance.yml: open glance.yml: The system cannot find the file specified.
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Put &lt;code>glance.yml&lt;/code> beside the executable or pass the full path with &lt;code>--config&lt;/code>.&lt;/p>
&lt;h3 id="glance-logs-a-config-error-but-the-exit-code-is-zero">Glance logs a config error but the exit code is zero&lt;/h3>
&lt;p>In this Windows capture, a file containing only &lt;code>pages: []&lt;/code> logged:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>Config has errors: no pages configured
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>That specific invalid run returned exit code 0. Do not use the process exit code alone as proof that a config is valid. Read the console and run &lt;code>config:validate&lt;/code> before starting the dashboard.&lt;/p>
&lt;h3 id="the-browser-cannot-connect">The browser cannot connect&lt;/h3>
&lt;p>First check that the Glance console is still open and that its start line names the same host and port you entered in the browser. Then inspect the listener:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>Get-NetTCPConnection -LocalPort &lt;span style="color:#ae81ff">8080&lt;/span> -State Listen
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>With the config above, the local address should be &lt;code>127.0.0.1&lt;/code>. If another process already owns 8080, select another unused port in both &lt;code>server.port&lt;/code> and the Glance self-check URL.&lt;/p>
&lt;h2 id="if-you-run-docker-instead">If you run Docker instead&lt;/h2>
&lt;p>The README&amp;rsquo;s recommended install is Docker Compose. The capture above covers only the native Windows run, so this route comes from the &lt;a href="https://github.com/glanceapp/glance/blob/v0.8.8/README.md" rel="noopener">v0.8.8 README&lt;/a> rather than from that test. Its manual Compose file, with the image pinned to the &lt;code>v0.8.8&lt;/code> tag (on Docker Hub as of November 18, 2026) and the port limited to the host:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">glance&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">container_name&lt;/span>: &lt;span style="color:#ae81ff">glance&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">glanceapp/glance:v0.8.8&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">restart&lt;/span>: &lt;span style="color:#ae81ff">unless-stopped&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">volumes&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./config:/app/config&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ports&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#e6db74">&amp;#34;127.0.0.1:8080:8080&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;blockquote>
&lt;p>&lt;strong>Warning:&lt;/strong> the README publishes &lt;code>8080:8080&lt;/code>, which Docker exposes on every host interface; Docker&amp;rsquo;s own docs call published ports insecure by default. The &lt;code>127.0.0.1:&lt;/code> prefix keeps the dashboard on the Docker host.&lt;/p>&lt;/blockquote>
&lt;p>Then fetch the starting config and start it, as the README does:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>mkdir config &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span> wget -O config/glance.yml https://raw.githubusercontent.com/glanceapp/glance/refs/heads/main/docs/glance.yml
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose up -d
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker logs glance
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Use that starting &lt;code>glance.yml&lt;/code> rather than this guide&amp;rsquo;s Windows config: it has no &lt;code>server&lt;/code> block, so Glance listens on all interfaces inside the container (its documented default) and the &lt;code>127.0.0.1:&lt;/code> publish rule does the limiting.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Warning:&lt;/strong> the Docker Containers widget needs the Docker socket, and Glance&amp;rsquo;s docs show mounting &lt;code>/var/run/docker.sock&lt;/code> into the container for it. Docker says only trusted users should be allowed to control its daemon, and that socket is the control socket the Docker CLI uses to drive the daemon. Glance&amp;rsquo;s &lt;code>sock-path&lt;/code> option can point at a proxied socket such as docker-socket-proxy instead, the narrower route its docs name.&lt;/p>&lt;/blockquote>
&lt;h2 id="the-setup-i-would-keep">The setup I would keep&lt;/h2>
&lt;p>Keep the native dashboard small at first: clock, calendar, local server stats, and a handful of service links. Leave it on loopback until you have a deliberate remote-access design. Remove widgets whose dependencies do not exist on the Windows host rather than accepting a permanent red error card.&lt;/p>
&lt;p>Glance v0.8.6 was quick to start and stayed modest in this capture, but the more useful result was failure behavior: a bad live edit preserved the last valid page, missing temperature did not break CPU/RAM/disk, and the Docker widget failed loudly instead of pretending the socket existed. Those are the boundaries that make the dashboard predictable.&lt;/p></description></item><item><title>Jellyfin Remote Access: Pick the Right Path for Your Situation (2026)</title><link>https://techfuelhq.com/tutorials/jellyfin-remote-access-2026/</link><pubDate>Tue, 25 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/jellyfin-remote-access-2026/</guid><atom:updated>2026-11-18T04:49:22Z</atom:updated><description>&lt;p>Jellyfin does not have a relay. That single architecture fact generates the question this page answers. When a Plex user hits play from a hotel, Plex&amp;rsquo;s own infrastructure brokers the connection; when Plex put that convenience behind a paywall in 2025, the &lt;a href="https://techfuelhq.com/articles/jellyfin-vs-plex-2026/">migration wave toward Jellyfin&lt;/a> began, and every migrant hit the same wall about a week in.&lt;/p>
&lt;p>Jellyfin gives you a remote-access switch and leaves the actual path from the outside world to your basement entirely to you. Its own networking docs say so plainly: since Jellyfin is entirely self-hosted, you must expose it to the internet yourself.&lt;/p>
&lt;p>The r/jellyfin community answers this question so often that one post is literally titled &lt;a href="https://www.reddit.com/r/jellyfin/comments/1vtff2e/im_kinda_tired_of_the_constant_remote_access/" rel="noopener">&amp;ldquo;I&amp;rsquo;m kinda tired of the constant remote access questions&amp;rdquo;&lt;/a>. Listing the options was never the hard part. Matching one to your situation is. So this guide routes first, then gives the setup and a test for each path.&lt;/p>
&lt;div class="verdict-card">
&lt;p>&lt;strong>TL;DR · Route yourself before reading anything else&lt;/strong>&lt;/p>
&lt;table>
&lt;thead>&lt;tr>&lt;th>Your situation&lt;/th>&lt;th>Use this&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody>
&lt;tr>&lt;td>Just you, on your own phone and laptop&lt;/td>&lt;td>&lt;strong>Tailscale&lt;/strong> (Path 1)&lt;/td>&lt;/tr>
&lt;tr>&lt;td>You + household, every device can install apps&lt;/td>&lt;td>&lt;strong>Tailscale&lt;/strong>, apps on each device (Path 1)&lt;/td>&lt;/tr>
&lt;tr>&lt;td>Family elsewhere, watching on smart TVs&lt;/td>&lt;td>&lt;strong>Reverse proxy + your own domain&lt;/strong> (Path 2)&lt;/td>&lt;/tr>
&lt;tr>&lt;td>Family elsewhere on TVs, but your ISP uses CGNAT&lt;/td>&lt;td>&lt;strong>VPS relay: Pangolin or WireGuard bounce&lt;/strong> (Path 3)&lt;/td>&lt;/tr>
&lt;tr>&lt;td>Non-technical viewers who will not install anything&lt;/td>&lt;td>&lt;strong>Reverse proxy&lt;/strong> - a URL in a browser is the only universal client (Path 2 or 3)&lt;/td>&lt;/tr>
&lt;tr>&lt;td>Hotel room / a TV you do not own&lt;/td>&lt;td>&lt;strong>Travel streaming stick with Tailscale&lt;/strong>, or laptop + HDMI (device table below)&lt;/td>&lt;/tr>
&lt;tr>&lt;td>Roku in another house&lt;/td>&lt;td>&lt;strong>Reverse proxy or VPS relay&lt;/strong> - no Tailscale client exists for Roku&lt;/td>&lt;/tr>
&lt;tr>&lt;td>Tempted by Cloudflare Tunnel because it is free&lt;/td>&lt;td>&lt;strong>Read Path 4 first&lt;/strong> - video streaming sits against Cloudflare's CDN terms&lt;/td>&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="why-just-use-tailscale-keeps-failing-people">Why &amp;ldquo;just use Tailscale&amp;rdquo; keeps failing people&lt;/h2>
&lt;p>Tailscale is the default answer in every thread, and for the person asking, it is usually right. It is also the answer I give for a solo setup, so this is not a takedown. The failures cluster in one place: &lt;strong>the devices you do not control.&lt;/strong>&lt;/p>
&lt;p>Tailscale reaches a device by running a client on it. TV coverage is better than most people assume: the &lt;a href="https://tailscale.com/docs/install/android" rel="noopener">Android client&lt;/a> installs from the Play Store on Android TV, there is an &lt;a href="https://tailscale.com/docs/install/appletv" rel="noopener">Apple TV app&lt;/a> for tvOS 17 or later, and &lt;a href="https://tailscale.com/docs/install/amazon-fire" rel="noopener">Fire TV&lt;/a> works with a catch. Tailscale is not available in the Amazon Appstore, so on a Fire TV you install the Android APK from Tailscale&amp;rsquo;s package server and apply updates by hand, and devices on Fire OS 5 or 6 or on Vega OS (the Fire TV Stick 4K Select among them) are not supported.&lt;/p>
&lt;p>But Tailscale&amp;rsquo;s &lt;a href="https://tailscale.com/docs/install" rel="noopener">supported-platform list&lt;/a> ends there for TVs. No Roku. No LG webOS. No Samsung Tizen. Jellyfin ships &lt;a href="https://jellyfin.org/downloads/clients/" rel="noopener">official apps for all three&lt;/a>, so the missing piece is the network path. Your mother-in-law&amp;rsquo;s Roku can run Jellyfin; it cannot run your VPN.&lt;/p>
&lt;p>The second failure is human. A tailnet wants an account relationship with every participant: you either share devices to their Tailscale account or manage logins for them. For a household that tolerates you, fine. For the relative who calls when the TV &amp;ldquo;stopped working,&amp;rdquo; each moving part you added is a future phone call.&lt;/p>
&lt;p>The long-thread version of this complaint is &lt;a href="https://www.reddit.com/r/jellyfin/comments/1tu1tvy/" rel="noopener">&amp;ldquo;I&amp;rsquo;m eyeing Jellyfin (currently use Plex w/ a Lifetime pass)&amp;rdquo;&lt;/a>, a holder of the old Plex deal asking whether Jellyfin can match that remote simplicity for non-technical family - and the answer is: only if you build the path that needs nothing installed, which is Path 2.&lt;/p>
&lt;p>So run Tailscale when you control the endpoints, and something with a plain HTTPS URL when you do not.&lt;/p>
&lt;h2 id="path-1-tailscale-or-another-mesh-vpn">Path 1: Tailscale (or another mesh VPN)&lt;/h2>
&lt;p>This is the path for you, your own devices, and a household that installs apps. It costs $0. The free &lt;a href="https://tailscale.com/pricing" rel="noopener">Personal plan&lt;/a> covers up to 6 users with unlimited devices, which is most homes.&lt;/p>
&lt;p>Setup, per &lt;a href="https://jellyfin.org/docs/general/post-install/networking/tailscale/" rel="noopener">Jellyfin&amp;rsquo;s own Tailscale page&lt;/a>:&lt;/p>
&lt;ol>
&lt;li>Install Tailscale on the Jellyfin server and sign in to your tailnet (&lt;code>sudo tailscale up&lt;/code> on Linux, the tray icon on Windows and macOS).&lt;/li>
&lt;li>Note the server&amp;rsquo;s Tailscale address. It starts with 100, for example &lt;code>100.12.34.56&lt;/code>.&lt;/li>
&lt;li>Install Tailscale on each viewing device and sign in to the same tailnet.&lt;/li>
&lt;li>In the Jellyfin app or a browser on that device, connect to &lt;code>http://100.12.34.56:8096&lt;/code> (your server&amp;rsquo;s address).&lt;/li>
&lt;/ol>
&lt;p>Nothing on your router changes and no port opens. Our &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale homelab guide&lt;/a> covers sharing and access rules, and the &lt;a href="https://techfuelhq.com/tutorials/jellyfin-setup-docker-homelab-2026/">Jellyfin Docker guide&lt;/a> covers the server side in Step 6. Traffic stays WireGuard-encrypted end to end, nothing is exposed to the internet, and CGNAT does not matter because every connection is outbound.&lt;/p>
&lt;p>Two caveats. Battery and cellular behavior on phones is solved, but every viewer&amp;rsquo;s device must keep its VPN toggled on, and the failure mode when it silently is not - &amp;ldquo;your server is down&amp;rdquo; - lands on you. And if you would rather self-host the coordination server too, that is &lt;a href="https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/">Headscale&lt;/a>, with the same client math. &lt;a href="https://techfuelhq.com/networking/netbird-vs-tailscale-2026/">NetBird is the other mesh VPN&lt;/a> worth comparing if you want to own the control plane.&lt;/p>
&lt;p>Do not confuse this path with Tailscale Funnel, which publishes a tailnet service to the open internet through Tailscale&amp;rsquo;s relays. Tailscale &lt;a href="https://tailscale.com/docs/features/tailscale-funnel" rel="noopener">documents Funnel traffic as subject to non-configurable bandwidth limits&lt;/a> - a constraint that rules it out for pushing video at your family every evening.&lt;/p>
&lt;h2 id="path-2-reverse-proxy--your-own-domain">Path 2: Reverse proxy + your own domain&lt;/h2>
&lt;p>This is the path for family on TVs and for viewers who install nothing, because any client with a browser or a Jellyfin app that accepts a URL can reach it. It needs a public IPv4 address and ports 80/443 forwarded on your router. The only recurring cost is an ordinary domain registration, since the proxy automates a free Let&amp;rsquo;s Encrypt TLS certificate.&lt;/p>
&lt;p>This is the path I validated end to end while writing this guide, on a bare Windows box with no Docker, because the claim &amp;ldquo;a reverse proxy in front of Jellyfin is fiddly&amp;rdquo; deserved a test. It is not fiddly anymore. The sequence, timed:&lt;/p>
&lt;ol>
&lt;li>Jellyfin 10.11.11 portable zip unpacked to a folder and started: &lt;strong>about three minutes&lt;/strong> from download to a listening server on port 8096. No installer, no admin rights.&lt;/li>
&lt;li>The setup wizard&amp;rsquo;s &lt;em>Set up Remote Access&lt;/em> screen shows one checkbox — &lt;strong>Allow remote connections to this server&lt;/strong> — already checked by default. I verified the shipped network config afterward through the API: remote access on, UPnP &lt;strong>off&lt;/strong>, HTTPS &lt;strong>off&lt;/strong>, Known Proxies empty. Jellyfin never opens your router for you and never brings its own TLS - both are deliberately your job, and both are exactly what the proxy provides.&lt;/li>
&lt;li>&lt;a href="https://caddyserver.com/" rel="noopener">Caddy&lt;/a> as the proxy, one binary, and the entire working config is this:&lt;/li>
&lt;/ol>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>media.yourdomain.com {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> reverse_proxy 127.0.0.1:8096
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>}
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>That is the whole file. With a real domain pointed at your IP, Caddy obtains and renews the Let&amp;rsquo;s Encrypt certificate on its own. Against my local instance I watched the three things that historically break proxied Jellyfin all come back clean: the web client served, logins authenticated, and the websocket upgrade returned &lt;code>101 Switching Protocols&lt;/code> with &lt;strong>zero&lt;/strong> websocket-specific configuration.&lt;/p>
&lt;p>That last one matters because Jellyfin&amp;rsquo;s &lt;a href="https://jellyfin.org/docs/general/post-install/networking/reverse-proxy/" rel="noopener">reverse-proxy docs&lt;/a> warn that not every proxy passes websockets by default - nginx wants explicit upgrade headers, and the equivalent toggle is the classic missed step in Nginx Proxy Manager. Caddy is also what Jellyfin&amp;rsquo;s own docs recommend first, &amp;ldquo;for its ease of use.&amp;rdquo; On the same evidence, I concur. (Choosing between Caddy, NPM, and Traefik is &lt;a href="https://techfuelhq.com/homelab/caddy-vs-nginx-proxy-manager-vs-traefik-2026/">its own comparison&lt;/a>.)&lt;/p>
&lt;p>One Windows-specific wrinkle from the test worth passing on: Caddy&amp;rsquo;s self-signed local mode pauses on an interactive certificate-trust prompt. Irrelevant for the real deployment - public certificates involve no local trust store - but if you dry-run with &lt;code>local_certs&lt;/code> first, expect that prompt.&lt;/p>
&lt;p>Two settings finish the job properly. Add the proxy&amp;rsquo;s IP to &lt;strong>Known Proxies&lt;/strong> in Jellyfin&amp;rsquo;s networking settings, or every viewer shows up in your logs as the proxy&amp;rsquo;s address instead of their own - the docs flag this, and the fresh-install default I captured (empty list) means it is always on you to set.&lt;/p>
&lt;p>And leave Jellyfin itself listening on plain 8096 bound to localhost or the LAN; the proxy is the only thing that should face the world. &lt;strong>Never forward 8096 directly&lt;/strong> - that is unencrypted HTTP with your login page on it, and it is the port-forward horror story the community warnings are actually about.&lt;/p>
&lt;p>What kills this path is not skill. It is &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">CGNAT&lt;/a> - if your ISP does not give you a real public IPv4, no amount of &lt;a href="https://techfuelhq.com/networking/port-forwarding-2026/">port forwarding&lt;/a> helps, and dynamic-DNS tricks change nothing. Check before you buy a domain. If your router&amp;rsquo;s WAN address falls in the 100.64.x-100.127.x range (&lt;a href="https://www.rfc-editor.org/rfc/rfc6598" rel="noopener">RFC 6598 shared address space&lt;/a>), or the &amp;ldquo;what is my IP&amp;rdquo; number differs from the router&amp;rsquo;s WAN number, you are CGNATed and you want Path 3.&lt;/p>
&lt;h3 id="path-2-step-by-step">Path 2, step by step&lt;/h3>
&lt;blockquote>
&lt;p>&lt;strong>Warning:&lt;/strong> forwarding 80 and 443 puts Jellyfin&amp;rsquo;s login page on the internet. If only your own devices need access, Path 1 is the option Jellyfin&amp;rsquo;s docs list for opening no ports at all.&lt;/p>&lt;/blockquote>
&lt;ol>
&lt;li>&lt;strong>Confirm a public IPv4&lt;/strong> with the CGNAT check above. Behind CGNAT, stop here and go to Path 3.&lt;/li>
&lt;li>&lt;strong>Point a name at your home.&lt;/strong> At your DNS provider, create an A record (AAAA for IPv6) for &lt;code>media.yourdomain.com&lt;/code> with your public IP. Caddy&amp;rsquo;s and Jellyfin&amp;rsquo;s guides both start here. If your ISP changes your address from time to time, a dynamic DNS client keeps the record current; our &lt;a href="https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/">dynamic DNS guide&lt;/a> covers ddclient, Docker and OPNsense setups.&lt;/li>
&lt;li>&lt;strong>Forward TCP 80 and 443 on the router to the machine running Caddy&lt;/strong>, not to Jellyfin. Add UDP 443 if you want HTTP/3, as Jellyfin&amp;rsquo;s docs note. Caddy needs both TCP ports reachable from outside to complete its default Let&amp;rsquo;s Encrypt challenges.&lt;/li>
&lt;li>&lt;strong>Start Caddy with the Caddyfile above.&lt;/strong> &lt;code>127.0.0.1:8096&lt;/code> is right only when Caddy and Jellyfin run on the same machine; otherwise use the Jellyfin server&amp;rsquo;s LAN address, as Jellyfin&amp;rsquo;s proxy guide does with its &lt;code>SERVER_IP_ADDRESS&lt;/code> placeholder. Caddy&amp;rsquo;s one-line equivalent is &lt;code>caddy reverse-proxy --from media.yourdomain.com --to 127.0.0.1:8096&lt;/code>.&lt;/li>
&lt;li>&lt;strong>In Jellyfin, add the proxy&amp;rsquo;s address to Known Proxies&lt;/strong> and check that remote access is allowed under Networking &amp;gt; Remote Access Settings. Jellyfin&amp;rsquo;s docs warn that remote-access settings behind a proxy only work once Known Proxies is set correctly.&lt;/li>
&lt;li>&lt;strong>Test from outside&lt;/strong> with the check below.&lt;/li>
&lt;/ol>
&lt;h2 id="path-3-vps-relay---the-cgnat-escape-hatch">Path 3: VPS relay - the CGNAT escape hatch&lt;/h2>
&lt;p>This fits everything Path 2 fits, for the case where the ISP will not give you a public IP or you refuse to open home ports. The going figure in &lt;a href="https://www.reddit.com/r/jellyfin/comments/1uqgqil/" rel="noopener">the community threads&lt;/a> is about &lt;strong>$5/month&lt;/strong> for a small VPS.&lt;/p>
&lt;p>The idea is to rent the public IP you do not have. A minimal VPS gets the public endpoint; your home server connects outward to it; visitor traffic enters the VPS and rides that outbound tunnel home. Jellyfin&amp;rsquo;s networking docs list this shape, a VPS reverse-proxying to your home network, among the common ways to expose a server. Three implementations, in ascending order of hand-holding:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>WireGuard bounce&lt;/strong> - the DIY version. WireGuard on both ends, forwarding rules on the VPS. Full control, most assembly; our &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">WireGuard on Proxmox guide&lt;/a> covers the VPN half. Jellyfin&amp;rsquo;s Tailscale page also shows a variant: Tailscale between the VPS and home, Caddy on the VPS pointing at the server&amp;rsquo;s 100.x address, and the VPS&amp;rsquo;s Tailscale address in Known Proxies.&lt;/li>
&lt;li>&lt;strong>FRP&lt;/strong> (fast reverse proxy) - the same shape with a purpose-built tool, popular in the budget threads.&lt;/li>
&lt;li>&lt;strong>&lt;a href="https://github.com/fosrl/pangolin" rel="noopener">Pangolin&lt;/a>&lt;/strong> - the reason this section is not just &amp;ldquo;run WireGuard.&amp;rdquo; It is a WireGuard-based, identity-aware tunneled reverse proxy: dashboard, per-app authentication, Let&amp;rsquo;s Encrypt handling, all self-hosted. Its &lt;a href="https://docs.pangolin.net/self-host/quick-install" rel="noopener">own requirements&lt;/a> state the deal plainly: a Linux server with a public IP, a domain, and ports 80/443 (TCP) plus 51820/21820 (UDP). Pangolin&amp;rsquo;s cloud &lt;a href="https://www.pangolin.net/pricing" rel="noopener">Basic plan is free&lt;/a> for up to 5 users and 5 sites if you want to try the model before renting anything.&lt;/li>
&lt;/ul>
&lt;p>The trade nobody advertises: every stream now transits the VPS, so your remote picture quality is capped by the VPS provider&amp;rsquo;s bandwidth and your home upload, whichever is worse. Budget VPS bandwidth caps are real; check the fine print against your bitrates before moving the family movie night onto one.&lt;/p>
&lt;h2 id="path-4-cloudflare-tunnel---free-easy-and-built-on-someone-elses-tolerance">Path 4: Cloudflare Tunnel - free, easy, and built on someone else&amp;rsquo;s tolerance&lt;/h2>
&lt;p>Cloudflare Tunnel deserves its reputation for polish: outbound-only connector, free HTTPS URL, CGNAT-proof, no client software for viewers. For a wiki or a dashboard I recommend it without hesitation - the &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">full comparison against Tailscale&lt;/a> covers where it shines.&lt;/p>
&lt;p>For Jellyfin specifically, read the terms before you build on it.&lt;/p>
&lt;p>Cloudflare&amp;rsquo;s &lt;a href="https://www.cloudflare.com/service-specific-terms-application-services/" rel="noopener">service-specific terms&lt;/a> (last updated September 28, 2026; read November 18, 2026) state that unless you are an Enterprise customer, &amp;ldquo;Cloudflare offers specific Paid Services (e.g., the Developer Platform, Images, and Stream) that you must use in order to serve video and other large files via the CDN,&amp;rdquo; and that Cloudflare &amp;ldquo;reserves the right to disable or limit your access to or use of the CDN&amp;rdquo; if you serve &amp;ldquo;video or a disproportionate percentage of pictures, audio files, or other large files&amp;rdquo; without them.&lt;/p>
&lt;p>Streaming your library through a free tunnel is exactly that. The record supports two observations at once. Enforcement against small personal servers is rare in practice — the community is full of people doing it quietly — and &lt;strong>no threshold is published anywhere&lt;/strong>, so any &amp;ldquo;under X TB you&amp;rsquo;re fine&amp;rdquo; claim you read is folklore, not policy.&lt;/p>
&lt;p>Both things are true, and together they mean the availability of your family&amp;rsquo;s media server depends on a policy Cloudflare applies at its own discretion. That is a fine risk for an experiment and a bad foundation for the thing your household relies on. There is also a mechanical constraint that bites before the policy does: the &lt;a href="https://developers.cloudflare.com/support/troubleshooting/http-status-codes/4xx-client-error/error-413/" rel="noopener">100 MB request-body cap&lt;/a> on Free and Pro plans breaks large uploads through the same hostname.&lt;/p>
&lt;p>If the tunnel&amp;rsquo;s shape is what you want - outbound-only, no exposed home ports, URL for everyone - Pangolin in Path 3 is that shape with the policy risk replaced by a small VPS bill.&lt;/p>
&lt;h2 id="check-it-from-outside-and-fix-the-usual-failures">Check it from outside, and fix the usual failures&lt;/h2>
&lt;p>Test from a phone on mobile data with Wi-Fi off, so the request really comes from outside your network.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Path 1:&lt;/strong> with Tailscale connected on the phone, open &lt;code>http://&amp;lt;server's 100.x address&amp;gt;:8096&lt;/code> in the browser or the Jellyfin app.&lt;/li>
&lt;li>&lt;strong>Paths 2 and 3:&lt;/strong> open &lt;code>https://media.yourdomain.com/System/Info/Public&lt;/code>. Jellyfin&amp;rsquo;s API answers that route without a login, with a short JSON block that includes &lt;code>ServerName&lt;/code> and &lt;code>Version&lt;/code>. If it loads over HTTPS with no certificate warning, DNS, the forwards, the certificate and the proxy all work. Then sign in from the Jellyfin app with the same address.&lt;/li>
&lt;/ul>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Symptom&lt;/th>
&lt;th scope="col">Likely cause&lt;/th>
&lt;th scope="col">Fix&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Symptom">The site never loads over HTTPS and Caddy logs certificate errors&lt;/td>
&lt;td data-label="Likely cause">The DNS record does not point at your public IP, or 80/443 do not reach Caddy&lt;/td>
&lt;td data-label="Fix">Fix the A/AAAA record and the router forwards; Caddy&amp;rsquo;s HTTP and TLS-ALPN challenges need those ports reachable from outside&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">502 Bad Gateway&lt;/td>
&lt;td data-label="Likely cause">The proxy answered but got no valid response from Jellyfin (MDN&amp;rsquo;s definition of 502)&lt;/td>
&lt;td data-label="Fix">Check the &lt;code>reverse_proxy&lt;/code> address and that Jellyfin is running; &lt;code>127.0.0.1&lt;/code> only works on the same machine&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">Works on home Wi-Fi, times out on mobile data&lt;/td>
&lt;td data-label="Likely cause">No public IPv4, or a missing forward&lt;/td>
&lt;td data-label="Fix">Run the CGNAT check in Path 2; behind CGNAT, use Path 3&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">Every remote viewer shows the proxy&amp;rsquo;s address, or remote-access limits do nothing&lt;/td>
&lt;td data-label="Likely cause">Known Proxies is empty or wrong&lt;/td>
&lt;td data-label="Fix">Add the proxy&amp;rsquo;s IP under Known Proxies&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">Pages load, but websocket connections fail in the browser console or proxy log&lt;/td>
&lt;td data-label="Likely cause">The proxy is not passing websockets&lt;/td>
&lt;td data-label="Fix">Caddy passes them by default; on nginx or Nginx Proxy Manager, turn websocket support on&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">Uploads over 100 MB fail with 413&lt;/td>
&lt;td data-label="Likely cause">Cloudflare&amp;rsquo;s Free and Pro plan upload cap (Path 4)&lt;/td>
&lt;td data-label="Fix">Serve that hostname by another path&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="remote-playback-upload-speed-and-transcoding">Remote playback: upload speed and transcoding&lt;/h2>
&lt;p>Once a path works, two things set the picture quality, and no access method fixes either. Your home upload (and, on Path 3, the VPS&amp;rsquo;s bandwidth) caps the bitrate that can leave the house. And when a file&amp;rsquo;s bitrate or codec does not suit the client, the server transcodes.&lt;/p>
&lt;p>Jellyfin&amp;rsquo;s &lt;a href="https://jellyfin.org/docs/general/post-install/transcoding/" rel="noopener">transcoding docs&lt;/a> say transcoding is always requested by the client: it sends the codecs, resolutions and bitrate it can handle, and the server picks the best-quality settings within its own capabilities. The docs list four playback types, lightest to heaviest: Direct Play, Remux, Direct Stream (audio transcoded) and Transcode (video transcoded), and the dashboard shows which one each stream is using.&lt;/p>
&lt;p>Video transcodes are where the server&amp;rsquo;s hardware matters. Jellyfin supports hardware-accelerated transcoding on modern Intel, AMD, NVIDIA, Apple and Rockchip GPUs, and its docs say HDR sources must be tone-mapped to SDR when transcoded and that a GPU is always recommended for it. Our &lt;a href="https://techfuelhq.com/articles/best-gpu-plex-jellyfin-transcode-2026/">transcoding GPU guide&lt;/a> covers which chips handle it, and the &lt;a href="https://techfuelhq.com/homelab/best-nas-for-plex-jellyfin-2026/">NAS guide for Plex and Jellyfin&lt;/a> covers boxes that do it in hardware. To keep one remote viewer from swamping the server, Jellyfin&amp;rsquo;s &lt;a href="https://jellyfin.org/docs/general/server/users/" rel="noopener">user settings&lt;/a> let you allow audio and video transcoding per user.&lt;/p>
&lt;h2 id="the-device-truth-table">The device truth table&lt;/h2>
&lt;p>The rows are where remote-access plans actually die. &amp;ldquo;Works&amp;rdquo; here means the normal Jellyfin app experience over that path.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Device&lt;/th>
&lt;th scope="col">Jellyfin app&lt;/th>
&lt;th scope="col">Tailscale (Path 1)&lt;/th>
&lt;th scope="col">Proxy/relay URL (Paths 2-3)&lt;/th>
&lt;th scope="col">Reality check&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Device">Android / Google TV&lt;/td>
&lt;td data-label="Jellyfin app">&lt;a href="https://jellyfin.org/downloads/clients/" rel="noopener">Official&lt;/a>&lt;/td>
&lt;td data-label="Tailscale (Path 1)">✅ &lt;a href="https://tailscale.com/docs/install/android" rel="noopener">Play Store client&lt;/a>&lt;/td>
&lt;td data-label="Proxy/relay URL (Paths 2-3)">✅&lt;/td>
&lt;td data-label="Reality check">Best-covered TV platform: both paths work&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Device">Fire TV&lt;/td>
&lt;td data-label="Jellyfin app">Official (Android TV app)&lt;/td>
&lt;td data-label="Tailscale (Path 1)">✅ &lt;a href="https://tailscale.com/docs/install/amazon-fire" rel="noopener">APK from Tailscale&amp;rsquo;s package server&lt;/a>, manual updates; &lt;strong>not&lt;/strong> Fire OS 5-6 or Vega OS devices such as the 4K Select stick&lt;/td>
&lt;td data-label="Proxy/relay URL (Paths 2-3)">✅&lt;/td>
&lt;td data-label="Reality check">Still a travel-stick option, with more setup than before&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Device">Apple TV&lt;/td>
&lt;td data-label="Jellyfin app">&lt;a href="https://github.com/jellyfin/Swiftfin" rel="noopener">Swiftfin&lt;/a> / Infuse&lt;/td>
&lt;td data-label="Tailscale (Path 1)">✅ &lt;a href="https://tailscale.com/docs/install/appletv" rel="noopener">App Store client&lt;/a>, tvOS 17 or later&lt;/td>
&lt;td data-label="Proxy/relay URL (Paths 2-3)">✅&lt;/td>
&lt;td data-label="Reality check">Tailscale&amp;rsquo;s only non-Android TV client&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Device">Roku&lt;/td>
&lt;td data-label="Jellyfin app">Official&lt;/td>
&lt;td data-label="Tailscale (Path 1)">❌ no client exists&lt;/td>
&lt;td data-label="Proxy/relay URL (Paths 2-3)">✅&lt;/td>
&lt;td data-label="Reality check">The single strongest argument for Path 2/3&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Device">LG webOS&lt;/td>
&lt;td data-label="Jellyfin app">Official&lt;/td>
&lt;td data-label="Tailscale (Path 1)">❌ no client&lt;/td>
&lt;td data-label="Proxy/relay URL (Paths 2-3)">✅&lt;/td>
&lt;td data-label="Reality check">Same story as Roku&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Device">Samsung Tizen&lt;/td>
&lt;td data-label="Jellyfin app">Official&lt;/td>
&lt;td data-label="Tailscale (Path 1)">❌ no client&lt;/td>
&lt;td data-label="Proxy/relay URL (Paths 2-3)">✅&lt;/td>
&lt;td data-label="Reality check">Same story as Roku&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Device">Xbox&lt;/td>
&lt;td data-label="Jellyfin app">Official&lt;/td>
&lt;td data-label="Tailscale (Path 1)">❌ no client&lt;/td>
&lt;td data-label="Proxy/relay URL (Paths 2-3)">✅&lt;/td>
&lt;td data-label="Reality check">Console app, URL-based access only&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Device">Phones / tablets / laptops&lt;/td>
&lt;td data-label="Jellyfin app">Official&lt;/td>
&lt;td data-label="Tailscale (Path 1)">✅&lt;/td>
&lt;td data-label="Proxy/relay URL (Paths 2-3)">✅&lt;/td>
&lt;td data-label="Reality check">Everything works; these were never the problem&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Device">Hotel / dorm TV&lt;/td>
&lt;td data-label="Jellyfin app">none of yours&lt;/td>
&lt;td data-label="Tailscale (Path 1)">via a stick you bring&lt;/td>
&lt;td data-label="Proxy/relay URL (Paths 2-3)">✅ if the TV has a browser (rough)&lt;/td>
&lt;td data-label="Reality check">See below&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The hotel row earns its own paragraph, because &lt;a href="https://www.reddit.com/r/jellyfin/comments/1uqgqil/" rel="noopener">a long r/jellyfin thread on it&lt;/a> converged on answers that surprise people. Casting from your phone mostly fails in hotels: hotel Wi-Fi typically runs AP isolation, so your phone and a Chromecast cannot see each other even on the same network.&lt;/p>
&lt;p>The frequent travelers in that thread &lt;strong>bring a streaming stick with Tailscale and Jellyfin already signed in&lt;/strong>, plug it into the room TV&amp;rsquo;s HDMI, and give the stick the hotel Wi-Fi — the tunnel is outbound, so captive portals and CGNAT do not matter.&lt;/p>
&lt;p>The road warriors in that thread report usable HDMI inputs in the large majority of rooms, with the occasional welded-on &amp;ldquo;hospitality mode&amp;rdquo; remote as the exception. The zero-cleverness fallback is a laptop and an HDMI cable. A GL.iNet-class travel router running the VPN for the whole room is the deluxe version of the same idea.&lt;/p>
&lt;p>If you run Path 2 or 3, the hotel problem mostly dissolves. Your domain works in any browser, including the TV&amp;rsquo;s, and in any Jellyfin app on hardware you bring.&lt;/p>
&lt;h2 id="the-security-baseline-whichever-path-you-picked">The security baseline, whichever path you picked&lt;/h2>
&lt;p>Paths 1 and 3-via-Pangolin put authentication in front of Jellyfin; Path 2 puts Jellyfin&amp;rsquo;s own login on the internet. Either way:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Password quality is the whole game on a public login page.&lt;/strong> Long, unique, per user, no shared &amp;ldquo;family&amp;rdquo; account with a weak password. Jellyfin&amp;rsquo;s account system is the only thing between a scanner and your library on Path 2.&lt;/li>
&lt;li>&lt;strong>Set a failed-login limit.&lt;/strong> Jellyfin&amp;rsquo;s user settings let you cap failed login attempts, after which the account stays locked until an administrator unlocks it.&lt;/li>
&lt;li>&lt;strong>Update the server.&lt;/strong> Jellyfin 10.11.11 is current as I write this; security fixes ride ordinary releases, and a version pinned in 2024 and forgotten is how exposed services rot. As of November 18, 2026 the newest release is Jellyfin 12.4 (October 26, 2026), and Jellyfin&amp;rsquo;s 12.0 notes ask for a full backup of the data directory before upgrading from 10.11, because the database changes prevent rolling back without a restore. The &lt;a href="https://techfuelhq.com/tutorials/jellyfin-setup-docker-homelab-2026/">setup guide&lt;/a> covers the container-update flow.&lt;/li>
&lt;li>&lt;strong>Leave automatic port mapping off.&lt;/strong> The setup wizard&amp;rsquo;s UPnP option is the one Jellyfin&amp;rsquo;s docs recommend disabling unless you specifically need it.&lt;/li>
&lt;li>&lt;strong>Set Known Proxies&lt;/strong> (Path 2/3), or your access logs record the proxy talking to itself while real client addresses vanish - which also breaks any fail2ban-style banning you add at the proxy layer later.&lt;/li>
&lt;li>&lt;strong>Do not log full request URLs at the proxy.&lt;/strong> Jellyfin&amp;rsquo;s docs note it sometimes passes &lt;code>api_key&lt;/code> in the URL; a proxy logging full paths writes credentials into its own logfiles.&lt;/li>
&lt;li>&lt;strong>Quick Connect ships enabled&lt;/strong> on a fresh 10.11.11 install - the code-based login on the sign-in page, verified on the test instance below. It is convenient for TV logins on your own tailnet; on a fully public instance, it is one more auth path you should consciously decide to keep or disable.&lt;/li>
&lt;li>&lt;strong>To turn Quick Connect off&lt;/strong>, Jellyfin&amp;rsquo;s docs give the path: Dashboard, General tab, clear &lt;em>Enable Quick Connect on this server&lt;/em>.&lt;/li>
&lt;/ul>
&lt;h2 id="what-i-tested-and-what-i-did-not">What I tested, and what I did not&lt;/h2>
&lt;p>The reverse-proxy path above is first-hand: Jellyfin 10.11.11 portable on Windows, Caddy 2.11.4 in front, wizard walked, defaults pulled from the live API, Quick Connect state read off the fresh install, websocket upgrade verified through the proxy, on 2026-08-25.&lt;/p>
&lt;p>The public-DNS leg ran against a local certificate authority rather than a routable domain, because I was not going to open ports on the network I ran the test from - the Let&amp;rsquo;s Encrypt half of Caddy&amp;rsquo;s job is its most automated part, but it is the one piece of Path 2 this test takes from documentation rather than observation.&lt;/p>
&lt;p>Tailscale&amp;rsquo;s TV-client coverage comes from Tailscale&amp;rsquo;s own install docs rather than a rack of TVs, and the hotel tactics come from the travel thread&amp;rsquo;s consensus, attributed as such; I have not road-tested them. I have not run Pangolin beyond its documentation and requirements - it is on the bench list, and if that test changes the Path 3 advice, this page moves with it.&lt;/p>
&lt;p>The setup steps, the outside check and the troubleshooting table come from Jellyfin&amp;rsquo;s, Caddy&amp;rsquo;s and Tailscale&amp;rsquo;s current documentation, read November 18, 2026 against Jellyfin 12.4; they were not run on that test instance.&lt;/p></description></item><item><title>Immich Setup and Google Photos Migration Guide (2026)</title><link>https://techfuelhq.com/tutorials/immich-google-photos-migration-2026/</link><pubDate>Thu, 11 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/immich-google-photos-migration-2026/</guid><atom:updated>2026-11-18T04:49:22Z</atom:updated><description>&lt;p>Moving ten years of family photos off Google Photos is high-stakes homelab work. Broken media servers cost an evening. Lost family originals hurt forever.&lt;/p>
&lt;p>I treat every Google Photos migration as a non-destructive, staged pipeline. First I stand up a version-pinned Immich stack with PostgreSQL on local SSD storage. Next I feed the raw Takeout &lt;code>.zip&lt;/code> archives straight into &lt;code>immich-go&lt;/code> without unzipping hundreds of gigabytes of duplicate album copies. Cloud deletion waits until last. I keep every photo untouched in Google Photos until &lt;code>pg_dumpall&lt;/code> and &lt;code>UPLOAD_LOCATION&lt;/code> survive a real restore onto a separate test instance.&lt;/p>
&lt;p>This page was checked against Immich v3.4.1 (November 11, 2026) and immich-go 0.32.0 on November 18, 2026. Still weighing photo platforms before committing? Read our &lt;a href="https://techfuelhq.com/tutorials/self-hosted-photo-library-immich-photoprism-ente-2026/">Immich vs PhotoPrism vs Ente comparison&lt;/a>.&lt;/p>
&lt;h2 id="hardware--storage-layout-requirements">Hardware &amp;amp; storage layout requirements&lt;/h2>
&lt;p>Immich&amp;rsquo;s &lt;a href="https://docs.immich.app/install/requirements/" rel="noopener">official system requirements&lt;/a> are 6 GB of RAM and 2 CPU cores minimum, with 8 GB and 4 cores recommended. Immich says the 6 GB floor matters most during uploads, which is exactly what a Takeout import is; a 4 GB system can run it only with machine learning switched off.&lt;/p>
&lt;p>Follow three storage rules before deploying:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Run Docker inside a full Linux VM on Proxmox.&lt;/strong> Immich says it runs well in a full virtual machine and that Docker in LXC containers is not recommended. Our &lt;a href="https://techfuelhq.com/homelab/lxc-vs-vm-proxmox-2026/">LXC vs VM guide&lt;/a> covers the trade-off.&lt;/li>
&lt;li>&lt;strong>Keep &lt;code>DB_DATA_LOCATION&lt;/code> on local NVMe/SSD.&lt;/strong> Immich says the Postgres data should ideally sit on local SSD storage and never on a network share of any kind, on a filesystem with Unix ownership and permissions (Immich names EXT4, ZFS and APFS as examples). Your bulk &lt;code>UPLOAD_LOCATION&lt;/code> library can live on a larger local ZFS/RAID pool or wired NAS mount; our &lt;a href="https://techfuelhq.com/homelab/best-nas-hard-drives-2026/">NAS drive guide&lt;/a> and &lt;a href="https://techfuelhq.com/homelab/nas-from-old-pc-2026/">old-PC NAS build&lt;/a> cover where that library can live.&lt;/li>
&lt;li>&lt;strong>Stage the Takeout zips outside &lt;code>UPLOAD_LOCATION&lt;/code>.&lt;/strong> Immich owns that folder (Step 2), so keep the downloaded archives on a separate staging disk such as &lt;code>/mnt/staging&lt;/code>, sized for the whole export. Budget the library itself at its original size plus 10 to 20 percent, Immich&amp;rsquo;s estimate for thumbnails and transcoded video.&lt;/li>
&lt;/ol>
&lt;h2 id="step-1-deploy-immich-with-docker-compose">Step 1: Deploy Immich with Docker Compose&lt;/h2>
&lt;p>Create a dedicated stack directory on your Docker host:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>mkdir -p /opt/stacks/immich &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span> cd /opt/stacks/immich
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Pin a specific &lt;a href="https://github.com/immich-app/immich/releases" rel="noopener">Immich GitHub release&lt;/a> rather than tracking floating tags blindly, and always download the matching &lt;code>docker-compose.yml&lt;/code> and &lt;code>example.env&lt;/code> from that release. v3.4.1 was the current release on November 18, 2026; for a newer one, change the tag:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>version&lt;span style="color:#f92672">=&lt;/span>v3.4.1
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>release&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;https://github.com/immich-app/immich/releases/download/&lt;/span>$version&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>wget -O docker-compose.yml &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$release&lt;span style="color:#e6db74">/docker-compose.yml&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>wget -O .env &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$release&lt;span style="color:#e6db74">/example.env&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Edit &lt;code>.env&lt;/code> (&lt;code>chmod 600 .env&lt;/code>) and set four core values before first boot:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>&lt;code>IMMICH_VERSION=v3.4.1&lt;/code>&lt;/strong>: The release&amp;rsquo;s &lt;code>example.env&lt;/code> ships with &lt;code>IMMICH_VERSION=v3&lt;/code>, which follows every v3 release. Set it to the exact tag you downloaded so the images match the Compose file (follow the &lt;a href="https://docs.immich.app/install/upgrading/" rel="noopener">official upgrade notes&lt;/a> whenever bumping versions later).&lt;/li>
&lt;li>&lt;strong>&lt;code>UPLOAD_LOCATION=/mnt/photos/immich&lt;/code>&lt;/strong>: Directory for managed originals, generated thumbnails, encoded videos, and built-in &lt;code>backups/&lt;/code>. Create this directory ahead of startup.&lt;/li>
&lt;li>&lt;strong>&lt;code>DB_DATA_LOCATION=./postgres&lt;/code>&lt;/strong>: Local SSD path for PostgreSQL + VectorChord vector indexes.&lt;/li>
&lt;li>&lt;strong>&lt;code>DB_PASSWORD&lt;/code>&lt;/strong>: Immich asks for only the characters &lt;code>A-Za-z0-9&lt;/code>, with no special characters or spaces. &lt;code>openssl rand -hex 24&lt;/code> produces a string that fits.&lt;/li>
&lt;/ul>
&lt;blockquote>
&lt;p>&lt;strong>Warning:&lt;/strong> the stock &lt;code>docker-compose.yml&lt;/code> publishes &lt;code>'2283:2283'&lt;/code>, which Docker exposes on every host interface; Docker&amp;rsquo;s own docs call published ports insecure by default. If a reverse proxy on the same host (Step 6) is the only way in, change that line to &lt;code>'127.0.0.1:2283:2283'&lt;/code> so only the host can reach it, and never forward 2283 on your router.&lt;/p>&lt;/blockquote>
&lt;p>Start the stack and verify all four containers (&lt;code>immich_server&lt;/code>, &lt;code>immich_machine_learning&lt;/code>, &lt;code>immich_redis&lt;/code> running Valkey 9, and &lt;code>immich_postgres&lt;/code>) report healthy:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker compose up -d
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose ps
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Immich requires the &lt;code>docker compose&lt;/code> command; the older &lt;code>docker-compose&lt;/code> is no longer supported. Open &lt;code>http://&amp;lt;your-host-ip&amp;gt;:2283&lt;/code> (or &lt;code>http://127.0.0.1:2283&lt;/code> on the host itself if you bound it to loopback) and register your admin account.&lt;/p>
&lt;h2 id="step-2-managed-upload_location-vs-read-only-external-libraries">Step 2: Managed &lt;code>UPLOAD_LOCATION&lt;/code> vs read-only external libraries&lt;/h2>
&lt;p>Immich supports two distinct storage modes, and picking the right one before importing saves painful migrations later:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Managed &lt;code>UPLOAD_LOCATION&lt;/code> (use this for Google Takeout + mobile phone auto-backup):&lt;/strong> Immich owns the folder hierarchy inside &lt;code>UPLOAD_LOCATION/upload&lt;/code> (and &lt;code>UPLOAD_LOCATION/library&lt;/code> if you enable the Storage Template engine). Never manually rename, move, or delete files inside &lt;code>UPLOAD_LOCATION&lt;/code> from the Linux shell!&lt;/li>
&lt;li>&lt;strong>&lt;a href="https://docs.immich.app/features/libraries/" rel="noopener">External Libraries&lt;/a> (use this for curated DSLR/Lightroom folders you organize yourself):&lt;/strong> Bind-mount your existing folder into &lt;code>immich-server&lt;/code> with &lt;code>:ro&lt;/code> (&lt;code>/mnt/nas/dslr-archive:/mnt/external/dslr:ro&lt;/code>) and register &lt;code>/mnt/external/dslr&lt;/code> under &lt;strong>Administration → External Libraries&lt;/strong>. Immich&amp;rsquo;s docs say the &lt;code>:ro&lt;/code> flag stops the web UI from deleting those images or writing metadata sidecars into the folder.&lt;/li>
&lt;/ul>
&lt;h2 id="step-3-mobile-app-auto-backup-setup">Step 3: Mobile app auto-backup setup&lt;/h2>
&lt;p>Install the official Immich app from the iOS App Store or Google Play Store, connect to &lt;code>http://&amp;lt;your-host-ip&amp;gt;:2283&lt;/code> (or your HTTPS reverse-proxy domain from Step 6), open the cloud-upload icon, select the camera albums (&lt;code>Recents&lt;/code> / &lt;code>Camera&lt;/code>) to watch, and enable Background Backup on Wi-Fi. On Android, enable Ignore Battery Optimizations so OS doze rules do not kill background uploads; on iOS, grant Background App Refresh and open the app periodically after shooting large 4K video batches.&lt;/p>
&lt;h2 id="step-4-enable-hardware-ml-acceleration-cuda-or-intel-openvino">Step 4: Enable hardware ML acceleration (CUDA or Intel OpenVINO)&lt;/h2>
&lt;p>During a 100,000-photo Takeout migration, CLIP smart search and face recognition are the heaviest jobs on the server. Offloading &lt;code>immich-machine-learning&lt;/code> to an NVIDIA GPU (&lt;code>-cuda&lt;/code>) or an Intel iGPU/Arc card (&lt;code>-openvino&lt;/code>) moves that work off the CPU without touching your originals. Immich still labels hardware-accelerated ML experimental and says CUDA is the most reliable backend.&lt;/p>
&lt;p>The documented route is to keep the release&amp;rsquo;s &lt;code>hwaccel.ml.yml&lt;/code> beside &lt;code>docker-compose.yml&lt;/code>, add the backend suffix to the image tag and uncomment the &lt;code>extends&lt;/code> block. On platforms that take only one Compose file, Immich documents inlining the same settings, which is what these snippets do:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>NVIDIA CUDA&lt;/strong> (compute capability 5.2 or higher, driver 545 or newer, and the &lt;a href="https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html" rel="noopener">NVIDIA Container Toolkit&lt;/a> on a Linux host):&lt;/li>
&lt;/ul>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">immich-machine-learning&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}-cuda&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">deploy&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">resources&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">reservations&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">devices&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">driver&lt;/span>: &lt;span style="color:#ae81ff">nvidia&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">count&lt;/span>: &lt;span style="color:#ae81ff">1&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">capabilities&lt;/span>: [&lt;span style="color:#ae81ff">gpu]&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;ul>
&lt;li>&lt;strong>Intel OpenVINO&lt;/strong> (Intel GPUs such as Iris Xe and Arc via &lt;code>/dev/dri&lt;/code>):&lt;/li>
&lt;/ul>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">immich-machine-learning&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}-openvino&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">devices&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/dev/dri:/dev/dri&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Both tags exist for v3.4.1 on GitHub&amp;rsquo;s container registry. Run &lt;code>docker compose pull &amp;amp;&amp;amp; docker compose up -d&lt;/code>, trigger a smart-search job, and inspect &lt;code>docker compose logs immich-machine-learning&lt;/code>: Immich&amp;rsquo;s docs say an &lt;code>Available ORT providers&lt;/code> line listing the matching provider (&lt;code>CUDAExecutionProvider&lt;/code> for CUDA) confirms the device is in use (&lt;a href="https://docs.immich.app/features/ml-hardware-acceleration/" rel="noopener">ML hardware acceleration docs&lt;/a>; configure video playback transcoding separately under &lt;a href="https://docs.immich.app/features/hardware-transcoding/" rel="noopener">hardware transcoding&lt;/a>).&lt;/p>
&lt;h2 id="step-5-migrate-google-photos-via-takeout">Step 5: Migrate Google Photos via Takeout&lt;/h2>
&lt;h3 id="why-google-takeout-splits-metadata-into-supplemental-metadatajson-sidecars">Why Google Takeout splits metadata into &lt;code>.supplemental-metadata.json&lt;/code> sidecars&lt;/h3>
&lt;p>Never unzip Takeout folders into browser uploads. Three Google Takeout quirks ruin naive folder uploads:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Split EXIF vs JSON sidecars:&lt;/strong> Whenever you adjust a capture date, add a GPS pin, type a description in Google Photos, or save WhatsApp/screenshot images that lack camera EXIF headers, Google &lt;strong>never writes those edits back into the JPEG/HEIC/MP4 file&lt;/strong>. Instead, Takeout puts them in an adjacent JSON file named &lt;code>IMG_1234.JPG.supplemental-metadata.json&lt;/code> (and because Google truncates sidecar filenames around 46–51 characters, long filenames turn into &lt;code>.supplemen.json&lt;/code>, &lt;code>.suppl.json&lt;/code>, or numbered &lt;code>(1).json&lt;/code> variants!).&lt;/li>
&lt;li>&lt;strong>Cross-archive splits:&lt;/strong> On multi-part exports (&lt;code>takeout-001.zip&lt;/code> through &lt;code>takeout-012.zip&lt;/code>), &lt;code>IMG_4092.MP4&lt;/code> frequently lands inside &lt;code>takeout-004.zip&lt;/code> while its &lt;code>.supplemental-metadata.json&lt;/code> lands inside &lt;code>takeout-005.zip&lt;/code>. Importing archives one at a time leaves thousands of files with missing sidecars and wrong dates!&lt;/li>
&lt;li>&lt;strong>500 GB duplicate album bloat:&lt;/strong> Takeout includes a photo once inside &lt;code>Photos from 2022/&lt;/code> &lt;strong>and a second full copy&lt;/strong> inside every album folder (&lt;code>Summer Trip/&lt;/code>, &lt;code>Favorites/&lt;/code>). Unzipping a 250 GB multi-album export can chew through 450–500 GB of scratch space immediately.&lt;/li>
&lt;/ol>
&lt;h3 id="what-a-takeout-does-not-carry">What a Takeout does not carry&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Anything added after you ask.&lt;/strong> Google warns an archive may not include changes made between your request and the archive&amp;rsquo;s creation, and items still being deleted are left out. Treat each export as a snapshot; the FAQ below covers catching up later.&lt;/li>
&lt;li>&lt;strong>Locked Folder items, possibly.&lt;/strong> Google&amp;rsquo;s help for copying photos to another service says to move items out of Locked Folder before transferring. Its Takeout page does not say either way, so move them out first or check a small export before you rely on it.&lt;/li>
&lt;li>&lt;strong>What immich-go skips by default.&lt;/strong> immich-go 0.32.0 leaves out trashed photos (&lt;code>--include-trashed&lt;/code> is off) and files with no JSON companion (&lt;code>--include-unmatched&lt;/code> is off), and it imports partner photos (&lt;code>--include-partner&lt;/code> is on). Decide on those three flags before the real run.&lt;/li>
&lt;/ul>
&lt;h3 id="export-takeout-cleanly-and-rehearse-on-a-small-sample-first">Export Takeout cleanly and rehearse on a small sample first&lt;/h3>
&lt;ol>
&lt;li>Open &lt;a href="https://takeout.google.com" rel="noopener">takeout.google.com&lt;/a>, click &lt;strong>Deselect all&lt;/strong>, and tick &lt;strong>Google Photos&lt;/strong> only.&lt;/li>
&lt;li>Click &lt;strong>Multiple formats / All photo albums included&lt;/strong> and leave every year and user album selected so &lt;code>immich-go&lt;/code> has both the master year files and album membership manifests.&lt;/li>
&lt;li>Choose &lt;strong>One-time archive&lt;/strong>, &lt;strong>Zip files&lt;/strong>, and the largest archive size the menu offers (fewer split boundaries; check your ISP cap first with our &lt;a href="https://techfuelhq.com/tools/data-usage-calculator/">data usage calculator&lt;/a>). Google&amp;rsquo;s &lt;a href="https://support.google.com/accounts/answer/3024190" rel="noopener">Takeout help page&lt;/a> says preparation can take from a few minutes to a few days.&lt;/li>
&lt;/ol>
&lt;p>Before running a 300 GB import, see what metadata edge cases look like in our offline &lt;a href="https://techfuelhq.com/downloads/immich-takeout-check/v1/sample.zip" download type="application/zip">Takeout verification sample kit (ZIP)&lt;/a> (with full hashes in &lt;a href="https://techfuelhq.com/downloads/immich-takeout-check/v1/results.json" download type="application/json">&lt;code>results.json&lt;/code>&lt;/a>), tested with &lt;a href="https://github.com/simulot/immich-go/releases/tag/v0.32.0" rel="noopener">&lt;code>immich-go 0.32.0&lt;/code>&lt;/a>:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Takeout input edge case&lt;/th>
&lt;th scope="col">Verified &lt;code>immich-go&lt;/code> behavior&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Takeout input edge case">Two distinct photos both named &lt;code>IMG_0001.jpg&lt;/code> shot during DST fallback (&lt;code>01:30&lt;/code> at &lt;code>-05:00&lt;/code> vs &lt;code>-06:00&lt;/code>)&lt;/td>
&lt;td data-label="Verified immich-go behavior">Both originals preserved byte-for-byte (&lt;code>06:30&lt;/code> and &lt;code>07:30 UTC&lt;/code>) without overwriting same-name collisions.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Takeout input edge case">Originals duplicated across &lt;code>Photos from YYYY&lt;/code> plus three named albums&lt;/td>
&lt;td data-label="Verified immich-go behavior">Stored once via content hash while retaining all five album memberships.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Takeout input edge case">Photo shot &lt;code>Jan 2, 00:15 +05:30&lt;/code> whose Takeout JSON listed &lt;code>Jan 1, 12:45 -06:00&lt;/code>&lt;/td>
&lt;td data-label="Verified immich-go behavior">Preserved exact &lt;code>18:45 UTC&lt;/code> instant rather than shifting the calendar day by 11.5 hours.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Then rehearse against your own export. &lt;code>--dry-run&lt;/code> simulates the whole upload without transferring anything, and &lt;code>--from-album-name&lt;/code> limits a real run to one album, so you can check its dates and album in Immich before committing the rest (both flags from the immich-go 0.32.0 upload reference):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>immich-go upload from-google-photos --dry-run &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --server&lt;span style="color:#f92672">=&lt;/span>http://127.0.0.1:2283 --api-key&lt;span style="color:#f92672">=&lt;/span>YOUR_KEY &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --log-file&lt;span style="color:#f92672">=&lt;/span>/mnt/staging/dry-run.log &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /mnt/staging/takeout-*.zip
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>immich-go upload from-google-photos --from-album-name&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;Summer Trip&amp;#34;&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --server&lt;span style="color:#f92672">=&lt;/span>http://127.0.0.1:2283 --api-key&lt;span style="color:#f92672">=&lt;/span>YOUR_KEY &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /mnt/staging/takeout-*.zip
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Swap &lt;code>YOUR_KEY&lt;/code> for the key you create below, or use the full run&amp;rsquo;s prompt, which reads the key into an environment variable instead of the command line.&lt;/p>
&lt;h3 id="stream-takeout-zip-files-directly-with-immich-go--sha-1-deduplication">Stream Takeout &lt;code>.zip&lt;/code> files directly with &lt;code>immich-go&lt;/code> + SHA-1 deduplication&lt;/h3>
&lt;p>Download the current &lt;a href="https://github.com/simulot/immich-go/releases" rel="noopener">&lt;code>immich-go&lt;/code> binary&lt;/a> on your server or workstation, generate an API key in your user settings on the Immich web interface (Immich lets you limit a key&amp;rsquo;s permissions), and pass &lt;strong>every &lt;code>.zip&lt;/code> part of your Takeout export together in a single command&lt;/strong> without unzipping them. &lt;code>IMMICH_GO_UPLOAD_API_KEY&lt;/code> is the environment variable immich-go 0.32.0 reads in place of &lt;code>--api-key&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">(&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> read -rsp &lt;span style="color:#e6db74">&amp;#39;Immich API key: &amp;#39;&lt;/span> IMMICH_GO_UPLOAD_API_KEY; echo
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> export IMMICH_GO_UPLOAD_API_KEY
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> immich-go upload from-google-photos &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --server&lt;span style="color:#f92672">=&lt;/span>http://127.0.0.1:2283 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --sync-albums&lt;span style="color:#f92672">=&lt;/span>true &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --pause-immich-jobs&lt;span style="color:#f92672">=&lt;/span>true &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --log-file&lt;span style="color:#f92672">=&lt;/span>/mnt/staging/immich-go.log &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /mnt/staging/takeout-*.zip
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">)&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Why this exact invocation works so cleanly:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Zero 500 GB unzip step:&lt;/strong> &lt;code>immich-go&lt;/code> indexes the central directory across all &lt;code>/mnt/staging/takeout-*.zip&lt;/code> files simultaneously, pairs truncated &lt;code>.supplemental-metadata.json&lt;/code> sidecars across archive boundaries, and streams files straight to Immich over HTTP.&lt;/li>
&lt;li>&lt;strong>&lt;code>--pause-immich-jobs=true&lt;/code> during huge imports:&lt;/strong> Pauses heavy background face-recognition and video-transcode queues while uploading so your server does not thrash disk I/O and RAM simultaneously, then resumes processing when the upload completes. It and &lt;code>--sync-albums&lt;/code> are both on by default in 0.32.0; writing them out keeps the intent visible. immich-go also takes a separate &lt;code>--admin-api-key&lt;/code> for managing server jobs.&lt;/li>
&lt;li>&lt;strong>SHA-1 server-side deduplication:&lt;/strong> Immich hashes every uploaded file with &lt;strong>SHA-1&lt;/strong>. When an identical &lt;code>IMG_2048.HEIC&lt;/code> sits in &lt;code>Photos from 2021/&lt;/code> and four Takeout album folders, Immich stores &lt;strong>one single copy&lt;/strong> on disk and attaches all four album links—making re-runs idempotent if your network drops halfway through! &lt;em>(Important nuance: if Takeout contains both &lt;code>IMG_2048.JPG&lt;/code> and &lt;code>IMG_2048-edited.JPG&lt;/code>, or a re-encoded copy with altered pixels, their SHA-1 hashes differ and both versions import as separate files.)&lt;/em>&lt;/li>
&lt;li>&lt;strong>&lt;code>--log-file&lt;/code>:&lt;/strong> writes immich-go&amp;rsquo;s log messages to a file you can inspect for Gate 1 below.&lt;/li>
&lt;/ul>
&lt;p>Revoke the temporary migration API key in Immich once &lt;code>immich-go&lt;/code> finishes with zero fatal errors, and let background Thumbnail, Smart Search, and Face Detection jobs drain under &lt;strong>Administration &amp;gt; Job Queues&lt;/strong>.&lt;/p>
&lt;h2 id="step-6-reverse-proxy-with-nginx-proxy-manager">Step 6: Reverse proxy with Nginx Proxy Manager&lt;/h2>
&lt;p>When exposing Immich on &lt;code>https://photos.yourdomain.com&lt;/code> (or internally over split-DNS + &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale&lt;/a>), forward HTTP traffic to &lt;code>immich_server:2283&lt;/code> with &lt;strong>Websockets Support ON&lt;/strong> and raise Nginx&amp;rsquo;s body-size ceiling so multi-gigabyte 4K phone videos never fail with &lt;code>413 Request Entity Too Large&lt;/code>. Immich must be served at the root of a (sub)domain, not a sub-path such as &lt;code>/immich&lt;/code> (&lt;a href="https://docs.immich.app/administration/reverse-proxy/" rel="noopener">Immich reverse proxy docs&lt;/a>). These lines come from Immich&amp;rsquo;s nginx example:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-nginx" data-lang="nginx">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">client_max_body_size&lt;/span> &lt;span style="color:#e6db74">50000M&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">proxy_read_timeout&lt;/span> &lt;span style="color:#e6db74">600s&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">proxy_send_timeout&lt;/span> &lt;span style="color:#e6db74">600s&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">send_timeout&lt;/span> &lt;span style="color:#e6db74">600s&lt;/span>;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-7-backup-strategy">Step 7: Backup strategy&lt;/h2>
&lt;p>Immich&amp;rsquo;s &lt;a href="https://docs.immich.app/administration/backup-and-restore/" rel="noopener">backup and restore documentation&lt;/a> splits your library across two inseparable halves:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>&lt;code>UPLOAD_LOCATION&lt;/code>:&lt;/strong> Immich says only &lt;code>library/&lt;/code>, &lt;code>upload/&lt;/code> and &lt;code>profile/&lt;/code> hold critical originals; &lt;code>thumbs/&lt;/code> and &lt;code>encoded-video/&lt;/code> can be regenerated by rerunning jobs. Immich also writes automatic database dumps into &lt;code>UPLOAD_LOCATION/backups/&lt;/code>, by default daily at 2:00 AM, keeping the last 14 (adjustable under Administration &amp;gt; Settings &amp;gt; Database Dump Settings). Those dumps hold metadata only, so back them up together with the originals.&lt;/li>
&lt;li>&lt;strong>PostgreSQL database dump:&lt;/strong> Stores users, albums, facial clusters, edited dates, captions, and every path mapping into &lt;code>UPLOAD_LOCATION&lt;/code>. Immich does not scan the library folder, so the database backup is essential. &lt;strong>Never rely on copying raw &lt;code>./postgres&lt;/code> bind-mount files while PostgreSQL is running&lt;/strong>—hot file copies of active Postgres data directories frequently corrupt!&lt;/li>
&lt;/ol>
&lt;p>For a dump of your own on top of the automatic ones, use Immich&amp;rsquo;s documented &lt;code>pg_dump&lt;/code> command (default database &lt;code>immich&lt;/code>, user &lt;code>postgres&lt;/code>) with gzip verification before promoting the archive:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e">#!/bin/bash
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e">&lt;/span>set -euo pipefail
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>umask &lt;span style="color:#ae81ff">077&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>backup_dir&lt;span style="color:#f92672">=&lt;/span>/mnt/backups/immich-db
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>install -d -m &lt;span style="color:#ae81ff">0700&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>tmp&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>mktemp &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">/.immich-db-XXXXXX.sql.gz&amp;#34;&lt;/span>&lt;span style="color:#66d9ef">)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>trap &lt;span style="color:#e6db74">&amp;#39;rm -f -- &amp;#34;$tmp&amp;#34;&amp;#39;&lt;/span> EXIT
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker exec -t immich_postgres &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> pg_dump --clean --if-exists --dbname&lt;span style="color:#f92672">=&lt;/span>immich --username&lt;span style="color:#f92672">=&lt;/span>postgres | gzip &amp;gt; &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$tmp&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>gzip --test &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$tmp&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>final&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">/immich-pgdump-&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>date -u +%Y%m%dT%H%M%SZ&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">.sql.gz&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>mv -- &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$tmp&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$final&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>trap - EXIT
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>printf &lt;span style="color:#e6db74">&amp;#39;Verified Immich DB dump: %s\n&amp;#39;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$final&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Pair that nightly SQL dump with an encrypted &lt;strong>3-2-1 backup&lt;/strong> (&lt;code>restic&lt;/code> or &lt;code>borg&lt;/code> backing up &lt;code>UPLOAD_LOCATION&lt;/code> + &lt;code>/mnt/backups/immich-db&lt;/code> to both a local NAS/PBS target and an off-site cloud or remote homelab disk). Our &lt;a href="https://techfuelhq.com/homelab/restic-vs-borg-vs-kopia-2026/">restic vs Borg vs Kopia comparison&lt;/a> helps you pick the tool.&lt;/p>
&lt;h3 id="mandatory-6-gate-checklist-before-deleting-a-single-google-photos-cloud-item">Mandatory 6-gate checklist before deleting a single Google Photos cloud item&lt;/h3>
&lt;p>Never delete cloud originals right after &lt;code>immich-go&lt;/code> finishes. Walk every row of this verification gate first:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Gate&lt;/th>
&lt;th scope="col">What to verify&lt;/th>
&lt;th scope="col">Pass criterion&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>1. &lt;code>immich-go&lt;/code> log audit&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Inspect the upload summary and skipped/unmatched lines in &lt;code>immich-go.log&lt;/code>&lt;/td>
&lt;td data-label="Pass criterion">&lt;code>0&lt;/code> failed uploads; any unmatched sidecars accounted for across all &lt;code>.zip&lt;/code> parts.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>2. Admin job queues&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Check &lt;strong>Administration &amp;gt; Job Queues&lt;/strong> in the Immich web UI&lt;/td>
&lt;td data-label="Pass criterion">&lt;code>0&lt;/code> failed jobs across Metadata Extraction, Thumbnail Generation, Video Transcoding, and Smart Search.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>3. Date &amp;amp; album spot-check&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Check 10 older pre-smartphone scans, WhatsApp/screenshot images, timezone travel photos, and 5 named albums&lt;/td>
&lt;td data-label="Pass criterion">Timeline dates match expected capture dates (not upload date!) and album counts match Google Photos.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>4. Byte-hash spot-check&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Download 5 full-resolution originals from Immich web UI and run &lt;code>sha256sum&lt;/code> against the files inside Takeout &lt;code>.zip&lt;/code>&lt;/td>
&lt;td data-label="Pass criterion">Exact &lt;code>SHA-256&lt;/code> match confirming uncorrupted original storage.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>5. 3-2-1 backup completion&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Verify local NAS backup + off-site &lt;code>restic&lt;/code>/cloud snapshot of both &lt;code>UPLOAD_LOCATION&lt;/code> and the database dump&lt;/td>
&lt;td data-label="Pass criterion">Independent off-host copy exists and &lt;code>restic check&lt;/code> passes.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>6. Isolated restore drill&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">On a disposable test VM, install the same Immich version, copy your &lt;code>UPLOAD_LOCATION&lt;/code> folders (including &lt;code>backups/&lt;/code>) into its fresh &lt;code>UPLOAD_LOCATION&lt;/code>, start it, and choose &lt;strong>Restore from backup&lt;/strong> on the welcome screen, which runs Immich&amp;rsquo;s folder integrity checks first&lt;/td>
&lt;td data-label="Pass criterion">Test instance opens on &lt;code>:2283&lt;/code> with intact albums, dates, faces, and playable original photos/videos!&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Even after all six gates pass, I archive the raw Google Takeout &lt;code>.zip&lt;/code> files onto a cold offline external hard drive on a shelf before deleting anything from Google&amp;rsquo;s cloud. Storage costs pennies per gigabyte. Twenty years of family photos cannot be re-shot.&lt;/p>
&lt;h2 id="common-issues">Common issues&lt;/h2>
&lt;p>Wrong timeline dates (hundreds of photos bunched on migration day): Usually caused by extracting Takeout folders and uploading JPEGs without their &lt;code>.supplemental-metadata.json&lt;/code> sidecars, or uploading &lt;code>takeout-001.zip&lt;/code> through &lt;code>takeout-010.zip&lt;/code> in separate runs when a photo and its JSON sidecar spanned adjacent archives. Re-run &lt;code>immich-go upload from-google-photos&lt;/code> passing &lt;code>/path/to/takeout-*.zip&lt;/code> in a single command.&lt;/p>
&lt;p>&lt;code>immich-machine-learning&lt;/code> container OOM-killed or restart-looping: Large imports running concurrent ML and video jobs on a 4–6 GB VM exhaust RAM. Give the VM 8–12 GB RAM, use &lt;code>--pause-immich-jobs=true&lt;/code> during &lt;code>immich-go&lt;/code> uploads, and lower the Face Detection and Smart Search job concurrency in Immich&amp;rsquo;s administration settings to &lt;code>1&lt;/code> or &lt;code>2&lt;/code>.&lt;/p>
&lt;p>Mobile app fails on large 4K video backups over HTTPS: the reverse proxy is rejecting the upload size with a &lt;code>413&lt;/code>. Set &lt;code>client_max_body_size 50000M;&lt;/code> on your proxy host (Step 6), or connect privately over &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale&lt;/a> or &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">self-hosted WireGuard&lt;/a>.&lt;/p>
&lt;p>Errors such as &lt;code>relation already exists&lt;/code> or a VectorChord extension error during a command-line database restore: Immich&amp;rsquo;s docs say the restore needs a completely fresh install whose server has never run, so reset &lt;code>DB_DATA_LOCATION&lt;/code> first, and that restoring a dump from a different Immich version may need database migrations. Follow the &lt;a href="https://docs.immich.app/administration/backup-and-restore/#restore-via-command-line" rel="noopener">official CLI restore steps&lt;/a>, which also rewrite the dump&amp;rsquo;s &lt;code>search_path&lt;/code> line before piping it into &lt;code>psql&lt;/code>, restore onto the version that made the dump, verify login, and only then upgrade.&lt;/p>
&lt;p>If you would rather keep files and photos on one platform, our &lt;a href="https://techfuelhq.com/tutorials/nextcloud-aio-docker-setup-2026/">Nextcloud AIO setup guide&lt;/a> is the general-purpose alternative.&lt;/p></description></item><item><title>Self-Hosted Photo Library 2026: Immich vs PhotoPrism vs Ente</title><link>https://techfuelhq.com/tutorials/self-hosted-photo-library-immich-photoprism-ente-2026/</link><pubDate>Sat, 09 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/self-hosted-photo-library-immich-photoprism-ente-2026/</guid><atom:updated>2026-11-18T04:49:22Z</atom:updated><description>&lt;p>Immich or Ente comes down to who can open your photos. Immich keeps your originals as plain files on the server and runs its machine learning there. Ente runs the machine learning on your phone and stores only end-to-end encrypted objects, on your server or on Ente&amp;rsquo;s cloud. I would run Immich for a family library on a box I already secure, and Ente when the server itself is not trusted. PhotoPrism is the third choice, with face recognition free in every edition and no phone app of its own.&lt;/p>
&lt;p>I picked one for the family library on my own homelab in May 2026. This walkthrough explains the call, who the other two are right for, and the specific failure modes you can avoid by choosing on purpose.&lt;/p>
&lt;h2 id="pick-in-one-line">Pick in one line&lt;/h2>
&lt;p>PhotoPrism is the odd one out: no native phone app of its own, and far fewer releases than the other two (TL;DR table below). Between Immich and Ente:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Pick Immich&lt;/strong> if you want a free Google-Photos-style server where faces, smart search and automatic phone backup work on server-side ML, and you accept that the originals sit on disk as plain files, protected by however well you secure the box. Immich&amp;rsquo;s own minimum is 6 GB of RAM and 2 cores.&lt;/li>
&lt;li>&lt;strong>Pick Ente&lt;/strong> if end-to-end encryption is the point. The server stores objects it cannot read, all ML runs on your devices, storage is any S3-compatible bucket, and the server needs 1 GB of RAM. You pay with a desktop-side Google Takeout import, no server-side ML, and, on your own server, a CLI step to lift each account&amp;rsquo;s storage quota. If you would rather not run a server at all, Ente runs the same service itself.&lt;/li>
&lt;/ul>
&lt;div class="visual-block">
&lt;div style="background:#0b1020;padding:24px 20px 22px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',sans-serif;color:#e8eaf2;">
&lt;div style="font-size:18px;font-weight:700;letter-spacing:-0.3px;">Who can read your library?&lt;/div>
&lt;div style="font-size:0.875rem;color:#93a0bd;margin-top:5px;line-height:1.55;max-width:640px;">Every other spec follows from one question &amp;mdash; does the AI run on the server or on your phone, and can the server read your photos at all? That single fork, not the feature checklist, is the real three-way split.&lt;/div>
&lt;div style="margin-top:18px;display:flex;flex-direction:column;gap:11px;">
&lt;div style="background:#10182a;border:1px solid rgba(255,255,255,0.07);border-left:1px solid var(--border-strong);border-radius:8px;padding:12px 13px;">
&lt;div style="display:flex;justify-content:space-between;align-items:center;gap:8px;flex-wrap:wrap;">&lt;span style="font-size:13.5px;font-weight:700;color:#eef1f8;">Immich&lt;/span>&lt;span style="display:inline-flex;align-items:center;gap:6px;font-size:0.8125rem;font-weight:700;color:#f0a7a7;background:#2a1417;border:1px solid #e0555744;border-radius:999px;padding:4px 9px;white-space:nowrap;">&lt;svg width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="#e07a7a" stroke-width="2" style="vertical-align:middle;">&lt;path d="M1 12s4-7 11-7 11 7 11 7-4 7-11 7-11-7-11-7z"/>&lt;circle cx="12" cy="12" r="3"/>&lt;/svg>SERVER SEES ALL&lt;/span>&lt;/div>
&lt;div style="display:flex;flex-wrap:wrap;align-items:center;gap:7px;margin-top:10px;font-size:0.875rem;">&lt;span style="background:#0d1626;border:1px solid #2b3a55;border-radius:6px;padding:5px 10px;color:#cfe0ff;">Your photos&lt;/span>&lt;span style="color:#5f6f8f;">&amp;rarr;&lt;/span>&lt;span style="background:var(--bg-raised);border:1px solid var(--border-strong);border-radius:6px;padding:5px 10px;color:var(--text);font-weight:600;">AI runs on the server&lt;/span>&lt;span style="color:#5f6f8f;">&amp;rarr;&lt;/span>&lt;span style="background:#0d1626;border:1px solid #2b3a55;border-radius:6px;padding:5px 10px;color:#cfe0ff;">readable originals on disk&lt;/span>&lt;/div>
&lt;div style="font-size:0.8125rem;color:#8b97b8;line-height:1.45;margin-top:9px;">Face recognition and search run for free on your box &amp;mdash; but anyone with the disk, a backup, or root can open every photo. Your privacy equals how well you secure the server.&lt;/div>
&lt;/div>
&lt;div style="background:#10182a;border:1px solid rgba(255,255,255,0.07);border-left:1px solid #5090e0;border-radius:8px;padding:12px 13px;">
&lt;div style="display:flex;justify-content:space-between;align-items:center;gap:8px;flex-wrap:wrap;">&lt;span style="font-size:13.5px;font-weight:700;color:#eef1f8;">PhotoPrism&lt;/span>&lt;span style="display:inline-flex;align-items:center;gap:6px;font-size:0.8125rem;font-weight:700;color:#f0a7a7;background:#2a1417;border:1px solid #e0555744;border-radius:999px;padding:4px 9px;white-space:nowrap;">&lt;svg width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="#e07a7a" stroke-width="2" style="vertical-align:middle;">&lt;path d="M1 12s4-7 11-7 11 7 11 7-4 7-11 7-11-7-11-7z"/>&lt;circle cx="12" cy="12" r="3"/>&lt;/svg>SERVER SEES ALL&lt;/span>&lt;/div>
&lt;div style="display:flex;flex-wrap:wrap;align-items:center;gap:7px;margin-top:10px;font-size:0.875rem;">&lt;span style="background:#0d1626;border:1px solid #2b3a55;border-radius:6px;padding:5px 10px;color:#cfe0ff;">Your photos&lt;/span>&lt;span style="color:#5f6f8f;">&amp;rarr;&lt;/span>&lt;span style="background:#0c1526;border:1px solid #5090e055;border-radius:6px;padding:5px 10px;color:#bcd6f5;font-weight:600;">AI runs on the server &lt;span style="color:#e0a060;">(faces included)&lt;/span>&lt;/span>&lt;span style="color:#5f6f8f;">&amp;rarr;&lt;/span>&lt;span style="background:#0d1626;border:1px solid #2b3a55;border-radius:6px;padding:5px 10px;color:#cfe0ff;">readable originals on disk&lt;/span>&lt;/div>
&lt;div style="font-size:0.8125rem;color:#8b97b8;line-height:1.45;margin-top:9px;">Same trust model as Immich &amp;mdash; the server holds unencrypted originals &amp;mdash; and face recognition is free here too; the paid Plus tier buys the admin web UI.&lt;/div>
&lt;/div>
&lt;div style="background:#10182a;border:1px solid rgba(255,255,255,0.07);border-left:1px solid #5dca7a;border-radius:8px;padding:12px 13px;">
&lt;div style="display:flex;justify-content:space-between;align-items:center;gap:8px;flex-wrap:wrap;">&lt;span style="font-size:13.5px;font-weight:700;color:#eef1f8;">Ente&lt;/span>&lt;span style="display:inline-flex;align-items:center;gap:6px;font-size:0.8125rem;font-weight:700;color:#9ff0c0;background:#0c2016;border:1px solid #5dca7a55;border-radius:999px;padding:4px 9px;white-space:nowrap;">&lt;svg width="13" height="14" viewBox="0 0 24 24" fill="none" stroke="#5dca7a" stroke-width="2" style="vertical-align:middle;">&lt;rect x="4" y="11" width="16" height="10" rx="2"/>&lt;path d="M8 11V7a4 4 0 0 1 8 0v4"/>&lt;/svg>SERVER SEES NOTHING&lt;/span>&lt;/div>
&lt;div style="display:flex;flex-wrap:wrap;align-items:center;gap:7px;margin-top:10px;font-size:0.875rem;">&lt;span style="background:#0d1626;border:1px solid #2b3a55;border-radius:6px;padding:5px 10px;color:#cfe0ff;">Your photos&lt;/span>&lt;span style="color:#5f6f8f;">&amp;rarr;&lt;/span>&lt;span style="background:#0c2016;border:1px solid #5dca7a55;border-radius:6px;padding:5px 10px;color:#c2f0d5;font-weight:600;">AI runs on your phone&lt;/span>&lt;span style="color:#5f6f8f;">&amp;rarr;&lt;/span>&lt;span style="background:#0c2016;border:1px solid #5dca7a55;border-radius:6px;padding:5px 10px;color:#c2f0d5;">encrypted blobs on disk&lt;/span>&lt;/div>
&lt;div style="font-size:0.8125rem;color:#8b97b8;line-height:1.45;margin-top:9px;">The only true end-to-end option: even root on the server sees ciphertext. The cost is that all ML runs on-device and a Google Takeout import is done from your laptop, not the box.&lt;/div>
&lt;/div>
&lt;/div>
&lt;div style="font-size:0.8125rem;color:#6b7794;margin-top:13px;line-height:1.4;">Trust model per each project's documentation, read September 26, 2026. "Server sees all" means the originals sit unencrypted on the server's filesystem; "server sees nothing" means it stores only end-to-end-encrypted blobs.&lt;/div>
&lt;/div>
&lt;/div>
&lt;h2 id="tldr">TL;DR&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Immich&lt;/th>
&lt;th scope="col">PhotoPrism&lt;/th>
&lt;th scope="col">Ente&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Latest stable release&lt;/td>
&lt;td data-label="Immich">v3.4.1, Nov 11, 2026&lt;/td>
&lt;td data-label="PhotoPrism">261029-963b58c50, Oct 29, 2026&lt;/td>
&lt;td data-label="Ente">Mobile app v1.3.70 (Android build on GitHub), Nov 13, 2026; desktop v1.7.31, Oct 27; the server has no separate GitHub release, and the quickstart pulls its image untagged&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Stable releases, Jan 1 to Nov 18, 2026&lt;/td>
&lt;td data-label="Immich">31, eight of them minor or major&lt;/td>
&lt;td data-label="PhotoPrism">7&lt;/td>
&lt;td data-label="Ente">28 mobile-app releases; the server has none&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Who can open your photos on the server&lt;/td>
&lt;td data-label="Immich">Anyone with the disk: originals are plain files under &lt;code>UPLOAD_LOCATION&lt;/code>&lt;/td>
&lt;td data-label="PhotoPrism">Anyone with the disk: originals are plain files in the originals folder&lt;/td>
&lt;td data-label="Ente">Nobody without your key: the server stores end-to-end encrypted objects&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Where faces and search run&lt;/td>
&lt;td data-label="Immich">The server&amp;rsquo;s ML container; CUDA, OpenVINO, ROCm, ARM NN or RKNN can accelerate it&lt;/td>
&lt;td data-label="PhotoPrism">The server; since build 261007 its built-in models can run on a supported NVIDIA GPU&lt;/td>
&lt;td data-label="Ente">Your phone or desktop, with ONNX Runtime&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Documented minimum server&lt;/td>
&lt;td data-label="Immich">6 GB RAM (8 GB recommended), 2 cores (4 recommended); an x86-64-v2 CPU for ML on x86 since v3&lt;/td>
&lt;td data-label="PhotoPrism">3 GB RAM, 2 cores, 64-bit OS, 4 GB swap&lt;/td>
&lt;td data-label="Ente">1 GB RAM, 1 core&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Phone apps&lt;/td>
&lt;td data-label="Immich">Native iOS and Android&lt;/td>
&lt;td data-label="PhotoPrism">PWA; third-party native apps (Gallery for PhotoPrism, PhotoSync, Stream)&lt;/td>
&lt;td data-label="Ente">Native iOS and Android, plus desktop apps&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Where the files live&lt;/td>
&lt;td data-label="Immich">A filesystem path, plus Postgres 14 to 19 with VectorChord&lt;/td>
&lt;td data-label="PhotoPrism">The originals folder, plus MariaDB 10.5.12+ or SQLite; PostgreSQL support is experimental since 261029&lt;/td>
&lt;td data-label="Ente">S3-compatible object storage (MinIO in the quickstart), plus Postgres&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Cost to self-host&lt;/td>
&lt;td data-label="Immich">Free, no paywalled features; optional lifetime supporter key, $100 per server or $25 per user (Immich&amp;rsquo;s July 2024 prices)&lt;/td>
&lt;td data-label="PhotoPrism">Community free; Essentials €2/month, Plus from €6/month, billed annually&lt;/td>
&lt;td data-label="Ente">Free; an admin raises each account&amp;rsquo;s storage quota with the Ente CLI&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Paid hosting listed by the project&lt;/td>
&lt;td data-label="Immich">-&lt;/td>
&lt;td data-label="PhotoPrism">PikaPods, from $6.50/month&lt;/td>
&lt;td data-label="Ente">Ente&amp;rsquo;s own cloud: 10 GB free, then $2.49/month for 50 GB up to $19.99/month for 2,000 GB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Getting your library out&lt;/td>
&lt;td data-label="Immich">Copy the originals; &lt;code>immich-go archive from-immich&lt;/code> writes a folder archive; albums and faces live in the database backups&lt;/td>
&lt;td data-label="PhotoPrism">Copy the originals folder; YAML sidecars hold photo metadata, and separate YAML files back up albums&lt;/td>
&lt;td data-label="Ente">The desktop app&amp;rsquo;s Export Data writes a local copy of your photos and videos; the Ente CLI exports too&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Licence&lt;/td>
&lt;td data-label="Immich">AGPL-3.0&lt;/td>
&lt;td data-label="PhotoPrism">AGPL (Community Edition)&lt;/td>
&lt;td data-label="Ente">AGPL-3.0&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Read from each project&amp;rsquo;s releases and documentation (Sources below): versions, release counts and prices on November 18, 2026, the other rows on September 26, 2026. The first two rows date fastest, so they are the only place this page counts releases. A dash means no project source names one. The prices are the projects&amp;rsquo; own list prices.&lt;/p>
&lt;h2 id="my-pick">My pick&lt;/h2>
&lt;p>I picked &lt;strong>Immich&lt;/strong> for the family library because its face recognition, smart search and phone apps all work for free.&lt;/p>
&lt;p>If your x86 CPU lacks x86-64-v2 support, you already run a PhotoPrism library you like, or you want end-to-end encryption with on-device ML, the answer changes. Each case is below.&lt;/p>
&lt;h2 id="how-i-evaluated-them">How I evaluated them&lt;/h2>
&lt;p>Three buckets:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>What the project ships in 2026&lt;/strong> — versions, release pace, and what is free for self-hosters.&lt;/li>
&lt;li>&lt;strong>What the install costs you&lt;/strong> — the project&amp;rsquo;s own hardware minimum, the CPU load during upload that KittMedia measured, disk, and how the phone app behaves.&lt;/li>
&lt;li>&lt;strong>What happens when something goes wrong&lt;/strong> — backup, leaving the platform, encryption, and release pace.&lt;/li>
&lt;/ol>
&lt;p>The figures come from each project&amp;rsquo;s documentation and GitHub releases, read September 26, 2026, with versions, release counts and prices re-read November 18, 2026. The RAM minimums are each project&amp;rsquo;s own, and the measured comparison is KittMedia&amp;rsquo;s.&lt;/p>
&lt;h2 id="immich">Immich&lt;/h2>
&lt;p>&lt;strong>Status, November 18, 2026.&lt;/strong> The current release is v3.4.1 (November 11), a bug-fix patch on v3.4.0 (November 10), which added JPEG XL support, tags on mobile, new Workflows filters and triggers, and a batch of security fixes (&lt;a href="https://github.com/immich-app/immich/releases" rel="noopener">releases&lt;/a>). v3.3.0 (October 7) let users share people with others in their cluster group and added birthday memories and auto-stacked mobile edits. Cluster groups arrived in v3.2.0 (September 10), and they carry a catch: joining a group requires resetting facial recognition for everyone in it, and &amp;ldquo;names and birth dates will be lost&amp;rdquo; (&lt;a href="https://github.com/immich-app/immich/releases/tag/v3.2.0" rel="noopener">v3.2.0 notes&lt;/a>).&lt;/p>
&lt;p>v3.0 raised the hardware floor. The &lt;a href="https://immich.app/blog/v3.0.0-release" rel="noopener">v3.0.0 release&lt;/a> (July 1, 2026) brought mobile non-destructive editing, a Workflows automation builder (preview), HLS real-time transcoding (preview), integrity checks, and slideshow and OCR in the mobile app. Most of its breaking changes are API changes that affect third-party tools. It also dropped pgvecto.rs. An install that never moved to VectorChord has to migrate first. The change that matters on old homelab hardware: since v3, the machine-learning container on x86 (amd64) needs the x86-64-v2 microarchitecture level. Immich says most CPUs released since about 2012 support it. Older chips stop at v2.7.5. In a VM, pick a supported CPU type (&lt;a href="https://docs.immich.app/install/requirements/" rel="noopener">requirements&lt;/a>).&lt;/p>
&lt;p>The ML stack runs on your server. Face detection and recognition, CLIP smart search and OCR run in the &lt;code>immich-machine-learning&lt;/code> container (OCR joined that pipeline in &lt;a href="https://github.com/immich-app/immich/releases/tag/v2.2.0" rel="noopener">v2.2.0&lt;/a>), and the embeddings live in Postgres through VectorChord (&lt;a href="https://docs.immich.app/administration/postgres-standalone/" rel="noopener">Postgres docs&lt;/a>). Hardware acceleration covers more than the other two (&lt;a href="https://docs.immich.app/features/ml-hardware-acceleration/" rel="noopener">ML acceleration docs&lt;/a>):&lt;/p>
&lt;ul>
&lt;li>&lt;strong>CUDA&lt;/strong>: NVIDIA, compute capability 5.2 or higher, driver 545 or newer (CUDA 12.3).&lt;/li>
&lt;li>&lt;strong>OpenVINO&lt;/strong>: Intel GPUs such as Iris Xe and Arc.&lt;/li>
&lt;li>&lt;strong>ROCm&lt;/strong>: AMD; the ROCm image needs at least 35 GiB of free disk.&lt;/li>
&lt;li>&lt;strong>ARM NN&lt;/strong>: Mali GPUs only, FP32 by default.&lt;/li>
&lt;li>&lt;strong>RKNN&lt;/strong>: Rockchip RK3566, RK3568, RK3576 and RK3588.&lt;/li>
&lt;li>&lt;strong>Video transcoding&lt;/strong>, a separate list: NVENC, Quick Sync, RKMPP and VAAPI (&lt;a href="https://docs.immich.app/features/hardware-transcoding/" rel="noopener">transcoding docs&lt;/a>).&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>What it needs.&lt;/strong> Immich&amp;rsquo;s minimum is 6 GB of RAM and 2 cores. It recommends 8 GB and 4 cores. A 4 GB system can run it with machine learning disabled (&lt;a href="https://docs.immich.app/install/requirements/" rel="noopener">requirements&lt;/a>). The Postgres data belongs on local SSD, never a network share. Immich also advises against running Docker inside an LXC container. That matters on Proxmox. The one first-hand side-by-side I found, &lt;a href="https://kittmedia.com/en/2025/ente-vs-immich-a-comparison/" rel="noopener">KittMedia&amp;rsquo;s&lt;/a> from June 2025 on a Ryzen 5 PRO 2400GE, saw Immich at more than 900 MiB while playing a video and peaking at 1.6 GiB and about 25% CPU during an upload. The same library took more than 24 hours to import into Immich and about 4 into Ente. That is one library on 2025 versions. For disk, Immich&amp;rsquo;s own requirements say thumbnails and transcoded video add 10 to 20 percent to the library on average.&lt;/p>
&lt;p>&lt;strong>Storage.&lt;/strong> Media goes to a filesystem path, &lt;code>UPLOAD_LOCATION&lt;/code>, and Immich&amp;rsquo;s FAQ shows a network share mounted as a Docker volume for it (&lt;a href="https://docs.immich.app/FAQ/" rel="noopener">FAQ&lt;/a>). The database is Postgres 14 to 19 with VectorChord (Immich&amp;rsquo;s stated range is 14 or newer, below 20). Background jobs queue through Redis via BullMQ (&lt;a href="https://docs.immich.app/developer/architecture/" rel="noopener">architecture docs&lt;/a>). The v3.4.1 compose file runs Valkey 9 there, beside a Postgres 14 image with VectorChord 0.4.3. For object storage, look at Ente.&lt;/p>
&lt;p>&lt;strong>Mobile.&lt;/strong> Native iOS and Android apps back up in the background. Since v3.0 they also edit non-destructively and read text with OCR, though v3.0 dropped three things from mobile editing: recoloring, live photos, and assets that exist only on the phone.&lt;/p>
&lt;p>&lt;strong>Pick Immich if&lt;/strong> you want everything included free, you have a server with 8 GB of RAM and 4 cores (Immich&amp;rsquo;s recommendation) and, on x86, a CPU that supports x86-64-v2, and you do not need end-to-end encryption.&lt;/p>
&lt;h2 id="photoprism">PhotoPrism&lt;/h2>
&lt;p>&lt;strong>Status, November 18, 2026.&lt;/strong> PhotoPrism ships date-stamped builds. The current stable is 261029-963b58c50 (October 29, 2026) (&lt;a href="https://github.com/photoprism/photoprism/releases" rel="noopener">releases&lt;/a>). It reworks the database layer and adds experimental PostgreSQL support, a new Export dialog in the photo viewer and updated maps. It also turns on MCP access for eligible users by default; PhotoPrism&amp;rsquo;s upgrade notes say to set &lt;code>PHOTOPRISM_DISABLE_MCP&lt;/code> to &amp;ldquo;true&amp;rdquo; to switch it off for everyone, and &lt;code>PHOTOPRISM_OAUTH_APPS&lt;/code> to &amp;ldquo;none&amp;rdquo; to stop outside apps connecting through OAuth. The build before it, 261007 (October 7), moved image classification to ONNX models and let all of PhotoPrism&amp;rsquo;s built-in models run on a supported NVIDIA GPU. Build 260919 (September 19) brought new face detection and embedding models; an existing library keeps its current model until you run &lt;code>photoprism faces migrate&lt;/code>, which re-embeds every face and keeps the names already assigned (&lt;a href="https://docs.photoprism.app/release-notes/" rel="noopener">release notes&lt;/a>).&lt;/p>
&lt;p>&lt;strong>Face recognition is free; the paid tiers buy administration.&lt;/strong> PhotoPrism Community Edition is AGPL and free, and its &lt;a href="https://www.photoprism.app/editions/" rel="noopener">editions page&lt;/a> (read September 26, 2026) marks People &amp;amp; Faces, Duplicate Detection and RAW images as included in every self-hosted edition, so the paid tiers sell extras around them: Essentials (€2 a month, billed annually) adds 3D vector and satellite maps, enhanced geocoding and the User and Viewer roles; Plus (from €6 a month) adds the admin web UI, hardened security and private chat. The same page lists PikaPods as a fully managed host from $6.50 a month (prices re-read November 18, 2026). The catches are on the phone and in the release pace.&lt;/p>
&lt;p>&lt;strong>Hardware.&lt;/strong> PhotoPrism asks for at least 2 cores, 3 GB of RAM, a 64-bit OS and 4 GB of swap (&lt;a href="https://docs.photoprism.app/getting-started/" rel="noopener">getting started&lt;/a>). RAM should match the core count. Video transcoding can use Intel Quick Sync and VA-API, NVIDIA, Vulkan, Apple Video Toolbox, or a Raspberry Pi (&lt;a href="https://docs.photoprism.app/getting-started/advanced/transcoding/" rel="noopener">transcoding docs&lt;/a>), and since build 261007 the built-in AI models can use a supported NVIDIA GPU too. The database is MariaDB 10.5.12 or newer, or SQLite 3, which PhotoPrism calls &amp;ldquo;generally not a good choice for users who require scalability and high performance&amp;rdquo;; PostgreSQL is experimental as of build 261029.&lt;/p>
&lt;p>Mobile is the weak spot. PhotoPrism ships an official PWA (&lt;a href="https://docs.photoprism.app/user-guide/pwa/" rel="noopener">PWA docs&lt;/a>) and lists three native apps that other companies and individual developers maintain (Gallery for PhotoPrism, PhotoSync, Stream) (&lt;a href="https://docs.photoprism.app/user-guide/native-apps/" rel="noopener">native apps docs&lt;/a>). If the family lives on iPhones, this is where PhotoPrism loses.&lt;/p>
&lt;p>&lt;strong>Pick PhotoPrism if&lt;/strong> the library already lives in folders you browse from a desktop, a PWA on the phone is acceptable, and its slower release pace is a feature rather than a worry.&lt;/p>
&lt;h2 id="ente-photos-self-hosted">Ente Photos (self-hosted)&lt;/h2>
&lt;p>&lt;strong>Status, November 18, 2026.&lt;/strong> The mobile app is at v1.3.70 (GitHub release photos-v1.3.70, an Android build, November 13) (&lt;a href="https://github.com/ente/ente/releases" rel="noopener">releases&lt;/a>). The desktop app is at v1.7.31 (October 27) (&lt;a href="https://github.com/ente/photos-desktop/releases" rel="noopener">desktop releases&lt;/a>). The server, Museum, has no GitHub release of its own. The quickstart pulls &lt;code>ghcr.io/ente/server&lt;/code> with no version tag, and Ente&amp;rsquo;s upgrade page says to replace any &lt;code>ghcr.io/ente-io/&lt;/code> image reference with &lt;code>ghcr.io/ente/&lt;/code> before pulling (&lt;a href="https://ente.com/help/self-hosting/installation/upgrade" rel="noopener">upgrade docs&lt;/a>).&lt;/p>
&lt;p>This is the only end-to-end encrypted option. All ML runs on the device with ONNX Runtime: MobileCLIP for search, YOLO5Face for face detection and MobileFaceNet for face embeddings, and the indexes are encrypted before they are stored on the server (&lt;a href="https://ente.com/ml/" rel="noopener">ML architecture page&lt;/a>). Cure53 audited Ente in a CERN-sponsored review (Ente&amp;rsquo;s post of November 3, 2025), and its new Rust crypto layer passed an independent review by winfunc (April 3, 2026) (&lt;a href="https://ente.com/blog/" rel="noopener">blog&lt;/a>).&lt;/p>
&lt;p>The server is small. Museum (Go), Postgres and any S3-compatible storage; the quickstart ships MinIO for the objects (&lt;a href="https://ente.com/help/self-hosting/administration/object-storage" rel="noopener">object storage docs&lt;/a>). Ente&amp;rsquo;s minimum is 1 GB of RAM and 1 core, with Docker Compose 2.30 or newer (&lt;a href="https://ente.com/help/self-hosting/installation/requirements" rel="noopener">requirements&lt;/a>). In KittMedia&amp;rsquo;s June 2025 comparison the Ente server apps used 130-150 MiB and the S3 store 300-500 MiB while playing a video. Uploads barely registered on the server. The phone does that work.&lt;/p>
&lt;p>&lt;strong>Two admin steps the quickstart leaves to you.&lt;/strong> The first account registered is treated as the admin until you whitelist one in &lt;code>museum.yaml&lt;/code>. Register yours first on anything reachable from outside (&lt;a href="https://ente.com/help/self-hosting/administration/users" rel="noopener">user management&lt;/a>). And each account&amp;rsquo;s storage quota and validity are raised with the Ente CLI: &lt;code>ente admin update-subscription -a ADMIN_EMAIL -u USER_EMAIL --no-limit True&lt;/code> (&lt;a href="https://ente.com/help/self-hosting/administration/cli" rel="noopener">CLI docs&lt;/a>).&lt;/p>
&lt;p>&lt;strong>2026 features.&lt;/strong> February&amp;rsquo;s update added likes and comments, plus an admin role. March brought an offline gallery and ML improvements, April added Memory Lane, and on September 9 came library sharing for families and on-device ML that Ente says is up to 10 times faster. On October 28 Ente announced a mosaic gallery, pinch gestures, new editing tools and refreshed albums in Photos 1.3.66, and a new Rust command-line tool (&lt;a href="https://ente.com/blog/" rel="noopener">blog&lt;/a>).&lt;/p>
&lt;p>&lt;strong>Or let Ente run it.&lt;/strong> Ente&amp;rsquo;s cloud gives 10 GB free, then $2.49 a month for 50 GB, $4.99 for 200 GB, $9.99 for 1,000 GB and $19.99 for 2,000 GB (&lt;a href="https://ente.com/#pricing" rel="noopener">pricing&lt;/a>, read November 18, 2026). The encryption model does not change.&lt;/p>
&lt;p>E2E has a cost. The server cannot read your photos. Ente&amp;rsquo;s Google Takeout import runs in the desktop app on your computer, and a more powerful server will not speed up its on-device ML.&lt;/p>
&lt;p>&lt;strong>Pick Ente if&lt;/strong> end-to-end encryption is non-negotiable, you want S3 storage or the smallest server, or you would rather pay Ente than run a server at all.&lt;/p>
&lt;h2 id="backup-restore-and-lock-in">Backup, restore, and lock-in&lt;/h2>
&lt;p>A self-hosted photo library is only as safe as the backup you actually run.&lt;/p>
&lt;p>&lt;strong>Immich&lt;/strong> stores originals under &lt;code>UPLOAD_LOCATION&lt;/code> as ordinary files. An &lt;code>rsync&lt;/code> to a second disk covers the photos. Albums and faces live in Postgres. Immich writes automatic database backups to &lt;code>UPLOAD_LOCATION/backups&lt;/code>, by default daily at 2:00 AM and keeping the last 14, but they hold metadata only, so they are no use in a restore unless a copy of the originals travels with them. Restores run from the web interface (&lt;a href="https://docs.immich.app/administration/backup-and-restore/" rel="noopener">backup and restore docs&lt;/a>). To walk away, &lt;a href="https://github.com/simulot/immich-go" rel="noopener">immich-go&lt;/a> has an &lt;code>archive from-immich&lt;/code> command that writes the library to a folder.&lt;/p>
&lt;p>&lt;strong>PhotoPrism&lt;/strong> keeps its index in MariaDB (or SQLite) and your photos in the originals folder. It also writes a YAML sidecar for each photo and YAML backups of albums, which let you view and restore album and photo metadata even without a database backup (&lt;a href="https://docs.photoprism.app/user-guide/backups/export/" rel="noopener">export docs&lt;/a>).&lt;/p>
&lt;p>&lt;strong>Ente&lt;/strong> is the most awkward to back up. Back up its Postgres database and encrypted object store together, because the photos cannot be decrypted without the per-file keys the database holds (&lt;a href="https://ente.com/help/self-hosting/administration/backup" rel="noopener">backup docs&lt;/a>). The export that gives you usable files is the desktop app&amp;rsquo;s Export Data, which writes a local copy and can keep syncing it, or the Ente CLI (&lt;a href="https://ente.com/help/photos/migration/export/" rel="noopener">export docs&lt;/a>). If you want to leave Ente later, plan it from a healthy desktop.&lt;/p>
&lt;p>Whichever you pick, back up the originals and the database to a different physical disk and a different building. The 3-2-1 rule covers family photos too; our &lt;a href="https://techfuelhq.com/homelab/restic-vs-borg-vs-kopia-2026/">restic vs Borg vs Kopia comparison&lt;/a> covers the tools that do it, and the &lt;a href="https://techfuelhq.com/homelab/best-nas-hard-drives-2026/">NAS drive guide&lt;/a> or an &lt;a href="https://techfuelhq.com/homelab/nas-from-old-pc-2026/">old-PC NAS&lt;/a> gives the second copy somewhere to live.&lt;/p>
&lt;h2 id="migration-off-google-photos">Migration off Google Photos&lt;/h2>
&lt;p>All three read a Google Takeout. Immich&amp;rsquo;s route is immich-go&amp;rsquo;s &lt;code>upload from-google-photos&lt;/code>, which the &lt;a href="https://techfuelhq.com/tutorials/immich-google-photos-migration-2026/">Immich Google Photos migration walkthrough&lt;/a> on this site takes step by step. PhotoPrism indexes the extracted Takeout from its originals or import folder and reads dates and locations from each photo&amp;rsquo;s JSON file, but it does not import Google&amp;rsquo;s albums yet (&lt;a href="https://docs.photoprism.app/user-guide/use-cases/google/" rel="noopener">Google Photos docs&lt;/a>); Ente imports in its desktop app and recommends extracting the ZIPs into one parent folder first, so each file meets its metadata (&lt;a href="https://ente.com/help/photos/migration/from-google-photos/" rel="noopener">Ente Takeout guide&lt;/a>). Budget disk for the move. A 200 GB library arrives as roughly 200 GB of ZIPs; PhotoPrism and Ente want them extracted, which is another 200 GB before the library lands on the server, so I would keep 600 GB free until the import is done. immich-go reads the ZIPs as they are, which saves the extraction.&lt;/p>
&lt;p>Moving between the three is harder than leaving Google. Dates are what break. A user moving an Immich library into Ente reported videos landing on the import date because the XMP sidecars were not read (&lt;a href="https://github.com/ente/ente/issues/9385" rel="noopener">ente#9385&lt;/a>). Export with sidecars, import one test folder, and check the dates before moving everything.&lt;/p>
&lt;p>If your library lives on a separate NAS or storage VM, this is a good moment to revisit storage layout. The Proxmox + TrueNAS + Unraid post on this site walks through which backend handles the photo-library access pattern best — sequential writes during ingest, then bursty random reads at thumbnail-rendering time. See &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">Proxmox vs TrueNAS vs Unraid storage backends 2026&lt;/a> for the IOPS math.&lt;/p>
&lt;h2 id="what-id-do-on-day-one">What I&amp;rsquo;d do on day one&lt;/h2>
&lt;ol>
&lt;li>Spin up a mini PC or VM with 4 cores and 16 GB of RAM: Immich&amp;rsquo;s recommended core count, twice its recommended RAM, and enough for any of the three. The &lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">best mini-PCs for homelab in 2026&lt;/a> shortlist works for all three projects.&lt;/li>
&lt;li>On x86, confirm the CPU (or the CPU type the VM is given) supports x86-64-v2 before installing Immich v3.&lt;/li>
&lt;li>If you have an NVIDIA GPU, point Immich&amp;rsquo;s ML at CUDA before the first import, so the first indexing pass over a large library runs on it.&lt;/li>
&lt;li>Run a 5,000-photo trial import before pointing the family at it. Check face recognition on real subjects, check the iOS background backup, and give it one weekend before committing.&lt;/li>
&lt;li>Back up the originals and the database separately. The originals are a filesystem; copy them with &lt;code>rsync&lt;/code>. The database has the faces, albums and embeddings, and Immich already dumps it nightly into &lt;code>UPLOAD_LOCATION/backups&lt;/code> for you to copy off the box.&lt;/li>
&lt;/ol>
&lt;hr>
&lt;p>&lt;em>Spinning up a Proxmox host for any of these? The &lt;a href="https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/">ZFS on Proxmox guide&lt;/a> covers pool setup and ARC tuning — photo ingest is write-heavy and ZFS compression with dataset isolation is the right way to organize photo storage separately from VM disks. For access from anywhere, the &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale tutorial&lt;/a> gets remote photo library access working without a public port. The full self-hosted stack (Immich + Jellyfin + Vaultwarden + 9 more) is mapped out in the &lt;a href="https://techfuelhq.com/articles/self-hosted-apps-replace-saas-2026/">12 best self-hosted apps article&lt;/a>, and if you would rather run Nextcloud for files and add a photo app to it, start with the &lt;a href="https://techfuelhq.com/tutorials/nextcloud-aio-docker-setup-2026/">Nextcloud AIO setup guide&lt;/a>.&lt;/em>&lt;/p></description></item><item><title>How to Self-Host a Local LLM on a Single RTX 5060 in 2026</title><link>https://techfuelhq.com/tutorials/self-host-local-llm-rtx-5060-2026/</link><pubDate>Wed, 06 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/self-host-local-llm-rtx-5060-2026/</guid><atom:updated>2026-11-18T04:49:22Z</atom:updated><description>&lt;p>The first time I spun up Llama 3.1 8B on my own machine, with no API key, no rate limit, and no telemetry phoning home, I sat there asking it the kind of half-formed questions I&amp;rsquo;d never paste into a hosted chat window. That moment is what most people are actually buying when they self-host a model. Not raw performance. Not even cost savings. The simple fact that the prompt and the answer never leave the box.&lt;/p>
&lt;p>The hardware math starts from NVIDIA&amp;rsquo;s launch prices: &lt;a href="https://www.nvidia.com/en-us/geforce/news/rtx-5060-desktop-family-laptop-5060-coming-soon/" rel="noopener">$299 for the 8GB RTX 5060&lt;/a>, which arrived in May 2025, and &lt;a href="https://investor.nvidia.com/news/press-release-details/2025/NVIDIA-Blackwell-GeForce-RTX-Arrives-for-Every-Gamer-Starting-at-299/default.aspx" rel="noopener">$429 for the 16GB RTX 5060 Ti&lt;/a>.&lt;/p>
&lt;p>&lt;strong>Street prices, November 17, 2026:&lt;/strong> Newegg listed the PNY Dual Fan OC RTX 5060 Ti 16GB at $799.99 and the PNY Dual Fan RTX 5060 8GB at $519.99, both far above launch. The &lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU price index&lt;/a> tracks the 5060 Ti 16GB every day, and our &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/">RTX 5060 Ti vs RX 9060 XT price breakdown&lt;/a> and &lt;a href="https://techfuelhq.com/articles/ram-ssd-price-crisis-2026/">the 2026 RAM/SSD price crisis&lt;/a> explain why.&lt;/p>
&lt;p>Open-weights models such as Llama 3.1 8B, Qwen 2.5 and Mistral 7B run well on these cards at 4-bit quantization. This guide is the build I&amp;rsquo;d hand a friend who asked me to skip the cloud and run their own assistant. If you want the wider view first, showing where the chat model sits next to image generation, speech, and a coding assistant, start with the &lt;a href="https://techfuelhq.com/articles/self-hosted-ai-stack-2026/">self-hosted AI stack overview&lt;/a>. For what fits at every VRAM size, not just these two cards, see &lt;a href="https://techfuelhq.com/articles/local-llm-by-gpu-vram-2026/">local LLMs by GPU VRAM&lt;/a>.&lt;/p>
&lt;h2 id="how-i-tested">How I tested&lt;/h2>
&lt;p>Everything in this guide was set up and timed on my own hardware in St. Louis County, MO. The primary test rig is an RTX 5060 Ti 16GB on a Linux box running Ollama as the daemon; an RTX 5060 8GB sits in a second machine I use to validate the smaller-model claims. Models pulled and benched between mid-April and early May 2026: Llama 3.1 8B, Llama 3.3 70B (Q4 quant, partially offloaded), Qwen 2.5 7B, and Mistral 7B, matching the set named in the rest of the article. The one gotcha that cost me an evening: Ollama&amp;rsquo;s default context window is 2048, and bumping it to 8192 on the 8GB card pushed me into shared-memory swap and tanked tokens/sec by about 40%. Lesson logged. Last verified: 2026-05-06 by LK Wood IV.&lt;/p>
&lt;p>The tokens/sec figures in the table come from published benchmarks for these exact cards: LocalScore for the RTX 5060 Ti 16GB and Database Mart&amp;rsquo;s Ollama 0.9.5 testing for the RTX 5060 8GB, cited at the table itself and re-read November 18, 2026. Street prices are a Newegg catalogue reading from November 17, 2026. The commands and settings below were checked against Ollama&amp;rsquo;s, llama.cpp&amp;rsquo;s and LM Studio&amp;rsquo;s documentation on November 18, 2026.&lt;/p>
&lt;h2 id="why-run-it-locally">Why run it locally&lt;/h2>
&lt;p>The privacy angle is the one that matters most. Financial planning prompts, draft emails about coworkers, half-formed business ideas: none of that should sit in a third-party log file. 8B-class models handle the daily work cleanly: summarization, code completion, and retrieval over your own documents, and with a local runner none of it leaves the machine.&lt;/p>
&lt;h2 id="rtx-5060-hardware-reality-check">RTX 5060 hardware reality check&lt;/h2>
&lt;p>Three cards in the family, two that matter for LLMs:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>RTX 5060 8GB&lt;/strong> — $299 at launch, &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5060-family/" rel="noopener">3,840 CUDA cores on Blackwell, 128-bit GDDR7&lt;/a>, 145 W total graphics power. Runs up to 7B-8B at 4-bit with usable speed.&lt;/li>
&lt;li>&lt;strong>RTX 5060 Ti 8GB&lt;/strong> — $379 at launch. Same VRAM ceiling, slightly more compute. Don&amp;rsquo;t buy this for LLMs; the 8GB ceiling is the bottleneck.&lt;/li>
&lt;li>&lt;strong>RTX 5060 Ti 16GB&lt;/strong> — $429 at launch, &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5060-family/" rel="noopener">4,608 CUDA cores, 759 AI TOPS, 128-bit GDDR7&lt;/a> at &lt;a href="https://www.bestgpusforai.com/gpu-comparison/5060-ti-vs-5070" rel="noopener">448 GB/s&lt;/a>, 180 W total graphics power. This is the LLM card.&lt;/li>
&lt;/ul>
&lt;p>The 8GB 5060 runs 7B-8B models at about 54-73 tokens/sec in Database Mart&amp;rsquo;s Ollama tests: enough for chat, coding help, and document Q&amp;amp;A. The 16GB 5060 Ti adds 14B models held entirely in VRAM, plus 30B-class MoE models with llama.cpp&amp;rsquo;s &lt;a href="https://github.com/ggml-org/llama.cpp/blob/master/tools/server/README.md" rel="noopener">&lt;code>--cpu-moe&lt;/code> offload&lt;/a>. On Newegg&amp;rsquo;s November 17 listings the step from 8GB to 16GB cost $280, and it is the step that changes which models you can run at all. I ran the 16GB for this guide; notes below assume it, with 8GB caveats called out where they matter. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-review-2026/">RTX 5060 Ti review&lt;/a>, the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-review-2026/">RTX 5060 review&lt;/a> and our &lt;a href="https://techfuelhq.com/articles/rtx-5060-ti-8gb-vs-16gb-2026/">5060 Ti 8GB vs 16GB comparison&lt;/a> cover the cards beyond LLM use.&lt;/p>
&lt;h3 id="where-to-buy">Where to buy&lt;/h3>
&lt;p>The 16GB 5060 Ti first, since it is the card this page recommends for LLMs, then the 8GB 5060 for 7B-8B models only. Both links are model searches, so you see every board partner&amp;rsquo;s card; the &lt;a href="https://techfuelhq.com/data/deal-or-mirage/">Deal or Mirage page&lt;/a> keeps the dated Newegg baseline to judge a Black Friday 5060 Ti price against.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=RTX&amp;#43;5060&amp;#43;Ti&amp;#43;16GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/tutorials/self-host-local-llm-rtx-5060-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DRTX%2B5060%2BTi%2B16GB" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/tutorials/self-host-local-llm-rtx-5060-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=RTX&amp;#43;5060&amp;#43;8GB&amp;#43;graphics&amp;#43;card&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/tutorials/self-host-local-llm-rtx-5060-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DRTX%2B5060%2B8GB" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/tutorials/self-host-local-llm-rtx-5060-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="software-stack-ollama-vs-lm-studio-vs-vllm-vs-llamacpp">Software stack: Ollama vs LM Studio vs vLLM vs llama.cpp&lt;/h2>
&lt;p>Four tools; three of them sit on the same llama.cpp foundation, and vLLM is its own engine. Pick by friction tolerance:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>llama.cpp&lt;/strong> — the &lt;a href="https://github.com/ggml-org/llama.cpp" rel="noopener">C/C++ inference engine&lt;/a> under the first three. Fastest, most flexible, most setup. You compile it, manage GGUF files, and write your own server config. Graduate here once Ollama starts feeling limited.&lt;/li>
&lt;li>&lt;strong>Ollama&lt;/strong> — daemon wrapping llama.cpp with a clean CLI and model registry. &lt;code>ollama pull qwen2.5:7b&lt;/code> and you&amp;rsquo;re chatting in 60 seconds. What I run on my Linux box for LAN serving.&lt;/li>
&lt;li>&lt;strong>LM Studio&lt;/strong> — desktop GUI on llama.cpp. Closed UI, open backend. Best for Windows users who want a polished interface and one-click downloads. Slightly slower than Ollama at dense-model decode (5-11% in &lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-lm-studio-rtx-5080-2026/">my same-GPU head-to-head&lt;/a>) but faster at prompt ingestion, and easier without the CLI.&lt;/li>
&lt;li>&lt;strong>vLLM&lt;/strong> — high-throughput batched serving for data center GPUs with PagedAttention. Overkill for a single 5060 unless you&amp;rsquo;re serving multiple concurrent users.&lt;/li>
&lt;/ul>
&lt;p>This guide shows &lt;strong>Ollama on Linux&lt;/strong> and &lt;strong>LM Studio on Windows&lt;/strong> because each is the lowest-friction path on its operating system. Either produces similar token rates on the same model and quantization.&lt;/p>
&lt;h2 id="step-by-step-setup--linux-ollama">Step-by-step setup — Linux (Ollama)&lt;/h2>
&lt;p>I run Ollama on Ubuntu 24.04 LTS with the NVIDIA proprietary 575+ driver. Steps:&lt;/p>
&lt;ol>
&lt;li>Install the NVIDIA driver (&lt;code>sudo ubuntu-drivers install&lt;/code>) and reboot. Verify with &lt;code>nvidia-smi&lt;/code>, which should print your card. Ollama&amp;rsquo;s &lt;a href="https://docs.ollama.com/gpu" rel="noopener">GPU page&lt;/a> lists the RTX 5060 and 5060 Ti (compute capability 12.0) and asks for driver 550 or newer; install the newest driver NVIDIA offers for your card.&lt;/li>
&lt;li>Install Ollama: &lt;code>curl -fsSL https://ollama.com/install.sh | sh&lt;/code>. It runs as a systemd service, and Ollama binds &lt;code>127.0.0.1:11434&lt;/code> by default, so only this machine can reach it.&lt;/li>
&lt;li>Pull a model: &lt;code>ollama pull qwen2.5:7b&lt;/code> (4.7GB in Ollama&amp;rsquo;s library). For 16GB cards, also try &lt;code>ollama pull qwen2.5:14b&lt;/code> (9.0GB).&lt;/li>
&lt;li>Test: &lt;code>ollama run qwen2.5:7b &amp;quot;Write a Python function to detect duplicate files by hash.&amp;quot;&lt;/code> Then run &lt;code>ollama ps&lt;/code>: the &lt;code>PROCESSOR&lt;/code> column should read &lt;code>100% GPU&lt;/code>. Any CPU share means part of the model spilled out of VRAM.&lt;/li>
&lt;li>Optional LAN exposure: run &lt;code>sudo systemctl edit ollama.service&lt;/code>, add &lt;code>Environment=&amp;quot;OLLAMA_HOST=0.0.0.0:11434&amp;quot;&lt;/code> under &lt;code>[Service]&lt;/code>, then &lt;code>sudo systemctl daemon-reload &amp;amp;&amp;amp; sudo systemctl restart ollama&lt;/code>. Point &lt;a href="https://github.com/open-webui/open-webui" rel="noopener">Open WebUI&lt;/a> from a &lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">low-power mini PC&lt;/a> at the GPU box.&lt;/li>
&lt;/ol>
&lt;blockquote>
&lt;p>&lt;strong>Warning:&lt;/strong> Ollama&amp;rsquo;s &lt;a href="https://docs.ollama.com/api/authentication" rel="noopener">local API needs no authentication&lt;/a>, so &lt;code>0.0.0.0&lt;/code> hands it to every device that can reach the box. Ollama&amp;rsquo;s default &lt;code>127.0.0.1&lt;/code> binding is the safe choice when Open WebUI runs on the same machine; otherwise set &lt;code>OLLAMA_HOST&lt;/code> to the box&amp;rsquo;s own LAN address rather than &lt;code>0.0.0.0&lt;/code>, firewall the port, and never forward it on your router. Ollama&amp;rsquo;s FAQ shows an Nginx proxy for putting a server you control in front of it, and our &lt;a href="https://techfuelhq.com/tutorials/ollama-docker-gpu-2026/">Ollama Docker guide&lt;/a> covers the same risk for containers.&lt;/p>&lt;/blockquote>
&lt;p>I treat the GPU box as a headless inference node and hit it from a laptop over &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">my 10G homelab link&lt;/a>.&lt;/p>
&lt;p>To update Ollama later, run the same install script again. Models live in &lt;code>/usr/share/ollama/.ollama/models&lt;/code> with the standard Linux installer; set &lt;code>OLLAMA_MODELS&lt;/code> on the service to keep them on a bigger SSD, and give the &lt;code>ollama&lt;/code> user access to that directory with &lt;code>sudo chown -R ollama:ollama &amp;lt;directory&amp;gt;&lt;/code>, as Ollama&amp;rsquo;s FAQ says. Ollama&amp;rsquo;s &lt;a href="https://docs.ollama.com/linux" rel="noopener">Linux page&lt;/a> also lists the uninstall steps: stop and disable the service, remove its unit file, binary and libraries, then remove the downloaded models and the &lt;code>ollama&lt;/code> user and group.&lt;/p>
&lt;h2 id="step-by-step-setup--windows-lm-studio">Step-by-step setup — Windows (LM Studio)&lt;/h2>
&lt;p>LM Studio is the one-installer path on Windows 11.&lt;/p>
&lt;ol>
&lt;li>Update the NVIDIA driver through the &lt;a href="https://www.nvidia.com/en-us/software/nvidia-app/" rel="noopener">NVIDIA app&lt;/a> or NVIDIA&amp;rsquo;s driver download page. Older drivers on Blackwell silently fall back to CPU inference.&lt;/li>
&lt;li>Install LM Studio from the &lt;a href="https://lmstudio.ai/" rel="noopener">official site&lt;/a>.&lt;/li>
&lt;li>In the Discover tab (Ctrl + 2), search &amp;ldquo;Qwen2.5 7B Instruct GGUF&amp;rdquo;. Pick the quantization — &lt;code>Q4_K_M&lt;/code> for the 8GB card or &lt;code>Q5_K_M&lt;/code>/&lt;code>Q6_K&lt;/code> for the 16GB; LM Studio&amp;rsquo;s own advice is a 4-bit option or higher. Download.&lt;/li>
&lt;li>In the Chat tab, load the model and send a test prompt. In Task Manager (&lt;code>Ctrl + Shift + Esc &amp;gt; Performance &amp;gt; GPU&lt;/code>), watch Dedicated GPU memory and Shared GPU memory while the model loads; Shared memory climbing means it is spilling out of VRAM.&lt;/li>
&lt;li>Optional: start the local server from LM Studio&amp;rsquo;s Developer tab (the &amp;ldquo;Start server&amp;rdquo; switch) or with &lt;code>lms server start&lt;/code>. Any tool that speaks the OpenAI API (Continue, your own scripts) can hit &lt;code>http://localhost:1234/v1&lt;/code>, the address LM Studio&amp;rsquo;s OpenAI-compatibility docs use. LM Studio can also serve on your local network; keep it on localhost unless another machine needs it.&lt;/li>
&lt;/ol>
&lt;p>Windows is friendlier; Linux is faster and cleaner once installed. For an always-on inference box, Linux wins on uptime and resource overhead.&lt;/p>
&lt;p>One note on storage: GGUF model files add up quickly. A &lt;code>Q5_K_M&lt;/code> file of a 14B parameter model takes roughly 10 GB on disk, and you will collect three or four before settling on a daily favorite.&lt;/p>
&lt;p>If you run this on a dedicated server with a NAS underneath, the storage layer matters more than people admit; the &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">Proxmox vs TrueNAS vs Unraid storage backend comparison for 2026&lt;/a> covers ZFS vs btrfs, NVMe SLOG, and the IOPS profile that keeps model loads from stalling on first inference.&lt;/p>
&lt;h2 id="8gb-vram-reality-vs-the-pcie-50-x8-partial-offload-cliff">8GB VRAM reality vs the PCIe 5.0 x8 partial-offload cliff&lt;/h2>
&lt;p>Dense LLM token generation is memory-bandwidth bound: every single output token has to read every active model weight once. Inside the RTX 5060&amp;rsquo;s onboard &lt;code>8 GB&lt;/code> GDDR7 pool (&lt;code>448 GB/s&lt;/code>), a &lt;code>3B–8B&lt;/code> model streams at roughly 54–114 tokens/sec across Database Mart&amp;rsquo;s tests. Spill even a handful of transformer layers out of VRAM, however, and every token waits on the card&amp;rsquo;s PCIe 5.0 x8 interface (&lt;code>~31.5 GB/s&lt;/code> unidirectional ceiling, half of a full x16 slot, or &lt;code>~15.7 GB/s&lt;/code> on older PCIe 4.0 motherboards) plus the CPU working from system RAM. Ollama&amp;rsquo;s FAQ makes the same point from the other side: a model that fits entirely on one GPU typically performs best because less data crosses the PCI bus.&lt;/p>
&lt;p>Instead of slowing down a little, generation falls off a cliff. Check any candidate GGUF in our &lt;a href="https://techfuelhq.com/tools/llm-vram-calculator/">LLM VRAM calculator&lt;/a> first, and use this fit matrix on the 8GB RTX 5060 versus the 16GB 5060 Ti:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Model &amp;amp; GGUF quant&lt;/th>
&lt;th scope="col">Weight file&lt;/th>
&lt;th scope="col">Total VRAM at &lt;code>4K–8K&lt;/code> ctx (&lt;code>FP16&lt;/code> vs &lt;code>Q8_0&lt;/code> KV)&lt;/th>
&lt;th scope="col">Fit on &lt;strong>8GB RTX 5060&lt;/strong> (Headless Linux vs Win 11)&lt;/th>
&lt;th scope="col">Fit on &lt;strong>16GB RTX 5060 Ti&lt;/strong>&lt;/th>
&lt;th scope="col">Expected decode behavior&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Model &amp;amp; GGUF quant">&lt;strong>3B–4B (&lt;code>Q4_K_M&lt;/code> / &lt;code>Q8_0&lt;/code>)&lt;/strong> &lt;em>(Llama 3.2 3B, Gemma 3 4B)&lt;/em>&lt;/td>
&lt;td data-label="Weight file">&lt;code>~2.0–3.8 GB&lt;/code>&lt;/td>
&lt;td data-label="Total VRAM at 4K–8K ctx (FP16 vs Q8_0 KV)">&lt;code>~2.6–4.8 GB&lt;/code>&lt;/td>
&lt;td data-label="Fit on 8GB RTX 5060 (Headless Linux vs Win 11)">&lt;strong>100% VRAM resident&lt;/strong> on both Windows 11 &amp;amp; Linux&lt;/td>
&lt;td data-label="Fit on 16GB RTX 5060 Ti">&lt;strong>100% VRAM resident&lt;/strong> (&lt;code>32K+&lt;/code> ctx easy)&lt;/td>
&lt;td data-label="Expected decode behavior">&lt;strong>About 75–114 tok/s&lt;/strong> across Database Mart&amp;rsquo;s 3B–4B models on the 8GB card&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model &amp;amp; GGUF quant">&lt;strong>7B–8B &lt;code>Q4_K_M&lt;/code>&lt;/strong> &lt;em>(Qwen 2.5 7B, Llama 3.1 8B, Mistral 7B)&lt;/em>&lt;/td>
&lt;td data-label="Weight file">&lt;code>~4.4–4.9 GB&lt;/code>&lt;/td>
&lt;td data-label="Total VRAM at 4K–8K ctx (FP16 vs Q8_0 KV)">&lt;code>~5.4–6.4 GB&lt;/code>&lt;/td>
&lt;td data-label="Fit on 8GB RTX 5060 (Headless Linux vs Win 11)">&lt;strong>100% VRAM resident&lt;/strong> at &lt;code>4K&lt;/code> on Win 11; fits &lt;code>8K&lt;/code> cleanly on Linux or on Win 11 with &lt;code>Q8_0&lt;/code> KV&lt;/td>
&lt;td data-label="Fit on 16GB RTX 5060 Ti">&lt;strong>100% VRAM resident&lt;/strong> up to &lt;code>32K–64K&lt;/code> ctx&lt;/td>
&lt;td data-label="Expected decode behavior">&lt;strong>About 54–73 tok/s&lt;/strong> on the 8GB 5060 (Database Mart)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model &amp;amp; GGUF quant">&lt;strong>7B–8B &lt;code>Q5_K_M&lt;/code>&lt;/strong> &lt;em>(Llama 3.1 8B / Qwen 2.5 7B higher fidelity)&lt;/em>&lt;/td>
&lt;td data-label="Weight file">&lt;code>~5.4–5.7 GB&lt;/code>&lt;/td>
&lt;td data-label="Total VRAM at 4K–8K ctx (FP16 vs Q8_0 KV)">&lt;code>~6.4–7.3 GB&lt;/code>&lt;/td>
&lt;td data-label="Fit on 8GB RTX 5060 (Headless Linux vs Win 11)">&lt;strong>Fits headless Linux&lt;/strong>; &lt;strong>tight or spills on Win 11&lt;/strong> above &lt;code>4K&lt;/code> ctx unless KV is &lt;code>Q8_0&lt;/code>, because the desktop holds some VRAM&lt;/td>
&lt;td data-label="Fit on 16GB RTX 5060 Ti">&lt;strong>100% VRAM resident&lt;/strong> with generous context&lt;/td>
&lt;td data-label="Expected decode behavior">Full GDDR7 speed if resident; drops sharply once layers spill on Windows&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model &amp;amp; GGUF quant">&lt;strong>14B &lt;code>Q4_K_M&lt;/code>&lt;/strong> &lt;em>(Qwen 2.5 14B, Phi-4 14B)&lt;/em>&lt;/td>
&lt;td data-label="Weight file">&lt;code>~8.5–9.0 GB&lt;/code>&lt;/td>
&lt;td data-label="Total VRAM at 4K–8K ctx (FP16 vs Q8_0 KV)">&lt;code>~9.8–11.2 GB&lt;/code>&lt;/td>
&lt;td data-label="Fit on 8GB RTX 5060 (Headless Linux vs Win 11)">&lt;strong>Spills ~25–40% of layers over PCIe 5.0 x8 to system RAM&lt;/strong> (never fits 8GB VRAM)&lt;/td>
&lt;td data-label="Fit on 16GB RTX 5060 Ti">&lt;strong>100% VRAM resident&lt;/strong> (&lt;code>~33 tok/s&lt;/code>, LocalScore)&lt;/td>
&lt;td data-label="Expected decode behavior">A fraction of GPU-resident speed on partial CPU offload, worse if Windows shared VRAM thrashes&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model &amp;amp; GGUF quant">&lt;strong>30B-A3B MoE (&lt;code>Q4_K_M&lt;/code> + &lt;code>--cpu-moe&lt;/code>)&lt;/strong> &lt;em>(Qwen3-Coder-30B)&lt;/em>&lt;/td>
&lt;td data-label="Weight file">&lt;code>~17–18 GB&lt;/code>&lt;/td>
&lt;td data-label="Total VRAM at 4K–8K ctx (FP16 vs Q8_0 KV)">Attention and shared layers on GPU, routed experts in system RAM&lt;/td>
&lt;td data-label="Fit on 8GB RTX 5060 (Headless Linux vs Win 11)">Too tight on 8GB (&lt;code>attention + KV&lt;/code> starve)&lt;/td>
&lt;td data-label="Fit on 16GB RTX 5060 Ti">&lt;strong>Hybrid option&lt;/strong>: llama.cpp keeps the MoE expert weights on the CPU&lt;/td>
&lt;td data-label="Expected decode behavior">Only ~3B parameters are active per token, which is what makes the hybrid workable&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h3 id="headless-linux-vs-the-windows-11-desktop-on-an-8gb-card">Headless Linux vs the Windows 11 desktop on an 8GB card&lt;/h3>
&lt;p>Why did bumping Ollama&amp;rsquo;s context window from &lt;code>2048&lt;/code> to &lt;code>8192&lt;/code> cost me 40% of my throughput on an 8GB setup until I tuned it? Operating-system VRAM overhead is the hidden culprit.&lt;/p>
&lt;p>On Windows 11, the desktop compositor (&lt;code>dwm.exe&lt;/code>), your monitors and any hardware-accelerated browser or chat windows hold part of that 8 GB before LM Studio or Ollama allocates a single tensor. Task Manager&amp;rsquo;s Performance &amp;gt; GPU page shows Dedicated GPU memory already in use; subtract it from 8 GB to see what a model really gets. On headless Ubuntu Server (no X11/Wayland desktop running), or with your monitor plugged into the CPU&amp;rsquo;s integrated graphics so the RTX 5060 runs as a pure compute card, more of the card is free for weights and context; &lt;code>nvidia-smi&lt;/code> shows the used figure.&lt;/p>
&lt;h3 id="tuning---ctx-size-num_ctx-and-flash-attention-to-stay-off-cpu-ram">Tuning &lt;code>--ctx-size&lt;/code>, &lt;code>num_ctx&lt;/code>, and Flash Attention to stay off CPU RAM&lt;/h3>
&lt;p>Keep an &lt;code>8B&lt;/code> model pinned inside 8GB VRAM at &lt;code>8K&lt;/code> context with Flash Attention and a quantized &lt;code>Q8_0&lt;/code> KV cache, supported in both &lt;a href="https://docs.ollama.com/faq" rel="noopener">Ollama&amp;rsquo;s environment settings&lt;/a> and &lt;a href="https://github.com/ggml-org/llama.cpp" rel="noopener">&lt;code>llama.cpp&lt;/code>&lt;/a>:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Ollama (&lt;code>sudo systemctl edit ollama.service&lt;/code> or Windows user env vars):&lt;/strong> Ollama turns Flash Attention on automatically where the backend supports it; &lt;code>OLLAMA_FLASH_ATTENTION=1&lt;/code> forces it. &lt;code>OLLAMA_KV_CACHE_TYPE=q8_0&lt;/code> uses about half the memory of the default &lt;code>f16&lt;/code> cache and needs Flash Attention. Current Ollama releases already &lt;a href="https://docs.ollama.com/context-length" rel="noopener">default to a 4k context&lt;/a> on cards with less than 24 GiB of VRAM; raise it per model with &lt;code>PARAMETER num_ctx 8192&lt;/code> in a Modelfile (or &lt;code>4096&lt;/code> on a busy Windows 11 desktop), or for every model with &lt;code>OLLAMA_CONTEXT_LENGTH=8192&lt;/code>, instead of blindly requesting &lt;code>32768&lt;/code>. Confirm residency with &lt;code>ollama ps&lt;/code>: the &lt;code>PROCESSOR&lt;/code> column must read &lt;strong>&lt;code>100% GPU&lt;/code>&lt;/strong>, never a CPU/GPU split.&lt;/li>
&lt;li>&lt;strong>Bare &lt;code>llama-server&lt;/code> (&lt;code>llama.cpp&lt;/code>):&lt;/strong> launch with &lt;code>llama-server -m model-q4_k_m.gguf -ngl 99 --ctx-size 8192 -fa on -ctk q8_0 -ctv q8_0 -ub 512&lt;/code>. Current builds take &lt;code>-fa on|off|auto&lt;/code> (default &lt;code>auto&lt;/code>), and &lt;code>-ctk&lt;/code>/&lt;code>-ctv q8_0&lt;/code> set the K and V cache types. &lt;code>llama-server&lt;/code> listens on &lt;code>127.0.0.1&lt;/code> unless you pass &lt;code>--host&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Disable NVIDIA Windows &amp;ldquo;Sysmem Fallback&amp;rdquo; traps:&lt;/strong> if Windows silently spills 400 MB into shared system memory instead of throwing a clean out-of-memory warning, your token rate craters without an error banner; watch Dedicated GPU Memory vs Shared GPU Memory in Task Manager (&lt;code>Ctrl + Shift + Esc &amp;gt; Performance &amp;gt; GPU&lt;/code>).&lt;/li>
&lt;/ul>
&lt;p>For a daily driver, I run &lt;code>Qwen 2.5 14B Q4_K_M&lt;/code> on the 16GB 5060 Ti and &lt;code>Llama 3.1 8B&lt;/code> or &lt;code>Qwen 2.5 7B Q4_K_M&lt;/code> on the 8GB 5060.&lt;/p>
&lt;h2 id="tokenssec-benchmarks">Tokens/sec benchmarks&lt;/h2>
&lt;p>Below are published third-party numbers, not vendor marketing. The 5060 Ti 16GB rows use &lt;a href="https://www.localscore.ai/accelerator/860" rel="noopener">LocalScore&amp;rsquo;s results&lt;/a> (Q4_K Medium models); the 5060 8GB rows use &lt;a href="https://www.databasemart.com/blog/ollama-gpu-benchmark-rtx5060" rel="noopener">Database Mart&amp;rsquo;s Ollama 0.9.5 testing on an RTX 5060 8GB&lt;/a> at 4-bit quantization. Both read November 18, 2026.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Model&lt;/th>
&lt;th scope="col">Quant&lt;/th>
&lt;th scope="col">Model size&lt;/th>
&lt;th scope="col">Card&lt;/th>
&lt;th scope="col">Tokens/sec (gen)&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Model">Llama 3.2 1B Instruct&lt;/td>
&lt;td data-label="Quant">Q4_K_M&lt;/td>
&lt;td data-label="Model size">-&lt;/td>
&lt;td data-label="Card">RTX 5060 Ti 16GB&lt;/td>
&lt;td data-label="Tokens/sec (gen)">214&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Llama 3.2 3B&lt;/td>
&lt;td data-label="Quant">4-bit&lt;/td>
&lt;td data-label="Model size">2.0 GB&lt;/td>
&lt;td data-label="Card">RTX 5060 8GB&lt;/td>
&lt;td data-label="Tokens/sec (gen)">96&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">DeepSeek-R1 7B&lt;/td>
&lt;td data-label="Quant">4-bit&lt;/td>
&lt;td data-label="Model size">4.7 GB&lt;/td>
&lt;td data-label="Card">RTX 5060 8GB&lt;/td>
&lt;td data-label="Tokens/sec (gen)">58&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Llama 3.1 8B&lt;/td>
&lt;td data-label="Quant">4-bit&lt;/td>
&lt;td data-label="Model size">4.9 GB&lt;/td>
&lt;td data-label="Card">RTX 5060 8GB&lt;/td>
&lt;td data-label="Tokens/sec (gen)">58&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Llama 3.1 8B Instruct&lt;/td>
&lt;td data-label="Quant">Q4_K_M&lt;/td>
&lt;td data-label="Model size">-&lt;/td>
&lt;td data-label="Card">RTX 5060 Ti 16GB&lt;/td>
&lt;td data-label="Tokens/sec (gen)">59&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Mistral 7B&lt;/td>
&lt;td data-label="Quant">4-bit&lt;/td>
&lt;td data-label="Model size">4.4 GB&lt;/td>
&lt;td data-label="Card">RTX 5060 8GB&lt;/td>
&lt;td data-label="Tokens/sec (gen)">73&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Qwen 2.5 14B Instruct&lt;/td>
&lt;td data-label="Quant">Q4_K_M&lt;/td>
&lt;td data-label="Model size">-&lt;/td>
&lt;td data-label="Card">RTX 5060 Ti 16GB&lt;/td>
&lt;td data-label="Tokens/sec (gen)">33&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Three observations stand out. First, the 7–8B class is the sweet spot for both cards, and the same Llama 3.1 8B lands at 58 and 59 tokens/sec on the two cards (different test setups, so read it as a rough match), so for a model that already fits, the 16GB card buys capacity, not speed. Second, the 14B row on the 16GB card is where the extra VRAM earns its upgrade cost. Third, the 1B Llama 3.2 figure (&lt;code>214 t/s&lt;/code>) flies through local RAG chunk tagging or IDE autocomplete. For a site-measured dataset on a bigger card, see our &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput data&lt;/a>.&lt;/p>
&lt;p>For comparison, the &lt;a href="https://www.tomshardware.com/pc-components/gpus/rtx-5070-vs-rtx-5060-ti-16gb" rel="noopener">RTX 5070 hits ~111 t/s in MLPerf Client vs 84 for the 5060 Ti 16GB&lt;/a>, roughly 33% faster, yet its 12GB VRAM ceiling forces offload on larger 14B long-context or 30B MoE setups that the 16GB 5060 Ti holds cleanly.&lt;/p>
&lt;p>One variable these numbers do not hinge on is the runner. When I put &lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-llamacpp-rtx-5080-2026/">Ollama and bare llama.cpp head-to-head on an RTX 5080&lt;/a> loading the identical GGUF files, the decode gap on dense models was 2–6%, so pick your tool for workflow rather than chasing miracle speedups.&lt;/p>
&lt;h2 id="common-pitfalls">Common pitfalls&lt;/h2>
&lt;p>Things that will eat an evening if you&amp;rsquo;re not warned:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Driver version.&lt;/strong> Ollama&amp;rsquo;s GPU page asks for driver 550 or newer, but install the newest driver NVIDIA lists for your card. Older drivers cause silent CPU fallback or mid-generation crashes. Check &lt;code>nvidia-smi&lt;/code> and &lt;code>ollama ps&lt;/code> before blaming the model.&lt;/li>
&lt;li>&lt;strong>Context length.&lt;/strong> Doubling context from 4K to 16K can double VRAM use on attention. If a 7B OOMs after a long conversation, shorten the window (&lt;code>num_ctx&lt;/code> in Ollama, slider in LM Studio).&lt;/li>
&lt;li>&lt;strong>Quantization confusion.&lt;/strong> Q4_K_M is the floor for general use. Q3_K_S sounds dumber on smaller models. Q2 only makes sense on 70B where any answer beats none.&lt;/li>
&lt;li>&lt;strong>Power draw.&lt;/strong> NVIDIA rates the RTX 5060 Ti at 180 W total graphics power and asks for a 600 W system power supply; for the RTX 5060 it is 145 W and 550 W.&lt;/li>
&lt;li>&lt;strong>Thermals.&lt;/strong> Stock cooler runs ~72°C under load in a ventilated case. If yours hits 85°C+, the chassis airflow is the problem. Two front intakes plus one rear exhaust is the floor.&lt;/li>
&lt;/ul>
&lt;h2 id="verdict--when-to-step-up-to-a-5070-or-5080">Verdict — when to step up to a 5070 or 5080&lt;/h2>
&lt;p>If your daily use is chat, code completion, document Q&amp;amp;A, and small-batch embedding, the 5060 Ti 16GB is where I&amp;rsquo;d stop. NVIDIA rates it at 180 W and asks for a 600 W power supply.&lt;/p>
&lt;p>Step up to a &lt;strong>5070 (12GB)&lt;/strong> only if you don&amp;rsquo;t care about 14B+ models and want raw speed on 7B workloads, or you&amp;rsquo;re doing image generation alongside LLMs.&lt;/p>
&lt;p>Step up to a &lt;strong>5080 (16GB)&lt;/strong> or &lt;strong>used 3090 (24GB)&lt;/strong> for batch inference for multiple users (see the &lt;a href="https://techfuelhq.com/pc-builds/1500-dollar-rtx-5060-ti-1440p-build-2026/">$1,500 RTX 5060 Ti 1440p build&lt;/a> as a starting chassis), or home fine-tuning. Llama 3.3 70B is 43 GB in Ollama&amp;rsquo;s library, so on any single one of these cards it means heavy offload to system RAM.&lt;/p>
&lt;p>The biggest mistake I see: people spending $1500 on a 5080 because reviews told them to, then running a 7B that&amp;rsquo;s identical speed on a $300 5060. Match the card to the workload, not the budget.&lt;/p>
&lt;p>Local LLMs used to be a research project. In 2026 they&amp;rsquo;re a weekend install on an entry-level RTX 50-series card. The only question is which model gets your prompts.&lt;/p>
&lt;hr>
&lt;p>&lt;em>Working out of St. Louis County. If you&amp;rsquo;re running a 5060 or 5060 Ti and seeing different tokens/sec on your stack, send your config and run notes to &lt;a href="mailto:contact@techfuelhq.com">contact@techfuelhq.com&lt;/a>.&lt;/em>&lt;/p>
&lt;h2 id="related-guides">Related guides&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/">RTX 5060 Ti vs RX 9060 XT — 1440p Showdown 2026&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://techfuelhq.com/articles/rtx-5060-ti-8gb-vs-16gb-2026/">RTX 5060 Ti 8GB vs 16GB&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://techfuelhq.com/pc-builds/1500-dollar-rtx-5060-ti-1440p-build-2026/">$1,500 RTX 5060 Ti 1440p Build for 2026&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">Best Mini PCs for a 2026 Homelab&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://techfuelhq.com/self-hosted/best-mcp-servers-homelab-2026/">Best MCP Servers for a Homelab: 11 Measured&lt;/a> — once the model runs, this is what wiring it to real tools costs in RAM&lt;/li>
&lt;li>&lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10Gbps Home Networking on a Budget&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://techfuelhq.com/tutorials/">Tutorials Hub&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>Port Forwarding: The Four Things That Must All Be True</title><link>https://techfuelhq.com/networking/port-forwarding-2026/</link><pubDate>Fri, 18 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/port-forwarding-2026/</guid><atom:updated>2026-11-18T04:49:11Z</atom:updated><description>&lt;p>A port forward is one line in a translation table. Traffic arrives at your router on a public port, the router rewrites the destination, and the packet goes to one machine inside your network.&lt;/p>
&lt;p>That is the whole mechanism. The reason this page runs long is that the mechanism is almost never what fails. Four separate conditions have to hold at once, they fail independently, and every one of them fails silently. A port checker reports &amp;ldquo;closed&amp;rdquo; for all four.&lt;/p>
&lt;p>One quick disambiguation before anything else, because two different things share this name. This page is about the rule in your router. If you came looking for &lt;code>ssh -L&lt;/code>, &lt;code>ssh -R&lt;/code> and &lt;code>-D&lt;/code>, that is a different tool with different failure modes, and it lives in &lt;a href="https://techfuelhq.com/networking/ssh-port-forwarding-tunneling-2026/">SSH port forwarding&lt;/a>.&lt;/p>
&lt;h2 id="set-up-and-test-one-forwarding-rule">Set up and test one forwarding rule&lt;/h2>
&lt;p>Start with the service documentation. Record the TCP or UDP protocol, the port the service listens on and the device that runs it. TCP and UDP are separate choices; forwarding one does not create a rule for the other.&lt;/p>
&lt;ol>
&lt;li>Confirm that the router holds a public IPv4 address rather than a CGNAT or private address.&lt;/li>
&lt;li>Reserve one LAN address for the destination device.&lt;/li>
&lt;li>Map the external port and protocol to that address and the service&amp;rsquo;s internal port.&lt;/li>
&lt;li>Allow the same protocol and port through the destination machine&amp;rsquo;s firewall.&lt;/li>
&lt;li>Test from a different network while the service is running, such as a phone with Wi-Fi off.&lt;/li>
&lt;/ol>
&lt;p>A forward makes an inbound service reachable. It does not reduce ping or speed up an existing outbound connection. Ping that jumps only while someone downloads or uploads is a queue at the slowest link, often the modem or router upload, and the fix is smart queue management on the router; the &lt;a href="https://techfuelhq.com/networking/best-wifi-7-router-2026/#lag-under-load">Wi-Fi 7 router guide&lt;/a> shows the wired test. If the service is for your own remote access, compare a &lt;a href="https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/">Tailscale or WireGuard path&lt;/a> before publishing a port to the internet.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Warning:&lt;/strong> a forward publishes that service to anyone who scans your public address, so forward one port to one host and never an admin page. To undo it, delete the rule in the router and remove the matching inbound rule on the host.&lt;/p>&lt;/blockquote>
&lt;h2 id="port-forwarding-not-working-check-these-in-order">Port forwarding not working? Check these in order&lt;/h2>
&lt;p>A port checker reports &amp;ldquo;closed&amp;rdquo; for every one of these failures, so work down the list instead of rewriting the rule:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Is the service running and listening on the port you forwarded, with the right protocol?&lt;/strong> TCP and UDP are separate rules.&lt;/li>
&lt;li>&lt;strong>Does your router hold a real public IPv4?&lt;/strong> A WAN address inside &lt;code>100.64.0.0/10&lt;/code> is carrier-grade NAT, and no forward can work (&lt;a href="#1-your-line-has-a-real-public-ipv4-address">condition 1&lt;/a>).&lt;/li>
&lt;li>&lt;strong>Is a second router translating upstream?&lt;/strong> A private WAN address means double NAT (&lt;a href="#1-your-line-has-a-real-public-ipv4-address">condition 1&lt;/a>), and a forgotten mesh node or travel router in router mode does the same (&lt;a href="#2-exactly-one-device-is-doing-the-translating">condition 2&lt;/a>).&lt;/li>
&lt;li>&lt;strong>Did the target&amp;rsquo;s LAN address change?&lt;/strong> Reserve it in DHCP (&lt;a href="#3-the-rule-points-at-an-address-that-does-not-move">condition 3&lt;/a>).&lt;/li>
&lt;li>&lt;strong>Is the host firewall dropping it?&lt;/strong> Windows blocks inbound traffic that matches no inbound rule by default (&lt;a href="#4-the-destination-machines-own-firewall-allows-it">condition 4&lt;/a>).&lt;/li>
&lt;li>&lt;strong>Are you testing from inside your own network?&lt;/strong> Test from a phone on cellular with Wi-Fi off.&lt;/li>
&lt;/ul>
&lt;h2 id="what-the-router-is-doing">What the router is doing&lt;/h2>
&lt;p>Your home network runs on private addresses. Mine sits on &lt;code>192.168.1.0/24&lt;/code>, and addresses in that range are not routable on the internet by design. When my desktop opens a connection outward, the router replaces the private source address with the one public address it owns and remembers the swap, so the reply finds its way back.&lt;/p>
&lt;p>That works because your machine started the conversation. The router has a table entry waiting for the reply.&lt;/p>
&lt;p>An unsolicited packet from outside has no such entry. The router receives it, finds nothing that explains where it should go, and drops it — no security feature was switched on to make that happen. The address translation simply has no answer to the question.&lt;/p>
&lt;p>A port forward supplies the missing answer in advance. You tell the router that anything arriving on TCP 32400 belongs to &lt;code>192.168.1.40&lt;/code>, permanently, whether or not that machine asked for it.&lt;/p>
&lt;p>So the rule you write has four parts: the external port, the internal address, the internal port, and the protocol. Get any of them wrong and nothing tells you.&lt;/p>
&lt;h2 id="the-four-conditions">The four conditions&lt;/h2>
&lt;p>Every one of these has to be true. Check them in this order, because each one makes the next one worth testing.&lt;/p>
&lt;h3 id="1-your-line-has-a-real-public-ipv4-address">1. Your line has a real public IPv4 address&lt;/h3>
&lt;p>This is the condition that ends the conversation for a growing number of people, and it is the first thing to check because you cannot fix it yourself.&lt;/p>
&lt;p>Read the WAN address on your router&amp;rsquo;s status page. Then compare it with what a what-is-my-IP site reports.&lt;/p>
&lt;p>If the two match, you have a real public address and this condition passes. If they differ, something upstream is translating your traffic, and the WAN address tells you which problem you have.&lt;/p>
&lt;p>An address inside &lt;code>100.64.0.0/10&lt;/code> means carrier-grade NAT. &lt;a href="https://www.rfc-editor.org/rfc/rfc6598.html" rel="noopener">RFC 6598&lt;/a> reserves that range as Shared Address Space, assigned for service provider use to number the link between a CGN device and customer equipment. You share one public address with other subscribers. There is no port on it that belongs to you, so there is nothing to forward, and no setting in your router changes that.&lt;/p>
&lt;p>Whether your provider will move you off it varies. On Spectrum&amp;rsquo;s own community forum, a verified employee answering one customer who asked to opt out of CG-NAT said there is no way to opt out, naming a static IP on a business account or a VPN as the two alternatives. That is one provider&amp;rsquo;s answer to one customer, so ask yours before planning around it. Hold on to the second half of that answer, because a tunnel out to somewhere with a public address is where this page ends up too.&lt;/p>
&lt;p>An address in &lt;code>192.168.x.x&lt;/code>, &lt;code>10.x.x.x&lt;/code> or &lt;code>172.16.x.x&lt;/code> through &lt;code>172.31.x.x&lt;/code>, the three private ranges &lt;a href="https://www.rfc-editor.org/rfc/rfc1918.html" rel="noopener">RFC 1918&lt;/a> sets aside, means double NAT instead: a second router upstream of yours, usually the ISP&amp;rsquo;s own gateway running in router mode with your equipment behind it. That one you can fix. Either put the ISP gateway into bridge or passthrough mode so your router holds the public address, or write the same forward twice, once on each device. Bridging is the better repair, because the second rule is a thing you will forget in a year. If you want to check whether a given address falls inside a private range, the &lt;a href="https://techfuelhq.com/tools/subnet-cidr-calculator/">subnet and CIDR calculator&lt;/a> will tell you.&lt;/p>
&lt;p>If your ISP changes your public address from time to time, the forward survives the change but anyone connecting by the old number does not. A &lt;a href="https://techfuelhq.com/networking/dynamic-dns-homelab-guide-2026/">dynamic DNS name&lt;/a> follows the address for you, and that guide also covers the CGNAT check above.&lt;/p>
&lt;h3 id="2-exactly-one-device-is-doing-the-translating">2. Exactly one device is doing the translating&lt;/h3>
&lt;p>Condition 1 finds the common version of this. The uncommon version is a router you forgot about: a mesh node in router mode rather than access-point mode, or a travel router still plugged in behind the main one.&lt;/p>
&lt;p>The symptom is a forward that is configured correctly on the device you are looking at and lands on a device that is not the one holding the public address. Count the boxes between your machine and the wall.&lt;/p>
&lt;h3 id="3-the-rule-points-at-an-address-that-does-not-move">3. The rule points at an address that does not move&lt;/h3>
&lt;p>Your router hands out LAN addresses by DHCP, and a lease expires. If the machine you forwarded to comes back on a different address after a reboot, your rule now points at whatever took its old one.&lt;/p>
&lt;p>Fix it in the router rather than on the host. Assign a DHCP reservation that ties the machine&amp;rsquo;s MAC address to one LAN address permanently. A static address configured on the host itself works too, as long as it sits outside the DHCP pool, which is a detail people skip and then spend an evening on an address conflict.&lt;/p>
&lt;h3 id="4-the-destination-machines-own-firewall-allows-it">4. The destination machine&amp;rsquo;s own firewall allows it&lt;/h3>
&lt;p>This is the one that catches experienced people, because the router configuration is visibly correct and the port still reads closed.&lt;/p>
&lt;p>The router forwards the packet. The host receives it and drops it.&lt;/p>
&lt;p>Microsoft documents the &lt;code>-DefaultInboundAction&lt;/code> values for &lt;code>Set-NetFirewallProfile&lt;/code> plainly: Block &amp;ldquo;blocks inbound network traffic that does not match an inbound rule&amp;rdquo;, and &amp;ldquo;the default setting when managing a computer is Block&amp;rdquo;. On my own Windows 11 desktop, reading the effective policy rather than the configured one, all three profiles agree:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>Get-NetFirewallProfile -PolicyStore ActiveStore |
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> Select-Object Name, Enabled, DefaultInboundAction
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;pre tabindex="0">&lt;code>Domain True Block
Private True Block
Public True Block
&lt;/code>&lt;/pre>&lt;p>Measured 2026-09-18 on Windows 11 Home build 26200. The &lt;code>ActiveStore&lt;/code> part matters. Querying the default store on the same machine returns &lt;code>NotConfigured&lt;/code> for all three, which reads like permissiveness and is not. The effective policy is Block.&lt;/p>
&lt;p>So a forward into a Windows host needs an inbound rule on that host as well. Most server software adds one at install time. Anything you unzipped and ran by hand did not.&lt;/p>
&lt;p>If the host sits on its own VLAN, check the router&amp;rsquo;s rules for that VLAN as well; the &lt;a href="https://techfuelhq.com/tutorials/vlans-homelab-2026/">homelab VLAN guide&lt;/a> shows how those rules are usually laid out.&lt;/p>
&lt;h2 id="the-automatic-version-and-why-it-keeps-not-working">The automatic version, and why it keeps not working&lt;/h2>
&lt;p>Routers can open these rules on request, without you touching the admin page. Three protocols do it: UPnP IGD, NAT-PMP, and PCP, the last of which &lt;a href="https://www.rfc-editor.org/rfc/rfc6887.html" rel="noopener">RFC 6887&lt;/a> defines as a way for a host to control how incoming packets are translated and forwarded by a NAT or a simple firewall.&lt;/p>
&lt;p>When it works it is genuinely better than a hand-written rule, because the application asks for exactly the port it needs and gives it back afterwards.&lt;/p>
&lt;p>It frequently does not work. Tailscale&amp;rsquo;s David Anderson, writing about NAT traversal in 2020, put the problem in one line: these protocols &amp;ldquo;might not be implemented on your devices. They might be disabled by default and nobody knew to turn them on.&amp;rdquo; He adds a detail worth knowing before you go looking for three separate settings, which is that &amp;ldquo;many devices come with a single &amp;lsquo;UPnP&amp;rsquo; checkbox that actually toggles UPnP, NAT-PMP and PCP all at once.&amp;rdquo;&lt;/p>
&lt;p>That single checkbox is also why the advice to disable UPnP for security is coarser than it sounds. Turning it off removes all three, including the two that never carried UPnP&amp;rsquo;s vulnerabilities.&lt;/p>
&lt;p>My position: leave it off, and write the rule by hand. A permanent rule you wrote is one you can find again. A rule some application opened for itself is one nobody will ever audit, and the reason UPnP has the reputation it has is that malware on a LAN machine can ask for a forward exactly as politely as your game does.&lt;/p>
&lt;h2 id="ipv6-does-not-have-port-forwarding-at-all">IPv6 does not have port forwarding at all&lt;/h2>
&lt;p>On IPv6 there is no address translation, so there is nothing to translate. Every device on your network already holds a globally routable address. What stands between the internet and that device is your router&amp;rsquo;s firewall policy, and nothing else.&lt;/p>
&lt;p>So the IPv6 equivalent of a port forward is a firewall rule, usually labelled a pinhole. You specify one address and one port, and you allow inbound traffic to it.&lt;/p>
&lt;p>The default behaviour is genuinely vendor-dependent. &lt;a href="https://www.rfc-editor.org/rfc/rfc6092.html" rel="noopener">RFC 6092&lt;/a>, the recommendations document for residential IPv6 gateways, requires in REC-49 that a gateway &amp;ldquo;MUST provide an easily selected configuration option that permits a &amp;rsquo;transparent mode&amp;rsquo; of operation that forwards all unsolicited flows regardless of forwarding direction&amp;rdquo;, and then adds that &amp;ldquo;the transparent mode of operation MAY be the default configuration&amp;rdquo;. A conforming router can ship wide open or closed. Check yours rather than assuming.&lt;/p>
&lt;h3 id="which-address-to-open-and-the-one-your-port-checker-will-hand-you">Which address to open, and the one your port checker will hand you&lt;/h3>
&lt;p>Here is the part that costs people an evening, and it is measurable rather than theoretical.&lt;/p>
&lt;p>A Windows machine does not hold one IPv6 address. It holds several at once, for different jobs. On my wired desktop, on a Charter line, I read the interface on 2026-09-18:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>Get-NetIPAddress -InterfaceAlias &lt;span style="color:#e6db74">&amp;#39;Ethernet 2&amp;#39;&lt;/span> -AddressFamily IPv6 |
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> Select-Object IPAddress, PrefixOrigin, SuffixOrigin, AddressState, PreferredLifetime
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>That returned eight addresses. Four were link-local and unique-local, which never reach the internet and are not what a pinhole targets. The other four were globally routable under the ISP&amp;rsquo;s delegated prefix, and those are the rows below. They appear as truncated SHA-256 hashes, because the addresses themselves identify the line:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">address (sha256, first 12)&lt;/th>
&lt;th scope="col">PrefixOrigin&lt;/th>
&lt;th scope="col">SuffixOrigin&lt;/th>
&lt;th scope="col">state&lt;/th>
&lt;th scope="col">preferred lifetime left&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="address (sha256, first 12)">&lt;code>8c54b72251e1&lt;/code>&lt;/td>
&lt;td data-label="PrefixOrigin">RouterAdvertisement&lt;/td>
&lt;td data-label="SuffixOrigin">Random&lt;/td>
&lt;td data-label="state">Preferred&lt;/td>
&lt;td data-label="preferred lifetime left">22:02:03&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="address (sha256, first 12)">&lt;code>3bcb63976cb9&lt;/code>&lt;/td>
&lt;td data-label="PrefixOrigin">RouterAdvertisement&lt;/td>
&lt;td data-label="SuffixOrigin">Random&lt;/td>
&lt;td data-label="state">Deprecated&lt;/td>
&lt;td data-label="preferred lifetime left">00:00:00&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="address (sha256, first 12)">&lt;code>51d7bac62b7c&lt;/code>&lt;/td>
&lt;td data-label="PrefixOrigin">RouterAdvertisement&lt;/td>
&lt;td data-label="SuffixOrigin">Link&lt;/td>
&lt;td data-label="state">Preferred&lt;/td>
&lt;td data-label="preferred lifetime left">23:59:05&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="address (sha256, first 12)">&lt;code>3e69fab27a83&lt;/code>&lt;/td>
&lt;td data-label="PrefixOrigin">Dhcp&lt;/td>
&lt;td data-label="SuffixOrigin">Dhcp&lt;/td>
&lt;td data-label="state">Preferred&lt;/td>
&lt;td data-label="preferred lifetime left">22:58:50&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>On this machine the two marked &lt;code>Random&lt;/code> are the two that &lt;code>ipconfig /all&lt;/code> labels &lt;strong>Temporary IPv6 Address&lt;/strong>, and I am reading the mapping off that correlation rather than off the property name. &lt;code>Random&lt;/code> does not by itself mean temporary: a stable SLAAC address also reports a randomized suffix on a host configured for it. The &lt;code>Link&lt;/code> row above is what tells me this box is not doing that. Check the &lt;code>ipconfig&lt;/code> labels on your own machine instead of trusting the mapping.&lt;/p>
&lt;p>Temporary addresses exist so that the address a remote server sees cannot be used to follow your machine around. &lt;a href="https://www.rfc-editor.org/rfc/rfc8981.html" rel="noopener">RFC 8981&lt;/a> describes them as &amp;ldquo;typically employed for initiating outgoing sessions&amp;rdquo; and used &amp;ldquo;for a short period of time (typically hours to days)&amp;rdquo; before being deprecated, with a default preferred lifetime of one day. My desktop&amp;rsquo;s own setting agrees: &lt;code>netsh interface ipv6 show privacy&lt;/code> reports a maximum preferred lifetime of 1d.&lt;/p>
&lt;p>Now the two measurements that make this concrete.&lt;/p>
&lt;p>&lt;strong>Windows sends outbound traffic from the temporary address.&lt;/strong> Asking the routing stack which source it would pick for a remote IPv6 host, without sending anything:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>Find-NetRoute -RemoteIPAddress &lt;span style="color:#ae81ff">2001&lt;/span>&lt;span style="color:#960050;background-color:#1e0010">:&lt;/span>&lt;span style="color:#ae81ff">4860&lt;/span>&lt;span style="color:#960050;background-color:#1e0010">:&lt;/span>&lt;span style="color:#ae81ff">4860&lt;/span>::&lt;span style="color:#ae81ff">8888&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>It returned &lt;code>8c54b72251e1&lt;/code>, the Preferred &lt;code>Random&lt;/code> one. That is the documented default, not a quirk: &lt;a href="https://www.rfc-editor.org/rfc/rfc6724.html" rel="noopener">RFC 6724&lt;/a> Rule 7 says &amp;ldquo;if SA is a temporary address and SB is a public address, then prefer SA.&amp;rdquo;&lt;/p>
&lt;p>&lt;strong>The temporary addresses really do go away, and the stable ones really do not.&lt;/strong> I read the same interface four days earlier, on 2026-09-14. The temporary address that was Preferred then, and that Windows was using as its source, is now not on the interface at all. Meanwhile &lt;code>51d7bac62b7c&lt;/code> and &lt;code>3e69fab27a83&lt;/code>, the stable SLAAC address and the DHCPv6 address, are the same two addresses they were four days ago, across a reboot in between.&lt;/p>
&lt;p>That is the rule, measured on one line rather than quoted from a standard: &lt;strong>the addresses ipconfig labels Temporary are the ones that disappear, and the plain &lt;code>IPv6 Address&lt;/code> and DHCPv6 lines are the ones a firewall rule should name.&lt;/strong>&lt;/p>
&lt;p>Which brings me to the part that makes this a trap rather than a curiosity. The obvious way to find out your own IPv6 address is to ask a website, and port-checking tools offer exactly that: yougetsignal&amp;rsquo;s open-ports page has a &amp;ldquo;Use Current IP&amp;rdquo; control, and it was in Bing&amp;rsquo;s top ten for &amp;ldquo;port forwarding&amp;rdquo; when I searched on 2026-09-18. Loaded from this desktop, that control pre-filled an IPv6 address. On 2026-09-14 it offered the temporary address current that day. On 2026-09-18 it offered &lt;code>8c54b72251e1&lt;/code>: the new temporary address, the same one &lt;code>Find-NetRoute&lt;/code> had just picked and the same Preferred &lt;code>Random&lt;/code> row from the table above.&lt;/p>
&lt;p>On both days I checked, it offered the temporary address and neither of the two stable ones. That is not a flaw in one tool. Any site that reports &amp;ldquo;your IP&amp;rdquo; can only report the address your connection arrived from, and Rule 7 above is what makes that the temporary one. So the entire category of what-is-my-IP controls will hand you the wrong address for this particular job, and the better the tool is at its actual job the more reliably it does so. Ask your own machine instead.&lt;/p>
&lt;p>Copy that into a router firewall rule and the rule works. It works for hours — long enough to close the admin page and call the job done. Then the address behind it is retired, the rule points at nothing, and the thing you are running stops answering with no configuration having changed.&lt;/p>
&lt;h2 id="when-to-stop-forwarding-entirely">When to stop forwarding entirely&lt;/h2>
&lt;p>There is a decent case that most people reading this should not write the rule at all.&lt;/p>
&lt;p>A forward is still the right tool in a few places. A self-hosted &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">WireGuard endpoint&lt;/a> needs exactly one forwarded UDP port and gives you an encrypted path to everything behind it, which is one rule instead of one per service. A game server for friends is a reasonable use. So is anything already designed to face the internet.&lt;/p>
&lt;p>Everywhere else, an overlay network has quietly become the better answer, because it satisfies condition 1 by refusing to depend on it. Both ends dial outward, so CGNAT stops being a problem instead of being an obstacle, and nothing on your router is open. That is the decision covered in &lt;a href="https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/">Tailscale vs WireGuard&lt;/a>, the &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale homelab guide&lt;/a> walks the setup, and &lt;a href="https://techfuelhq.com/networking/tailscale-vs-cloudflare-tunnel-2026/">neither Tailscale nor a Cloudflare Tunnel needs an inbound port&lt;/a>. The cost is client software on whatever is connecting, which is the one thing a forwarded port never demands, and it is why the answer is not unanimous.&lt;/p>
&lt;p>If your ISP gateway turns out to have no usable forwarding table or no IPv6 firewall controls at all, which is common on carrier-supplied hardware, the fix is your own router behind it in bridge mode. The &lt;a href="https://techfuelhq.com/networking/best-wifi-7-router-2026/">Wi-Fi 7 router picks&lt;/a> cover that purchase with current pricing.&lt;/p>
&lt;p>And if what you wanted was to reach one media server from outside, the service-specific version of this decision is worked through end to end in &lt;a href="https://techfuelhq.com/tutorials/jellyfin-remote-access-2026/">Jellyfin remote access&lt;/a>, including why forwarding its plain HTTP port is the one setup nobody should copy.&lt;/p>
&lt;h2 id="remote-desktop-use-a-private-path-first">Remote Desktop: use a private path first&lt;/h2>
&lt;p>For Remote Desktop, the safer default is no public router rule. Microsoft says a Windows 11 Pro, Enterprise or Education PC can accept incoming RDP while Windows Home cannot act as the host. On the host, turn on &lt;strong>Settings → System → Remote Desktop&lt;/strong>, allow only the accounts that need access, keep Network Level Authentication enabled, and confirm the Windows firewall rule.&lt;/p>
&lt;p>Then connect both devices through a VPN or private overlay. Tailscale&amp;rsquo;s &lt;a href="https://tailscale.com/docs/solutions/access-remote-desktops-using-windows-rdp" rel="noopener">Windows RDP guide&lt;/a> has you install Tailscale at both ends and connect to the destination&amp;rsquo;s private Tailscale name or address. That path works without publishing the RDP service through the router. Microsoft also names a VPN as an outside-network option in its &lt;a href="https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/remote-desktop-allow-access" rel="noopener">Remote Desktop setup guide&lt;/a>.&lt;/p>
&lt;p>If an organization deliberately exposes RDP through a gateway, that is a managed security design rather than the simple home-router recipe on this page. Do not copy a generic TCP 3389 forward and call the access path finished.&lt;/p>
&lt;h2 id="what-a-port-forwarding-app-can-mean">What a port-forwarding app can mean&lt;/h2>
&lt;p>The phrase &amp;ldquo;port-forwarding app&amp;rdquo; hides three different layers. A program can ask the router for a temporary mapping through UPnP or NAT-PMP, relay TCP on the host, or build a tunnel to another network. None of those proves that your router has a permanent inbound rule. Identify which layer the software controls before following its instructions.&lt;/p>
&lt;p>Windows &lt;code>netsh interface portproxy&lt;/code> is the host-relay case. Microsoft&amp;rsquo;s command reference says &lt;code>v4tov4&lt;/code> listens on one local IPv4 address and TCP port and connects onward to another address and port. It handles TCP only. You still need the Windows firewall rule, and reaching it from the internet still requires a public path and a router forward to the Windows host.&lt;/p>
&lt;p>Transmission is the automatic-router case. Its current configuration reference names &lt;code>peer_port&lt;/code> as 51413 by default and &lt;code>port_forwarding_enabled&lt;/code> as the UPnP or NAT-PMP switch. The same document says Transmission 4 still defaults to deprecated kebab-case keys unless its version 5 save format is enabled. Transmission&amp;rsquo;s guide treats the Windows firewall and router mapping as separate steps. If automatic mapping is unavailable, forward the configured peer port to the computer running Transmission and match its protocol instructions.&lt;/p>
&lt;p>A COM port is a fourth, unrelated meaning. In Windows, &lt;code>COM1&lt;/code> names a serial communications resource. Changing or remapping that COM number helps a local serial application find a device; it does not publish a TCP or UDP service through NAT. A serial-to-network gateway would introduce a network port, but that is a different product and configuration.&lt;/p>
&lt;h2 id="what-i-measured-and-what-i-did-not">What I measured and what I did not&lt;/h2>
&lt;p>The Windows figures here are first-hand, from read-only commands on my own wired desktop: Windows 11 Home build 26200, Charter line, captured 2026-09-14 and again 2026-09-18. The IPv6 addresses appear only as truncated hashes because the addresses identify the connection. The prefix owner comes from ARIN&amp;rsquo;s registry, which returns Charter Communications LLC for that block.&lt;/p>
&lt;p>Three things are outside what I tested, and they change what you should trust.&lt;/p>
&lt;p>I did not read the router. That means I cannot tell you whether this line is behind CGNAT, and I cannot tell you what this router does with unsolicited inbound IPv6. Both are things the sections above tell you to check on your own router.&lt;/p>
&lt;p>I did not press the port checker&amp;rsquo;s test button. Watching which address it pre-fills is reading the page; running its scan submits a probe against the operator&amp;rsquo;s own address to a third party. So the address it offers is measured, and whether its test runs over IPv6 is not something I checked.&lt;/p>
&lt;p>The disappearance of that temporary address has two possible causes I cannot separate, since the four-day window contained both a reboot and several preferred lifetimes. Either retires a temporary address and neither touches the stable pair, so the advice is the same, but I am not going to claim a mechanism I did not isolate.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://www.rfc-editor.org/rfc/rfc1918.html" rel="noopener">RFC 1918&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.rfc-editor.org/rfc/rfc6598.html" rel="noopener">RFC 6598&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.rfc-editor.org/rfc/rfc6092.html" rel="noopener">RFC 6092&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.rfc-editor.org/rfc/rfc6724.html" rel="noopener">RFC 6724&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.rfc-editor.org/rfc/rfc6887.html" rel="noopener">RFC 6887&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.rfc-editor.org/rfc/rfc8981.html" rel="noopener">RFC 8981&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/powershell/module/netsecurity/set-netfirewallprofile" rel="noopener">Microsoft Set-NetFirewallProfile reference&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows/win32/fwp/wmi/nettcpipprov/msft-netipaddress" rel="noopener">Microsoft MSFT_NetIPAddress reference&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/powershell/module/nettcpip/find-netroute" rel="noopener">Microsoft Find-NetRoute reference&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows-server/networking/technologies/netsh/netsh-interface-portproxy" rel="noopener">Microsoft netsh interface portproxy reference&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows/win32/devio/communications-resource-handles" rel="noopener">Microsoft communications resource handles&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://github.com/transmission/transmission/blob/main/docs/Editing-Configuration-Files.md?plain=1" rel="noopener">Transmission configuration reference&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://github.com/transmission/transmission/blob/main/docs/Port-Forwarding-Guide.md?plain=1" rel="noopener">Transmission port-forwarding guide&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://tailscale.com/blog/how-nat-traversal-works" rel="noopener">Tailscale: how NAT traversal works&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/remote-desktop-allow-access" rel="noopener">Microsoft: enable Remote Desktop on your PC&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://tailscale.com/docs/solutions/access-remote-desktops-using-windows-rdp" rel="noopener">Tailscale: access remote desktops using Windows RDP&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://community.spectrum.net/discussion/172901/opt-out-of-carrier-grade-nat-cg-nat" rel="noopener">Spectrum community: CGNAT opt-out discussion&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>ROG Astral RTX 5080 OC Review: First-Party 4K Benchmarks</title><link>https://techfuelhq.com/gpu-reviews/rog-astral-rtx-5080-oc-review-2026/</link><pubDate>Fri, 12 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gpu-reviews/rog-astral-rtx-5080-oc-review-2026/</guid><atom:updated>2026-11-18T04:48:40Z</atom:updated><description>&lt;p>&lt;strong>Rating: 4.4 / 5&lt;/strong>&lt;/p>
&lt;p>At stock my ASUS ROG Astral RTX 5080 OC games at 266 to 340 W and 63 to 72 °C with the fans near-silent. On my hand-tuned profile it ran Cyberpunk 2077 at 4K without ray tracing at 58 FPS (49 at the 1% low), Alan Wake 2 with RT Ultra and DLSS Quality at 49, and path-traced Cyberpunk at 135 FPS with DLSS Quality and MFG 4x. ASUS lists it at 357.6 mm long and 3.8 slots thick, and HWCooling read its performance BIOS limit at 400 W. Newegg&amp;rsquo;s catalogue did not list the Astral in stock on November 17, 2026, and the cheapest new RTX 5080 it did list, ZOTAC&amp;rsquo;s Solid Core OC at $2,199.99, cost more than twice the RTX 5080&amp;rsquo;s $1,000 launch MSRP (GamersNexus). Buy it for a 4K high-refresh screen. At 1440p it is the wrong card.&lt;/p>
&lt;p>It is the card in my own rig, hung vertically on the riser of a HYTE Y60 next to a Ryzen 7 7800X3D, a ROG STRIX B650-A, 64 GB of DDR5-6000 and an NZXT Kraken 360, driving a Gigabyte AORUS FO48U 48-inch 4K OLED. I benchmarked it June 8 to 11, 2026. It links at PCIe 4.0 x16 in this system. All data in this review is first-party, measured on my own bench. The dataset behind my measurements is open under CC BY 4.0 at &lt;a href="https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/">/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/&lt;/a>.&lt;/p>
&lt;p>All numbers on this page are first-party. The Astral 5080 OC was measured on my current bench; the competitor points (RTX 4080, RTX 4080 Super, RTX 5080 FE) were measured on my retired 2024–2025 bench and normalized to my own baselines, as documented in the dataset.&lt;/p>
&lt;h2 id="the-astral-5080-oc-in-one-table">The Astral 5080 OC in one table&lt;/h2>
&lt;p>My rows are my own card; TechPowerUp&amp;rsquo;s game results are its launch sample, tested at stock in its own scenes (&lt;a href="https://www.techpowerup.com/review/asus-geforce-rtx-5080-astral-oc/" rel="noopener">TechPowerUp&lt;/a>, January 30, 2025), for what I have not run.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Question&lt;/th>
&lt;th scope="col">Answer&lt;/th>
&lt;th scope="col">Source&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Question">Cyberpunk 2077, 4K, no ray tracing&lt;/td>
&lt;td data-label="Answer">58 FPS average, 49 at the 1% low, on my manual profile. TechPowerUp at stock: 76.2&lt;/td>
&lt;td data-label="Source">my bench, June 2026; TechPowerUp, January 30, 2025&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Cyberpunk 2077, 4K path tracing&lt;/td>
&lt;td data-label="Answer">19 FPS native; 135 with DLSS Quality and MFG 4x at 62 ms PC latency, manual profile&lt;/td>
&lt;td data-label="Source">my bench, June 2026&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Alan Wake 2, 4K&lt;/td>
&lt;td data-label="Answer">49 FPS with RT Ultra and DLSS Quality on my manual profile. TechPowerUp at stock, no ray tracing: 65.2&lt;/td>
&lt;td data-label="Source">my bench, June 2026; TechPowerUp, January 30, 2025&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Starfield, 4K&lt;/td>
&lt;td data-label="Answer">80.6 FPS at stock&lt;/td>
&lt;td data-label="Source">TechPowerUp, January 30, 2025; not run on my card&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Horizon Forbidden West, 4K&lt;/td>
&lt;td data-label="Answer">90.2 FPS at stock&lt;/td>
&lt;td data-label="Source">TechPowerUp, January 30, 2025; not run on my card&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Silent Hill 2, 4K&lt;/td>
&lt;td data-label="Answer">49.8 FPS at stock&lt;/td>
&lt;td data-label="Source">TechPowerUp, January 30, 2025; not run on my card&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Gaming temperature&lt;/td>
&lt;td data-label="Answer">63 to 72 °C core and 72 to 82 °C memory at stock&lt;/td>
&lt;td data-label="Source">my bench, June 2026&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Noise&lt;/td>
&lt;td data-label="Answer">near-silent at stock; up to about 51 dBA on my manual profile. TechPowerUp&amp;rsquo;s meter at 50 cm: 36.3 dBA on the performance BIOS, 25.8 dBA on the quiet BIOS&lt;/td>
&lt;td data-label="Source">my bench, June 2026; TechPowerUp, January 30, 2025&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Gaming board power&lt;/td>
&lt;td data-label="Answer">266 to 340 W at stock (HWiNFO64). TechPowerUp measured 388 W in gaming&lt;/td>
&lt;td data-label="Source">my bench, June 2026; TechPowerUp, January 30, 2025&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Idle board power&lt;/td>
&lt;td data-label="Answer">13 to 20 W at stock; 52 to 71 W at the Windows desktop across a week of August captures&lt;/td>
&lt;td data-label="Source">my bench, June 2026; &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-power-efficiency/">LLM power-efficiency dataset&lt;/a>, August 2026&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Power limit&lt;/td>
&lt;td data-label="Answer">ships at 400 W; my manual profile&amp;rsquo;s +12% target is 448 W; the March 14, 2025 BIOS allows 450 W&lt;/td>
&lt;td data-label="Source">Club386; my dataset&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Size&lt;/td>
&lt;td data-label="Answer">357.6 x 149.3 x 76 mm, 3.8 slots&lt;/td>
&lt;td data-label="Source">ASUS spec page&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">PSU&lt;/td>
&lt;td data-label="Answer">850W recommended; one 16-pin connector, 1-to-3 adapter in the box&lt;/td>
&lt;td data-label="Source">ASUS spec page&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Price&lt;/td>
&lt;td data-label="Answer">Not in stock in Newegg&amp;rsquo;s catalogue on November 17, 2026; the cheapest new RTX 5080 there was $2,199.99 (ZOTAC Solid Core OC)&lt;/td>
&lt;td data-label="Source">Newegg; &lt;a href="https://techfuelhq.com/data/deal-or-mirage/#sku-geforce-rtx-5080-16gb">RTX 5080 row in Deal or Mirage&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Question">Coil whine&lt;/td>
&lt;td data-label="Answer">mild: only in uncapped game menus, gone with any frame cap&lt;/td>
&lt;td data-label="Source">my card in the coil whine database&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="what-asus-ships">What ASUS ships&lt;/h2>
&lt;p>From &lt;a href="https://rog.asus.com/us/graphics-cards/graphics-cards/rog-astral/rog-astral-rtx5080-o16g-gaming/spec/" rel="noopener">ASUS&amp;rsquo;s spec page&lt;/a> (read 2026-09-26) unless a line says otherwise:&lt;/p>
&lt;ul>
&lt;li>GPU: GeForce RTX 5080, 10,752 CUDA cores, 16 GB GDDR7 on a 256-bit bus at 30 Gbps (30 Gbps x 256 bits / 8 = 960 GB/s)&lt;/li>
&lt;li>Boost clock: 2,760 MHz in default mode, 2,790 MHz in OC mode. NVIDIA&amp;rsquo;s reference boost is 2.62 GHz (&lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5080/" rel="noopener">NVIDIA spec page&lt;/a>)&lt;/li>
&lt;li>Power: NVIDIA rates the RTX 5080 at 360 W Total Graphics Power. The Astral ships at 400 W, and ASUS&amp;rsquo;s March 14, 2025 BIOS raised its ceiling to 450 W (&lt;a href="https://www.club386.com/asus-boosts-rog-astral-geforce-rtx-5080-power-limits-to-450w-via-bios-update/" rel="noopener">Club386&lt;/a>)&lt;/li>
&lt;li>Connector: one 16-pin, with a 1-to-3 adapter cable in the box&lt;/li>
&lt;li>Recommended PSU: 850W, which ASUS bases on a fully overclocked GPU and CPU&lt;/li>
&lt;li>Size: 357.6 x 149.3 x 76 mm, 3.8 slots&lt;/li>
&lt;li>Outputs: three DisplayPort 2.1b and two HDMI 2.1b&lt;/li>
&lt;li>In the box: a ROG graphics card holder, a magnet, a PCB ruler and a keycap&lt;/li>
&lt;/ul>
&lt;figure>
&lt;picture>
&lt;source type="image/webp" srcset="https://techfuelhq.com/images/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-front-on-fans-800.webp 800w, https://techfuelhq.com/images/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-front-on-fans-1600.webp 1600w" sizes="(max-width: 1080px) 100vw, 860px">
&lt;img src="https://techfuelhq.com/images/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-front-on-fans-1600.jpg" width="1600" height="900" alt="Straight-on view of the ROG Astral RTX 5080's three Axial-tech fans and the rotation dial at the end of the card" loading="lazy" decoding="async">
&lt;/picture>
&lt;figcaption>The three front fans of the quad-fan Axial-tech cooler straight-on, with the rotation dial at the card's end.&lt;/figcaption>
&lt;/figure>
&lt;h2 id="bench-results-3dmark-synthetic">Bench results: 3DMark synthetic&lt;/h2>
&lt;p>All numbers below are TechFuelHQ first-party. Three profiles on the same card, all scores dated 2026-06-11 in the dataset CSV. &lt;strong>Stock&lt;/strong> is out-of-box defaults, &lt;strong>Factory OC&lt;/strong> is the ASUS-shipped OC profile, and &lt;strong>Manual OC&lt;/strong> is my hand-tuned GPU Tweak III profile: +328 MHz core, +2,996 MHz memory, +12% power target.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Test&lt;/th>
&lt;th scope="col" style="text-align: right">Stock&lt;/th>
&lt;th scope="col" style="text-align: right">Factory OC&lt;/th>
&lt;th scope="col" style="text-align: right">Manual OC&lt;/th>
&lt;th scope="col" style="text-align: right">Manual vs stock&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Test">Time Spy (DX12, 1440p)&lt;/td>
&lt;td style="text-align: right" data-label="Stock">32,350&lt;/td>
&lt;td style="text-align: right" data-label="Factory OC">33,200&lt;/td>
&lt;td style="text-align: right" data-label="Manual OC">34,500&lt;/td>
&lt;td style="text-align: right" data-label="Manual vs stock">+6.6%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">Time Spy Extreme (DX12, 4K)&lt;/td>
&lt;td style="text-align: right" data-label="Stock">16,244&lt;/td>
&lt;td style="text-align: right" data-label="Factory OC">16,961&lt;/td>
&lt;td style="text-align: right" data-label="Manual OC">17,600&lt;/td>
&lt;td style="text-align: right" data-label="Manual vs stock">+8.3%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">Port Royal (ray tracing)&lt;/td>
&lt;td style="text-align: right" data-label="Stock">20,300&lt;/td>
&lt;td style="text-align: right" data-label="Factory OC">21,673&lt;/td>
&lt;td style="text-align: right" data-label="Manual OC">22,500&lt;/td>
&lt;td style="text-align: right" data-label="Manual vs stock">+10.8%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">Speed Way (DX12 Ultimate)&lt;/td>
&lt;td style="text-align: right" data-label="Stock">9,010&lt;/td>
&lt;td style="text-align: right" data-label="Factory OC">9,100&lt;/td>
&lt;td style="text-align: right" data-label="Manual OC">9,900&lt;/td>
&lt;td style="text-align: right" data-label="Manual vs stock">+9.9%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Test">Steel Nomad (4K, non-RT)&lt;/td>
&lt;td style="text-align: right" data-label="Stock">8,150&lt;/td>
&lt;td style="text-align: right" data-label="Factory OC">8,400&lt;/td>
&lt;td style="text-align: right" data-label="Manual OC">9,200&lt;/td>
&lt;td style="text-align: right" data-label="Manual vs stock">+12.9%&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;figure>
&lt;img src="https://techfuelhq.com/images/gpu-reviews/rog-astral-rtx-5080/chart-02-3dmark-time-spy.svg" alt="3DMark Time Spy Graphics bar chart: Stock 32,350, Factory OC 33,200, Manual OC 34,500 (TechFuelHQ first-party)" width="1200" height="500" loading="lazy" decoding="async" style="display:block;margin:1.5rem auto;max-width:100%;height:auto;border:1px solid #1e1e3a;border-radius:8px;" />
&lt;figcaption>3DMark Time Spy Graphics across the three tune profiles, measured on my card.&lt;/figcaption>
&lt;/figure>
&lt;p>The factory profile adds 1.0 to 6.8 percent over stock depending on the test, and my manual profile adds 6.6 to 12.9. These are real gains — fully reproduced across multiple run cycles. Speed Way is the odd one. The factory profile barely moved it (+1.0%), and the manual profile moved it 9.9 percent. The manual gain is largest in Steel Nomad, the test UL released on May 21, 2024 to improve upon Time Spy; it runs at native 4K and UL rates it roughly three times heavier than Time Spy (&lt;a href="https://benchmarks.ul.com/news/3dmark-steel-nomad-is-out-now" rel="noopener">UL&lt;/a>).&lt;/p>
&lt;h2 id="clock-headroom">Clock headroom&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Profile&lt;/th>
&lt;th scope="col">Sustained boost clock in Time Spy&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Profile">RTX 5080 FE reference&lt;/td>
&lt;td data-label="Sustained boost clock in Time Spy">2,671 MHz&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Profile">Astral OC Default (factory)&lt;/td>
&lt;td data-label="Sustained boost clock in Time Spy">2,784 MHz&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Profile">Astral OC Mode BIOS&lt;/td>
&lt;td data-label="Sustained boost clock in Time Spy">2,885 MHz&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Profile">Astral Manual OC&lt;/td>
&lt;td data-label="Sustained boost clock in Time Spy">2,918 MHz&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The Astral&amp;rsquo;s default profile ran 113 MHz above my Founders Edition reference run, OC mode another 101 MHz, and my manual profile, hand-tuned in User Mode 2, 33 MHz more: 247 MHz in all. All of these are sustained boost clocks measured during Time Spy runs, not theoretical peak clocks. ASUS rates the card at 2,760 MHz in default mode and 2,790 MHz in OC mode. Both profiles ran above their rating. In my 25-minute manual-profile game log below, the core averaged 3,202 MHz against 2,918 MHz in Time Spy.&lt;/p>
&lt;h2 id="dlss-4-multi-frame-generation-the-numbers">DLSS 4 Multi Frame Generation: the numbers&lt;/h2>
&lt;p>&lt;strong>Cyberpunk 2077 · 4K path tracing · manual profile · my bench&lt;/strong>&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Mode&lt;/th>
&lt;th scope="col">Avg FPS&lt;/th>
&lt;th scope="col">PC latency (Reflex on)&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Mode">Native PT&lt;/td>
&lt;td data-label="Avg FPS">19&lt;/td>
&lt;td data-label="PC latency (Reflex on)">95 ms&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">DLSS 4 Quality, no FG&lt;/td>
&lt;td data-label="Avg FPS">40&lt;/td>
&lt;td data-label="PC latency (Reflex on)">45 ms&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">DLSS 4 Quality + MFG 2x&lt;/td>
&lt;td data-label="Avg FPS">90&lt;/td>
&lt;td data-label="PC latency (Reflex on)">55 ms&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">DLSS 4 Quality + MFG 4x&lt;/td>
&lt;td data-label="Avg FPS">135&lt;/td>
&lt;td data-label="PC latency (Reflex on)">62 ms&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Native path tracing is unplayable at 19 FPS. DLSS Quality alone doubles the frame rate to 40 and halves the latency to 45 ms. Frame generation then adds frames and some latency back: MFG 2x reached 90 FPS at 55 ms (10 ms over DLSS Quality alone) and MFG 4x 135 FPS at 62 ms (7 ms more). Against native, that is 7 times the frame rate at two-thirds of the latency.&lt;/p>
&lt;p>At 4x, three of every four frames on screen are generated from the rendered ones. On my 4K OLED, path-traced Cyberpunk at 135 FPS with Reflex on is the most visually convincing gaming experience I&amp;rsquo;ve seen on consumer hardware. The input still responds at 62 ms.&lt;/p>
&lt;h2 id="4k-gaming-results-five-tests">4K gaming results (five tests)&lt;/h2>
&lt;p>&lt;strong>4K, manual profile, my bench.&lt;/strong>&lt;/p>
&lt;p>The five rows below cover three games on GPU Tweak III User Mode 2. The RT Ultra rows for Cyberpunk and Alan Wake 2 use DLSS Quality at 4K output; native path tracing is a separate Cyberpunk run. The &lt;a href="https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/revisions/1.4.1/dataset.json" download type="application/json">June data download, revision 1.4.1&lt;/a> identifies the five configurations individually. I measured stock power and temperature; the FPS table has no matching stock or factory-OC results.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Game&lt;/th>
&lt;th scope="col">Avg FPS&lt;/th>
&lt;th scope="col">1% Low&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Game">Cyberpunk 2077 Ultra Raster&lt;/td>
&lt;td data-label="Avg FPS">58&lt;/td>
&lt;td data-label="1% Low">49&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Game">Cyberpunk 2077 RT Ultra (DLSS-Q)&lt;/td>
&lt;td data-label="Avg FPS">50&lt;/td>
&lt;td data-label="1% Low">41&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Game">Cyberpunk 2077 Path Tracing native&lt;/td>
&lt;td data-label="Avg FPS">19&lt;/td>
&lt;td data-label="1% Low">15&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Game">Alan Wake 2 RT Ultra (DLSS-Q)&lt;/td>
&lt;td data-label="Avg FPS">49&lt;/td>
&lt;td data-label="1% Low">38&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Game">Black Myth: Wukong Cinematic&lt;/td>
&lt;td data-label="Avg FPS">34&lt;/td>
&lt;td data-label="1% Low">27&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The 1% lows sit at 78 to 84 percent of the average in every run, native path tracing included.&lt;/p>
&lt;p>My 58 FPS in Cyberpunk 2077 without ray tracing is about a quarter below TechPowerUp&amp;rsquo;s 76.2 at stock. My run used the game&amp;rsquo;s built-in benchmark scene (the dataset&amp;rsquo;s method note) and TechPowerUp uses its own scene, so they are not the same test, but a gap that size is why a recorded stock re-run heads my list below. I have not run these games on the stock or factory profiles, or Starfield, Horizon Forbidden West and Silent Hill 2 at all; the table at the top carries TechPowerUp&amp;rsquo;s numbers for those.&lt;/p>
&lt;h2 id="power-and-thermals">Power and thermals&lt;/h2>
&lt;p>&lt;strong>Both profiles measured on my bench, June 8 to 11, 2026 (HWiNFO64, board power at the GPU sensor); the power-limit row lists the shipping limit and my configured target.&lt;/strong>&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Metric&lt;/th>
&lt;th scope="col">Astral Stock&lt;/th>
&lt;th scope="col">Astral Manual OC&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Metric">Power limit&lt;/td>
&lt;td data-label="Astral Stock">400 W (ships at)&lt;/td>
&lt;td data-label="Astral Manual OC">448 W (+12% power target)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Metric">Idle board power&lt;/td>
&lt;td data-label="Astral Stock">13–20 W&lt;/td>
&lt;td data-label="Astral Manual OC">20–30 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Metric">Gaming board power&lt;/td>
&lt;td data-label="Astral Stock">266–340 W&lt;/td>
&lt;td data-label="Astral Manual OC">~271 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Metric">Maximum board power under stress&lt;/td>
&lt;td data-label="Astral Stock">360 W&lt;/td>
&lt;td data-label="Astral Manual OC">400 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Metric">Idle temperature&lt;/td>
&lt;td data-label="Astral Stock">30–42 °C&lt;/td>
&lt;td data-label="Astral Manual OC">under ~50 °C&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Metric">Gaming core temperature&lt;/td>
&lt;td data-label="Astral Stock">63–72 °C&lt;/td>
&lt;td data-label="Astral Manual OC">~58 °C&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Metric">Memory junction temperature&lt;/td>
&lt;td data-label="Astral Stock">72–82 °C&lt;/td>
&lt;td data-label="Astral Manual OC">60–72 °C&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Metric">Load noise&lt;/td>
&lt;td data-label="Astral Stock">near-silent&lt;/td>
&lt;td data-label="Astral Manual OC">up to ~51 dBA&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>448 W is the +12% power target of my manual GPU Tweak III profile; the card ships at 400 W. The dataset lists a 450 W VBIOS ceiling. ASUS offered that ceiling in its March 2025 BIOS. At stock the highest draw I logged under stress was 360 W. On the manual profile it peaked at 400 W against its 448 W target. The card has two BIOSes on a switch, performance and quiet. On the launch firmware, HWCooling read the quiet BIOS&amp;rsquo;s limit at 360 W, adjustable to 400 W, and the performance BIOS&amp;rsquo;s at 400 W (&lt;a href="https://www.hwcooling.net/en/asus-rog-astral-geforce-rtx-5080-oc-ed-brutalism-in-pc/" rel="noopener">HWCooling&lt;/a>, February 3, 2025).&lt;/p>
&lt;p>The manual profile ran cooler and louder. Its fans ran up to about 51 dBA, audible from a meter away, and held the core near 58 °C and the memory at 60 to 72 °C, against 63 to 72 °C and 72 to 82 °C near-silent at stock. For quiet, flip the switch. TechPowerUp measured 25.8 dBA on the quiet BIOS against 36.3 dBA on the performance BIOS, at 70 against 62 °C. If you want lower draw and heat at the same clocks, the &lt;a href="https://techfuelhq.com/articles/rtx-5080-undervolt-guide-2026/">RTX 5080 undervolt guide&lt;/a> covers the curve method against this card&amp;rsquo;s stock numbers.&lt;/p>
&lt;p>August 19 capture, stock 448 W power limit. Running four LLMs through ollama, the card drew a median 265 to 344 W at 3,060 to 3,266 MHz, and at the Windows desktop it drew 52 to 71 W across a week of captures (&lt;a href="https://techfuelhq.com/data/rtx-5080-llm-power-efficiency/">LLM power-efficiency dataset&lt;/a>). The &lt;a href="https://techfuelhq.com/articles/rtx-5080-perf-per-watt-ai-24-7-2026/">perf-per-watt writeup&lt;/a> covers this card as an always-on inference node. In those desktop captures multi-monitor output held the card in P0.&lt;/p>
&lt;h3 id="sustained-load-telemetry-a-25-minute-log">Sustained-load telemetry: a 25-minute log&lt;/h3>
&lt;p>I logged board power, clocks, temperature, utilization and the throttle-reason register every five seconds across a 25-minute gaming session (HWiNFO64, June 28, 2026, on the hand-tuned profile). Across &lt;strong>308 samples&lt;/strong>:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Metric&lt;/th>
&lt;th scope="col">Min&lt;/th>
&lt;th scope="col">Avg&lt;/th>
&lt;th scope="col">Max&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Metric">Power draw&lt;/td>
&lt;td data-label="Min">87 W&lt;/td>
&lt;td data-label="Avg">261 W&lt;/td>
&lt;td data-label="Max">326 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Metric">Core temp&lt;/td>
&lt;td data-label="Min">45 °C&lt;/td>
&lt;td data-label="Avg">56 °C&lt;/td>
&lt;td data-label="Max">60 °C&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Metric">SM (core) clock&lt;/td>
&lt;td data-label="Min">2,985 MHz&lt;/td>
&lt;td data-label="Avg">3,202 MHz&lt;/td>
&lt;td data-label="Max">3,232 MHz&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Metric">GPU utilization&lt;/td>
&lt;td data-label="Min">1 %&lt;/td>
&lt;td data-label="Avg">85 %&lt;/td>
&lt;td data-label="Max">98 %&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>&lt;strong>Throttle events across the entire session: zero.&lt;/strong> The card held a roughly 3,200 MHz core the whole time, never hit a thermal or power cap, and averaged 261 W, well under the manual profile&amp;rsquo;s 448 W target, at a 56 °C average core temperature. That is the practical part a spec sheet can&amp;rsquo;t tell you: on this cooler, in this case, the 5080 is not temperature- or power-throttled in real gaming, so the clocks you see are the clocks you keep. The raw log, all 308 rows, is published in the &lt;a href="https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/sustained-gaming-telemetry-2026-06-28.csv" download type="text/csv">open dataset&lt;/a>.&lt;/p>
&lt;figure>
&lt;picture>
&lt;source type="image/webp" srcset="https://techfuelhq.com/images/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-installed-case-800.webp 800w, https://techfuelhq.com/images/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-installed-case-1600.webp 1600w" sizes="(max-width: 1080px) 100vw, 860px">
&lt;img src="https://techfuelhq.com/images/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-installed-case-1600.jpg" width="1600" height="900" alt="The ROG Astral RTX 5080 OC mounted in my case, three fans and the lit top bar facing the glass, the ROG PCB ruler from the box below it" loading="lazy" decoding="async">
&lt;/picture>
&lt;figcaption>The Astral in my case, with the ROG PCB ruler from the box below it.&lt;/figcaption>
&lt;/figure>
&lt;p>Coil whine on my card is mild. It scores 1 in the site&amp;rsquo;s &lt;a href="https://techfuelhq.com/data/coil-whine-database/">coil whine database&lt;/a>, audible only in uncapped game menus and gone with any frame cap.&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/#files">card&amp;rsquo;s data package&lt;/a> includes this observation as JSON and CSV, with its original submission and listening conditions. It is a subjective report from this unit, without a calibrated acoustic measurement.&lt;/p>
&lt;h2 id="generational-positioning">Generational positioning&lt;/h2>
&lt;p>&lt;strong>4K raster index, RTX 4080 Super = 100. All points TechFuelHQ first-party — the Astral on my current bench; the RTX 4080, 4080 Super and 5080 FE on my retired 2024–2025 bench, normalized as the dataset documents.&lt;/strong>&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Card&lt;/th>
&lt;th scope="col">Index&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Card">RTX 4080&lt;/td>
&lt;td data-label="Index">96&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Card">RTX 4080 Super&lt;/td>
&lt;td data-label="Index">100 (baseline)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Card">RTX 5080 FE&lt;/td>
&lt;td data-label="Index">114&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Card">Astral 5080 OC (manual)&lt;/td>
&lt;td data-label="Index">123&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>On the manual profile the Astral lands 23% above the RTX 4080 Super and 8% above the 5080 FE in 4K raster.&lt;/p>
&lt;h2 id="the-5080-oc-vs-5090-question">The 5080 OC vs. 5090 question&lt;/h2>
&lt;p>The RTX 5090 ran 30% to 68.9% faster than the RTX 5080 at 4K in &lt;a href="https://gamersnexus.net/gpus/nvidia-geforce-rtx-5080-founders-edition-review-benchmarks-vs-5090-7900-xtx-4080-more" rel="noopener">GamersNexus&amp;rsquo;s testing&lt;/a>, commonly 45 to 55 percent, with Dying Light 2 at 56 in raster. GamersNexus gave the launch MSRPs as $1,000 for the 5080 and $2,000 for the 5090. If you need the most native 4K frame rate without frame generation, the 5090 is the card. For 4K at maximum raster settings, DLSS Quality with or without MFG, and RT at DLSS Quality, the 5080 does the job. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5090-vs-5080-2026/">RTX 5090 vs RTX 5080 comparison&lt;/a> has the full decision table.&lt;/p>
&lt;p>The price changes that math. ASUS priced the Astral at $1,500 at launch (TechPowerUp, January 30, 2025). On November 17, 2026 the cheapest new RTX 5080 of any brand in Newegg&amp;rsquo;s catalogue was $2,199.99, already more than the 5090&amp;rsquo;s launch MSRP, and &lt;a href="https://www.tomshardware.com/pc-components/gpus/lowest-gpu-prices-tracking" rel="noopener">Tom&amp;rsquo;s Hardware&amp;rsquo;s price tracker&lt;/a> put the best US RTX 5080 price at $2,235 the same day. Budget for the board you actually buy, not the reference card&amp;rsquo;s MSRP; the &lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU price index&lt;/a> follows the RTX 5080 daily. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5080-review-2026/">RTX 5080 review&lt;/a> covers the GPU across boards, and &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-ti-vs-5080-2026/">RTX 5070 Ti vs RTX 5080&lt;/a> the cheaper step down; the &lt;a href="https://techfuelhq.com/tools/gpu-comparison/?a=GeForce&amp;#43;RTX&amp;#43;5080&amp;amp;b=GeForce&amp;#43;RTX&amp;#43;5070&amp;#43;Ti&amp;amp;res=1440p">GPU comparison tool&lt;/a> puts the two side by side.&lt;/p>
&lt;h2 id="the-1440p-case">The 1440p case&lt;/h2>
&lt;p>At 1440p this card is overkill. &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware&amp;rsquo;s GPU hierarchy&lt;/a> says an RTX 5070 or RX 9070 already gives a high-refresh experience at 1440p, and the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5070-review-2026/">RTX 5070 review&lt;/a> and &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rx-9060-xt-1440p-showdown-2026/">RTX 5060 Ti vs RX 9060 XT review&lt;/a> cover the cards that make sense at that resolution. At 1440p you would be buying the 5080 for Multi Frame Generation and ray tracing, and a quad-fan flagship at this price is the wrong way to buy either.&lt;/p>
&lt;h2 id="build">Build&lt;/h2>
&lt;p>ASUS lists the card at 357.6 mm long, 149.3 mm tall and 3.8 slots thick. Measure before you order. Mine hangs vertically on the HYTE Y60&amp;rsquo;s riser, which takes its weight off the slot; in a horizontal build use the ROG graphics card holder that ships in the box. For the complete rig this card runs in, see the &lt;a href="https://techfuelhq.com/pc-builds/2500-dollar-7800x3d-rtx-5080-4k-build-2026/">$2,500 RTX 5080 + 7800X3D 4K build&lt;/a>, and for power supply sizing the &lt;a href="https://techfuelhq.com/articles/what-psu-for-rtx-5080-2026/">RTX 50-series PSU guide&lt;/a>.&lt;/p>
&lt;figure>
&lt;picture>
&lt;source type="image/webp" srcset="https://techfuelhq.com/images/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-top-geforce-rtx-branding-800.webp 800w, https://techfuelhq.com/images/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-top-geforce-rtx-branding-1600.webp 1600w" sizes="(max-width: 1080px) 100vw, 860px">
&lt;img src="https://techfuelhq.com/images/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-top-geforce-rtx-branding-1600.jpg" width="1600" height="900" alt="Top-down view of the ROG Astral RTX 5080 showing the illuminated GeForce RTX lettering along the top edge of the card" loading="lazy" decoding="async">
&lt;/picture>
&lt;figcaption>The illuminated GeForce RTX lettering along the card's top edge.&lt;/figcaption>
&lt;/figure>
&lt;p>The ARGB top bar (ROG logo and stripe) runs through Aura Sync. Mine is a static purple to match the DDR5.&lt;/p>
&lt;figure class="post-video">
&lt;video controls preload="none" playsinline loop muted poster="/videos/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-rgb-cycle-poster.jpg" width="1920" height="1080">
&lt;source src="https://techfuelhq.com/videos/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-rgb-cycle-1080.webm" type="video/webm">
&lt;source src="https://techfuelhq.com/videos/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-rgb-cycle-1080.mp4" type="video/mp4">
&lt;source src="https://techfuelhq.com/videos/gpu-reviews/rog-astral-rtx-5080/rog-astral-5080-rgb-cycle-720.mp4" type="video/mp4">
&lt;/video>
&lt;figcaption>The ARGB top bar mid-cycle, a 17-second silent loop on my own card.&lt;/figcaption>
&lt;/figure>
&lt;h2 id="is-the-astral-the-best-rtx-5080-graphics-card">Is the Astral the best RTX 5080 graphics card?&lt;/h2>
&lt;p>That depends on what you are buying a 5080 for. On the measured side, the Astral gives an RTX 5080 more cooling and clock headroom than the Founders Edition. Its default profile sustained 2,784 MHz in Time Spy against 2,671 MHz for the reference run. The manual profile indexes 8 percent above the 5080 FE in 4K raster. At stock the card games near-silent at 63 to 72 °C, and the 25-minute log on the manual profile shows no throttle events.&lt;/p>
&lt;p>Those gains cost money and space. Newegg&amp;rsquo;s catalogue did not list the card in stock on November 17, 2026, when its cheapest new RTX 5080 cost $2,199.99 against a $1,000 launch MSRP, and ASUS lists it at 357.6 mm and 3.8 slots against the Founders Edition&amp;rsquo;s 304 mm and 2 slots. Only this board and the Founders Edition are compared on this page. Cards from other brands were not tested, so it cannot name one 5080 as the best for everyone. For a 4K screen and a case that fits it, the numbers above are the case for the Astral. For anything else, the &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5090-vs-5080-2026/">RTX 5090 vs RTX 5080 comparison&lt;/a> and the 1440p section above cover the alternatives.&lt;/p>
&lt;h3 id="the-best-looking-5080-and-the-white-edition">The best-looking 5080 and the white edition&lt;/h3>
&lt;p>Looks are subjective, so here is what a second reviewer wrote. TechPowerUp, which reviewed the Astral OC, says ASUS positioned the Astral brand above its ROG Strix series for &amp;ldquo;premium aesthetics and powerful air cooling,&amp;rdquo; and that its RGB lighting &amp;ldquo;isn&amp;rsquo;t as flashy&amp;rdquo; as Strix lighting: &amp;ldquo;it&amp;rsquo;s subtle and neatly executed—but what draws your attention are the textured metal alloy surfaces&amp;rdquo; (&lt;a href="https://www.techpowerup.com/review/asus-geforce-rtx-5080-astral-oc/" rel="noopener">TechPowerUp&lt;/a>, January 30, 2025, re-read October 10, 2026).&lt;/p>
&lt;p>Buyers who want a white card have a version of this one. ASUS lists a &lt;a href="https://rog.asus.com/us/graphics-cards/graphics-cards/rog-astral/rog-astral-rtx5080-o16g-white/spec/" rel="noopener">ROG Astral GeForce RTX 5080 White OC Edition&lt;/a> with the same clocks, dimensions, slot width, recommended PSU and 16-pin connector as the standard card. The box swaps in white accessories and adds a ROG Ring. The measurements on this page are from the standard Astral. The page does not rank white cards from other brands, so the best white GPU for a given case is a question of fit and budget rather than frame rate.&lt;/p>
&lt;h2 id="who-should-buy-this">Who should buy this&lt;/h2>
&lt;p>&lt;strong>Buy it if:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>You game at 4K on a high-refresh display (120 Hz or faster, OLED or IPS)&lt;/li>
&lt;li>Multi Frame Generation and path tracing in games like Cyberpunk 2077 and Alan Wake 2 are why you are upgrading&lt;/li>
&lt;li>Your case clears 357.6 mm and 3.8 slots (ASUS&amp;rsquo;s figures)&lt;/li>
&lt;li>You have budgeted for an RTX 5080 above $2,000: the cheapest new one Newegg listed on November 17, 2026 was $2,199.99, and the Astral was not in stock there that day&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Skip it if:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>Your display is 1440p or 1080p: an RTX 5070 or RX 9070 covers high-refresh 1440p, per Tom&amp;rsquo;s Hardware&lt;/li>
&lt;li>You want an RTX 5080 at the lowest price: this is the ROG Astral, and the extra money buys cooling, noise and clock headroom, not a different GPU&lt;/li>
&lt;/ul>
&lt;p>To check PSU margin and case clearance for this exact card, &lt;a href="https://techfuelhq.com/tools/pc-builder/?gpu=gpu-rog-astral-5080-oc">load it in the PC Builder&lt;/a>.&lt;/p>
&lt;h2 id="what-i-have-not-measured-yet">What I have not measured yet&lt;/h2>
&lt;ol>
&lt;li>Cyberpunk 2077 at 4K without ray tracing at stock, every setting recorded, because my manual-profile run sits about a quarter below TechPowerUp&amp;rsquo;s stock result. Then the five 4K test cases on the stock and factory profiles; every game result from my card on this page uses my manual profile.&lt;/li>
&lt;li>Starfield, Horizon Forbidden West and Silent Hill 2 at 4K on my card, so those rows stop depending on TechPowerUp&amp;rsquo;s sample.&lt;/li>
&lt;li>Noise with a sound meter at a stated distance, stock and manual, with the fan speed beside it.&lt;/li>
&lt;/ol>
&lt;h2 id="verdict">Verdict&lt;/h2>
&lt;p>&lt;strong>Rating: 4.4/5.&lt;/strong> The ROG Astral RTX 5080 OC is the best GPU I have used — and the right one for my 48-inch 4K OLED. DLSS 4 Multi Frame Generation holds up under measurement: path-traced Cyberpunk 2077 at 135 FPS and 62 ms on my manual profile on a 4K panel plays better than the native 19 FPS. At stock it is near-silent at 63 to 72 °C, and the factory and manual profiles add 1 to 13 percent in 3DMark.&lt;/p>
&lt;p>The price costs it the fifth point. With the cheapest new RTX 5080 at $2,199.99 at Newegg on November 17, 2026, even the cheapest 5080 now costs more than the RTX 5090&amp;rsquo;s launch MSRP, and the Astral&amp;rsquo;s value case is entirely 4K-specific. If the display and the game library justify it, buy it, and the &lt;a href="https://techfuelhq.com/articles/best-gpu-4k-gaming-2026/">best 4K GPU guide&lt;/a> sets it against the other 4K tiers. Otherwise, buy a 1440p-class card and a better monitor.&lt;/p>
&lt;hr>
&lt;p>&lt;em>The full first-party benchmark dataset, with the 25-minute telemetry CSV and the method notes, is at &lt;a href="https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/">/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/&lt;/a>. The &lt;a href="https://techfuelhq.com/reviews/rog-strix-b650a-review-2026/">ROG STRIX B650-A review&lt;/a> covers the motherboard in the same build.&lt;/em>&lt;/p>
&lt;p>&lt;strong>Where to buy the ASUS ROG Astral RTX 5080 OC:&lt;/strong> &lt;a href="https://www.amazon.com/dp/B0DQSD7YQC?tag=techfuelhq-20" rel="nofollow sponsored">Check Amazon&lt;/a> &amp;middot; &lt;a href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;mid=44583&amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16814126742" rel="nofollow sponsored">Check Newegg&lt;/a>. Affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/p></description></item><item><title>Move a Proxmox VM to a New Host Without a Cluster (2026)</title><link>https://techfuelhq.com/tutorials/proxmox-migrate-vm-without-cluster-2026/</link><pubDate>Wed, 17 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/proxmox-migrate-vm-without-cluster-2026/</guid><atom:updated>2026-11-18T04:45:25Z</atom:updated><description>&lt;p>&lt;code>qm migrate&lt;/code> moves a guest to another node of the same cluster. Between two standalone Proxmox VE hosts there are three routes: &lt;code>qm remote-migrate&lt;/code> (or &lt;code>pct remote-migrate&lt;/code>) straight to the other host, a backup restored on the new host, or &lt;code>zfs send&lt;/code> when both hosts keep guests on ZFS. The table below picks one by downtime, storage type and what each needs. It is written for Proxmox VE 9.2 (released May 21, 2026) against its 9.2.14 manual pages, dated November 6, 2026. (For live migration and high availability inside a cluster, see &lt;a href="https://techfuelhq.com/tutorials/proxmox-clustering-ha-2026/">Proxmox clustering and HA&lt;/a>. Setting up the new machine first? &lt;a href="https://techfuelhq.com/articles/how-to-install-proxmox-ve-2026/">Install Proxmox VE&lt;/a> on it, and size it with the &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">capacity planner&lt;/a>.)&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Keep the source until the new copy boots.&lt;/strong> &lt;code>remote-migrate&lt;/code> leaves the source VM stopped and locked unless you pass &lt;code>--delete 1&lt;/code>; &lt;code>qm unlock &amp;lt;vmid&amp;gt;&lt;/code> gives it back if the move goes wrong. Backup and restore and ZFS send leave the source guest in place.&lt;/p>&lt;/blockquote>
&lt;h2 id="which-method-fits-your-move">Which method fits your move&lt;/h2>
&lt;p>Look up both hosts&amp;rsquo; storage type first. Each storage in &lt;code>/etc/pve/storage.cfg&lt;/code> starts with a &lt;code>&amp;lt;type&amp;gt;: &amp;lt;STORAGE_ID&amp;gt;&lt;/code> line, such as &lt;code>lvmthin: local-lvm&lt;/code> or &lt;code>zfspool: local-zfs&lt;/code>.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Method&lt;/th>
&lt;th scope="col">Downtime&lt;/th>
&lt;th scope="col">Storage it can cross&lt;/th>
&lt;th scope="col">Needs&lt;/th>
&lt;th scope="col">Sources&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Method">&lt;code>qm remote-migrate --online&lt;/code>, running VM&lt;/td>
&lt;td data-label="Downtime">Usually under a second (qm chapter, online migration)&lt;/td>
&lt;td data-label="Storage it can cross">Any, for attached disks; TPM-state and unused disks follow the next row&lt;/td>
&lt;td data-label="Needs">7.3+ on both hosts, API token, no snapshots, no ISO, a CPU type the new CPU supports&lt;/td>
&lt;td data-label="Sources">&lt;a href="https://pve.proxmox.com/pve-docs/qm.1.html" rel="noopener">qm(1)&lt;/a>, &lt;a href="https://pve.proxmox.com/pve-docs/chapter-qm.html" rel="noopener">qm chapter&lt;/a>, &lt;a href="https://git.proxmox.com/?p=qemu-server.git;a=blob;f=src/PVE/QemuMigrate.pm;hb=HEAD" rel="noopener">QemuMigrate.pm&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Method">&lt;code>qm remote-migrate&lt;/code>, stopped VM&lt;/td>
&lt;td data-label="Downtime">The full disk copy&lt;/td>
&lt;td data-label="Storage it can cross">ZFS only to ZFS; LVM, LVM-thin, directory, NFS, CIFS, BTRFS and Ceph RBD among themselves&lt;/td>
&lt;td data-label="Needs">7.3+ on both hosts, API token, no snapshots, no ISO&lt;/td>
&lt;td data-label="Sources">&lt;a href="https://pve.proxmox.com/pve-docs/qm.1.html" rel="noopener">qm(1)&lt;/a>, &lt;a href="https://git.proxmox.com/?p=pve-storage.git;a=blob;f=src/PVE/Storage.pm;hb=HEAD" rel="noopener">pve-storage&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Method">&lt;code>pct remote-migrate --restart&lt;/code>, container&lt;/td>
&lt;td data-label="Downtime">Shutdown, copy, start&lt;/td>
&lt;td data-label="Storage it can cross">The stopped-VM rule for a raw root disk; a subvolume needs a target that takes subvolumes&lt;/td>
&lt;td data-label="Needs">7.3+ on both hosts, API token, no snapshots&lt;/td>
&lt;td data-label="Sources">&lt;a href="https://pve.proxmox.com/pve-docs/pct.1.html" rel="noopener">pct(1)&lt;/a>, &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pct.html" rel="noopener">pct chapter&lt;/a>, &lt;a href="https://git.proxmox.com/?p=pve-container.git;a=blob;f=src/PVE/LXC/Migrate.pm;hb=HEAD" rel="noopener">Migrate.pm&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Method">&lt;code>vzdump&lt;/code>, then &lt;code>qmrestore&lt;/code> or &lt;code>pct restore&lt;/code>&lt;/td>
&lt;td data-label="Downtime">Shutdown to first boot: backup, copy, restore&lt;/td>
&lt;td data-label="Storage it can cross">Any (&lt;code>--storage&lt;/code>)&lt;/td>
&lt;td data-label="Needs">Space for the archive on both hosts&lt;/td>
&lt;td data-label="Sources">&lt;a href="https://pve.proxmox.com/pve-docs/chapter-vzdump.html" rel="noopener">vzdump chapter&lt;/a>, &lt;a href="https://pve.proxmox.com/pve-docs/qmrestore.1.html" rel="noopener">qmrestore(1)&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Method">Restore from Proxmox Backup Server&lt;/td>
&lt;td data-label="Downtime">Final backup plus restore; final backup plus a boot with &lt;code>--live-restore&lt;/code>&lt;/td>
&lt;td data-label="Storage it can cross">Any (&lt;code>--storage&lt;/code>)&lt;/td>
&lt;td data-label="Needs">PBS storage on both hosts, same encryption key&lt;/td>
&lt;td data-label="Sources">&lt;a href="https://pve.proxmox.com/pve-docs/qmrestore.1.html" rel="noopener">qmrestore(1)&lt;/a>, &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pvesm.html" rel="noopener">storage chapter&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Method">&lt;code>zfs send&lt;/code> and &lt;code>zfs receive&lt;/code>, or &lt;code>pve-zsync&lt;/code>&lt;/td>
&lt;td data-label="Downtime">One incremental send after shutdown&lt;/td>
&lt;td data-label="Storage it can cross">ZFS to ZFS only&lt;/td>
&lt;td data-label="Needs">ZFS on both hosts, root SSH, the config copied by hand&lt;/td>
&lt;td data-label="Sources">&lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.4/8/zfs-send.8.html" rel="noopener">zfs-send(8)&lt;/a>, &lt;a href="https://pve.proxmox.com/wiki/PVE-zsync" rel="noopener">PVE-zsync&lt;/a>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The storage rule comes from pve-storage: a ZFS pool imports only ZFS streams, while LVM, LVM-thin, directory, NFS, CIFS, BTRFS and Ceph RBD storage all exchange raw-format volumes, so a stopped VM, or a container whose root disk is a raw image, can go from &lt;code>local-lvm&lt;/code> to a directory storage on the new host but not to &lt;code>local-zfs&lt;/code>. A container stored as a subvolume (BTRFS, or a size 0 root disk on directory storage) exports as &lt;code>tar+size&lt;/code>, which only storage that takes subvolumes can import; for one of those, back up and restore. Containers never go live. The pct manual lists &lt;code>--online&lt;/code>, but the pct chapter says running containers cannot be live-migrated. Offline, the copy time is the downtime. The &lt;a href="https://techfuelhq.com/tools/transfer-time-calculator/?size=100&amp;amp;unit=1000&amp;amp;disk=550&amp;amp;link=125&amp;amp;eff=0.92">transfer time calculator&lt;/a> opens on a 100 GB disk over gigabit. Containers and VMs follow different rules here; the &lt;a href="https://techfuelhq.com/homelab/lxc-vs-vm-proxmox-2026/">LXC vs VM guide&lt;/a> covers why.&lt;/p>
&lt;h2 id="before-you-move">Before you move&lt;/h2>
&lt;p>Check these on both hosts before the first command:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Storage and space.&lt;/strong> &lt;code>pvesm status&lt;/code> on the target lists each storage and its free space; every disk of the guest needs room on the storage you name.&lt;/li>
&lt;li>&lt;strong>Bridge.&lt;/strong> The target needs the bridge the guest uses, or map it with &lt;code>--target-bridge&lt;/code> (remote-migrate) and fix the network device after a restore.&lt;/li>
&lt;li>&lt;strong>A free VMID&lt;/strong> on the target. &lt;code>qmrestore&lt;/code> and &lt;code>pct restore&lt;/code> refuse one that exists unless you add &lt;code>--force&lt;/code>.&lt;/li>
&lt;li>&lt;strong>CPU type.&lt;/strong> A VM on CPU type &lt;code>host&lt;/code> can stop on arrival after a live move to a different CPU (see Method 1).&lt;/li>
&lt;li>&lt;strong>Snapshots and ISOs&lt;/strong> for remote-migrate: delete the snapshots and set the CD drive to &amp;ldquo;Do not use any media&amp;rdquo;.&lt;/li>
&lt;li>&lt;strong>Passthrough devices.&lt;/strong> The qm chapter says passed-through PCI or USB devices block live migration, and a passthrough setting may need adapting to the device&amp;rsquo;s location on the target. Note them, move the guest offline, and add the device again on the new host: a &lt;a href="https://techfuelhq.com/tutorials/gpu-passthrough-proxmox-vm-2026/">GPU passthrough VM&lt;/a> needs the new host&amp;rsquo;s IOMMU and vfio-pci setup first, and a &lt;a href="https://techfuelhq.com/tutorials/home-assistant-proxmox-2026/">Home Assistant VM&lt;/a> needs its USB radio mapped again.&lt;/li>
&lt;/ol>
&lt;h2 id="method-1-qm-remote-migrate-direct-supports-live">Method 1: &lt;code>qm remote-migrate&lt;/code> (direct, supports live)&lt;/h2>
&lt;p>&lt;code>qm remote-migrate&lt;/code> arrived in Proxmox VE 7.3 (November 22, 2022), and the 9.2.14 manual still marks it &amp;ldquo;EXPERIMENTAL feature!&amp;rdquo;. &lt;a href="https://www.proxmox.com/en/products/proxmox-datacenter-manager/overview" rel="noopener">Proxmox Datacenter Manager&lt;/a>, whose 1.0 release came on &lt;a href="https://pdm.proxmox.com/docs/roadmap.html" rel="noopener">December 4, 2025&lt;/a>, adds live migration between independent clusters to a web UI.&lt;/p>
&lt;p>&lt;strong>Syntax (VM):&lt;/strong>&lt;/p>
&lt;pre tabindex="0">&lt;code>qm remote-migrate &amp;lt;vmid&amp;gt; [&amp;lt;target-vmid&amp;gt;] &amp;lt;target-endpoint&amp;gt; \
--target-bridge &amp;lt;bridge&amp;gt; --target-storage &amp;lt;storage&amp;gt; [OPTIONS]
&lt;/code>&lt;/pre>&lt;p>The &lt;code>&amp;lt;target-endpoint&amp;gt;&lt;/code> is:&lt;/p>
&lt;pre tabindex="0">&lt;code>apitoken=PVEAPIToken=user@realm!token=SECRET,host=ADDRESS[,fingerprint=FP][,port=PORT]
&lt;/code>&lt;/pre>&lt;h3 id="make-the-token-on-the-target-host">Make the token on the target host&lt;/h3>
&lt;pre tabindex="0">&lt;code>pveum user token add root@pam migrate --privsep 0
&lt;/code>&lt;/pre>&lt;p>It prints the secret once. It cannot be shown again. &lt;code>--privsep 0&lt;/code> gives the token root&amp;rsquo;s full rights. To keep privilege separation on, create it without that flag and grant it a role on &lt;code>/&lt;/code>:&lt;/p>
&lt;pre tabindex="0">&lt;code>pveum acl modify / --tokens &amp;#39;root@pam!migrate&amp;#39; --roles Administrator
&lt;/code>&lt;/pre>&lt;p>The target&amp;rsquo;s migration tunnel checks &lt;code>VM.Allocate&lt;/code> on &lt;code>/vms/&amp;lt;vmid&amp;gt;&lt;/code> and &lt;code>Sys.Incoming&lt;/code> on &lt;code>/&lt;/code>, and the API reference adds that further checks run during the migration, which is why I would not build a narrow role for a one-off move. In the GUI the token lives under Datacenter → Permissions → API Tokens. Remove it afterwards with &lt;code>pveum user token delete root@pam migrate&lt;/code>.&lt;/p>
&lt;p>Read the target&amp;rsquo;s fingerprint on the target:&lt;/p>
&lt;pre tabindex="0">&lt;code>openssl x509 -fingerprint -sha256 -noout -in /etc/pve/nodes/$(hostname)/pve-ssl.pem
&lt;/code>&lt;/pre>&lt;p>If you installed a custom or Let&amp;rsquo;s Encrypt certificate, read &lt;code>/etc/pve/local/pveproxy-ssl.pem&lt;/code> instead. Leave &lt;code>fingerprint=&lt;/code> out and, with the default certificate, the command stops with &lt;code>fingerprint '&amp;lt;value&amp;gt;' not verified, abort!&lt;/code>, which hands you the value.&lt;/p>
&lt;h3 id="run-it-on-the-source-host">Run it on the source host&lt;/h3>
&lt;p>Replace &lt;code>&amp;lt;secret&amp;gt;&lt;/code> and &lt;code>&amp;lt;fingerprint&amp;gt;&lt;/code> with the target&amp;rsquo;s values, and pick a target VMID that is free there.&lt;/p>
&lt;pre tabindex="0">&lt;code>qm remote-migrate 134 205 \
&amp;#39;apitoken=PVEAPIToken=root@pam!migrate=&amp;lt;secret&amp;gt;,host=192.168.1.20,fingerprint=&amp;lt;fingerprint&amp;gt;&amp;#39; \
--target-bridge vmbr0 --target-storage local-lvm --online
&lt;/code>&lt;/pre>&lt;p>That moves running VM 134 to become VM 205 on 192.168.1.20, with its disks on &lt;code>local-lvm&lt;/code> and its network on &lt;code>vmbr0&lt;/code>. Keep the single quotes. Inside double quotes an interactive bash reads the &lt;code>!&lt;/code> as history expansion.&lt;/p>
&lt;p>Name the storage. One storage ID sends every disk there, and &lt;code>source:target&lt;/code> pairs map each one, as in &lt;code>local-lvm:local-zfs,tank:tank&lt;/code>. Onto &lt;code>local-zfs&lt;/code>, only a running VM&amp;rsquo;s attached disks make it; see the table. The special value &lt;code>1&lt;/code> is refused with &lt;code>remote migration requires explicit storage mapping!&lt;/code>; qm(1) still documents &lt;code>1&lt;/code> as a self-map, and the API refuses it for remote migration. &lt;code>--target-bridge 1&lt;/code> is accepted and keeps each bridge name. Other options: &lt;code>--online&lt;/code> for a running VM, &lt;code>--delete 1&lt;/code> to remove the source after a successful move, and &lt;code>--bwlimit&lt;/code> in KiB/s.&lt;/p>
&lt;p>What it refuses:&lt;/p>
&lt;ul>
&lt;li>A guest with snapshots: &lt;code>remote migration with snapshots not supported yet&lt;/code>. Delete them, or use Method 2.&lt;/li>
&lt;li>An ISO in the CD drive: &lt;code>local cdrom image&lt;/code>. Set the drive to &amp;ldquo;Do not use any media&amp;rdquo; first.&lt;/li>
&lt;li>An offline disk going between ZFS and anything else: &lt;code>no matching import/export format found for storage&lt;/code>. Proxmox staff confirmed on July 3, 2025 that the ZFS plugin only accepts volumes exported from ZFS.&lt;/li>
&lt;/ul>
&lt;p>Without &lt;code>--delete 1&lt;/code> the source VM stays stopped and locked afterwards. Proxmox staff gave &lt;code>qm unlock&lt;/code> as the way out on December 2, 2024.&lt;/p>
&lt;p>Containers take the same endpoint, &lt;code>--target-bridge&lt;/code> and &lt;code>--target-storage&lt;/code>:&lt;/p>
&lt;pre tabindex="0">&lt;code>pct remote-migrate 120 220 \
&amp;#39;apitoken=PVEAPIToken=root@pam!migrate=&amp;lt;secret&amp;gt;,host=192.168.1.20,fingerprint=&amp;lt;fingerprint&amp;gt;&amp;#39; \
--target-bridge vmbr0 --target-storage local-lvm --restart
&lt;/code>&lt;/pre>&lt;p>&lt;code>--restart&lt;/code> shuts the container down, kills it if it is still running after &lt;code>--timeout&lt;/code> seconds (180 by default), copies it offline and starts it on the target. Because that copy is offline, a container never moves between ZFS and non-ZFS storage this way. Use Method 2 instead.&lt;/p>
&lt;p>New hardware is where a live move bites. A VM with CPU type &lt;code>host&lt;/code> can stop on arrival if the new CPU lacks a flag it was started with, and the qm chapter gives live migration between Intel and AMD hosts no guarantee. Move such a VM offline, or switch it to a generic type such as &lt;code>x86-64-v2-AES&lt;/code> and restart it before the move.&lt;/p>
&lt;h2 id="method-2-vzdump--qmrestore--pct-restore-most-reliable">Method 2: &lt;code>vzdump&lt;/code> + &lt;code>qmrestore&lt;/code> / &lt;code>pct restore&lt;/code> (most reliable)&lt;/h2>
&lt;p>This route works between any two storage types.&lt;/p>
&lt;p>Shut the guest down first. The default snapshot mode backs up a running guest while it keeps running, and stop mode starts a VM again as soon as the backup begins. Either way, anything written after that point stays on the old host.&lt;/p>
&lt;pre tabindex="0">&lt;code>qm shutdown 777
vzdump 777 --compress zstd --dumpdir /var/lib/vz/dump
&lt;/code>&lt;/pre>&lt;p>For a container, &lt;code>pct shutdown 777&lt;/code> comes first. Continue only after shutdown succeeds, and keep the source guest stopped. The file name carries the guest type, VMID and backup time: &lt;code>vzdump-qemu-777-2026_09_26-07_10_00.vma.zst&lt;/code> for a VM, &lt;code>.tar.zst&lt;/code> for a container. Replace the example archive paths below with the actual file produced by your backup.&lt;/p>
&lt;p>Copy it:&lt;/p>
&lt;pre tabindex="0">&lt;code>rsync -avP /var/lib/vz/dump/vzdump-qemu-777-2026_09_26-07_10_00.vma.zst root@192.168.1.20:/var/lib/vz/dump/
&lt;/code>&lt;/pre>&lt;p>Restore it on the new host, a VM and then a container:&lt;/p>
&lt;pre tabindex="0">&lt;code>qmrestore /var/lib/vz/dump/vzdump-qemu-777-2026_09_26-07_10_00.vma.zst 500 --storage local-zfs
pct restore 600 /var/lib/vz/dump/vzdump-lxc-777-2026_09_26-07_10_00.tar.zst --storage local-zfs
&lt;/code>&lt;/pre>&lt;p>Always pass &lt;code>--storage&lt;/code> here. Without it, &lt;code>qmrestore&lt;/code> allocates each disk on the storage named in the backup, which fails when the new host has no storage by that name. Pick a free VMID, or add &lt;code>--force&lt;/code> to overwrite one. &lt;code>--unique&lt;/code> gives the guest a new random MAC address: use it only if the old copy will run again on the same network, since a DHCP reservation keyed to the old MAC stops matching.&lt;/p>
&lt;h3 id="restoring-from-proxmox-backup-server">Restoring from Proxmox Backup Server&lt;/h3>
&lt;p>If both hosts can reach one PBS datastore, add it on the new host (Datacenter → Storage → Add → Proxmox Backup Server) and restore from its backups. There is no file to copy. Shut the source guest down and take a final PBS backup before restoring, then keep the source stopped. For encrypted backups the new host needs the same key, because without it the backups are inaccessible. A VM can start at once with &lt;code>--live-restore&lt;/code> (or the GUI checkbox) while the data copies in the background, but reads stay slow until the data arrives and a failed live-restore leaves the VM in an undefined state. With &lt;code>--live-restore&lt;/code>, the downtime is that final backup plus a boot.&lt;/p>
&lt;h2 id="method-3-zfs-send-and-zfs-receive-zfs-on-both-hosts">Method 3: &lt;code>zfs send&lt;/code> and &lt;code>zfs receive&lt;/code> (ZFS on both hosts)&lt;/h2>
&lt;p>The full copy runs while the guest is up; the incremental stream after shutdown contains the changes since the first snapshot. Pool and dataset setup on the new host is in the &lt;a href="https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/">ZFS on Proxmox guide&lt;/a>. On a default ZFS install the &lt;code>local-zfs&lt;/code> storage is the &lt;code>rpool/data&lt;/code> dataset. The example uses &lt;code>rpool/data/vm-134-disk-0&lt;/code>; check the disk names in &lt;code>/etc/pve/qemu-server/134.conf&lt;/code> and substitute your actual volumes. Choose a free target VMID and destination volume names that do not already exist.&lt;/p>
&lt;p>Send the full copy with the VM running:&lt;/p>
&lt;pre tabindex="0">&lt;code>zfs snapshot rpool/data/vm-134-disk-0@move1
zfs send rpool/data/vm-134-disk-0@move1 | ssh root@192.168.1.20 zfs receive rpool/data/vm-205-disk-0
&lt;/code>&lt;/pre>&lt;p>Then shut it down and send only what changed:&lt;/p>
&lt;pre tabindex="0">&lt;code>qm shutdown 134
zfs snapshot rpool/data/vm-134-disk-0@move2
zfs send -i @move1 rpool/data/vm-134-disk-0@move2 | ssh root@192.168.1.20 zfs receive rpool/data/vm-205-disk-0
&lt;/code>&lt;/pre>&lt;p>Do both sends for every disk in &lt;code>/etc/pve/qemu-server/134.conf&lt;/code>, EFI and TPM-state disks included. Finish all full sends before shutdown, and take every final snapshot only after shutdown succeeds. Keep the source stopped. An incremental receive needs the target&amp;rsquo;s newest snapshot to match the stream&amp;rsquo;s source. Do not touch the received volume in between.&lt;/p>
&lt;p>Copy the config across:&lt;/p>
&lt;pre tabindex="0">&lt;code>scp /etc/pve/qemu-server/134.conf root@192.168.1.20:/root/134.conf
&lt;/code>&lt;/pre>&lt;p>On the target, put it in place. Check first that &lt;code>qm list&lt;/code> on the target shows no VM 205:&lt;/p>
&lt;pre tabindex="0">&lt;code># Destructive if VM 205 already exists: this overwrites its config
cp /root/134.conf /etc/pve/qemu-server/205.conf
&lt;/code>&lt;/pre>&lt;p>Edit &lt;code>205.conf&lt;/code> so each disk line names the new volume, for example &lt;code>scsi0: local-zfs:vm-205-disk-0,size=32G&lt;/code>, and start it with &lt;code>qm start 205&lt;/code>.&lt;/p>
&lt;p>&lt;code>pve-zsync&lt;/code> runs the same sends from cron, every 15 minutes by default, and keeps the guest config on the target under &lt;code>/var/lib/pve-zsync/&lt;/code>. Version 2.4.0 is the Debian 13 build that Proxmox VE 9 uses. Its wiki page was last edited in December 2020. The tool needs IP addresses rather than host names; the guest restores by the same manual steps as above.&lt;/p>
&lt;h2 id="the-pitfalls-that-bite">The pitfalls that bite&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>ZFS on one side only.&lt;/strong> A stopped VM, every container and a running VM&amp;rsquo;s TPM-state disk copy offline, and an offline copy between ZFS and other storage fails. Inside a cluster the same limit reads &lt;code>cannot migrate from storage type 'lvmthin' to 'zfspool'&lt;/code>.&lt;/li>
&lt;li>&lt;strong>&lt;code>--target-storage 1&lt;/code>.&lt;/strong> Refused for remote migration. Name the storage.&lt;/li>
&lt;li>&lt;strong>Bridge naming.&lt;/strong> The new host needs the bridge the guest uses, or map it with &lt;code>--target-bridge&lt;/code>. A VM whose bridge is missing does not start, and the task log names the bridge.&lt;/li>
&lt;li>&lt;strong>VMID conflicts.&lt;/strong> &lt;code>qmrestore&lt;/code> and &lt;code>pct restore&lt;/code> refuse a VMID that exists unless you add &lt;code>--force&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Snapshots and ISOs&lt;/strong> block remote-migrate. Remove them first.&lt;/li>
&lt;/ul>
&lt;h2 id="after-the-move-check-then-retire-the-source">After the move: check, then retire the source&lt;/h2>
&lt;ol>
&lt;li>Start the guest on the target (&lt;code>qm start &amp;lt;vmid&amp;gt;&lt;/code> or &lt;code>pct start &amp;lt;vmid&amp;gt;&lt;/code>) and confirm &lt;code>qm status &amp;lt;vmid&amp;gt;&lt;/code> reports &lt;code>running&lt;/code>.&lt;/li>
&lt;li>If the VM runs the QEMU guest agent, &lt;code>qm guest cmd &amp;lt;vmid&amp;gt; network-get-interfaces&lt;/code> shows the address it took. A restore keeps the MAC address unless you used &lt;code>--unique&lt;/code>.&lt;/li>
&lt;li>Open the services the guest provides from another machine, and add back any passthrough device.&lt;/li>
&lt;li>Only then remove the source. After a remote-migrate without &lt;code>--delete 1&lt;/code> it is stopped and locked: &lt;code>qm unlock &amp;lt;vmid&amp;gt;&lt;/code> first.&lt;/li>
&lt;/ol>
&lt;pre tabindex="0">&lt;code># Destructive: on the SOURCE host, deletes the old VM and all its disks
qm destroy &amp;lt;vmid&amp;gt;
&lt;/code>&lt;/pre>&lt;p>For a container the command is &lt;code>pct destroy &amp;lt;vmid&amp;gt;&lt;/code>, which deletes the container and its files.&lt;/p>
&lt;p>If you are moving guests off a host so you can rebuild it, read the &lt;a href="https://techfuelhq.com/tutorials/proxmox-ve-8-to-9-upgrade-2026/">PVE 8 to 9 upgrade gotchas&lt;/a> before you reinstall.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;p>Read September 26, 2026; the manuals, error strings, permissions and Datacenter Manager date were re-read November 18, 2026.&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://pve.proxmox.com/pve-docs/qm.1.html" rel="noopener">Proxmox &lt;code>qm&lt;/code> manual&lt;/a>, &lt;a href="https://pve.proxmox.com/pve-docs/pct.1.html" rel="noopener">&lt;code>pct&lt;/code> manual&lt;/a>, &lt;a href="https://pve.proxmox.com/pve-docs/qmrestore.1.html" rel="noopener">&lt;code>qmrestore&lt;/code> manual&lt;/a>, &lt;a href="https://pve.proxmox.com/pve-docs/vzdump.1.html" rel="noopener">&lt;code>vzdump&lt;/code> manual&lt;/a> and &lt;a href="https://pve.proxmox.com/pve-docs/pvesm.1.html" rel="noopener">&lt;code>pvesm&lt;/code> manual&lt;/a>, version 9.2.14, November 6, 2026 (qm, pct and pvesm re-read November 18, 2026)&lt;/li>
&lt;li>Proxmox VE chapters: &lt;a href="https://pve.proxmox.com/pve-docs/chapter-qm.html" rel="noopener">QEMU/KVM&lt;/a> (online migration, CPU type), &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pct.html" rel="noopener">containers&lt;/a> (migration), &lt;a href="https://pve.proxmox.com/pve-docs/chapter-vzdump.html" rel="noopener">backup and restore&lt;/a>, &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pvesm.html" rel="noopener">storage&lt;/a> (storage.cfg, PBS encryption), &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pveum.html" rel="noopener">user management&lt;/a> (API tokens)&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/pve-docs/api-viewer/" rel="noopener">Proxmox VE API viewer&lt;/a> (&lt;code>remote_migrate&lt;/code> and &lt;code>mtunnel&lt;/code> permissions)&lt;/li>
&lt;li>Proxmox source at git HEAD: &lt;a href="https://git.proxmox.com/?p=qemu-server.git;a=blob;f=src/PVE/QemuMigrate.pm;hb=HEAD" rel="noopener">QemuMigrate.pm&lt;/a> and &lt;a href="https://git.proxmox.com/?p=qemu-server.git;a=blob;f=src/PVE/API2/Qemu.pm;hb=HEAD" rel="noopener">API2/Qemu.pm&lt;/a> (qemu-server), &lt;a href="https://git.proxmox.com/?p=pve-container.git;a=blob;f=src/PVE/LXC/Migrate.pm;hb=HEAD" rel="noopener">LXC/Migrate.pm&lt;/a> (pve-container), &lt;a href="https://git.proxmox.com/?p=pve-storage.git;a=blob;f=src/PVE/Storage.pm;hb=HEAD" rel="noopener">Storage.pm&lt;/a> and &lt;a href="https://git.proxmox.com/?p=pve-storage.git;a=blob;f=src/PVE/Storage/ZFSPoolPlugin.pm;hb=HEAD" rel="noopener">ZFSPoolPlugin.pm&lt;/a> (pve-storage)&lt;/li>
&lt;li>More Proxmox source at git HEAD: &lt;a href="https://git.proxmox.com/?p=pve-storage.git;a=blob;f=src/PVE/Storage/BTRFSPlugin.pm;hb=HEAD" rel="noopener">BTRFSPlugin.pm&lt;/a> and &lt;a href="https://git.proxmox.com/?p=pve-storage.git;a=blob;f=src/PVE/Storage/RBDPlugin.pm;hb=HEAD" rel="noopener">RBDPlugin.pm&lt;/a> (raw-image formats), &lt;a href="https://git.proxmox.com/?p=pve-common.git;a=blob;f=src/PVE/Network.pm;hb=HEAD" rel="noopener">Network.pm&lt;/a> (missing bridge), &lt;a href="https://git.proxmox.com/?p=pve-apiclient.git;a=blob;f=src/PVE/APIClient/LWP.pm;hb=HEAD" rel="noopener">LWP.pm&lt;/a> (fingerprint check), and the web UI labels in &lt;a href="https://git.proxmox.com/?p=pve-manager.git;a=blob;f=www/manager6/qemu/CDEdit.js;hb=HEAD" rel="noopener">CDEdit.js&lt;/a>, &lt;a href="https://git.proxmox.com/?p=pve-manager.git;a=blob;f=www/manager6/dc/Config.js;hb=HEAD" rel="noopener">dc/Config.js&lt;/a> and &lt;a href="https://git.proxmox.com/?p=pve-manager.git;a=blob;f=www/manager6/Utils.js;hb=HEAD" rel="noopener">Utils.js&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_certs_api_gui" rel="noopener">Certificates for API and web GUI&lt;/a> (&lt;code>pve-ssl.pem&lt;/code>, &lt;code>pveproxy-ssl.pem&lt;/code>) and the &lt;a href="https://git.proxmox.com/?p=pve-zsync.git;a=blob;f=debian/changelog;hb=HEAD" rel="noopener">pve-zsync changelog&lt;/a> (2.4.0 for Debian 13, June 17, 2025)&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/wiki/Roadmap" rel="noopener">Proxmox VE Roadmap&lt;/a> (7.3 on November 22, 2022; 9.2 on May 21, 2026), the &lt;a href="https://pdm.proxmox.com/docs/roadmap.html" rel="noopener">Proxmox Datacenter Manager roadmap&lt;/a> (1.0 on December 4, 2025) and the &lt;a href="https://pve.proxmox.com/wiki/PVE-zsync" rel="noopener">PVE-zsync wiki&lt;/a>&lt;/li>
&lt;li>OpenZFS 2.4 &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.4/8/zfs-send.8.html" rel="noopener">zfs-send(8)&lt;/a> and &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.4/8/zfs-recv.8.html" rel="noopener">zfs-recv(8)&lt;/a>&lt;/li>
&lt;li>Proxmox forum, staff replies: &lt;a href="https://forum.proxmox.com/threads/8-3-qm-remote-migrate.158335/" rel="noopener">source VM locked after remote-migrate&lt;/a> (December 2, 2024) and &lt;a href="https://forum.proxmox.com/threads/migration-between-clusters-fails-no-matching-import-export-format-found-for-storage.168094/" rel="noopener">ZFS accepts only ZFS exports&lt;/a> (July 3, 2025)&lt;/li>
&lt;/ul></description></item><item><title>Proxmox Cluster Management: Build a 2-Node Cluster or 3-Node HA (2026)</title><link>https://techfuelhq.com/tutorials/proxmox-clustering-ha-2026/</link><pubDate>Sat, 13 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/proxmox-clustering-ha-2026/</guid><atom:updated>2026-11-18T04:45:25Z</atom:updated><description>&lt;p>A single Proxmox node is fine until it isn&amp;rsquo;t. The drive fails. The NIC dies. You need to reboot for a kernel update and everything goes down.&lt;/p>
&lt;p>A Proxmox cluster solves this. It is two or more nodes that share cluster state and can migrate VMs between them. It can also restart VMs automatically when a node fails.&lt;/p>
&lt;p>This guide follows Proxmox VE 9.2 and its 9.2.14 admin guide (November 6, 2026), with the PVE 8 syntax noted where it differs. It covers the 2-node architecture with a QDevice and the cleaner 3-node architecture that doesn&amp;rsquo;t need one, then shared storage, live migration, HA placement, the fencing question you can&amp;rsquo;t skip, and the day-to-day work of adding and removing nodes. Each node starts as a plain &lt;a href="https://techfuelhq.com/articles/how-to-install-proxmox-ve-2026/">Proxmox VE install&lt;/a>; for the boxes themselves, the &lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">homelab mini PC guide&lt;/a> and the &lt;a href="https://techfuelhq.com/homelab/ms-01-as-a-homelab-node/">MS-01 node review&lt;/a> cover small machines with the spare NICs a cluster wants.&lt;/p>
&lt;h2 id="what-a-proxmox-cluster-gives-you">What a Proxmox cluster gives you&lt;/h2>
&lt;p>Proxmox clustering has two distinct features that people sometimes conflate:&lt;/p>
&lt;p>&lt;strong>1. Cluster management (no shared storage required)&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>Unified web UI: manage all nodes from one panel&lt;/li>
&lt;li>Centralized user and permission management&lt;/li>
&lt;li>Pool-based resource allocation across nodes&lt;/li>
&lt;li>Planned VM migration between nodes, with shared disks or disk transfer&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>2. High Availability (HA) - requires recoverable disks + fencing&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>Automatic VM restart on surviving node when a node fails&lt;/li>
&lt;li>HA watchdog groups with priority ordering&lt;/li>
&lt;li>Fencing to prevent split-brain and data corruption&lt;/li>
&lt;/ul>
&lt;p>You can run a cluster for migration and unified management without HA. HA also needs reliable quorum, fencing, spare capacity and every required guest disk on an eligible recovery node. After a node fails, its guest restarts from disk on a surviving node once fencing permits recovery, so the guest&amp;rsquo;s RAM contents are lost and its applications may need to recover from the interrupted writes. Expect downtime during that restart.&lt;/p>
&lt;h2 id="architecture-2-node-vs-3-node">Architecture: 2-node vs 3-node&lt;/h2>
&lt;h3 id="3-node-cluster-recommended">3-node cluster (recommended)&lt;/h3>
&lt;p>Three nodes each have a vote in corosync. Quorum is 2 votes (majority). If any single node fails:&lt;/p>
&lt;ul>
&lt;li>2 surviving nodes form quorum&lt;/li>
&lt;li>Cluster continues operating&lt;/li>
&lt;li>HA restarts VMs on surviving nodes&lt;/li>
&lt;/ul>
&lt;p>This is the clean architecture. No workarounds, no QDevice, straightforward HA.&lt;/p>
&lt;h3 id="2-node-cluster-with-qdevice">2-node cluster with QDevice&lt;/h3>
&lt;p>Two nodes cannot hold quorum on their own. Each losing the other would leave one node alone, and one vote does not equal a majority of two.&lt;/p>
&lt;p>The solution is a QDevice: a third machine that provides a tie-breaking vote. It runs &lt;code>corosync-qnetd&lt;/code> as the arbiter, and each cluster node runs the &lt;code>corosync-qdevice&lt;/code> client.&lt;/p>
&lt;pre tabindex="0">&lt;code>Node 1 (vote) + Node 2 (vote) + QDevice (vote) = 3 votes total
Quorum = 2 votes required
&lt;/code>&lt;/pre>&lt;p>If Node 1 fails: Node 2 + QDevice = 2 votes → quorum → cluster continues.
If the QDevice fails: Node 1 + Node 2 = 2 votes → quorum maintained (QDevice is just a tiebreaker).
If Node 1 + QDevice both fail: Node 2 alone = 1 vote → no quorum → node fences itself.&lt;/p>
&lt;p>The QDevice can be any Debian or Ubuntu machine that has the &lt;code>corosync-qnetd&lt;/code> package and a stable network path to both nodes: a Raspberry Pi, an LXC on a third server or a VM on a NAS.&lt;/p>
&lt;pre tabindex="0">&lt;code> node1 ── corosync link0 (UDP 5405-5412) ── node2
│ │
└────── TCP 5403 ── QDevice (qnetd) ───────┘
disks: shared NFS/iSCSI, or local ZFS replicated node1 &amp;lt;-&amp;gt; node2
&lt;/code>&lt;/pre>&lt;p>Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pvecm.html" rel="noopener">Cluster Manager documentation&lt;/a>, re-read on 2026-11-18, adds details that matter for a 2-node cluster:&lt;/p>
&lt;ul>
&lt;li>QDevices are supported for even-numbered clusters and recommended for 2-node clusters that need higher availability.&lt;/li>
&lt;li>The QDevice talks to the nodes over TCP/IP and can sit outside the cluster LAN. Corosync&amp;rsquo;s low-latency requirement does not apply to it.&lt;/li>
&lt;li>In a tie between two equal halves that cannot see each other but can both see the QDevice, the QDevice votes for the partition with the lowest node ID.&lt;/li>
&lt;li>With only two plain votes and no QDevice, losing one node loses quorum. Proxmox says the cluster then switches to read-only mode.&lt;/li>
&lt;li>For odd-numbered clusters, Proxmox currently discourages a QDevice. If it fails, no other node may fail without losing quorum. The setup command&amp;rsquo;s own message says &amp;ldquo;Clusters with an odd node count are not officially supported!&amp;rdquo;&lt;/li>
&lt;/ul>
&lt;h2 id="prerequisites">Prerequisites&lt;/h2>
&lt;p>For a 2-node + QDevice cluster:&lt;/p>
&lt;ul>
&lt;li>2 Proxmox hosts (any hardware, same or different specs)&lt;/li>
&lt;li>1 QDevice host (Raspberry Pi, mini PC, or any Debian/Ubuntu system)&lt;/li>
&lt;li>All three on the same network (or VLANs with routing between them)&lt;/li>
&lt;li>&lt;strong>No existing Proxmox clusters&lt;/strong> on any node. Clusters can only be created, not merged&lt;/li>
&lt;li>UDP ports 5405-5412 open between the nodes for corosync, plus SSH on TCP port 22&lt;/li>
&lt;li>Synchronized date and time, and the same Proxmox VE version on every node&lt;/li>
&lt;li>Each node installed with its final hostname and IP address. Proxmox says neither can be changed after the cluster exists&lt;/li>
&lt;/ul>
&lt;p>For HA (optional, beyond basic clustering):&lt;/p>
&lt;ul>
&lt;li>Shared storage accessible from eligible recovery nodes, or local ZFS replicated to those nodes&lt;/li>
&lt;li>Watchdog device for fencing (the kernel softdog works everywhere; a hardware/IPMI watchdog where the board offers one)&lt;/li>
&lt;/ul>
&lt;h2 id="step-1-create-the-cluster-on-node-1">Step 1: Create the cluster on node 1&lt;/h2>
&lt;p>Log into node 1&amp;rsquo;s Proxmox web UI or SSH in:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Create the cluster (run on node 1 only)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>pvecm create mycluster --link0 &amp;lt;node1-ip&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Verify the cluster is created:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>pvecm status
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Should show: Quorum information, Node ID 1, Member count 1&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-2-join-node-2-to-the-cluster">Step 2: Join node 2 to the cluster&lt;/h2>
&lt;p>&lt;strong>Back up first.&lt;/strong> Joining overwrites everything in &lt;code>/etc/pve&lt;/code> on the joining node, and a node that holds guests cannot join. If node 2 already runs guests, back each one up with &lt;code>vzdump&lt;/code> to storage off that node, and restore them under new IDs after the join; Proxmox&amp;rsquo;s Cluster Manager chapter gives this as the workaround.&lt;/p>
&lt;p>From node 2, join the existing cluster:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Run on node 2. Destructive: overwrites node 2&amp;#39;s /etc/pve&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>pvecm add &amp;lt;node1-ip&amp;gt; --link0 &amp;lt;node2-ip&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This prompts for node 1&amp;rsquo;s root password. After joining, verify from node 1:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>pvecm nodes
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Should show both nodes listed&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>At this point, both nodes appear in the web UI under Datacenter. The cluster exists but cannot survive a node loss. With 2 nodes, both votes are needed for quorum, so losing either node means no quorum.&lt;/p>
&lt;p>Two cautions from Proxmox&amp;rsquo;s documentation before you join a node:&lt;/p>
&lt;ul>
&lt;li>Joining overwrites everything in &lt;code>/etc/pve&lt;/code> on the joining node. A node that already holds guests cannot join, and it inherits the cluster&amp;rsquo;s storage configuration.&lt;/li>
&lt;li>To put corosync on its own network, pass the link addresses: &lt;code>pvecm add &amp;lt;node1-ip&amp;gt; --link0 &amp;lt;node2-ip&amp;gt;&lt;/code> (as above), and add &lt;code>--link1&lt;/code> for a redundant second link. Corosync supports up to 8 links.&lt;/li>
&lt;/ul>
&lt;h2 id="step-3-set-up-the-qdevice">Step 3: Set up the QDevice&lt;/h2>
&lt;p>On the QDevice machine (Debian/Ubuntu) install &lt;code>corosync-qnetd&lt;/code>. This machine is the &lt;strong>arbiter&lt;/strong>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>apt update &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span> apt install -y corosync-qnetd
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;code>corosync-qdevice&lt;/code> is the node-side client, and it goes on every cluster node. Proxmox&amp;rsquo;s documentation lists this as a manual step before the setup command:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Run on node 1 and node 2&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>apt install -y corosync-qdevice
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Make sure all nodes are online, then on node 1 configure the QDevice:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>pvecm qdevice setup &amp;lt;qdevice-ip&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This copies the cluster SSH key to the QDevice and configures corosync on all nodes to include the QDevice vote. It needs root SSH access to the QDevice machine. Use key-based access, or allow root password login temporarily during setup. If setup reports &amp;ldquo;Host key verification failed&amp;rdquo;, run &lt;code>pvecm updatecerts&lt;/code> and try again.&lt;/p>
&lt;p>Verify:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>pvecm status
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Quorate: Yes&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Total votes: 3 (node1 + node2 + qdevice)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Expected votes: 3&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Quorum: 2 &amp;lt;- the threshold, printed separately&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The &lt;code>Qdevice&lt;/code> flag should appear in the &lt;code>pvecm status&lt;/code> output. If the QDevice shows as Not Alive (NA), check that TCP port 5403 on the QDevice machine is reachable from the nodes.&lt;/p>
&lt;h2 id="step-4-choose-storage-for-migration-and-ha">Step 4: Choose storage for migration and HA&lt;/h2>
&lt;p>The &lt;a href="https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_migration" rel="noopener">VM migration reference&lt;/a> allows transfer of local disks. The &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pvesr.html" rel="noopener">storage replication reference&lt;/a> explicitly allows HA with replicated local ZFS. Choose a recovery design:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Disk design&lt;/th>
&lt;th scope="col">Planned migration while source works&lt;/th>
&lt;th scope="col">Recovery after source-node failure&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Disk design">Shared NFS, iSCSI/LVM or Ceph&lt;/td>
&lt;td data-label="Planned migration while source works">Eligible VMs can migrate without copying shared disks&lt;/td>
&lt;td data-label="Recovery after source-node failure">HA can restart on an eligible node if the storage remains available&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Disk design">Local ZFS with Proxmox replication&lt;/td>
&lt;td data-label="Planned migration while source works">Copy changes since the replica&amp;rsquo;s last sync&lt;/td>
&lt;td data-label="Recovery after source-node failure">HA is supported on replica targets; writes after the last successful sync can be lost&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Disk design">Local disks without replication&lt;/td>
&lt;td data-label="Planned migration while source works">Copy disks to target storage; live migration depends on VM eligibility&lt;/td>
&lt;td data-label="Recovery after source-node failure">No surviving disk copy for HA; recover the source or restore a backup&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h3 id="local-zfs-replication">Local ZFS replication&lt;/h3>
&lt;p>Create a local ZFS storage with the same storage ID on each target and sufficient free space. In the guest&amp;rsquo;s &lt;strong>Replication&lt;/strong> panel, add a job targeting the intended recovery node, set its schedule, and verify a successful initial sync with &lt;code>pvesr status&lt;/code> and the job log. Every local disk needed to boot and run the guest must be covered; a disk excluded from replication will not appear on the recovery node.&lt;/p>
&lt;p>Restrict HA placement to replica targets. Use a restricted group on PVE 8 or a strict node-affinity rule on PVE 9 to keep recovery, placement and migration within nodes that hold all the guest&amp;rsquo;s disks and dependencies. Check replicas and job errors before enabling HA.&lt;/p>
&lt;p>The recovery point is the last successful sync. Failed jobs can leave it older than the configured interval. Replication and HA still need independent backups.&lt;/p>
&lt;p>The shared-storage alternatives follow below. A single NAS can remain a failure point even when several Proxmox nodes use it.&lt;/p>
&lt;h3 id="nfs-easiest-for-homelab">NFS (easiest for homelab)&lt;/h3>
&lt;p>If you have a TrueNAS or any NFS server:&lt;/p>
&lt;p>In Proxmox web UI: Datacenter → Storage → Add → NFS&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Setting&lt;/th>
&lt;th scope="col">Value&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Setting">ID&lt;/td>
&lt;td data-label="Value">&lt;code>nfs-shared&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Server&lt;/td>
&lt;td data-label="Value">&lt;code>192.168.1.x&lt;/code> (NFS server IP)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Export&lt;/td>
&lt;td data-label="Value">&lt;code>/mnt/pool/proxmox&lt;/code> (your NFS export path)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Content&lt;/td>
&lt;td data-label="Value">&lt;code>Disk image, CT template, ISO image, VZDump backup file&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Nodes&lt;/td>
&lt;td data-label="Value">All (select all cluster nodes)&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>After adding, both nodes should see the same NFS storage in their storage list.&lt;/p>
&lt;p>&lt;strong>Verify from both nodes:&lt;/strong>&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># On both node1 and node2&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ls /mnt/pve/nfs-shared/
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Both should show the same directory contents&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="iscsi">iSCSI&lt;/h3>
&lt;p>For better performance than NFS, an iSCSI target (TrueNAS, OpenMediaVault, or a dedicated SAN):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Discover iSCSI targets&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>iscsiadm -m discovery -t st -p &amp;lt;iscsi-server-ip&amp;gt;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Log in to target&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>iscsiadm -m node -T &amp;lt;target-name&amp;gt; -p &amp;lt;iscsi-server-ip&amp;gt; --login
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Add in Proxmox UI: Datacenter → Storage → Add → iSCSI, then put plain &lt;strong>LVM&lt;/strong> on top. Do not use LVM-thin here: it is not cluster-aware and cannot be shared between nodes, so it cannot back HA or live migration. That is the whole point of this section.&lt;/p>
&lt;h3 id="ceph-advanced-distributed-storage">Ceph (advanced, distributed storage)&lt;/h3>
&lt;p>Ceph runs on the Proxmox nodes themselves — each node contributes disks to a distributed object store. No separate NAS required.&lt;/p>
&lt;p>Ceph requires:&lt;/p>
&lt;ul>
&lt;li>3+ Proxmox nodes (Ceph quorum is formed by an odd number of &lt;strong>monitors&lt;/strong>, not OSDs)&lt;/li>
&lt;li>A dedicated disk per node for Ceph OSD (separate from the OS disk)&lt;/li>
&lt;li>Low-latency network between nodes (10GbE strongly recommended)&lt;/li>
&lt;/ul>
&lt;p>Set up via Proxmox web UI: Datacenter → Ceph → Install → follow wizard. Ceph is powerful but adds complexity.&lt;/p>
&lt;p>&lt;strong>Two nodes and Ceph?&lt;/strong> Not as Proxmox documents it. Its &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pveceph.html" rel="noopener">Ceph chapter&lt;/a> says a hyper-converged Proxmox and Ceph cluster must use at least three servers, that at least three monitors are needed for quorum, and recommends at least 12 OSDs spread evenly across three or more nodes. On two nodes, use local ZFS with replication or NFS.&lt;/p>
&lt;h2 id="step-5-live-migration">Step 5: Live migration&lt;/h2>
&lt;p>For an eligible VM, live migration can use shared disks or transfer local disks. In the web UI:&lt;/p>
&lt;ol>
&lt;li>Select a VM&lt;/li>
&lt;li>Right-click → Migrate&lt;/li>
&lt;li>Target node: select the other node&lt;/li>
&lt;li>Select online migration for a running VM; review target storage mappings if local disks need transfer&lt;/li>
&lt;li>Click Migrate&lt;/li>
&lt;/ol>
&lt;p>&lt;strong>From the CLI:&lt;/strong>&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Live migrate VM ID 100 to node2&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>qm migrate &lt;span style="color:#ae81ff">100&lt;/span> node2 --online
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># For a VM with local disks, permit their transfer; check target storage first&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>qm migrate &lt;span style="color:#ae81ff">100&lt;/span> node2 --online --with-local-disks &lt;span style="color:#ae81ff">1&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Use &lt;code>qm help migrate&lt;/code> for the options on your installed release. Check CPU compatibility, target disk space and matching guest networks. PCI/USB passthrough and other resources tied to one host can block live migration. A container migration is a separate workflow; these &lt;code>qm&lt;/code> commands are for VMs.&lt;/p>
&lt;p>Time depends on effective throughput, memory dirty rate and how much disk data must move. Test a noncritical representative guest on your installed PVE release, keep its application active during migration, and record task duration and any lost connections. Test a return migration too.&lt;/p>
&lt;p>Two migration settings from Proxmox&amp;rsquo;s documentation are worth knowing:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Secure vs insecure mode.&lt;/strong> Secure mode encrypts the migration channel. Insecure mode sends guest RAM unencrypted, which can expose secrets, so Proxmox recommends secure mode unless you control the network.&lt;/li>
&lt;li>&lt;strong>Migration network.&lt;/strong> By default, migration traffic uses the cluster network. To use a dedicated network, pass it for one migration with &lt;code>qm migrate 100 node2 --online --migration_network 10.1.2.0/24&lt;/code>, or set &lt;code>migration: secure,network=10.1.2.0/24&lt;/code> in &lt;code>/etc/pve/datacenter.cfg&lt;/code>. Always set the migration type alongside the network there.&lt;/li>
&lt;/ul>
&lt;p>Proxmox recommends CPUs from the same vendor with similar capabilities for online migration. Its reference says cross-vendor migration can sometimes work but is not guaranteed; validate the guest CPU model before relying on it.&lt;/p>
&lt;h2 id="step-6-enable-high-availability">Step 6: Enable High Availability&lt;/h2>
&lt;p>Fencing is what makes HA safe. Without it, a node that becomes unreachable (but is not actually down) could keep running VMs while the surviving node restarts the same VMs, corrupting shared storage.&lt;/p>
&lt;h3 id="how-proxmox-fencing-works-watchdog-self-fencing">How Proxmox fencing works: watchdog self-fencing&lt;/h3>
&lt;p>Proxmox VE does not use external fence agents. There is no fencing dialog in the GUI, which trips up people arriving from Pacemaker/corosync setups.&lt;/p>
&lt;p>Instead, every node running HA resources arms a hardware watchdog timer. If the node loses quorum, &lt;code>pve-ha-lrm&lt;/code> stops petting the watchdog and the node hard-resets itself after about 60 seconds. Only after that window does the cluster recover the VMs elsewhere. (&lt;a href="https://pve.proxmox.com/pve-docs/chapter-ha-manager.html#ha_manager_fencing" rel="noopener">Proxmox HA manager documentation&lt;/a>)&lt;/p>
&lt;p>Out of the box Proxmox uses the Linux kernel &lt;code>softdog&lt;/code> module, which loads automatically the first time a node runs an HA resource. On a homelab you typically configure nothing at all. It is software fencing rather than hardware fencing, but it is the supported default and it prevents split-brain.&lt;/p>
&lt;p>Verify the watchdog device exists once an HA resource is active:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ls /dev/watchdog
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="using-a-hardware-watchdog-boards-with-ipmibmc">Using a hardware watchdog (boards with IPMI/BMC)&lt;/h3>
&lt;p>Boards with a BMC usually expose a true hardware watchdog (&lt;code>ipmi_watchdog&lt;/code>; many Intel boards expose &lt;code>iTCO_wdt&lt;/code>). It keeps fencing working even if the kernel itself wedges, which softdog cannot guarantee. Select it in &lt;code>/etc/default/pve-ha-manager&lt;/code> (&lt;strong>not&lt;/strong> &lt;code>resources.cfg&lt;/code>, which holds HA resource stanzas — writing this key there corrupts it), then reboot the node:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>WATCHDOG_MODULE&lt;span style="color:#f92672">=&lt;/span>ipmi_watchdog
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Blacklist competing watchdog modules if the BMC and chipset both expose one. Exactly one driver should own &lt;code>/dev/watchdog&lt;/code>.&lt;/p>
&lt;h3 id="enable-ha-for-a-vm">Enable HA for a VM&lt;/h3>
&lt;p>Fencing is armed automatically with the watchdog, so this is the only step most homelabs perform:&lt;/p>
&lt;ol>
&lt;li>Web UI → Select VM → More → Manage HA&lt;/li>
&lt;li>Click &amp;ldquo;Add HA&amp;rdquo;&lt;/li>
&lt;li>On PVE 8 only, optionally pick an HA group; on PVE 9, placement comes from node-affinity rules (Step 7)&lt;/li>
&lt;li>Max Restart: 3 (restart attempts before abandoning)&lt;/li>
&lt;li>Max Relocate: 3 (move attempts to another node)&lt;/li>
&lt;/ol>
&lt;p>Or CLI:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ha-manager add vm:100 --state started --max_restart &lt;span style="color:#ae81ff">3&lt;/span> --max_relocate &lt;span style="color:#ae81ff">3&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Check HA status:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ha-manager status
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Shows: vm:100 in state started, node: node1&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>When node1 fails, a quorate cluster waits for fencing and restarts VM 100 on an eligible node with its disks available. With local ZFS replication, that is a replica target and recovery uses the last successful sync.&lt;/p>
&lt;p>&lt;strong>Test failover before you trust it.&lt;/strong> Put a noncritical guest under HA, then cut power to its node (or pull its cluster network cable) and watch &lt;code>ha-manager status&lt;/code> on a surviving node. The HA manager documentation says the lost node&amp;rsquo;s watchdog fires after 60 seconds, and only then are its services recovered on another node, so expect a gap of a minute or more before the guest boots elsewhere. Bring the node back, check that the guest returns if failback applies, and only then put real services under HA.&lt;/p>
&lt;h2 id="step-7-ha-placement-node-affinity-rules-pve-9-or-groups-pve-8">Step 7: HA placement: node-affinity rules (PVE 9) or groups (PVE 8)&lt;/h2>
&lt;p>On Proxmox VE 9, placement is a node-affinity rule. The official HA manager reference says &amp;ldquo;HA Groups are deprecated and migrated to HA Node Affinity rules since Proxmox VE 9.0&amp;rdquo; (&lt;a href="https://pve.proxmox.com/pve-docs/chapter-ha-manager.html" rel="noopener">ha-manager docs&lt;/a>, checked 2026-11-18), and the &lt;a href="https://techfuelhq.com/tutorials/proxmox-ve-8-to-9-upgrade-2026/">8 to 9 upgrade&lt;/a> converts existing groups for you. This rule prefers node1 and allows node2:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># PVE 9.x: prefer node1 (priority 2), allow node2 (priority 1), non-strict&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ha-manager rules add node-affinity ha-rule1 --resources vm:100 --nodes node1:2,node2:1
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Rules are non-strict by default, so the VM may run elsewhere if neither node is available. For replicated local storage, make the rule strict so recovery stays on valid replica targets: &lt;code>ha-manager rules set node-affinity ha-rule1 --strict 1&lt;/code>. Datacenter → HA → Affinity Rules shows the same thing in the web UI. When node1 returns, the default failback setting moves the VM back to the highest-priority node.&lt;/p>
&lt;p>On PVE 8, the same preference is an HA group:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># PVE 8: a group that prefers node1 but allows node2&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ha-manager groupadd ha-group1 --nodes node1:2,node2:1 --restricted &lt;span style="color:#ae81ff">0&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># node1:2 = priority 2 (preferred), node2:1 = priority 1 (failover)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># restricted 0 = allow running on any node if no listed node is online&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ha-manager set vm:100 --group ha-group1
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>For replicated local storage on PVE 8, use a restricted group covering only valid replica targets.&lt;/p>
&lt;h2 id="managing-a-proxmox-cluster-add-remove-and-edit">Managing a Proxmox cluster: add, remove and edit&lt;/h2>
&lt;p>These tasks come from Proxmox&amp;rsquo;s &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pvecm.html" rel="noopener">Cluster Manager documentation&lt;/a>, re-read on 2026-11-18.&lt;/p>
&lt;h3 id="remove-a-node">Remove a node&lt;/h3>
&lt;p>Do this in order:&lt;/p>
&lt;ol>
&lt;li>Move every guest off the node and back up any local data.&lt;/li>
&lt;li>Remove replication jobs that involve the node. Otherwise, Proxmox warns, the job becomes irremovable.&lt;/li>
&lt;li>If you use a QDevice, remove it first with &lt;code>pvecm qdevice remove&lt;/code>.&lt;/li>
&lt;li>If you run Ceph, destroy the node&amp;rsquo;s OSDs one at a time, wait for HEALTH_OK, and remove its monitor and manager first.&lt;/li>
&lt;li>Power the node off and make sure it cannot come back on this network with its current configuration.&lt;/li>
&lt;li>From a remaining node, run &lt;code>pvecm delnode &amp;lt;nodename&amp;gt;&lt;/code>, then confirm with &lt;code>pvecm nodes&lt;/code>.&lt;/li>
&lt;/ol>
&lt;p>A &amp;ldquo;could not kill node (error = cs_err_not_exist)&amp;rdquo; message can be ignored. Afterwards, remove &lt;code>/etc/pve/nodes/&amp;lt;nodename&amp;gt;&lt;/code> once you have confirmed the name, remove the node from any HA rules, and remove its key from &lt;code>/etc/pve/priv/authorized_keys&lt;/code>. To reuse the hardware, reinstall Proxmox VE and join it again.&lt;/p>
&lt;h3 id="change-the-node-count-with-a-qdevice-in-place">Change the node count with a QDevice in place&lt;/h3>
&lt;p>Proxmox says to remove the QDevice first, add or delete the nodes, and set the QDevice up again once the node count is even.&lt;/p>
&lt;h3 id="edit-corosyncconf-safely">Edit corosync.conf safely&lt;/h3>
&lt;p>On Proxmox VE 9.2 with HA in use, disarm HA first so a brief quorum loss during the change does not fence a node, and re-arm it when corosync is healthy again. The HA manager documentation warns that HA does not protect your services while disarmed, so keep the window short:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ha-manager crm-command disarm-ha freeze
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># ... corosync change ...&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ha-manager crm-command arm-ha
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Edit a copy and leave the live file untouched. Raise &lt;code>config_version&lt;/code> in the copy:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>cp /etc/pve/corosync.conf /etc/pve/corosync.conf.new
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># edit corosync.conf.new and increase config_version&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cp /etc/pve/corosync.conf /etc/pve/corosync.conf.bak
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Destructive: the next line replaces the live cluster configuration on every node&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>mv /etc/pve/corosync.conf.new /etc/pve/corosync.conf
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>systemctl status corosync
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>journalctl -b -u corosync
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If the change is not applied automatically, run &lt;code>systemctl restart corosync&lt;/code>.&lt;/p>
&lt;h3 id="after-a-full-power-loss">After a full power loss&lt;/h3>
&lt;p>A cluster is not quorate while every node is off. On startup, &lt;code>pve-guests&lt;/code> waits for quorum and then starts guests flagged to start on boot, so guest startup is delayed until enough nodes are back. Proxmox recommends a UPS, especially with HA; &lt;a href="https://techfuelhq.com/homelab/ups-testing-reality-2026/">how to test a UPS&lt;/a> covers checking that yours will actually carry the nodes.&lt;/p>
&lt;h2 id="monitoring-cluster-health">Monitoring cluster health&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Cluster-wide status&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>pvecm status
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Node status &lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>pvecm nodes
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># HA manager status&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ha-manager status
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Corosync ring status (network health between nodes)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>corosync-cfgtool -s
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Check for quorum issues&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>corosync-quorumtool
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>In the web UI: Datacenter → Summary shows all nodes with CPU/RAM/disk graphs and cluster status.&lt;/p>
&lt;h2 id="common-issues">Common issues&lt;/h2>
&lt;p>&lt;strong>&amp;ldquo;Cluster not quorate&amp;rdquo;&lt;/strong> — Usually means the QDevice is unreachable or a node went offline without fencing. Check &lt;code>corosync-cfgtool -s&lt;/code> for ring status. Confirm QDevice is running &lt;code>systemctl status corosync-qdevice&lt;/code>.&lt;/p>
&lt;p>&lt;strong>Local-disk migration fails&lt;/strong> - Read the migration task log and check destination storage IDs, free space, disk mappings and local-resource restrictions. Local disks are supported; moving everything to shared storage is not the only remedy. If the target reports an existing guest or conflicting volume, inspect that conflict before retrying or deleting anything.&lt;/p>
&lt;p>&lt;strong>HA manager won&amp;rsquo;t start VMs&lt;/strong> — check &lt;code>ha-manager status&lt;/code>. The usual causes are lost quorum (the surviving side can&amp;rsquo;t fence-and-recover until quorum returns) or a resource stuck in an error state after a failed recovery. The HA manager documentation says the only way out of the error state is disabling the resource: bring it to a safe state, run &lt;code>ha-manager set vm:&amp;lt;id&amp;gt; --state disabled&lt;/code>, fix the cause, then request &lt;code>--state started&lt;/code> again.&lt;/p>
&lt;p>&lt;strong>Corosync ring 0 errors&lt;/strong> — Network instability between nodes. Check physical connectivity, switch port speed (ensure both nodes are at full duplex), and that the corosync network isn&amp;rsquo;t saturated. Corosync is very sensitive to dropped packets.&lt;/p>
&lt;h2 id="network-recommendations">Network recommendations&lt;/h2>
&lt;ul>
&lt;li>Dedicate a network interface or VLAN for corosync (&lt;code>--link0&lt;/code> parameter)&lt;/li>
&lt;li>VM traffic on a separate interface or VLAN from cluster communication&lt;/li>
&lt;li>10GbE between nodes for live migration (1GbE works but migration is slow)&lt;/li>
&lt;li>Storage traffic on a third interface if possible&lt;/li>
&lt;/ul>
&lt;p>The &lt;a href="https://techfuelhq.com/tutorials/vlans-homelab-2026/">VLANs for the homelab guide&lt;/a> covers network segmentation for cluster + storage + VM traffic with OPNsense and managed switches, and the &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE homelab networking guide&lt;/a> covers the faster migration link. Before HA, check that the surviving nodes have room for the failed node&amp;rsquo;s guests; the &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">capacity planner&lt;/a> does that arithmetic per host.&lt;/p>
&lt;hr>
&lt;p>&lt;em>Cluster storage architecture connects to ZFS. The &lt;a href="https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/">ZFS on Proxmox guide&lt;/a> covers local storage pool creation; for cluster scenarios, set up local ZFS before joining nodes to the cluster.&lt;/em>&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://pve.proxmox.com/wiki/Cluster_Manager" rel="noopener">Proxmox VE Cluster Manager&lt;/a> &amp;ndash; official wiki for pvecm, corosync, quorum, and QDevice setup. The &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pvecm.html" rel="noopener">pve-docs chapter&lt;/a>, version 9.2.14, was re-read on 2026-11-18 for requirements, node removal, corosync editing, QDevice setup, and migration settings.&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/wiki/High_Availability" rel="noopener">Proxmox VE High Availability&lt;/a> &amp;ndash; official docs for ha-manager, groups, fencing, and the watchdog.&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/wiki/Storage" rel="noopener">Proxmox VE Storage&lt;/a> &amp;ndash; official reference for NFS, iSCSI, and other shared storage used by HA and live migration.&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/pve-docs/chapter-pvesr.html" rel="noopener">Proxmox VE Storage Replication&lt;/a> and &lt;a href="https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_migration" rel="noopener">VM migration&lt;/a> &amp;ndash; local ZFS replicas, their recovery-point limitation, and local-disk migration. Checked 2026-10-12 in the project&amp;rsquo;s &lt;a href="https://github.com/proxmox/pve-docs/blob/master/pvesr.adoc" rel="noopener">replication source&lt;/a> and &lt;a href="https://github.com/proxmox/pve-docs/blob/master/qm.adoc" rel="noopener">VM source&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster" rel="noopener">Deploy Hyper-Converged Ceph Cluster&lt;/a> and the &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pveceph.html" rel="noopener">pve-docs Ceph chapter&lt;/a> &amp;ndash; the three-server minimum, three monitors for quorum and the 12-OSD recommendation, read 2026-11-18.&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/pve-docs/chapter-ha-manager.html" rel="noopener">High Availability chapter&lt;/a>, version 9.2.14, read 2026-11-18 &amp;ndash; the 60-second watchdog, node-affinity rules and strictness, failback, error-state recovery and disarming HA for maintenance.&lt;/li>
&lt;li>&lt;a href="https://git.proxmox.com/?p=pve-cluster.git;a=blob;f=src/PVE/CLI/pvecm.pm;hb=HEAD" rel="noopener">pvecm.pm in pve-cluster&lt;/a> &amp;ndash; the odd-node-count message printed by &lt;code>pvecm qdevice setup&lt;/code>.&lt;/li>
&lt;/ul></description></item></channel></rss>