How Our Curing Salt Calculator Works

A transparent description of the calculator’s formulas, input assumptions, rounding behavior and limitations.

Updated 2026-09-27 · Educational reference · Verify product labels and current official guidance

Purpose

The calculator is an educational formulation tool. Its job is to make the arithmetic visible and reproducible. It is not a validated process model and does not replace a tested recipe, food-safety plan or applicable regulation.

Unit conversion

Meat weight is normalized to grams before calculations. The conversion constants used by the tool are:

1 kg = 1,000 g
1 lb = 453.59237 g
1 oz = 28.34952 g

Calculation bases

MethodBasis in this tool
Equilibrium Dry CureMeat weight in grams
Equilibrium BrineMeat weight + added water in grams
Retained Pump / PickupGreen meat weight × (1 + retained pickup)

Salt and sugar

Total salt (g) = Basis (g) × salt target %
Sugar (g) = Basis (g) × sugar target %

The current interface estimates the “additional salt” component by subtracting the calculated non-nitrite/non-nitrate fraction of the cure blend. This is a model assumption, not a guarantee that a proprietary curing product is literally composed only of sodium chloride outside its declared curing salts.

Nitrite PPM

Curing salt (g) = (Target PPM × Basis) ÷ (Nitrite Fraction × 1,000,000)
PPM = (Cure mass × Nitrite Fraction × 1,000,000) ÷ Basis

When the input mode is set to a cure-mix percentage, the tool calculates the resulting modeled PPM from that cure amount and the entered nitrite concentration.

Reference comparisons

The calculator includes a limited U.S. bacon comparison based on USDA FSIS's published bacon page. The displayed comparison is informational and is intentionally not presented as a universal “safe” meter. No reference is shown when the selected product/method does not map cleanly to the configured comparison.

Input guardrails

The calculators refuse formulation-style nitrite results above 200 ppm ingoing sodium nitrite. This is a deliberate product safeguard, not a claim that 200 ppm is a universal legal limit. Product- and method-specific limits can be lower, and requirements vary by jurisdiction. The U.S. general reference for cured products other than bacon is 200 ppm; bacon has method-specific limits. The tool therefore asks users to check the exact product label, applicable rule and tested recipe before treating a number as a formulation.

Method-specific U.S. bacon guardrails: pumped/massaged and immersion-cured bacon use a 120 ppm reference, while dry-cured bacon uses a 200 ppm reference, calculated on the applicable skin-free green-weight basis. Those limits are checked before the tool renders a formulation result. Cure #2 also reports nitrite and nitrate separately and refuses configured nitrate/nitrite values that exceed the cited U.S. reference thresholds.

Cure-time estimate scope

The homepage thickness heuristic (one day per 6 mm at the thickest point, plus a two-day buffer) is shown only for the equilibrium dry-cure method. Equilibrium brine and pump/injection processes are timed by the recipe or validated process — immersion and pumping schedules depend on solution strength, injection distribution and equipment, not on slab thickness — so the results panel displays no numeric estimate for those methods.

Rounding

Inputs are calculated at full JavaScript precision, while the interface displays rounded values for readability. When a result is close to an important threshold, use the unrounded formulation math, product label and applicable rule rather than relying on a display-rounding edge case.

What the calculator does not determine

  • Whether a curing process achieves pathogen control.
  • Whether a fermented/dried product is shelf-stable.
  • Whether a commercial process complies with every applicable regulation.
  • Whether a manufacturer's label direction is appropriate for your particular recipe.

Sources and review policy

Safety-related claims are linked to current official or university-extension references. The site should be re-reviewed whenever a cited official source or product formulation changes. The current editorial review date is September 15, 2026.

Inspect the calculator
Use the main tool and expand the math breakdown to compare the result with the formulas above.

Open methodology in practice →

The three calculation bases, exactly

MethodCalculation basisFormula inputsWhere used
Equilibrium dry cureMeat weight (green)Weight × targets; PPM on meat basisBacon dry cure, whole muscles, jerky
Equilibrium brineMeat weight + measured added waterSame targets on the combined massWet cures, corned beef, hams
Retained pump / injectionGreen meat × (1 + retained pickup %)PPM compared on green-meat denominatorCommercial-style pumped bacon/ham

The denominator choice is the single most common divergence between calculators and recipes. When our result disagrees with a recipe, check the basis first — a “2% salt” brine recipe on a meat-only basis is not comparable to one written on a meat-plus-water basis, and the difference is not subtle at 40% added water.

Full formula list

toGrams(v, unit): g = 1 / kg = 1,000 / lb = 453.59237 / oz = 28.34952
Basis (dry) = meat weight
Basis (brine) = meat + water
Basis (pump) = meat × (1 + pickup%)
Cure (g) = (Target PPM × Basis) ÷ (Nitrite fraction × 1,000,000)
Resulting PPM = (Cure × Nitrite fraction × 1,000,000) ÷ Basis
Plain salt (g) = Total salt target − Cure × (1 − nitrite fraction − nitrate fraction)
Nitrate delivered (mg) = Cure × nitrate fraction × 1,000
Teaspoon estimate = Cure grams ÷ 5.7 (density-approximate, Cure #1-style blend)
Cure-time heuristic (EQ dry, whole muscle) = ceil(thickness mm ÷ 6) + 2 days

The salt-deduction line matters more than it looks: a Cure #1 gram carries ~93.75% salt, so 5 g of blend contributes 4.69 g toward the salt target. Calculators that ignore this produce “total salt” numbers that overshoot by up to 20% at typical doses. Ours treats the non-nitrite, non-nitrate portion of the blend as salt explicitly, and shows the assumption in the math breakdown.

Reference limits used by the guardrails

GuardrailThresholdSourceBehavior when exceeded
General ingoing nitrite cap200 ppm9 CFR 424.21Result refused with explanation (not silently clamped)
Comminuted sausage reference156 ppm9 CFR 424.21Used as the default target and gauge marker
Bacon pumped/immersion120 ppmFSIS bacon guidance / 9 CFR 424.22Gauge marker; bacon calculator preset
Bacon dry-cured200 ppmFSIS bacon guidance / 9 CFR 424.22Gauge marker; bacon calculator preset
Bacon + nitrateNot permittedFSIS bacon frameworkCure #2/nitrate selection blocked for bacon with an explanation
Pumped bacon accelerator (commercial)550 ppm ascorbate/erythorbateFSIS bacon guidanceReferenced in notes; not a calculator input

Verification protocol for every release

  1. Golden-example test: 2,000 g at 156 ppm with 6.25% must return 4.99 g cure, 45.32 g plain salt at a 2.5% target, 312 mg nitrite, 1.13 g/lb, 2.50 g/kg. Any deviation blocks release.
  2. Reverse test: feeding the output back through the PPM direction must reproduce the input target to 0.01 ppm.
  3. Basis tests: brine and pump models checked with hand-computed bases (e.g., 1 kg + 500 g water at 2% salt = 30 g salt, not 20 g).
  4. Guardrail tests: 201 ppm input refuses; bacon + Cure #2 refuses; 0% nitrite with a PPM target refuses with guidance.
  5. Unit tests: lb/oz/kg/g conversions verified against the exact factors above, and the teaspoon note checked against the 5.7 g density assumption.

Known limitations we state up front

  • The tool models ingoing formulation only — it does not predict residual nitrite, color development, flavor or shelf life.
  • The teaspoon conversion carries a real ±20% density tolerance across retail blends; grams are the honest unit.
  • The cure-time heuristic is a whole-muscle planning aid, not a validated schedule for ground, fermented or injected products.
  • Jurisdictions outside the U.S. apply different limits and permitted products; our guardrails cite U.S. references and say so.
  • Prague Powder-brand naming is used generically because searchers use it that way; no brand relationship exists and label verification is always required.