Where these recipes come from
Every dish, ingredient and nutrition figure here comes from the Ministry of Food and Drug Safety recipe database for prepared foods. We did not rewrite or summarise the text, and none of the recipes are ours.
What we loaded
1,155 of the 1,156 recipes in the source listing. Data as of 2026-09-05.
Licence: 이용허락범위 제한 없음(공공데이터포털 표기)
What we left out
- One recipe, 비타 오이 물김치 (id 2980), is missing. 식품안전나라 상세 화면이 시스템 오류를 낸다(2026-09-05 확인 · 앞뒤 번호는 정상). Its ingredients and method cannot be fetched, and inventing them was not an option.
- 4 recipes have an empty ingredient field in the source. Their method and nutrition are intact so the page is published, but they cannot be found by ingredient. This is a different thing from a fragment we failed to read, so it is counted separately.
How the ingredient sentence was split
- The source gives ingredients as one free-text block. The dish name sits on the first line and subheadings such as "고명" appear in the middle. Splitting it gave 13,057 ingredient fragments.
- Counts in brackets are kept apart from weights. In "연두부 75g(3/4모)" the weight is 75g and "3/4모" is kept as written.
- Spelling variants are merged only when a preparation word is separated by a space ("다진 마늘" becomes 마늘). 280 fragments were merged that way, and the merged wording is shown on the ingredient page.
- Dried and fresh, low-sodium and regular are not merged. They are different things in a fridge. 대파, 파 and 쪽파 stay separate too.
- That leaves 1,755 ingredients. Ingredients used by only one dish were kept, because those are exactly the awkward leftovers.
- 3 fragment(s) we could not read at all are kept as written on the dish page rather than thrown away.
Why the two boxes score differently
For an ingredient you have too much of we look at its share of the dish by weight. A dish using a spoonful will not empty a box. For a leftover we only look at whether it is used at all, because so few dishes use it that being used is the whole point. Dishes that satisfy both come first.
Where a service key would be needed
The same data sits on Korea's open data portal as an open API (Ministry of Food and Drug Safety, Recipe DB for prepared foods), but fetching all of it needs a service key. The public sample key returns the total count and five records only. So we read it from the ministry's own Food Safety Korea pages, which need no key, and bake it at build time. That is why nothing but the photos leaves your browser when you use this.
What we do not do
- We never substitute a similar ingredient. Only an exact name is added, and near matches are offered for you to pick.
- We do not suggest replacements. The source has no such data, so making it up is inventing.
- We do not rank by taste, difficulty or popularity. The source has no such values.
- Energy and nutrition are shown as printed and no further. We say nothing about diets or illness.