Frutas Verduras En Ingles

Listing fruits and vegetables in English for practical use

I spent too much time trying to build a simple bilingual reference list for produce. The goal was straightforward: a clean, usable way to map common frutas verduras en ingles translations without the usual clutter that comes with educational content. What I ended up with is just a practical breakdown based on what actually comes up in real situations, not what textbooks assume people need to know. The biggest issue nobody talks about is regional variation. In the US, you'll see "bok choy" spelled three different ways in grocery stores. In the UK, "courgette" replaces "zucchini." "Aubergine" vs "eggplant" is just the start. I learned this the hard way when someone asked me to translate a recipe for "courgettes" and I initially wrote "berinjela" — which is eggplant in Brazilian Portuguese. That mistake cost me a few awkward minutes on a call. The workaround was always to include both terms when the produce has regional synonyms.

Common frutas verduras en ingles categories

Here's how I organize what actually matters in daily use. I separate by how frequently items come up and how often they trip people up.

Leafy greens and alliums

Spinach = espinafre
Kale = couve (the curly kind, not a repolho)
Celery = aipo
Arugula = rúcula
Shallot = chalota (distinct from cebola-roxa, though they overlap)
Leek = alho-poró
Garlic = alho
Onion = cebola People consistently confuse kale with collard greens. In Portuguese, both can map to "couve," but kale is specifically "couve encaracolada" or just "kale" on menus now. I started adding the scientific names on my reference sheets when working with restaurants. It cuts miscommunication down significantly.

Root vegetables and tubers

Carrot = cenoura
Potato = batata
Sweet potato = batata-doce
Beetroot = beterraba
Parsnip = nabo-branco (rare in Brazil, but comes up in recipes)
Turnip = nabo
Radish = rabanete
Ginger = gengibre The parsnip is the one item that doesn't have a clean Portuguese equivalent in most of Brazil. I just leave it as "parsnip" on menus and add a brief description. Trying to force a translation like "cenoura branca" creates more confusion than it solves.

Solanaceous and nightshades

Tomato = tomate
Potato = batata (already listed above)
Eggplant = berinjela (US) / berinjela or beringela (PT)
Courgette / Zucchini = abobrinha
Pepper (bell) = pimentão
Chili pepper = pimenta One detail that trips people up: "pepper" in English covers both sweet bell peppers and hot chilies. In Portuguese, "pimentão" is specifically the sweet variety. If a recipe says "pepper" without context, you need to look at the dish type to determine which one. I keep a note on my reference sheets flagging this ambiguity. It saves time when translating cooking instructions.

Bruccoli family and cruciferous vegetables

Broccoli = brócolis
Cauliflower = couve-flor
Cabbage = repolho
Kohlrabi = couve-rábano (uncommon but growing)
Bok choy = pak choi or chinesinha

Fruits commonly used as vegetables

Avocado = abacate
Avocado also maps to "pêra-bode" in some regions, though that's outdated.
Pumpkin = abóbora (but specifics matter — "butternut" is a different texture)
Butternut squash = abóbora moranga or butternut
Acorn squash = abóbora cabotiá When I first built my reference, I grouped all squashes under "abóbora." That worked until someone needed to distinguish between a butternut and a butternut for a dietary restriction document. The texture and sugar content differ enough that the single translation became a problem. Now I list them separately with the most common Portuguese names used in each market.

Tropical and citrus fruits

Mango = manga
Papaya = mamão
Pineapple = abacaxi
Guava = goiaba
Lime = limão (specifically "limão-tahiti" in most of Brazil)
Lemon = limão (the yellow kind, "limão-siciliano")
Orange = laranja
Grapefruit = toranja The lime situation is a classic pain point. In English, "lime" and "lemon" are distinct. In Portuguese, both are "limão" depending on the region. I always specify the scientific name or the variety when there's ambiguity. It takes one extra word but prevents real mistakes, especially in medical or nutritional contexts.

Berries and stone fruits

Strawberry = morango
Blueberry = mirtilo
Raspberry = framboesa
Blackberry = amora
Peach = pêssego
Nectarine = nectarina
Plum = ameixa
Cherry = cereja

When translations break down completely

Some items don't translate cleanly because they simply don't exist in the target culture. "Fennel" is one example. In Portugal, you might find "funcho," but in much of Brazil, people just call it "funcho" without knowing what it is. I encountered this when a client asked me to translate a shopping list and "fennel bulbs" came up. I wrote "bulbos de funcho" and added a note saying it's the same plant used for its aromatic bulb and seeds. That extra context prevented the buyer from picking the wrong thing at the store. Another problematic case is "watercress." The direct translation is "agrião," but not everyone knows this word outside of culinary circles. I've started including both the translation and a short descriptor for items like this on my sheets. It adds about two seconds per entry but prevents confusion.

A practical way to organize your own list

I don't recommend memorizing these. I recommend building a personal reference that you can actually use. Here's the system that works for me: Start with the items you encounter most often. For most people, that's the produce section of a standard supermarket. Get those first. Add the less common items as you need them. A static master list becomes useless once it gets too long because you stop consulting it.

Group by how you'd encounter them, not alphabetically. A shopping trip doesn't go A to Z. It goes leafy greens, then roots, then whatever's on sale. Organize your list the same way. When you're actually using it in a store or kitchen, you're looking for things in clusters, not alphabetical order. Include the regional variants. If an item has a US and UK name, write both. If it has a PT-BR and PT-PT difference, note it. This takes marginally more effort upfront but saves you from second-guessing yourself later.

Keep it in a format you can access offline. A phone note, a printed card, whatever works. The moment it's locked behind an app or requires internet, you'll lose access at the worst possible time — usually when you're standing in a grocery store trying to figure out what "nopal" means. If you're building this for work, like menu translation or product labeling, I'd recommend adding a column for the Portuguese-speaking region you're targeting. Brazil and Portugal differ enough on produce names that a single list will cause issues. Two columns, five extra minutes of setup, and you avoid a whole category of mistakes.