Calorie Tracking in Australia: Kilojoules, Labels and Apps Built for Somewhere Else

If you've ever tried to track food in Australia using a mainstream app, you'll know the specific friction. The packet says 1,450 kJ. The app wants calories. The database entry is for an American product with an American serving size. Somewhere in the middle you do arithmetic you shouldn't have to, and eventually you stop bothering.

None of the big trackers were built here, and it shows. Here's how the Australian system actually works, and how to track inside it without fighting your own food labels.

#Australia runs on kilojoules, by law

Australia adopted the metric system in the 1970s, and since the joule is the international unit for energy, it became the standard for food labelling under the Food Standards Code. Every packaged product sold here must list energy in kilojoules per 100g — or per 100ml for liquids — as well as per serving.

That per-100g column is the most useful number on the packet and the most ignored. It's standardised by law, which means it's the only figure you can compare directly across two products. Serving sizes, by contrast, are set by the manufacturer and vary considerably.

#The conversion, and the shortcut

One calorie is about 4.184 kilojoules. So:

• kJ to calories: divide by 4.184 (or just by 4 for a quick estimate)
• Calories to kJ: multiply by 4.184

The "rule of 4" is what most people actually use in the aisle. It overestimates calories slightly, by around 4%, which is well inside the error of everything else in food tracking.

Some worked conversions:

• 8,700 kJ ≈ 2,080 calories
• 2,000 kJ ≈ 478 calories
• 1,000 kJ ≈ 239 calories
• 500 kJ ≈ 120 calories

#What 8,700 kJ actually means

You'll have seen the line in small print at the bottom of menu boards: "The average adult daily energy intake is 8,700 kJ." That's not decoration — it's a legal requirement.

The point of the 8,700 figure is comparison. If a burger is 3,180 kJ, that's about 37% of the reference day in one item — which is a far more useful thing to know than the raw number.

Two caveats worth holding onto. First, 8,700 kJ is a labelling reference for an average adult, not a target for you. Your actual requirement depends on your size, age, sex and activity — a very active teenager might need 12,000 kJ while a sedentary older adult needs considerably less. Second, it's a maintenance figure, not a weight loss one.

#Losing weight in kilojoules

The arithmetic is the same as anywhere; only the unit changes. A deficit of around 2,000 to 2,500 kJ per day below maintenance is commonly cited as producing roughly half a kilogram of loss per week. For many Australian adults that lands somewhere between 5,500 and 7,000 kJ a day, though it varies a lot with body size and activity.

Intakes below about 3,500 kJ per day shouldn't be attempted without medical supervision. And if you want a number that's actually yours rather than an average, a GP or an Accredited Practising Dietitian is the right place to get it.

#Where the apps fall down here

Three specific problems, all of them fixable.

Unit mismatch. The app shows calories, the packet shows kilojoules, and you convert in your head several times a day. Most apps let you switch the display to kJ in settings, and almost nobody does. It's the single highest-value setting change for an Australian user — it means the number you read is the number you enter.

Database mismatch. Search a global database for a common Australian product and you'll often get an American equivalent with a different formulation and a different serving size. Our biscuits, spreads, breads and dairy aren't the same products, and generic entries assume US conventions.

Serving size mismatch. This one is subtle and does real damage. A US entry might assume a serving that bears no relation to what's on your plate. When the database entry and the packet disagree, work from the per-100g column — it's the only figure that's legally standardised.

#Drinks are their own problem

Australian beer glassware is genuinely the most confusing in the English-speaking world, and it defeats database-driven tracking outright. A schooner in Sydney is 425ml. The same word in Adelaide gets you 285ml. A pint in Brisbane is 570ml; in Adelaide it's 425ml.

So an app entry labelled "1 pint of beer" can be wrong by 25% depending on which state you're standing in, before anyone has estimated anything. Roughly: a pot or middy is around 500 kJ, a schooner around 750 kJ, a pint about 1,000 kJ, and a jug around 2,000 kJ, all at full strength.

#The Australian Guide to Healthy Eating

Worth knowing about, because it's the official framework and it takes a different approach entirely. Published by the NHMRC, the AGHE is a plate divided into five food groups by area, with vegetables and grain foods taking the largest shares, followed by fruit, dairy and alternatives, and lean meats and alternatives.

It deals in serves rather than energy — a serve of vegetables, a serve of dairy. That's a deliberate choice: for a lot of people, hitting food group targets is more useful and more sustainable than counting energy at all. If numbers aren't working for you, the AGHE is a legitimate alternative rather than a lesser one.

#A practical setup

If you're tracking in Australia, this is roughly the shortest path to something that works:

• Switch your app to kilojoules. Same unit as every label you'll read.
• Learn your maintenance in kJ, not calories, so you never convert.
• Use the per-100g column when a database entry and a packet disagree.
• Log drinks separately, by volume rather than by the name on the menu.
• Don't fight the database for local foods. If your app can't find a Vegemite serve or a Coles roast chook, describing it is faster than hunting for an entry that doesn't exist.

That last point is the reason voice logging suits an Australian user particularly well. "Two Weet-Bix with milk" or "half a barbecue chook and a serve of chips" doesn't require a database to contain those exact products — it just needs to understand what you said. Which is a smaller problem than maintaining an Australian food database, and a lot smaller than asking you to do unit conversion at breakfast.