Diablo IV GUIDE

Diablo 4 Loot Filter: Hide, Show and Recolor Without Losing Sight of Upgrades

Start a Diablo 4 loot filter with visible checks, not aggressive hiding. Learn what Hide, Show, Recolor, and Codex Upgrade Check do in the researched guide, then test rules without assuming an unverified conflict priority.

Original illustration contrasting crafting scraps and iron ingots with a leather purse and gold coins.

Diablo 4’s native loot filter combines item conditions with display actions such as Hide, Show, and Recolor. For players building their first filter, start by making useful categories recognizable, then hide only categories you have checked you no longer need. Do not assume an unverified rule priority will protect an upgrade from a conflicting Hide rule.

Start here: the filter controls what you see on the ground; it is not a promise of better drops. This walkthrough is based mainly on Maxroll’s researched instructions, not hands-on testing, and uses October 24, 2026 as its cutoff. Desktop code import also should not be promised as an identical console workflow.

Separate the condition from the display action

Maxroll’s Loot Filter guide, updated July 21, explains that filters combine conditions to hide unwanted items or recolor item names on the floor. Conditions describe which items a rule addresses. The display action describes how those matching items should be presented.

Its examples include Visibility selections for Hide All and Show, plus Recolor rules. Those examples are separate demonstrations, not a single finished configuration to combine blindly. A rule that identifies a rarity and one that identifies a Codex opportunity may overlap; the research does not establish which action wins if you give them incompatible instructions.

For a returning character, begin with a written objective such as identifying equipment worth inspecting for a Codex upgrade. That is clearer than copying a strict filter whose author no longer needs categories that remain useful to your character.

Choose actions that match the question you are asking

Your goal Action to consider Check before expanding it
Make a candidate category stand out Recolor Does the condition identify the items you intended?
Explicitly display a category Show Does another enabled rule conflict with it?
Reduce a category you no longer need to see Hide All Have you inspected its relevance first?
Identify a possible Codex improvement Codex Upgrade Check condition Are you still looking for those upgrades?
Understand unexpected behavior Isolate rules while testing Are you changing only one display decision?

These are decision aids, not a claim about matching precedence. Maxroll confirms that several rules can be active in one filter, but that alone does not establish first-match, last-match, or an automatic safety override. Avoid relying on any of those explanations without verified documentation.

Use Codex checks before hiding broad equipment groups

Maxroll’s recoloring example includes the Codex Upgrade Check condition and instructs readers to select it. That offers a specific purpose for a rule: noticing equipment relevant to Codex improvement rather than treating all items of one rarity as interchangeable clutter.

Suppose your equipped items look settled, but your Codex still has gaps. A broad decision to hide equipment you would not personally equip can overlook that separate reason to inspect it. Review the Codex and Aspects checklist before deciding that an entire equipment category is irrelevant.

The researched guide specifically warns that its non-Ancestral Legendary hiding section should only be enabled when those items are no longer needed. That warning is more useful here than copying its progression labels or an item-power threshold. Your needs, not a borrowed strictness name, should determine when a category disappears.

Test visibility before making the filter strict

As a cautious workflow, begin with the category visible and inspect examples of what its condition selects. Recoloring can help make that inspection easier without immediately removing the category from sight. This is a recommended testing approach, not a claim that a particular color or rule set has been tested here.

Change one decision at a time. If an item appears differently than you expected, review the enabled rules addressing that category and isolate them rather than guessing their priority. Do not use a hidden-item shortcut as a safety net: the supplied research did not verify a universal key or identical platform behavior.

Also keep ground visibility separate from inventory policy. The inventory and stash organization guide concerns physical items you retain. A filter helps decide what to notice; it does not decide whether every noticed item belongs in storage.

Import codes with platform limits in mind

For code import, Maxroll says the code must already be copied. Its desktop-oriented sequence is New Filter, then import code, then confirm. After importing, inspect the actual enabled rules before relying on the result, especially any broad hiding decisions inherited from somebody else’s progression stage.

The same source says console players cannot directly import code from the guide. Do not translate the desktop clipboard steps into a guaranteed console feature. Use the instructions available on your platform and preserve the same caution about categories you still need.

Blizzard’s Lord of Hatred page provides official background mentioning a Loot Filter. Its promotional wording is not the evidence for these operational steps, conflict behavior, or platform support; those details come from the scoped Maxroll research. No later patch or future PTR feature is treated as already effective here.

Frequently asked questions

Does a loot filter increase the quality of drops?

The cited mechanism concerns ground-item visibility and name coloring. This guide makes no claim that a filter changes item generation, improves drop quality, or guarantees more valuable results. It changes your presentation of loot.

Will a Show rule always override Hide?

The supplied research does not verify conflict priority. Do not assume Show automatically protects a matching item from Hide. Remove contradictory actions or isolate rules during testing rather than depending on an undocumented ordering rule.

Should I hide all non-Ancestral Legendary items immediately?

No. Maxroll explicitly warns to enable that hiding choice only when you no longer need those items. Check Codex needs and inspect the category first. Start with visibility, verify the condition, and tighten the filter only when your own requirements support it.

Related guides

Explore the Diablo 4 Guides collection.

Sources and editorial notes

This article is an editorial explanation, not a personal gameplay test report, current-season build ranking or guarantee of results. Version-sensitive item text, availability, access requirements and recipes must be checked against current developer information and the in-game interface. Historical sources are identified in the article rather than treated as current patch certification.

Cover image: a reused AI-generated editorial illustration from LootGo, not an official gameplay screenshot or an exact depiction of these mechanics.