Browse the Palette, Not the Pattern: A Blog Post on plaid-patterns.com/plaid-random-browse

If the single-seed page is about committing to one plaid, the Plaid Random Browse page is about something earlier and stranger in the design process: finding out what colors you're in the mood for.

It looks, at first, like a contact sheet. Plaid after plaid, stacked down the page. Pattern #499375885 in lime and slate. Pattern #15946942501 in pink and magenta. Pattern #41154183858 in mint and coral. Each one labeled with a long seed number that, on its own, tells you nothing.

But look at the URL behind each thumbnail and the trick of the page becomes obvious. Every plaid has two things baked into it: a seed= and a colors= parameter — a four-color hex string. The seed controls the geometry. The colors control the mood. And what you're actually browsing isn't really plaids. You're browsing palettes, with plaids as the preview.

The page is a palette flea market

Most color tools — Color Hunt, Colors, Adobe's whole color wheel apparatus — show you palettes as five neat swatches in a row. Which is honest, but also kind of useless. Five swatches in a row tell you almost nothing about how those colors will feel once they're crashing into each other across a real surface.

The browse page solves that by skipping the abstraction. Instead of swatches, you see the palette already deployed — woven into stripes, intersecting at the diagonals, sitting next to itself in different proportions. You can tell at a glance whether a palette is going to read as sweet or sour, calm or loud, vintage or sci-fi. The plaid is the load test.

So the workflow becomes:

1. Scroll the page like a flea market table.
2. Stop when a color combination grabs you. Not because the pattern is right — it might not be — but because the palette is.
3. Click through.
4. Now generate variations on that palette: same four colors, new seeds, new stripe arrangements, new symmetries, until the pattern catches up to the palette.

Why this order matters

There's a real argument hiding inside this UI. It's saying: colors are the decision, geometry is the consequence.

That tracks with how designers actually work. You almost never start a project thinking "I want stripes of width 12px alternating with stripes of width 4px." You start thinking "I want this to feel like a summer linen" or "I want it to feel like a 70s ski lodge." Those are palette thoughts, not pattern thoughts. Once the palette is locked, the geometry can be rolled like dice until something lands.

The browse page mirrors that order exactly. It puts color discovery on the outside loop — slow, deliberate, scroll-driven — and shoves pattern variation onto the inside loop, where it belongs, as cheap fast rerolls.

The seed numbers stop mattering, and that's the point

Pattern #87136227822 is a real, specific, byte-for-byte reproducible plaid. So is Pattern #14103bf02a71… etc. They have addresses. But once you're using this page the way it wants to be used, you stop caring about the seed and start caring about the colors= half of the URL.

That's a quiet design move worth noticing. The page surfaces the less important identifier (the seed, which controls the part you'll happily re-roll) and tucks the more important identifier (the four hex codes, which carry the actual taste) into the link. You browse with your eyes; the URL carries the palette for you when you click through.

What designers actually get out of this

For a designer or pattern seeker, the page does three jobs at once:

• A mood board you didn't have to assemble. Each thumbnail is a palette in context, not in the abstract.
• A taste filter that's faster than a color picker. Saying "no" to a palette takes a quarter-second of scrolling. Saying "yes" takes a click.
• A handoff to a variation engine. Once you pick the palette, the same generator that made the thumbnail will keep making more — same colors, new geometries — until the pattern matches the palette's promise.

It's the same generative-discovery loop as the single-seed page, but moved up a level. There, you were discovering plaids. Here, you're discovering palettes through plaids — which is a much more useful thing to discover, because the palette is the part you'll carry into the rest of the project anyway.

The honest version of how color choice works

Nobody actually picks a palette by reasoning about hue, saturation, and value. They pick it by seeing a combination in the wild and going, yeah, that one. This page is just being honest about that. It puts hundreds of palettes in the wild, lets you scroll until one snags you, and then says: okay, now let's make plaids out of it until you're happy.

No sliders. No color theory homework. No twelve-tab Figma file of options. Just: scroll, recognize, click, reroll.

That's not a worse way to design. It might be the way design was always quietly working, finally given a UI that matches.