NSF H1 vs H2 Food-Grade Lubricants: What the Difference Means for Maintenance

NSF H1 lubricants are registered for use where incidental food contact is possible, while NSF H2 lubricants are permitted only where contact with food is impossible. The categories come from the NSF Nonfood Compounds Registration Program, which replaced the USDA approval scheme in 1999. Picking the wrong category, or letting the two mix in the workshop, is the difference between a defensible trace event and a contamination incident. Here is what each category means, where it belongs, and how maintenance teams keep them apart.

What the NSF registration categories mean

NSF registers lubricants by where they may be used relative to food:

• H1 (incidental food contact): permitted at lube points where a drip, mist, or splash could realistically reach product. H1 formulations may only use substances listed in FDA regulation 21 CFR 178.3570, and contact with food is capped at 10 parts per million (ppm).
• H2 (no possibility of food contact): permitted only where neither the lubricant nor the lubricated surface can ever touch food. Formulation rules are looser, but H2 products must not intentionally contain heavy metals, carcinogens, or mutagens.
• H3 (soluble oils): edible-grade oils used to clean and rust-protect hooks, trolleys, and similar equipment, mostly in meat plants. Treated equipment must be cleaned before returning to service.

Two related marks: 3H covers release agents that touch food directly, and ISO 21469 certifies hygienic lubricant manufacturing beyond H1 registration.

Where H1 and H2 belong on the line

The dividing question is physical: under a realistic failure, could this lubricant reach product or a product-contact surface? If yes, the point requires H1.

• Typical H1 points: filler and seamer bearings, mixer and agitator seals, conveyor chains above open product, gearboxes mounted over the line, pneumatics exhausting near product zones.
• Typical H2 points: enclosed drivetrains in separated utility areas, compressors in the plant room, forklifts and pallet trucks, pumps on non-product services.

Make the call per lubrication point, not per machine. The same filler can have an H1 gearbox above the bowl and an H2 motor bearing at floor level, which is why lubrication surveys and asset-level records beat a blanket policy.

Worked example: one small leak, one big problem

Suppose a gearbox above a mixing vessel blows a seal and loses 50 ml of oil into a 2,000 kg batch of sauce:

1. Gear oil has a density of roughly 0.9 g/ml, so 50 ml weighs about 45 g, or 45,000 mg.
2. Concentration: 45,000 mg divided by 2,000 kg gives 22.5 mg/kg, which is 22.5 ppm.
3. That is more than double the 10 ppm ceiling that applies even to H1, so the batch is blocked no matter what was in the gearbox.
4. With an H2 oil the event escalates to a food-safety incident: no amount of H2 lubricant in product is acceptable, and everything produced since the last verified-clean inspection becomes suspect.

On a 2,000 kg batch, 10 ppm corresponds to just 20 g of oil, about 22 ml. H1 does not make leaks acceptable; it makes trace-level incidental contact defensible while you fix the root cause.

Why plants still use H2, and when that is defensible

H2 lubricants persist because their wider additive chemistry historically gave better extreme-pressure performance and service life in heavily loaded gearboxes and hydraulics. Modern synthetic H1 products on PAO and PAG base stocks have closed most of that gap, so many plants now standardize on H1 site-wide, which eliminates the most dangerous failure mode: a technician grabbing the wrong cartridge during a night-shift breakdown. If you keep H2 for performance reasons, a mixed inventory is only as safe as its labeling, storage, and task discipline.

Preventing cross-contamination between lube types

• Color-code end to end. Match the color on container, grease gun, lube point tag, and task instruction.
• Dedicate application equipment. One grease gun per product; a gun that ever held H2 grease can transfer it to an H1 point.
• Segregate storage. H1 products get their own sealed, labeled cabinet; never decant into unmarked containers.
• Run a lubrication survey. List every lube point, assign a category to each, and record the decision against the asset.
• Risk-assess the exceptions. Where H2 remains near production areas, use FMEA to score the leak paths and document the safeguards.
• Train operators too. If operators grease under an autonomous maintenance program, they need the same category training as technicians.

Put lubricant identity in the system, not in memory

Most cross-contamination traces back to tribal knowledge: the retiring technician knew which grease went where, and the successor guessed. A computerized maintenance management system (CMMS) removes the guesswork:

• Each asset carries its lube specification: product name, NSF category, and registration number.
• Each preventive lubrication task names the exact product, quantity, and point before the job starts.
• Completed work orders build a per-asset lubrication history, exactly the evidence BRCGS, IFS, and FSSC 22000 auditors request.
• Scheduled lube routes shift the program from reactive to proactive maintenance.

Where Fabrico fits

Fabrico is an EU-built CMMS and real-time production monitoring platform with EU data residency: the data foundation for exactly this kind of program. In Fabrico's CMMS, every asset holds its lubrication specification, every preventive task states the registered product and quantity, and every completed work order becomes auditable history tied to the machine. Spare-parts management keeps H1 and H2 stock itemized separately, so stores issue what the task prescribes. And because Fabrico tracks overall equipment effectiveness (OEE) in real time, you can verify that lubrication-related stoppages shrink as the program matures.

Frequently Asked Questions

Can I use an H2 lubricant if food contact is merely unlikely?

No. H2 requires no possibility of contact, not low probability. If a drip, splash, or mist could reach product under any realistic failure, the point requires H1. "Unlikely" is the scenario H1 exists for.

Does H1 registration mean the lubricant is edible or safe to leak into food?

No. H1 means the formulation uses permitted substances and incidental contact up to 10 ppm is tolerated. A visible leak usually exceeds 10 ppm quickly and still requires batch evaluation and repair. Edible-oil products fall under H3, a separate category.

How do auditors check lubricant compliance?

They ask for the lubrication survey, check that stored products match the approved list and carry NSF registration numbers, then test traceability: they pick an asset and ask which lubricant was applied, when, and by whom. Per-asset task records in a CMMS answer that in seconds; a paper lube chart usually cannot.

Ready to put your lubrication program on a per-asset, audit-ready footing? Book a Fabrico demo and see how lube-type tracking, preventive scheduling, and work order history come together in one system.