A field guide to global desserts
DessertCat is a slow, patient catalogue of the world's sweets — a single place to learn what something is, where it's from, and how to make it. Independently published, grown recipe by recipe.
i. Why DessertCat exists
Most recipe sites treat desserts as interchangeable — a brownie is a brownie, a flan is a flan, and the box you tick at the supermarket on the way home is what matters. DessertCat starts from a different premise: that every named sweet on the planet has a place it comes from, a story for being there, and a way of being made that is worth getting right.
We don't try to compete with the big recipe networks on volume or on speed-of-publish. We try, instead, to be the place you come when you've heard a name you don't know — dodol, luqaimat, kuzumochi, kremna rezina — and want a real answer to what is that, where is it from, and how do I make it.
ii. Who runs it
DessertCat is a small, independently published project, written and edited by a team of home cooks who travel often and read widely. We are not professional pastry chefs and we don't pretend to be; what we have is the patience to learn one sweet at a time, the willingness to cook each recipe twice before it goes up, and a long-standing interest in the question of where things come from.
The project started from a single shelf of cookbooks that kept asking more questions than they answered — what exactly is dodol, why does topfenstrudel use curd cheese rather than ricotta, why do Argentines call their cream-and-dulce-de-leche frozen dessert cremoso when the rest of the world would call it ice cream. The site grew from there. It is read in over forty countries; we hear most often from cooks abroad looking for their grandmother's sweet from home.
iii. How recipes are tested
Each recipe is cooked at least twice in our own kitchen before publication — once to test the proportions and timings, once to confirm we can reproduce the result the next day from the written page alone. Where a regional dessert traditionally uses an ingredient or technique that's hard to source outside its origin, we say so plainly and suggest the substitution that will get you closest, rather than rewriting the recipe to be "easier" and lose its character.
We don't accept paid placements, sponsored recipes, or affiliate links in the body of a recipe page. The footer occasionally links to cookbooks or kit we think are genuinely worth owning; those are flagged separately and never affect what appears on a recipe.
iv. A note on cultural respect
When we cook food that isn't ours — which, for any catalogue of the world's desserts, is most of it — we try to credit it. That means naming places, naming techniques, naming the people whose work made the recipe what it is. Where there are genuine regional disagreements — is baklava Turkish or Greek? is dodol Indonesian or Malaysian? — we describe the disagreement rather than declare a winner.
We also try, where we can, to use a dessert's native name first and its translation second. Topfenstrudel, not "Austrian quark strudel"; khanom chan, not "layered Thai cake". A name in its own language is the smallest possible respect for where a thing comes from.
If you spot something we've got wrong — a misattribution, an inaccurate history, an ingredient that wouldn't actually be used — please tell us. We will fix it.
v. Where to find us
- Contact — corrections, suggestions, hellos
- RSS feed — one new dessert each week
- All recipes — the full A-to-Z catalogue
- By cuisine — twenty-two traditions, six continents