Read the anchor first
Start with Cape. Set it, then stop before it becomes louder than Superman really is.
🦸 Superheroes
A fan-made gameplay palette for Superman with hex, RGB, and HSB values for each playable color part. Study the reference, then test your color memory.
suit
rgb(36, 107, 179)
HSB(210° 80% 70%)
cape
rgb(204, 31, 31)
HSB(0° 85% 80%)
Color Study
Don't study the palette. Read it once, then play. The reveal will tell you what your memory changed.
Start with Cape. Set it, then stop before it becomes louder than Superman really is.
Suit tells you whether the palette still has structure. If it disappears or fights the anchor, your guess is already drifting.
The numbers are here for review, not for copying. Play first. Use the reveal to name the miss.
Do not change everything. Fix one thing: hue, saturation, or brightness. That is how the page becomes practice.
Use this round to see whether bold red-vs-blue anchors stay disciplined once the reveal exposes oversaturation and contrast drift.
Run the hero benchmark →Superman works as a first study page because the red cape and blue suit create a clean two-part palette almost every player can recognize before the timer pressure kicks in.
That makes this page useful beyond search intent alone: it teaches the difference between knowing a character instantly and matching the exact brightness and saturation that Toon Tone scores.
Superman is not hard because the palette is obscure. He is hard in the safer, beginner way: memory makes the red hotter and the blue louder than the target values.
If you can notice that drift here, you build the habit you need later for darker or lower-contrast pages where the mistakes are harder to spot.
See how this palette compares with another iconic challenge before you decide what to play next.
Compare Superman vs BatmanStarter Benchmark
Treat Superman as the benchmark for clean contrast. The goal is not to admire the character; it is to learn how two obvious color parts still drift apart in memory.
Suit
darkest control point
Suit acts as the darkest control point for Superman. It is the darkest part in the palette, so even a small brightness miss can flatten the whole character. It is one of the calmer pieces, so players often forget how much restraint it needs. Use Suit against Cape to check whether your guess kept the right contrast relationship.
rgb(36, 107, 179) · HSB(210° 80% 70%)
Cape
brightest and loudest anchor
Cape acts as the brightest and loudest anchor for Superman. It is the brightest part in the palette, so players often remember it as cleaner or more glowing than it really is. This is also the most saturated piece, which makes it the easiest part to overcook. Use Cape against Suit to check whether your guess kept the right contrast relationship.
rgb(204, 31, 31) · HSB(0° 85% 80%)
Use this page as a first benchmark, not as a forever comfort pick.
Move on once the reveal stops surprising you in the same way every run.
If Superman now feels stable, use the practice path to decide whether you should branch into Mario for another clean benchmark or into Batman for darker precision work.
Open the practice pathSuperman gives you bright, high-recognition anchors first. Batman asks for low-brightness precision before most players have learned how Toon Tone punishes subtle contrast misses.
He trains red-vs-blue contrast control, plus the habit of noticing when memory makes both colors cleaner and louder than the target palette.
Players usually push the cape red too hot and the suit blue too vivid at the same time, which makes the result feel iconic but score lower than expected.
Mario is a natural lateral benchmark if you want another clean red-blue page, while Batman is the right next step if you want to test whether your brightness control is actually real.
Faster than a speeding bullet, wears red trunks over blue tights
A strong Superman score does not mean you are done learning. It means you finally have a baseline for what clean two-color contrast feels like in Toon Tone.
Use that baseline to judge whether the next palette is hard because the colors are truly subtler, or because your first benchmark was never as stable as it looked.