Reconcile Salt-Gram and Sodium-Milligram Labels at the Weight Eaten — Free
A jar can list salt in grams while a carton lists sodium in milligrams. Add those printed numbers directly and the total has no meaning. This receipt makes the label convention and portion mass visible before combining anything.
The proof surface
Pack-count tools answer how many snacks to buy. This job reconciles unlike nutrition-label units at the actual eaten mass, retaining a separate conversion note for salt-derived rows. It does not prescribe a nutrient target or treat a label as a laboratory measurement.
InputFood code | sodium or salt | label amount per 100 g | grams eaten; sodium milligrams per gram of salt under your label convention
Rare devicePack-count tools answer how many snacks to buy. This job reconciles unlike nutrition-label units at the actual eaten mass, retaining a separate conversion note for salt-derived rows. It does not prescribe a nutrient target or treat a label as a laboratory measurement.
Output artifactRecorded portion sodium-equivalent total with row-by-row context
Cost$0 local calculation · no card, paid key, subscription or signup · proposed filing price is not for sale
Sample, not your facts: Illustrative inputs: Soup bowl | sodium | 420 | 250; Bread slices | salt | 1.1 | 80. Sodium milligrams per gram of salt under your label convention = 400. Recorded portion sodium-equivalent total: 1402 mg sodium-equivalent. All records are invented.
Before using the salt-label receipt
Use only labels expressed per 100 grams and portions measured in grams. A per-serving label needs a verified serving-mass conversion before it belongs in this log; a liquid per-100-milliliter label cannot silently become a per-100-gram label. The supplied 400 mg-per-gram model corresponds to dividing salt grams by 2.5 and converting grams to milligrams. It is a labeling convention, not a test of a food's chemical composition. Change it only to match a verified convention in your source. No recommended daily ceiling is built in. This tool is useful for organizing a conversation about labels, particularly when records from different countries use different terms, without determining what anyone should eat.
Why the flat version breaks
Adding grams to milligrams
The numeral 1.1 for salt is not smaller than 420 mg sodium in a directly comparable sense. The units and nutrient definitions differ. Enter the label type and let the receipt show the conversion; do not first convert a salt amount yourself and then keep its type as salt, which would convert it twice.
Scaling a serving label as though it were per 100 g
A label stating 420 mg per serving may describe a 250 g serving already. Multiplying that number by 2.5 again would overcount. Verify both the nutrient unit and the denominator. This parser deliberately accepts only one stated per-100-g model instead of guessing from a plausible amount.
Turning a partial food list into a daily verdict
Two entered portions are two entered portions. Missing snacks, drinks and added ingredients stay outside the total. A receipt with many rows is still not evidence that the whole day was captured. Retain the recorded-food scope and ask a qualified professional about dietary interpretation rather than attaching a clinical label to the sum.
How to work the salt-label receipt
Copy the label basis before the amount
Identify whether the printed nutrient is sodium in milligrams or salt in grams, then confirm that its denominator is 100 g. Put the word sodium or salt in the second cell. An anonymous food code is enough; brand names, diagnoses and family members' diets are unnecessary to the calculation. Keep a photograph or original label privately for review.
Measure the portion on the same mass basis
Enter grams actually eaten, not the full package mass unless the whole package was consumed. Drained contents and undrained contents may have different label conventions. If the portion was estimated from volume, obtain a suitable mass basis rather than assuming density. The calculator cannot determine whether a food was prepared in the labeled condition.
Convert the nutrient, then scale the portion
For a sodium row, multiply its mg-per-100-g amount by portion grams divided by 100. For a salt row, first multiply salt grams by the supplied sodium-mg-per-salt-g factor, then use the same portion fraction. Sum the resulting milligram quantities only after both conversions; the row notes retain the original type and factor.
Keep the tally's scope with a diet question
Describe which portions are included when presenting the receipt. Ask a registered dietitian or clinician to confirm the label convention and any medically relevant goals. The tool does not decide whether a tally is low, high, adequate or safe, and it does not fill in unrecorded meals. Salt-conversion marks indicate a modeling step, not an adverse health finding.
What the salt-label receipt separates
Question
Before
Inspect this instead
Adding grams to milligrams
The numeral 1.1 for salt is not smaller than 420 mg sodium in a directly comparable sense. The units and nutrient definitions differ. Enter the label type and let the receipt show the conversion; do not first convert a salt amount yourself and then keep its type as salt, which would convert it twice.
Measure the portion on the same mass basis
Scaling a serving label as though it were per 100 g
A label stating 420 mg per serving may describe a 250 g serving already. Multiplying that number by 2.5 again would overcount. Verify both the nutrient unit and the denominator. This parser deliberately accepts only one stated per-100-g model instead of guessing from a plausible amount.
Convert the nutrient, then scale the portion
Turning a partial food list into a daily verdict
Two entered portions are two entered portions. Missing snacks, drinks and added ingredients stay outside the total. A receipt with many rows is still not evidence that the whole day was captured. Retain the recorded-food scope and ask a qualified professional about dietary interpretation rather than attaching a clinical label to the sum.
Keep the tally's scope with a diet question
This salt-label receipt replaces a manual count or calculation, not source verification or the responsible person’s review.
Run it on the samples, right here
FIRST-LOAD
HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.
Label-conversion arithmetic only, not nutrition or treatment advice. Confirm the label basis and any medically relevant intake goal with a registered dietitian or qualified clinician; do not change a prescribed diet from this tally.
Data note: The salt-label receipt processes Food code | sodium or salt | label amount per 100 g | grams eaten locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.
Go deeper: the companion app files the same reading as a till receipt with a tear-off foot
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the salt-label receipt reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
The salt-label receipt answer stays complete for free. The proposed $4 one-time filing layer adds row CSV, print and five local reading summaries, not hidden answers. Checkout is unavailable; the article demo remains unlimited.
Label-conversion arithmetic only, not nutrition or treatment advice. Confirm the label basis and any medically relevant intake goal with a registered dietitian or qualified clinician; do not change a prescribed diet from this tally.
What this is built on
Method: For a sodium row, multiply its mg-per-100-g amount by portion grams divided by 100. For a salt row, first multiply salt grams by the supplied sodium-mg-per-salt-g factor, then use the same portion fraction. Sum the resulting milligram quantities only after both conversions; the row notes retain the original type and factor.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.
Before: salt and sodium label numbers were added without a common unit. After: each eaten portion carries its label convention and converted milligrams.
Setting: Sodium milligrams per gram of salt under your label convention = 400. Expected summary: 1402 mg sodium-equivalent.
The soup contributes 420 × 250/100 = 1,050 mg sodium. The bread label uses salt grams: 1.1 × 400 × 80/100 = 352 mg sodium-equivalent under the supplied conversion. Their total is 1,402 mg. The receipt preserves the salt label and marks its conversion basis rather than making the two printed label numbers appear comparable without units.
Sample B — changed plan
Cheese piece | salt | 1.8 | 30
Pea portion | sodium | 5 | 125
Setting: Sodium milligrams per gram of salt under your label convention = 400. Expected summary: 222.25 mg sodium-equivalent.
The cheese contributes 1.8 × 400 × 0.3 = 216 mg equivalent; the peas contribute 5 × 1.25 = 6.25 mg directly. The total is 222.25 mg. This is a tally for the two entered portions, not a daily intake estimate. If an unrecorded sauce or cooking ingredient was eaten, the calculator has no basis to include it.
Sample C — boundary convention
Plain-water label | sodium | 0 | 250
Setting: Sodium milligrams per gram of salt under your label convention = 400. Expected summary: 0 mg sodium-equivalent.
A zero printed sodium amount scaled by a 250 g portion remains zero in this labeling model. A rounded label zero may not mean chemically absent sodium, and an incomplete label is not a zero label. This boundary only checks the arithmetic for an explicitly entered zero. It provides no assurance about suitability for a medical diet or the rest of the day's intake.
Optional AI formatting, never the calculation
Manual entry completes this salt-label receipt for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.
Format only these fictional or non-sensitive notes for a salt-label receipt. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Food code | sodium or salt | label amount per 100 g | grams eaten; the setting is Sodium milligrams per gram of salt under your label convention. Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.
An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.