Collecting texture and material, not just color

Pull up any moodboard app and sort by what people actually save, and you'll find the same thing over and over: color swatches, layout screenshots, a palette of five hex codes pretending to summarize a whole aesthetic. Almost nobody saves a close-up of a scratched brass handle or a photo that captures how linen creases when you fold it. Texture gets flattened out before it ever makes it onto the board.

That's a real gap, not a minor omission. In interiors, product design, fashion, even interface design, material is doing as much work as color — sometimes more. A room reads as "warm" because of nubby wool and raw plaster, not because someone picked a beige. A product feels premium because of the drag of a matte-anodized dial, not its Pantone. If your references only capture how something looks in a flat, evenly lit photo, you're collecting half the story and building from it anyway.

Color is the part that photographs well

The reason color dominates moodboards isn't that it matters more — it's that it survives compression. A JPEG can carry hue and value across any screen, any lighting, any device, with almost no loss. Texture can't. Grain, weight, sheen, the give of a surface under a fingertip — all of that depends on light angle, scale, and context that a thumbnail throws away. So people default to what's easy to capture, and the board quietly becomes a color study wearing a moodboard's clothes.

Once you notice this, you start seeing it everywhere. A "coastal" board that's all pale blues and no rope, no salt-worn wood, no sun-bleached canvas. A "brutalist" UI board that borrowed the grays but none of the poured-concrete roughness that made the original buildings feel the way they did. The color got copied. The material — the actual reason the thing felt a certain way — got left behind.

Notice material the way you'd notice a smell

Material qualities don't announce themselves in a glance the way color does. You have to go looking. When something catches your eye, ask a second question after "what color is this": what would it feel like to touch? Would it be cool or warm against your hand? Does it have give, or is it rigid? Is the surface interrupted — scratched, pilled, sanded — or is it factory-smooth? These questions force you to read the photo for information that isn't strictly visual, which is exactly the information a flat screenshot tends to hide.

This matters even in categories that seem purely visual. A UI shadow reads as "soft" or "hard" because it's implying a material property — how far a surface sits above the one behind it, how light wraps around its edge. Skeuomorphic design leaned on this directly; flat design still borrows it constantly through elevation and blur. If you're collecting interface references and only tagging them by color and layout, you're missing the cue that's doing the most emotional work.

Collect the close-up and the context shot together

A single texture photo rarely tells you enough on its own. A macro shot of woven fabric shows you the weave but not the scale — is this a chunky throw blanket or a fine suiting wool? Save the close-up for the detail and a wider shot for scale and behavior: how the material drapes, how it catches light across a whole surface, how it sits next to other materials in a real space. Scale is one of the things that gets lost fastest when you're only saving pretty crops, and it's one of the first things a client or teammate will ask about.

The same logic applies to product and packaging work. A tight shot of a brushed-aluminum edge tells you about the finish. A shot of someone holding the object tells you about weight, proportion, and how the material behaves under a thumb. Neither photo alone is a material reference — together they are.

Chase behavior, not just appearance

The most useful material references capture a material doing something: fabric creasing at a knee, paint cracking at a corner, water beading on a waxed surface, leather darkening where hands have touched it for years. That's behavior, and behavior is what a specifier or a fabricator or a developer actually needs to know. "This should look like aged brass" is a color instruction. "This should patina and streak the way aged brass does when it's handled" is a material instruction, and it's the one that survives translation into a real object or interface.

When you're browsing and you hit a photo that shows a material mid-transformation — worn, weathered, stressed, reacting to light or moisture — save it even if the color isn't quite right. You can correct color later with almost no effort. You can't fake behavior after the fact; you either specified it up front or you didn't.

A color is a fact you can read off a screen. A material is a promise about how something will behave in someone's hands — and no hex code has ever kept that promise.

Build a small vocabulary instead of a big pile

Rather than saving every interesting texture you pass, build a short list of material words that matter for the project — say, "raw," "worn," "cool-to-the-touch," "soft-edged" — and only save references that clearly speak to one of them. This does two things. It stops the board from becoming a texture scrapbook with no throughline, and it gives you language you can actually hand to someone else. "I want it to feel raw, like this" is a brief. A folder of forty unlabeled close-ups is homework.

Group by that vocabulary instead of by material type. A cluster labeled "worn" might mix weathered wood, cracked leather, and a chipped ceramic glaze — different materials, same behavior, and that's the point. It tells you what quality you're actually chasing across the whole project, not just which materials happen to be trendy this season.

The same problem shows up in every discipline

In interiors, it's the difference between a board that says "warm neutrals" and one that actually shows the nub of a boucle chair against a smooth plaster wall — the contrast is what reads as warm, not the color alone. In fashion, a flat lay of fabric swatches tells you almost nothing about drape; a photo of the same fabric moving on a body tells you whether it's structured enough to hold a shape or soft enough to fall into one. In product design, the difference between "matte" and "soft-touch matte" is the difference between a surface that looks non-reflective and one that also feels slightly rubbery under a thumb — and only one of those descriptions is useful to whoever specs the finish.

Interface design is the least obvious case but it's not exempt. Depth, elevation, and surface hierarchy are all material metaphors borrowed from the physical world — a card "lifts" off the background, a button has a subtle "press," a glass panel is "frosted." Collecting references for that kind of UI work means paying attention to how light, blur, and shadow behave in physical material photography, not just other people's interface screenshots. A photograph of frosted glass or brushed metal will teach you more about a convincing depth effect than a hundred screenshots of other apps that already flattened the idea once.

Sanity-check the reference before you trust it

Photos lie about material more than they lie about anything else. Studio lighting can make cheap laminate look like stone. A wide-angle lens can make a thin plaster skim coat look like a thick, hand-troweled wall. Before a texture reference goes into a real brief, ask where it came from — is this a manufacturer's hero shot designed to flatter the material, or a candid photo of it in use? The second kind is worth more, even if it's less polished, because it hasn't been lit and cropped to hide the material's actual limits.

If you can, pair every glossy reference with a rougher one: a showroom photo next to a photo of the same material after six months of actual wear. The gap between those two tells you more about whether a material will hold up to the brief than either photo does on its own — and it stops you from specifying something that only ever looked good under a stylist's lighting rig.