FODMAP apps and lists disagree because they are rarely answering the same question. One entry may be a laboratory-tested serving of a specific food, another a guess from an ingredient list, another an older value copied from a list that has since moved on. Before trusting either color, check five things: the serving, the food, the cutoff, the source and the gaps.
If you have two apps open, two lists that contradict each other, or a scanner that says red for a product your dietitian said was fine, you are not doing it wrong. Researchers who compared popular US low FODMAP lists found that they often disagreed, and the people who built the diet have said openly that FODMAP levels vary with ingredients and processing (McMeans 2017; Monash FODMAP blog).
This guide is a troubleshooting worksheet, not a verdict on any app. It walks through the five checks in order, uses clearly labeled hypothetical examples (no invented lab values), and ends with what to do when a conflict will not resolve. If you are choosing a tool rather than untangling a conflict, see our comparison of low FODMAP apps or the side-by-side comparison with the Monash app instead.
Why do FODMAP apps and lists disagree in the first place?
A 2017 comparison of three popular US low FODMAP lists, all downloaded in May 2015, found 332 unique foods between them, and 50.9% appeared on only one list. Among the 162 foods listed more than once, 35 (21.3%) were in outright disagreement. The lists differed in coverage, detail and age before any app was involved (McMeans 2017).
That small study is the closest thing to a baseline for the problem. Its authors defined disagreement narrowly: one list fully restricting a food while another allowed it fully or partly. Even so, more than one in five shared foods fell into that bucket. They also noted that none of the three lists gave guidance on combining foods, which is a separate source of confusion we cover later and in the guide to FODMAP stacking examples.
The same pattern shows up on Reddit. In r/FODMAPS, one person tested several scanning apps against foods they already believed were safe and was surprised by how far the apps differed, including on an ingredient such as sugar beet fiber that did not appear in the official app at all (r/FODMAPS scanning apps thread). Another thread asked about a large gap between two testing programs for canned corn, and a reply from the team behind a low FODMAP education site pointed out that nobody can tell which corn product, variety or processing was tested versus what is in your cupboard (r/FODMAPS canned corn thread). If you are choosing between the two popular US shopping scanners, see Fig vs Spoonful.
Three structural reasons sit underneath nearly every complaint:
- The data are not one dataset. Laboratory programs, crowd-sourced barcode databases, clinic handouts and websites each hold different entries produced in different ways.
- The diet is built on thresholds, not labels. A food is low FODMAP up to a certain amount, so any source that drops the amount can flip a color.
- Foods are not constant. A named food is really a population of samples that vary by variety, ripeness, region, storage and processing.
The five checks below turn those three ideas into a routine you can run in about a minute per food.
How do I check a FODMAP disagreement? The five-check worksheet
When two sources conflict, run five checks in a fixed order: serving size, food match, cutoff and stacking, source and date, and missing data. Most conflicts dissolve at the first or second check. The table gives the question to ask at each step and the most common culprit, so you can see where a conflict is coming from.
| Check | Question to ask | Typical cause of a conflict |
|---|---|---|
| 1. Tested serving vs inference | Is each rating tied to a stated serving, and was it tested or guessed from an ingredient list? | One app shows a tested small serving; the other flags the ingredient regardless of amount |
| 2. Food identity and match | Are both entries the same variety, ripeness, part, preparation and regional product? | Ripe vs unripe, head vs stalk, firm vs silken, UK vs US product |
| 3. Cutoffs and stacking | Do both sources use the same cutoff values, and are you eating this alongside other servings? | Slightly different thresholds; a rating given for a single food in isolation |
| 4. Data source and date | Who produced the number, in which country, and when? | An old list copied forward; a re-tested food; a different country |
| 5. Missing data | Is a blank being shown as low, or as unknown? | A product with no ingredient list or an unrecognized ingredient scored green |
Write the five questions on a sticky note if it helps. The sections below take each in turn.
Check 1: is the rating a tested serving or an ingredient-list guess?
A tested serving comes from laboratory measurement of the FODMAPs in a defined amount of food. An ingredient-list estimate reads the names on a label and applies rules. They are different kinds of answer, so they can legitimately disagree. Monash says scanning apps give an estimate that is less accurate than laboratory testing (Monash FODMAP blog).
The reason is structural. Quantifying FODMAPs takes chromatography and enzymatic assays on a prepared sample, which is how the underlying food composition tables were built (Muir 2009; Muir 2007). Monash describes its process as sourcing multiple independent samples, freeze-drying and milling them, extracting the carbohydrates and measuring them by liquid chromatography, with a dietitian then setting the green, amber and red serving sizes (Monash FODMAP lab blog). A barcode scanner does none of that. It looks a product up and matches words.
Researchers who used the ingredient-list method deliberately show how much remains unresolved by it. In a Portuguese study, 436 pre-packaged gluten-free and lactose-free products were classified from their ingredient lists against Monash cutoffs and serving sizes: 53.0% came out low, 24.3% high and 22.7% unknown (Barreirinhas 2025). The authors concluded that labels should be more specific to allow more accurate dosing. Nearly a quarter of products could not be classified at all, which is exactly the gap a scanner has to fill with a color.
A hypothetical illustration (invented for this guide, with no measured values). Imagine a jar of tomato sauce with onion powder on the label. App A, a scanner, sees "onion powder" and shows red. App B holds a laboratory-tested entry for a different brand of tomato sauce and shows green at a quarter-cup serving. Both are behaving as designed. App A answered "does a high FODMAP ingredient appear?" App B answered "was this sauce, at this serving, tested?" The conflict is not about which app is smarter. It is that one question has a yes-or-no answer and the other is a dose question.
What to do with this check:
- Find the serving size on both entries. If one rating has no serving attached, it is carrying less information.
- Ask whether the entry is a tested food or a parsed label. Scanners say so in their small print; official lab-based apps describe their testing.
- Treat a certification logo differently from a scan. A logo means the finished product was assessed against thresholds; a scan means an ingredient list was matched to rules. For a deeper look at what scanners can and cannot see, read our guide to low FODMAP barcode scanner apps.
Check 2: are both entries really the same food?
A named food is a range of samples, not a single value. FODMAP content shifts with variety, ripeness, the part of the plant, processing and the product's regional recipe. Banana is the best-known case: Monash re-tested it after people reported discomfort with ripe fruit and updated the app, noting that growing and storage conditions can change fructan levels (Monash banana update). Sourdough is a classic case of conflicting ratings; see is sourdough bread low FODMAP?.
Several sub-causes live here, and each has a documented basis.
Ripeness and storage. FODMAP Friendly lists ripeness, storage, location, variety and processing as factors that move FODMAP content, noting that ripe bananas contain more fructans than unripe ones (FODMAP Friendly). Monash's banana article says published work links plant fructan accumulation to stressors such as cold and drought, and that banana fructan content rises under cold storage and ripening (Monash banana update). A list written before such a re-test, or an app that has not picked up the update, will show a different result without anyone being careless.
Part of the food. A dietitian-run database notes that FODMAP content differs by part: the head of broccoli versus the stalk, or the green versus the white of a leek (Fodmapedia). A list that says "broccoli" with no part and a list that separates them are not contradicting each other. They are describing different things.
Variety. FODMAP Friendly gives the example that oyster mushrooms are lower in mannitol than shiitake (FODMAP Friendly). Even within a food group of processed grains, laboratory analysis found a wide spread: fructan per portion as eaten ran from 0.6 g in dark rye bread down to 0.07 g in spelt bread, and from 0.96 g in wheat-free muesli down to 0.11 g in oats (Biesiekierski 2011). "Bread" or "muesli" is not one thing.
Processing. Monash gives firm versus silken tofu as the textbook case: the ingredient lists are near identical, but pressing and straining remove FODMAP-containing liquid, so the two forms have very different ratings (Monash FODMAP blog). In a laboratory study of 35 plant-based foods, the processing steps that most reduced FODMAP content were pickling and canning (Tuck 2018). Canned and dried versions of the same ingredient often cannot be treated as the raw one.
Country and product formulation. The review that introduced the cutoffs notes that processing and ingredients vary between countries, and that in the USA the use of high fructose corn syrup may contribute to higher excess fructose in some processed foods (Varney 2017). The authors of the review of the diet's controversies stress that food composition data need to be current and local (Hill 2017). A UK reader who looks up a US product, or the reverse, can see a mismatch that is real.
The r/FODMAPS thread above also raises a practical version of this: a manufacturer can change a recipe while keeping the same barcode, so a stored entry may no longer describe what is in your hand (r/FODMAPS scanning apps thread). Monash makes the same point, adding that in Australia many scanner databases are crowd-sourced or third party and not regulated, which is why ingredients can be missed after a reformulation (Monash FODMAP blog).
A hypothetical illustration (invented, no values). One list says "avocado: avoid." A second says "avocado: small serving." A third says "guacamole: fine." The first is food-level with no serving, the second is food-level with a serving, and the third is a different prepared food. All three can be defensible. Match the entry to the exact thing you are eating: the part, the ripeness, the preparation, the brand and the country.
Check 3: do the apps use the same cutoffs, and are you stacking servings?
Both major testing programs classify foods against FODMAP cutoffs, but a dietitian-authored comparison reports that Monash and FODMAP Friendly use slightly different cutoff values in some cases. Separately, a rating is for one food in isolation, so several fine servings together can still exceed what your gut tolerates.
The cutoffs themselves have a documented basis. They were derived from FODMAP levels in typical servings of foods that commonly trigger symptoms and of foods that are generally well tolerated, and their reliability has been tested in dietary studies (Varney 2017). The controlled feeding trial that showed the diet reduces IBS symptoms aimed for less than 0.5 g of FODMAPs per meal on the low FODMAP diet (Halmos 2014). So the cutoffs are about dose across a meal, not a verdict on a food.
FODMAP Everyday, a dietitian-led site, compares the two programs and says their cutoffs are slightly different in places, with the biggest dissimilarity for lactose, and that this partly explains why entries for the same food differ between the apps (FODMAP Everyday). We cite that as a secondary summary rather than quote its numbers. If you want to compare precisely, read each program's own published thresholds.
A parallel Reddit thread, started by the team behind a low FODMAP education site, makes a point that comes up often in the community: many people use both apps, and one commenter noted that no testing body will exactly match their own responses to food, so more information helps them judge risk (r/FODMAPS Monash and FODMAP Friendly thread). That is lived experience rather than evidence, but it matches the dose logic.
Dose also explains the stacking problem. Polyols are dose dependent: in a randomized, double-blind study, 10 g challenges of sorbitol or mannitol increased gut symptoms in people with IBS, regardless of how well they absorbed the polyol (Yao 2014). The same logic applies across a meal. An app that rates each ingredient green cannot tell you that three green servings of the same FODMAP subgroup, eaten together, may add up. That is not a disagreement between apps. It is a limit of any single-food rating, and our guide to FODMAP stacking examples walks through realistic combinations.
Check 4: who produced the number, and when?
The source and date matter because FODMAP knowledge keeps moving. Monash says it re-tests foods from time to time because agricultural and environmental factors change FODMAP levels and its methods have become more sensitive (Monash banana update). It also warns that free aggregator apps may keep an old rating after re-testing (Monash FODMAP blog).
Three source types are worth telling apart.
Primary laboratory data. Monash states that it tests three independent brands for each processed food and collects fruit and vegetable samples from ten stores, five supermarkets and five greengrocers (Monash FODMAP blog). FODMAP Friendly says it uses an independent, accredited laboratory, prepares composite samples, and compares results with its own thresholds (FODMAP Friendly). Both are primary sources, which is why two entries from them can both be valid yet differ.
Aggregators and lists. Monash describes free apps and AI tools as often scraping data from websites, blogs and older papers, which can leave outdated or conflicting values (Monash FODMAP blog). Fodmapedia's own advice is to avoid any list older than a year and to prefer lists that give weights and break foods into parts (Fodmapedia). Those are the opinions of the sources, not a measured standard, but they point at the same question: what is the date, and what did the list start from?
Handouts. Monash notes that clinic handouts often use a simple low-versus-high split, whereas the real system is thresholds, so a handout saying a food is high may be hiding a green serving size (Monash FODMAP blog). Printouts also age. A printed list from a few years ago is a fixed snapshot of a moving field.
A fourth item sits in the same family: a re-test. When Monash re-tested banana, the app changed (Monash banana update). Two sources that both once agreed can come apart simply because one updated and the other did not. Monash states that it cannot comment on discrepancies between its app and other public sources (Monash FODMAP blog), so the practical move is to check dates and sources rather than wait for an explanation.
A hypothetical illustration (invented, no values). Source P is a printed handout from several years ago that rates a fruit red. Source Q is an app entry updated this year that gives a small green serving. Source P is not lying and Source Q is not rogue. P is an old snapshot and Q is a newer, serving-based entry. When dates differ, the newer, serving-based, lab-based entry should usually carry more weight, with the caveat that a rating still does not know your own tolerance.
Check 5: is a gap being shown as low?
The fifth check is the most dangerous because it hides inside a green light. If a tool cannot find a product, cannot read its ingredient list, or does not recognize an ingredient, the honest output is "unknown", not "low". A 2025 study found 22.7% of pre-packaged products could not be classified from their ingredient lists (Barreirinhas 2025).
This is where two apps can disagree for a reason that has nothing to do with FODMAP science. One shows gray or "no data" for a product; another quietly treats an unmatched ingredient as acceptable and lights it up green. The 436-product study above shows how often unknowns occur even when researchers go looking for them. The Reddit thread mentioned earlier makes the practical side vivid: an ingredient absent from the official app, with online searches giving conflicting answers, left the person with a best guess and a small-serving assumption rather than a fact (r/FODMAPS scanning apps thread).
The risks are not symmetric. A false green may produce symptoms and muddy a reintroduction test. A false red quietly narrows your diet. Both are worse than an honest "I do not know". So a good habit is to read the app's treatment of gaps before you read its colors:
- Does it have an explicit "unknown" or "no data" state? If it never shows one, it is hiding gaps.
- Does a missing ingredient count as low? Look in the app's help or about page.
- Does a blank product screen give you a color anyway? If so, ignore that color.
For transparency, here is how Clairop handles this, as documented on our own comparison page and method page: FODMAP values come from published food-composition papers, each cited, and ingredients without a value are shown as no data, never as low. We are not affiliated with Monash University, and nothing here is a claim that one approach replaces another; a tool that shows its gaps simply gives you more to check.
What do I do when the disagreement will not resolve?
When all five checks leave a genuine conflict, treat the food as uncertain, not as safe or forbidden. Prefer the laboratory-based, serving-specific, current and local entry, keep portions modest outside stacked meals, and take the question to a dietitian trained in the diet. Structured reintroduction is the tool that settles individual tolerance.
A practical order of operations:
- Pin the serving. Write down the amount each source is talking about. Often the apps agree once amounts are aligned.
- Pin the food. Confirm variety, part, ripeness, preparation, brand and country. If you cannot match them, say so and move on.
- Prefer the stronger source. Laboratory-tested, serving-based and recent beats list-derived, undated and unspecific. This is a ranking of evidence, not a ranking of brands.
- Do not stack a doubtful food. If you are unsure, do not combine it with other items from the same FODMAP subgroup in the same meal.
- Decide what the uncertainty costs. If the food is rarely eaten, skip it for now. If it is a staple, plan to test it properly rather than guess.
For the last point, the framework is reintroduction. The low FODMAP diet is described in the clinical literature as three stages: restriction, reintroduction and personalization, often delivered across at least two dietitian appointments (Whelan 2018). Reintroduction is the step designed to answer whether a specific food, at a specific amount, bothers you. Our guide to how to reintroduce foods after the low FODMAP diet walks through it, and the diet itself is meant to be temporary, not a permanent list of red foods.
One Reddit commenter in the scanning thread put the beginner's dilemma well: during the elimination and reintroduction phases, pre-packaged foods add variables, so keeping choices simple and then using scanners later, once your own triggers are known, can work better. That is community advice, not a rule, and your dietitian may see it differently. It does fit the logic that a controlled test is only as clean as the foods in it.
Does a disagreement mean the Monash app is wrong?
No. A disagreement tells you two sources differ, not which one is wrong. Monash states that its app data are analyzed in its own laboratory under published methods, with sampling to FSANZ guidelines, and it declines to comment on discrepancies with other sources. A difference more often reflects scope, serving, date or method than an error.
It helps to separate three claims that get blended on forums.
"The lab data are rigorous." Both major programs describe independent sampling and laboratory methods. That is a reason to treat their entries as the strongest available evidence for the foods they cover (Monash FODMAP blog; FODMAP Friendly).
"The lab data cover everything I eat." They do not. A sample of three brands cannot be your brand, and a testing program cannot cover every regional product. In the r/FODMAPS thread, a commenter noted that few UK products appear in the official app unless the maker has taken part in certification, which pushes people toward scanners to fill the gap (r/FODMAPS scanning apps thread). That is a coverage issue, and the apps' disagreement partly reflects each trying to fill it differently.
"A green light means I will be fine." Hill and colleagues warn that suboptimal dietary advice and inaccurate FODMAP composition data can lead to disappointing responses to the diet (Hill 2017). A green rating also does not capture your threshold, other triggers, or the fact that IBS symptoms have causes beyond FODMAPs. If symptoms persist despite careful choices, our guide on what to do if low FODMAP does not work covers the next steps.
The takeaway is not to pick a team. A community comment sums up a sensible stance: neither source is necessarily wrong, they are guidelines, and if a reaction bothers you, adjust to suit yourself. Treat each source as strong evidence about a sample, and your own response as the final test.
Are FODMAP lists and apps reliable enough to use?
Yes, if you use them for what they do well. Laboratory-based, serving-specific entries are the most reliable guide to typical FODMAP content, and the cutoffs have been tested in dietary studies. They are less reliable for untested products, undated lists and anything that drops serving size. They never replace your own reintroduction results.
Here is a rough ladder of reliability, from stronger to weaker. It is a reasoning aid, not a measured scale, and the order reflects how directly each source measures the thing you care about.
| Source type | What it tells you | Main weakness |
|---|---|---|
| Laboratory-tested food with stated serving | Typical FODMAP content at a defined amount | A sample, not your exact item; date and region matter |
| Certified finished product | The finished product was assessed against thresholds | Only covers participating products; thresholds differ by program |
| Dietitian-curated list with weights and dates | Summarized lab data in usable form | Only as current as its last update |
| Ingredient-list scanner | Whether known high FODMAP ingredients appear | Cannot see amounts or processing; may be outdated or incomplete |
| Undated list, handout or AI summary | A rough prompt | No serving, no date, no lab source; Monash warns these can be outdated or conflicting |
Two things keep that table honest. First, ranking a source higher does not make it infallible. Laboratory values describe samples, and the cutoffs have been tested in dietary studies, but individual tolerance still varies (Varney 2017). Second, ranking a source lower does not make it useless. A scanner is a reasonable filter at six o'clock in a supermarket aisle, as long as you remember it is an estimate and you check the packet when it matters.
If a source shows its sample, serving and date, that transparency is itself a reliability signal. If it shows only a color, ask what is behind the color.
Why does my own body disagree with the app?
Sometimes the apps agree with each other and still disagree with how you feel. FODMAP ratings describe typical samples at stated servings. Your symptoms also depend on other foods in the meal, other triggers such as fat or caffeine, stress, sleep, hormones and your own threshold. A green food can still bother you, and a red one may not.
Monash itself notes that if you tolerate a food well there is no need to remove it, and that the diet only needs to be as strict as your symptoms require (Monash banana update). A related Reddit thread includes a plain statement of the same idea from someone who is more sensitive to fructans in bread than most people and treats their own red line as lower than the app's (r/FODMAPS Monash and FODMAP Friendly thread).
A simple way to turn that into evidence is to keep a log of what you ate, the amount, and what happened over the following hours and days. Paper works. So does an app such as Clairop, where you can log meals by tap, voice or a typed sentence. The point is to replace "the app said red" with "this food at this amount did or did not bother me on these dates". That record is also what you take to a dietitian, and our method page explains how Clairop treats such patterns, including requiring a minimum number of meals before showing anything.
Clairop logs meals, symptoms and stool in seconds, then looks for the foods your gut reacts to, including reactions that land days later.
For red-flag symptoms, do not try to sort them out by comparing apps. Blood in the stool, unexplained weight loss, fever, symptoms that wake you at night, signs of anemia, symptoms that start after 50, or a family history of bowel cancer or inflammatory bowel disease all need a doctor promptly. A food rating cannot tell you what is causing those.
Myths about conflicting FODMAP information
Several beliefs make FODMAP disagreements more stressful than they need to be. Each can be answered from the sources above: that one app must be right, that red means never, that newer is always better, and that a green light is a guarantee. Sorting them out lowers the stakes of any single conflict.
Myth: one of the two apps must be wrong. Two valid tests can differ because of variety, ripeness, region, storage, processing and slightly different cutoffs (FODMAP Everyday; FODMAP Friendly). Variation is a property of food, not necessarily an error.
Myth: red means never eat it. The low FODMAP system is about serving size. Monash's own scanner article gives examples of foods that are fine at small servings and problematic at larger ones, which is why a single color with no amount can mislead (Monash FODMAP blog).
Myth: the newest source is always the best. Newer is better only when it is also serving-specific, sourced and local. A new aggregator page with no lab behind it is still an aggregator.
Myth: if the label has no high FODMAP ingredient, it is low FODMAP. Added fibers, polyols and quantity can matter. A 10 g challenge of sorbitol or mannitol increased symptoms in people with IBS in a controlled study (Yao 2014), and labels rarely say how much is present.
Myth: I should avoid a food until the apps agree. Waiting for perfect agreement can lead to needless restriction, which is a real cost of the diet. Structured reintroduction exists precisely because lists cannot settle your personal tolerance.
Myth: an AI chatbot can referee between apps. Monash points out that AI models are trained on existing text, cannot see hidden FODMAPs, and may not know, for example, why firm tofu differs from silken tofu (Monash FODMAP blog). An unsourced answer is another opinion to check, not a tie-breaker.
When should I get a dietitian or doctor involved?
Involve a dietitian trained in the low FODMAP diet if conflicts are driving you to cut out many foods, if you are unsure how to reintroduce, or if you feel anxious about eating. Involve a doctor promptly for red-flag symptoms. The diet is intended as a short, structured process, not a permanent restriction.
Concrete signs it is time to ask for help:
- You have cut out more foods than the diet requires because of conflicting information.
- You cannot tell whether symptoms are improving, and your records are muddled by uncertain foods.
- You are anxious or distressed around food, or finding eating increasingly restrictive.
- You have not had a proper reintroduction and are still in the strict phase after several weeks.
- You have any red-flag symptom listed above.
A trained dietitian can settle many conflicts on the spot, because they know which sources they trust for which foods, and they can set up reintroduction so your own response becomes the tie-breaker. The clinical review of the diet describes it as a three-stage process with practical guidance for each stage (Whelan 2018). That support is worth more than any extra app.
The short version
FODMAP apps disagree because their entries come from different kinds of evidence, about slightly different foods, at different servings, under different cutoffs, from different years, and sometimes with gaps painted green. Run the five checks, prefer the tested, serving-specific and current entry, treat what remains as uncertain, and let reintroduction answer the rest.
- Serving: is each rating tied to a tested serving, or guessed from a label?
- Food: same variety, part, ripeness, preparation, brand and country?
- Cutoffs and stacking: same thresholds, and are you combining servings?
- Source and date: who tested it, where and when?
- Gaps: is "no data" being shown as low?
If you want a tool comparison rather than a tie-breaker, see our page on low FODMAP apps, the side-by-side comparison with the Monash app and the guide to low FODMAP barcode scanner apps. When a food keeps causing doubt, reintroduce it deliberately and record the result, because that is the only test that is about you.




