Why won't my filament color match a printer?

Color is the number-one reason a queue item won't match a printer, and it's the one that confuses people most - a printer is loaded with what looks like the right color, but the item still won't start. This guide is the complete reference: how SimplyPrint actually decides whether two colors match, the strictness setting that controls it, the two tools that fix a mismatch (color clusters and color mapping), and when to reach for each.

If you're troubleshooting a stuck queue item in general (not just color), start with why won't my printer print this queue item? and come back here for the color detail.

In this article

• The short version
• How color matching actually works
• The strictness setting: "Material colors must match"
• Worked examples: what matches and what doesn't
• Fix 1: color clusters (treat colors as equivalent)
• Fix 2: color mapping (rewrite one color to another)
• Clusters vs mapping: which one do I want?
• Material type matters too (and material clusters)
• Where a color comes from: auto-tagging and the palette
• Settings quick reference and defaults
• Related articles

The short version

• SimplyPrint matches color on the actual color - both the color name and the hex code - not just the name.
• How close is "close enough" is set by Material colors must match (in your queue / AutoPrint matching criteria). The default is Similar match.
• Fix a stubborn mismatch two ways: a color cluster (declare two colors equal - works both directions, and even at the strictest setting) or a color mapping (rewrite one color into another when files are tagged).
• "Material shrinkage" is a slicer setting for dimensional accuracy. It has nothing to do with color matching - if you came here about that, it won't help.

How color matching actually works

Every queue item that's tagged with a color carries two pieces of information: a color name (like "Red") and a hex code (like #D50000). The printer's loaded spool carries the same two pieces. When SimplyPrint checks whether the printer can run the item, it compares the colors - and it does not just compare the names.

There's one important split in how strict that comparison is:

• On a single-material printer, the check is strict: the color matches only when the name and the hex both agree (or a color cluster says they're equal). Two spools both called "red" with different hex codes are treated as different colors.
• On a printer with a multi-material system (Bambu Lab AMS, Prusa MMU, Creality CFS, Anycubic ACE), SimplyPrint builds a color map to assign each of the file's colors to a loaded slot. That mapping can be smarter - it can treat near-identical colors as the same by resolving each to its nearest named color - and how smart is exactly what the strictness setting below controls.

Either way, clearly different colors never match on their own, and you bridge a deliberate near-miss with a color cluster or a color mapping.

The strictness setting: "Material colors must match"

In your matching criteria (Settings › Print queue, and separately Settings › AutoPrint) there's a dropdown labelled Material colors must match, with the help text "Select the level of precision to use when matching colors." It has five levels, from strictest to loosest:

When to use which:

• Exact match - color-critical work where the wrong shade is a reject (production farms printing to a spec). Combine with clusters for the handful of colors you treat as interchangeable.
• Similar match (default) - the right choice for almost everyone. It stops a free printer sitting idle just because "Navy" and "Dark Blue" are named differently, while still refusing to print your red part in green.
• Any color - when color genuinely doesn't matter (prototypes, jigs, internal parts) and you just want the queue to use whatever's loaded. This effectively turns the color check off.

This dropdown is one of a whole set of matching-criteria toggles (nozzle, bed, material type, size, temperatures). For the full list, defaults, and a strict-vs-loose workflow across all of them, see why won't my printer print this queue item?.

Worked examples: what matches and what doesn't

All examples assume default settings (Similar match) unless noted.

The queue inspector shows this as the Color reason on any printer that's excluded, so you never have to guess which of these you've hit.

Fix 1: color clusters (treat colors as equivalent)

A color cluster is a group of colors you've declared interchangeable. When one color in a cluster is detected on a file, every other color in that cluster is also accepted as a match. Clusters are the right fix when several colors should always count as the same working color - three brands of black, "Natural" and "White", or a set of near-identical reds.

Two things make clusters powerful:

• They work both directions - membership is equivalence, not a one-way rule.
• They count as an exact match, so a cluster bridges colors even when your strictness is set to Exact match. Tighten the global setting, keep your handful of known-equivalents flowing.

How to build one (Settings › Tagging › Colors › Color clusters):

1. Click Add color cluster. Each cluster needs at least 2 colors.
2. For each entry, set a color. You have three ways:

• Type a hex and/or a color name by hand.
• Pick from the palette swatches.
• Use Import colors / Get color from... to pull real colors from a source (see below).

3. Optionally set a specific material on an entry ("Optional specific material") so the equivalence only applies to that material - e.g. cluster these two reds only for PLA. Leave it blank to apply to any material.
4. Save. Clusters apply everywhere colors are matched - the queue, AutoPrint, the control panel and the file selector.

The "Get color from..." sources (the "select from a file / a printer" part). Instead of typing hex codes, pull the exact colors that already exist in your setup:

• Filament database - pick a brand and material to grab its colors from the Open Filament Database.
• A printer - grab a color currently set on one of a printer's slots, including colors the printer itself reported that don't have a name yet.
• A file - grab a file's tagged colors, plus the raw colors detected inside the file.

That last two are the fix for the most common real cause of a mismatch: the color your slicer baked into the file has a slightly different hex than the color on your spool. Grab both (one from A file, one from A printer), drop them in a cluster, and they'll match from now on.

Fix 2: color mapping (rewrite one color to another)

A color mapping is a one-directional rewrite: "whenever a file is tagged as color A, store it as color B instead." As the panel puts it, you can map "Red" to "Crimson", optionally only for a specific material. Unlike a cluster, a mapping actually changes the color stored on the item - it's applied when the file is auto-tagged, not at match time.

Build one at Settings › Tagging › Colors › Color mapping: set the From color (a hex, optionally scoped to a material) and the To color (hex + name). Mapping is the right tool when a slicer or profile keeps producing a color you'd rather standardise on - you're normalising your data at the source, so everything downstream lines up.

Clusters vs mapping: which one do I want?

They solve the same symptom differently, and the distinction matters:

Rule of thumb: reach for a cluster first (it's non-destructive and bidirectional). Use a mapping when you specifically want to clean up incoming color data so it's consistent everywhere.

Material type matters too (and material clusters)

Color is only half of "material". A queue item can match on color and still be excluded because the material type is wrong - blue PLA won't run on a printer loaded with blue PETG. Two related controls:

• Strict material type match (on by default) - "Use branded material types rather than generic. Generic PLA will not match with Bambu Lab PLA Basic if this setting is enabled." Turn it off to match at the family level (any PLA matches any PLA). This defaults to strict for a good reason: branded materials genuinely differ - in temperatures, flow, density and even shrinkage - so treating them as identical can hurt a print.
• Material clusters - the material equivalent of color clusters. Declare two material types equal (your house-brand PLA and PLA+) so they match each other. Set them up in Settings › Tagging › Materials.

Where a color comes from: auto-tagging and the palette

Most items get their color automatically when they're sliced or added - auto-tagging reads the file and applies a color name and hex. If items are consistently getting the wrong color, the fix is upstream in your tagging rules rather than per-item. Two settings shape what color gets recorded:

• Single-color files - by default, a single-color file is tagged with its material type but no color (the assumption is it's the default color, not a color-specific job). If you want single-color files to carry their color too, enable "Auto-tag color on single-extrusion files" in Settings › Tagging.
• The color picker palette (Settings › Tagging › Colors › Color picker palette) - controls which colors are offered when assigning colors. Five modes: Standard palette (default - standard + your custom + brand colors), Custom palette only, Filament inventory (only colors of spools you own), Loaded filament only, and Loaded color tags only (strictest). Two optional locks go with it: Lock selection to the palette (hide the "add custom color" option) and Don't auto-tag colors outside the palette (drop a detected color that isn't in your palette; this one only appears once you pick a non-standard palette mode). Both are off by default.

For the full auto-tagging picture, see auto-tagging and auto printer-model selection. For per-slot color on multi-material printers, see multi-material color mapping.

Settings quick reference and defaults

Everything that affects color matching, and where to find it:

Related articles

• Why won't my printer print this queue item?
• All about the "Tags" feature
• Auto-tagging and auto printer-model selection
• Multi-material color mapping
• Auto-matching queue items to printers

Updated on: 04/07/2026