General guidance, not medical or dietary advice. Kidney disease varies by stage and treatment — follow the daily limits your nephrologist or renal dietitian sets. Full disclaimer.
Eating for kidney disease means holding potassium, phosphorus and sodium inside limits your care team sets. Any one dish is easy; twenty-one meals a week that all land inside the caps is the hard part.
This is a complete 7-day example week from real recipes here. Every dish carries at most 600 mg of potassium and 300 mg of phosphorus per serving, verified against USDA data — not estimated.
Potassium (K) and phosphorus (P) are per serving and verified against USDA data; sodium (Na) is a per-serving estimate. Tap any dish for the full recipe and complete nutrition.
Most renal meal plans list dishes with no numbers at all. Every recipe here is grounded against a USDA-derived database, and a dish whose potassium or phosphorus can’t be verified is never shown as kidney-friendly. Sodium is a per-serving estimate, totalled per day. Common clinician targets run near 2,000 mg potassium, 800–1,000 mg phosphorus and 1,500 mg sodium a day — but use your care team’s limits, not these.
Repeats are a feature: one breakfast twice, one dinner double-batched. Most excess phosphorus comes from additives in processed meat, colas and packaged baked goods, which absorb far more completely than the phosphorus in whole food. Leaching works too — cut root vegetables small, boil them in plenty of water, discard it.
Set your own potassium, phosphorus and sodium caps in the kidney-friendly profile: every generated meal, swap and side respects them, each day totals against your numbers, and one tap rewrites anything that doesn’t fit.
No — organizational help, not medical advice. Follow the limits your nephrologist or renal dietitian sets.
At most 600 mg potassium and 300 mg phosphorus per serving, grounded against USDA data. A dish that can’t be verified never qualifies.
Yes — set your own limits and generate a week to them. This page is one example of what those constraints produce.
It uses only verified recipes and repeats rather than padding with unverified ones. Batch-cooking a dish whose numbers you already trust is good renal practice anyway.