Defect Rate Calculator
Calculate defect rates, defect density, DPMO, yield, and sigma levels for quality assurance and production metrics.
Calculate Defect Metrics
Enter your production or inspection data to calculate quality metrics.
Total number of units, items, or opportunities inspected
Total number of defects identified during inspection
Number of potential defect opportunities per unit. Used for DPMO calculation. Default is 1 if not specified.
What This Calculator Does
Defect rate sounds simple enough—how many bad ones out of the total. But once you start digging into quality metrics, you've got DPMO, sigma levels, yield percentages, and a dozen other ways to slice the same data. This calculator handles the math so you don't have to pull out a spreadsheet every time someone asks for numbers.
Plug in your inspection data, and you'll get the key metrics used in manufacturing QA, Six Sigma programs, and software testing. Everything calculates in your browser—your data stays on your machine.
Defect Rate (Percentage)
The most intuitive metric. If you inspected 1,000 widgets and found 15 duds, that's a 1.5% defect rate. Simple division, expressed as a percentage:
Defect Rate = (Defects ÷ Units Inspected) × 100
Yield
Just the flip side of defect rate—what percentage passed. A 1.5% defect rate means 98.5% yield. Manufacturing folks tend to talk in yield; QA people often prefer defect rate. Same information, different framing.
DPMO (Defects Per Million Opportunities)
This one gets interesting when each unit has multiple things that could go wrong. Say you're inspecting circuit boards with 50 solder joints each. Finding 100 bad joints across 1,000 boards doesn't mean 10% of boards are bad—it's 100 defects out of 50,000 opportunities. DPMO normalizes this:
DPMO = (Defects ÷ (Units × Opportunities per Unit)) × 1,000,000
The "per million" part lets you compare processes with wildly different volumes.
Sigma Level
Here's where statistics meets marketing. Sigma levels map defect rates to standard deviations from perfection. Six Sigma (3.4 DPMO) became a whole management philosophy—but at its core, it's just a way to express "very, very few defects."
| Sigma | DPMO | Yield |
|---|---|---|
| 2σ | 308,538 | 69.15% |
| 3σ | 66,807 | 93.32% |
| 4σ | 6,210 | 99.38% |
| 5σ | 233 | 99.977% |
| 6σ | 3.4 | 99.99966% |
Whether you actually need Six Sigma quality depends entirely on what you're making. Medical devices? Probably yes. T-shirt printing? Probably overkill.
Where These Metrics Get Used
Manufacturing
Production line monitoring, supplier scorecards, ISO compliance, customer quality reports. If you're in manufacturing QA, you're probably calculating these weekly if not daily.
Software Development
Defects per thousand lines of code (KLOC) for code quality. Bug escape rate for testing effectiveness. Release readiness metrics. The formulas translate directly—just define what counts as a "unit" and what counts as a "defect."
Service Operations
Order accuracy rates. Billing error rates. Customer complaint rates. Any process where you can count "should have worked" and "didn't work" fits this framework.
Getting Useful Numbers
A few things that matter more than the calculator itself:
- Define "defect" clearly. Sounds obvious, but disagreements here make metrics meaningless. Write it down. Get everyone to agree.
- Sample properly. Inspecting 100% is often impractical. If you're sampling, use statistical methods—not "grab a handful from the bin."
- Track trends, not just snapshots. One week's defect rate matters less than the direction over months. Is it improving? Getting worse? That's what drives action.
- Dig into root causes. Counting defects is step one. Understanding why they happen is where improvement actually comes from.
How We Calculate It
For transparency, here are the exact formulas:
- Defect Rate: (Defects ÷ Total Units) × 100
- Yield: 100 − Defect Rate
- DPMO: (Defects ÷ (Total Units × Opportunities)) × 1,000,000
- Defect Density: Defects ÷ Total Units
- Sigma Level: Approximated from DPMO using standard conversion tables
The sigma calculation uses a lookup approximation. For mission-critical applications where precision matters, you'd want proper statistical analysis—but for reporting and general tracking, this gets you there.