Is there a hidden way to select less vibrant colors on the Snapmaker selector?

Oct 28, 2026 Last reply: 1 hour ago 5 Replies

First reply

Ray_Quarry

The colour you pick in the selector is purely cosmetic for the preview, so it will never affect how your part actually comes out. What matters is the filament you physically load, so if you want a muted grey, the real solution is buying or mixing a desaturated grey PLA, not…

Read the full reply

I'm running into a weird issue while prepping a custom print job on my Snapmaker, and I need some advice. I'm trying to get a specific muted grey for a small functional part, but the colour selector only gives me options that are way too strong or too dark. I keep selecting the closest grey shade available, but even that one looks highly saturated when I preview it. It seems like they only include the most vivid versions of these standard PLA colors. Is there some setting or maybe a different menu where the less aggressive, more muted tones are stored? I'm having trouble getting the exact subtle look I'm aiming for. I checked the material list, but it just shows the brightest possibilities. Does anyone know if there is a hidden palette for those more subdued colours? Any tips on finding something less intense would be appreciated.


The colour you pick in the selector is purely cosmetic for the preview, so it will never affect how your part actually comes out. What matters is the filament you physically load, so if you want a muted grey, the real solution is buying or mixing a desaturated grey PLA, not hunting for one in the software menu. That said, I get the annoyance with the preview. On my Snapmaker I hit the same wall when I was planning a multi-part print and the preset list only had garish options. Two things fixed it for me. First, in the desktop app you can open the colour settings and adjust the shade with sliders rather than being stuck with the presets, so you can dial the saturation down until the preview looks like what you actually want. Second, and this is the part that took me a while to accept: the mapping screen at the print task stage lets you assign any colour block to any loaded filament. So if the closest preset is some punchy charcoal but your spool is a soft dove grey, you just map the model section to the right tray and ignore the visual mismatch.

If you're doing automatic colour assignment from a model painted with multiple shades, the limited presets do cause collisions, which sounds closer to what the original thread was complaining about. The workaround I settled on was to paint the model with deliberately different presets, even ugly ones, then remap each one to the correct physical spool before slicing. Tedious the first time, but it becomes routine. There are also plugins and spool management add-ons floating around that let you store a custom entry with the exact shade code for each spool you own, which removes the guesswork entirely if you swap filaments often. But for a single small functional part, the sliders in the app plus a manual map at the print stage should get you there without any extra setup.

Still figuring this machine out myself so forgive me if this is a dumb question, but I mostly print single colour stuff for repairs around the house and never touched the painting tools. Now I want to try a two-tone bracket and this thread has me worried. If two sections of my model end up on the same preset by accident, does the slicer just merge them into one colour block, or does it warn me first? I'd rather find out now than mid print. Also curious if those custom shade entries carry over between projects or if you redo them each time.

This thread is clearing up a lot for me because I honestly thougt the machine could somehow tell what colour the spool was just by looking at it. I've only ever loaded one at a time and never paid attention to the mapping step. So if I swap a spool for a diffrent colour mid-project, does the machine remember which tray had which one, or do I have to tell it every time?

Yeah the auto mapping thing bites me too when I slice anything with more than two colours. My trick is to just pick presets that are visually far apart on purpose, like red and teal, even if they've got nothing to do with the real filament. Looks ridiculous in the preview but the mapping never mixes them up that way. One thing I've wondered though, does anyone know if custom colour entries stick around after an app update? I made a few a while back and they seemed to vanish on me, so now I just don't trust saving them.

Something I've noticed with these preview colours is that half the problem is the render itself, not the palette. The preview appears to apply some shading and lighting to the model surface, so even a genuinely desaturated grey preset ends up looking punchier on screen than the actual filament will under room light. I stopped judging shades from the preview and started comparing spools to a printed swatch instead, which cured most of my mismatch complaints. Also, if you're being precise about it, monitor calibration shifts how those presets read, so two people can pick different 'closest' greys for the same spool and both be right on thier own screens.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required