20 Free Calculators That Show Their Working

Zusammenfassung

Pixel shares the build story behind EziSolutions, a free site with 20 calculators for fees, ROAS, customer LTV, taxes, loans and more. The announcement covers its simple Python, HTML and JavaScript stack, Cloudflare deployment, formula-checking feature and unexpected SEO lessons—useful insights for developers building practical web tools.

DEV Community

I built 20 calculators that show their working. Here's the stack, the bugs and the SEO surprise

Most online calculators give you a number and expect you to trust it. I wanted the opposite: under every result, a line that prints the exact sum with your numbers in it, so you can check it by hand. That became EziSolutions, a free site with 20 calculators: Etsy, Mercari, Poshmark, Venmo, Stripe, Square and Fiverr fees, ROAS, customer LTV, CPM, BMI, TDEE, VAT, loans, freelance rates and a few more. No framework, no backend, no signup. Here's how it's built, the bugs that taught me something, and an honest look at the SEO side, which didn't go the way I expected. I built it with help from an AI coding assistant, and checked every formula and fee myself. The stack (deliberately boring) Python build script. content.py holds every page as data: title, description, form fields, the explanation, FAQs and sources. build.py turns it into plain HTML files in public/. Vanilla JavaScript. One tools.js file with one function per calculator. No React, no bundler. Cloudflare Workers with static assets. The Worker just serves public/. _headers sets security headers and _redirects handles old URLs. GitHub + Workers Builds. Every push to main runs npx wrangler deploy. About 40 seconds from git push to live. The whole deploy config is this: {
"name": "icy-shape-8ab9",
"compatibility_date": "2026-11-01",
"assets": {
"directory": "./public",
"not_found_handling": "404-page",
"html_handling": "auto-trailing-slash"
},
"routes": [
{ "pattern": "ezisolutions.online", "custom_domain": true },
{ "pattern": "www.ezisolutions.online", "custom_domain": true }
],
"workers_dev": false
}
I commit the built public/ folder instead of building on Cloudflare. It's less elegant, but the deploy step has nothing to break, and I can see exactly what ships in every diff. The feature: a "working" line under every result Each calculator ends by calling one helper: function work(text) { set('ez-working', text); }

// Inside the Venmo calculator:
work(money(amt) + ' × ' + pct + '% + ' + money(fixed) + ' = ' + money(fee) + ' fee');
// → "$100.00 × 2.99% = $2.99 fee"
It's a tiny thing, but it changed how I wrote every calculator. If I couldn't print a clean one-line sum, the logic was probably too clever, and I simplified it. Bug 1: "How much should I charge to receive $100?" Fee calculators get asked this a lot. The textbook answer is: amount to charge = (amount you want + fixed fee) ÷ (1 − percentage)
For Venmo's 2.99% that gives $103.0821, which I rounded up to $103.09. But Venmo rounds its fee to the cent, so $103.08 already leaves exactly $100.00. I was telling people to overcharge by a cent. Worse, the formula falls apart for fees with a cap or minimum. Stripe's ACH fee is 0.8% capped at $5. To receive $1,000 you need $1,005, but the formula said $1,008.06. The fix was to stop solving it algebraically and search over whole cents instead: // Smallest amount (in cents) whose fee still leaves want.
function askFor(want, pct, fixed, feeFn) {
let lo = Math.round(want * 100);
let hi = Math.ceil((want + fixed + 1) / Math.max(1 - pct / 100, 0.01) * 100) + 100;
while (lo < hi) {
const mid = Math.floor((lo + hi) / 2);
if (mid / 100 - feeFn(mid / 100) >= want - 1e-9) hi = mid; else lo = mid + 1;
}
return lo / 100;
}
feeFn is the real fee function, with rounding, caps and minimums, so whatever rule a platform uses, the answer is exact. The formula only sets the upper bound for the search. Bug 2: my test caught a wrong number in my own article Every tool page has a worked example in the text. I test each calculator by filling it with the example's numbers in headless Chrome (plain Chrome DevTools Protocol, no test framework) and comparing the output with what the page says. That's how I found the $103.09 bug: the calculator and the article disagreed. Testing against the prose turned out to be a cheap way to keep the explanations honest. Bug 3: the security header that would have blocked my revenue My Content-Security-...
20 Free Calculators That Show Their Working
Powered by Readybot.io

Das Neueste von Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …