Why Texture Is the Flavor You Don't Mention

Ask someone about the best meal of their life and they will reach for flavor words — buttery, smoky, bright, deep. But run the description back slowly and what you usually find underneath is texture: the snap of a perfectly fried skin, the give of a still-warm dumpling, the way a ripe peach releases its juice the moment your teeth break the surface. We remember texture and describe flavor, and that small mistranslation is responsible for a great deal of cooking that almost works but somehow does not.

I want to take this seriously, because it is one of the few aspects of cooking where the gap between casual eaters and serious cooks is mostly a vocabulary problem. The sensations are universal. The words to point at them are not.

Texture is multimodal in the strict sensory sense — it is not one thing your mouth notices but several at once. There is the bite, the resistance a food gives before it yields. There is the crunch or crackle, an acoustic event that your inner ear hears through your jawbone before any sound reaches the room. There is smoothness or grit on the tongue, juiciness, the timing of moisture release, the residue left behind after you swallow. Charles Spence, who runs the Crossmodal Research Laboratory at Oxford and writes about what he calls gastrophysics, has spent two decades showing that these channels are inseparable from what we call flavor — change the sound of a crisp and people report it tastes staler; change the weight of a spoon and the dessert on it tastes denser. Flavor, in the lab, behaves as a composite. Texture is one of its largest components, and the one we are worst at noticing while it is happening.

There is a plausible evolutionary reason for this. Crunch, in particular, appears to function as a freshness signal. A crisp apple, a snapping vegetable, a fresh-shelled nut — these sounds correlate with hydration, intactness, recent harvest. A limp leaf or a soggy crust is a leaf or crust that has been sitting around, that has lost water, that may have started to decompose. Our ancestors did not need to know this consciously; the pleasure response did the work. Which is why a salad with limp lettuce feels not just disappointing but slightly wrong — your nervous system has flagged something the menu did not.

Japanese has the vocabulary problem solved in a way English does not. The word 食感 (shokkan) means, roughly, "the feeling of eating," and it is treated as a separate evaluative dimension from taste. A dish can be praised for its shokkan independently of its flavor. The language that hangs off this concept is dense and specific: mochi-mochi for a chewy elastic bounce, sara-sara for something light and dry-flowing, paki-paki for a brittle clean snap, fuwa-fuwa for soft and airy, shari-shari for a fine granular crunch like fresh-shaved ice or a perfectly ripe pear. The food writer Mariko Furukawa has argued that this vocabulary is not just decorative — it changes what cooks pay attention to, because you cannot easily aim at what you cannot name. A culture that distinguishes mochi-mochi from fuwa-fuwa will produce cooks who distinguish those targets when they cook.

This is also why a serious kaiseki meal, or for that matter a serious tasting menu in any tradition, sequences textures across the meal the way a composer sequences dynamics. Soft into crunchy into soft again, with a palate-refreshing acid or a granular pickle placed where the mouth would otherwise fatigue. A meal of seven soft courses, no matter how well-flavored each one is, exhausts the mouth in a specific way. Texture is what keeps attention awake.

There are several views on this. Western culinary writing — recipe books, restaurant reviews, the whole apparatus — has historically privileged flavor descriptors, with texture appearing mostly as adjective garnish (crispy, tender, juicy) rather than as a structural concern. Japanese tradition, and to a lesser extent some Southeast Asian and Indian writing, treats texture as a primary axis. My view is the harder one: texture is roughly half of the experience of a meal, and any cook who is not thinking about it explicitly is leaving half the dish to luck. A perfectly seasoned bowl of fried rice with one overcooked, mushy grain pocket fails. A beautifully composed salad with one rubbery shrimp fails. The flavors can be flawless and the dish will still not land, because the body has already filed it under "something is wrong here."

This is the great-meal memory test, and I think anyone reading can run it for themselves. Pick the best meal you remember. Sit with it for a moment. The first words that come will be flavor words — but push past them and ask what your mouth was actually doing. The crackle of skin against the give of fat underneath. The way a noodle resisted before it surrendered. The exact moment a tomato released its juice. That is almost always where the memory lives. The flavor is what you reach for to describe it, because that is the vocabulary you have. The texture is what made it the meal.

For more on how attention and context shape taste, see Why Eating Alone Makes Food Taste Worse; for a close-in look at how the simple act of cutting changes the sensory experience itself, see Why Thin Slices Taste Different From Thick Slices. Once you start noticing texture as its own dimension, the dishes you cook begin to change before the recipes do.