Building the Universal Recipe Scaler: A Local-First, Ad-Free Kitchen Utility

Why I Built This (And Why Most Recipe Tools Are Broken)

Recipe blogs in 2026 are a tax on home cooks.

You arrive looking for ratios. You leave with three popups, a video ad that follows you down the page, two newsletter prompts, an autoplay TikTok, and 2,400 words of life story before the actual recipe. Then the recipe is in cups and Fahrenheit and you need to scale it down for two servings instead of six.

I cook constantly. I want a tool that does one thing well — take ingredient quantities, give me scaled and unit-converted ingredient quantities. No life story. No paywall. No subscription.

So I built one.

The Stack: Vanilla on Purpose

The whole tool is one HTML file, one CSS file, one JS file. No React, no backend, no auth, no database, no loading spinner.

Frontend. Plain HTML, CSS, and JavaScript. No framework. The total app size is under 100 KB, which means it loads instantly on any connection.

Storage. Browser localStorage. If you paste a recipe, scale it, and accidentally close the tab, your exact ingredients are still there when you reopen the page. Nothing leaves the browser — there's no server to leave to.

Hosting. GitHub Pages. Static hosting, free tier, no infrastructure to maintain.

Schema. JSON-LD WebApplication markup so Google and AI assistants understand exactly what the page is: a free software utility published by Built by Josh Studio LLC.

The whole stack fits in a single browser tab. The bet is that "minimal" beats "feature-rich" for a tool you reach for ten seconds at a time.

The Regex Problem Nobody Mentions

Scaling numbers is trivial. Multiply by two. Done.

Parsing culinary natural language is not.

Recipes don't write quantities the same way twice. "1 cup", "1 c.", "1 c", "1 cup of", "1 Cup", "1 Cups" (plural where it shouldn't be) — all valid in the wild. Plus fractional units: "1/2 tsp", "½ teaspoon", "0.5 t". Plus compound quantities: "1 1/2 cups". Plus prefix qualifiers: "About 2 tbsp", "Roughly 1 cup", "Heaping ¾ teaspoon".

I ended up building a master dictionary that catches every plausible spelling, abbreviation, and casing of every unit I care about. Tablespoon, tbsp, tbsps, Tbsp, T (capital T because lowercase t is teaspoon — that single ambiguity caused a real bug during testing). Cup, cups, c, c., C. Pound, lb, lbs, lb. — and pound's plural is "lbs" not "lbss", so the pluralization rule has to be unit-aware.

The regex catches all of these case-insensitively, captures the quantity (including fractions and compound quantities), and normalizes the unit to a canonical form before scaling and converting. Most of the engineering time on this project went into the dictionary, not the math.

Smart Formatting: When Grams Become Kilograms

A common failure mode in recipe converters: convert 2 pounds to grams (907g), scale by 3, output "2721 grams of flour". The math is right. The presentation is bad. Nobody actually wants to read a kitchen instruction that says "2721 grams" — they want "2.72 kg".

The scaler auto-shifts units when the magnitude crosses a threshold:

• Grams → Kilograms above 1000g
• Milliliters → Liters above 1000ml

The shift happens after scaling, not before. So if you scale a recipe down and the result is 600g, it stays in grams. Scale up to 1200g, it becomes 1.2 kg automatically.

Small detail. Removes a real friction point that hit me constantly in other tools.

The Scale-Lock: Don't Double the Temperature

The biggest breakthrough on this build was teaching the tool what not to scale.

If you double a recipe, you do not double the temperature. 350°F stays 350°F. Same for cooking time, oven settings, pan dimensions, knife depth. These are non-scalable values that often appear in ingredient-adjacent contexts — "Bake at 350°F", "Cut into 1-inch cubes", "Rest for 10 minutes".

The scaler ignores temperatures and dimensional measurements (inch, cm, mm) automatically. They pass through unchanged. Only ingredient quantities — the things measured in cups, tablespoons, ounces, grams, etc. — get scaled and converted.

To make this airtight in the UI, the tool explicitly guides users to paste only the ingredient list, not the full recipe with instructions. That input constraint sidesteps the harder problem of distinguishing "preheat oven to 400°F for 30 minutes" (don't scale anything) from "mix 30 oz of flour" (scale this).

Constrained input, simpler logic, fewer edge cases. The right tradeoff for a tool meant to be used in ten seconds.

Glassmorphism Over Culinary Warmth

The visual design is a frosted-glass card layered over a warm food-photo background. The look sits somewhere between premium iOS app and modern recipe magazine.

The point isn't aesthetics for their own sake. A recipe scaler that looks like a free 2008 utility is a recipe scaler that gets used once and abandoned. Looking like a tool you'd pay for makes it a tool you'll come back to.

The interactive prep list closes the loop. Once your recipe is scaled, each ingredient becomes clickable — tap to cross it out as you measure. One-click Copy to Clipboard and Print Recipe buttons handle the handoff to your actual cooking surface — phone propped on the counter, printout next to the cutting board.

Three details that turn "math utility" into "kitchen tool I'll actually use."

Try It

The Universal Recipe Scaler is live at builtbyjoshstudio-cyber.github.io/universal-recipe-scaler. Free. No signup. No email gate. Runs entirely in your browser — your data never leaves your device.

Drop in your next holiday recipe and scale it for the number you actually have at the table. Or shrink a favorite cookie dough to a single-batch Tuesday-night quantity. That's what it's built for.

If you build something cool with it, or hit a recipe format the parser can't handle, send it to me. The dictionary keeps expanding.

Frequently Asked Questions

Is the Universal Recipe Scaler free?

Yes — completely free, with no signup, no email gate, and no premium tier. It's hosted on GitHub Pages and the entire tool runs in your browser.

Does it work offline?

Once the page has loaded, yes — there's no backend to call. If you load it on a flight or with bad Wi-Fi, it keeps working. localStorage means your last recipe stays saved between sessions even without an internet connection.

Why can't I paste the full recipe with instructions?

The tool intentionally only scales ingredient lists. Pasting the full recipe (with cooking times and temperatures) would risk the math engine scaling cooking times — "bake for 30 minutes" becoming "bake for 60 minutes" when you double a recipe. Restricting input to the ingredient list keeps the conversions accurate.

Why does it convert to kg/L automatically but leave temperatures alone?

Temperatures and dimensions (inches, centimeters) don't scale with recipe size. If you double a recipe, the oven still bakes at the same temperature for the same time. The tool ignores those values entirely and only scales ingredient quantities. Auto-converting grams to kilograms above 1000g is purely a presentation choice — easier to read 1.2 kg than 1200 g.

Does it store my recipes? Where does my data go?

The tool uses browser localStorage, which lives on your device. Nothing is sent to a server. If you clear your browser data, the saved recipe is gone. If you switch devices, the recipe doesn't transfer — it's truly local. There's no account system because there's nothing to account for.

Can I use it on my phone?

Yes. The interface is responsive and works on phones, tablets, and laptops. The interactive prep checklist is especially useful on a phone propped up next to the cutting board while you're actually cooking.

What's the technology behind it?

Plain HTML, CSS, and JavaScript. No framework. No backend. Single-page utility under 100 KB total. Hosted on GitHub Pages. JSON-LD WebApplication schema for search engines. The whole thing is intentionally minimal — the goal is to be the fastest thing you can find when you need to scale a recipe.