Bonferroni Correction Calculator

Bonferroni Correction Calculator

Adjust a family-wise alpha, correct a raw p-value, compare the Sidak threshold, and estimate the family-wise error rate from any per-comparison alpha.

đŸ§ȘMultiple-Testing Presets

🔱Correction Inputs

Use the setting to label the breakdown and reporting notes.

The total false-positive rate you want across the family.

Count planned hypotheses in the same claim family.

Enter one unadjusted p-value; repeat for others as needed.

Shows FWER if every test is judged at this single-test alpha.

Bonferroni is conservative; Sidak assumes independent tests.

Role changes interpretation wording, not the correction math.

Use more decimals when m is large or thresholds are tiny.

Bonferroni alpha 0.004167 family alpha divided by m
Adjusted p-value 0.045600 min(raw p x m, 1)
Sidak alpha 0.004265 independent-test threshold
FWER at alpha per test 45.96% 1 - (1 - alpha per)^m

🧭Current Correction Grid

12Tests m
0.050Family alpha
0.003800Raw p
0.91p / Bonf alpha
2.35%Sidak gap
PassBonferroni
PassSidak
11.4xFWER / alpha
0.004167Needed raw p
CorrectedReport style

📐Formula Breakdown

Bonferroni adjusted alphaαBonf = αfamily / m. A raw p-value passes when p ≀ αBonf.
Bonferroni adjusted p-valuepadj = min(p x m, 1). A corrected p-value passes when padj ≀ αfamily.
Sidak adjusted alphaαSidak = 1 - (1 - αfamily)1/m. It is slightly less conservative when tests are independent.
Family-wise error rateFWER = 1 - (1 - αper)m. This shows false-positive risk when each test uses the entered per-test alpha.

📋Preset Scenario Comparison

ScenariomFamily AlphaRaw pBonf AlphaAdj pSidak AlphaTypical Read
Clinical biomarker panel120.050.00380.0041670.04560.004265Just passes Bonferroni at 5%
A/B metrics dashboard80.050.01200.0062500.09600.006391Raw signal does not survive
Neuroimaging ROI set640.050.000900.0007810.05760.000801Close but above corrected threshold
Candidate SNP screen5000.050.000120.0001000.06000.000103Suggestive candidate signal
RNA pathway sweep12000.050.0000300.00004170.03600.0000427Passes a strict family correction
Education item audit240.100.00600.0041670.14400.004386Exploratory flag only
Sensor fault bank400.010.000310.0002500.01240.000251Misses a 1% family rule
Ecology species contrasts180.050.00410.0027780.07380.002845Report as uncorrected evidence
Marketing segment slices300.050.00190.0016670.05700.001708Near miss after correction

⚖Bonferroni vs Sidak Reference

MethodThreshold FormulaAssumptionConservatismWhen To Prefer
Bonferroni alphaα / mNo independence requiredOften conservativeDefault simple family control
Bonferroni p-valuemin(p x m, 1)Same as Bonferroni alphaOften conservativeReporting corrected p-values
Sidak alpha1 - (1 - α)^(1/m)Independent testsSlightly less conservativeIndependent planned comparisons
No correctionα per testSingle isolated testNo family controlOnly one primary hypothesis
Holm contextStep-down thresholdsOrdered p-valuesLess conservative than BonferroniFull family p-value lists
FDR contextControls expected false discoveriesMany discoveries expectedDifferent error goalLarge screening studies

📈FWER Lookup at Common Per-Test Alpha

Tests mFWER at 0.05FWER at 0.01Bonf Alpha for 0.05Sidak Alpha for 0.05
29.75%1.99%0.0250000.025321
522.62%4.90%0.0100000.010206
1040.13%9.56%0.0050000.005116
2064.15%18.21%0.0025000.002561
5092.31%39.50%0.0010000.001026
10099.41%63.40%0.0005000.000513
500>99.99%99.34%0.0001000.000103

🔍Multiple-Testing Reporting Checks

CheckGood PracticeRisk PatternWhy It MattersCalculator Field
Family definitionTests answer one planned familyConveniently excluding testsChanges the correction thresholdNumber of tests m
Alpha chosen firstFamily alpha set before analysisAlpha moved after seeing p-valuesInflates false-positive claimsFamily-wise alpha
Raw p precisionUse full unrounded p-valueOnly p < 0.05 availableAdjusted p needs numeric detailRaw p-value
Method statedName Bonferroni or SidakOnly says correctedReaders need the error ruleDecision method
FWER contextShow risk from uncorrected alphaTreating many tests as one testExplains why correction is neededPer-comparison alpha
Exploratory screenLabel as hypothesis-generatingClaims confirmation from a sweepCorrection does not fix weak designP-value role

💡Practical Correction Tips

Count the family before testing: Bonferroni protects the family you define. Moving tests in or out after viewing results weakens the false-positive control.
Use adjusted p-values for reporting: padj = min(p x m, 1) lets readers compare every result against the same family alpha.
Compare Sidak cautiously: Sidak is mathematically exact for independent tests, while Bonferroni stays valid as a simple upper-bound control.
Separate screening from confirmation: Very large families can need tiny thresholds, so use follow-up validation for discoveries from broad exploratory screens.

Let’s say you’re testing a new drug on three symptoms simultanously. You get important results for only one of those three symptom. Hooray! But then you discover later that running all three together raised the chances of getting a false positive by chance from five percent to fifteen percent. That’s the sneaky pitfall of multiple testing.

If you performs multiple statistical tests within a single study, each additional test multiply your chances of being wrong. Use the Bonferroni correction to fix this inflation.

Why Bonferroni Correction Is Important

Enter your exact number of comparisons into the calculator above. It will crunch the numbers and adjust p-values (or alpha level) to match. This helps you know what you can call a finding rather than just noise pretending to be a signal.

Just calculate your desired family-wise error rate (typically five percent), then divide by the number of comparisons you made. So if you did ten comparisons, now your new threshold for statistical significance is half a percent. Why does that feel so harsh? Because that’s its job. It’s being as conservative as possible. So you increase your confidence in your findings, they’re probably not a fluke! But this comes at the cost of losing some ability to pick up on really small, significant effects. That’s what most researchers is reluctant to sign off on. “I just want my data to speak!” but also “and I want to make sure my data isn’t lying to me.”

This little tool on page makes it easier to understand that changing either the raw p-value or alpha threshold will always result in the same decision. Most people trip up on question of what makes a test. Just because it’s obvious doesn’t mean it should of been counted. Ten biomarker measurements? That’s 10 tests. Now separate each one into genders? You’ve just doubled your family size there. The calculator asks you to specifically define this family. It also provides presets so you can load common study designs, such as A/B testing dashboards and clinical panels. These give the abstract numbers a concrete set of study designs to attach too.

Because the risk of over- (or under-) correcting something based off a small pilot study and doing the same thing with a massive genomic screen is too easy. The penalty for staring harder becomes steeper very quickly, and context matter.

The other thing that’s shown on this calculator (which it compares to the Bonferroni result) is what’s called the Sidak adjustment. It involve a more complicated exponential equation, and it assume that your tests are independent. So in practical terms, the actual numbers you come up with using Bonferroni vs. Sidak will often be pretty similar, particularly if you have only a few test and are doing something like a.05 significance test. But when you’re talking hundreds of variables, even the tiniest mathematical variation in the cutoff might make result go from significant to non-significant. Having both in side-by-side format lets you assess just how vulnerable your results are to the independence assumption.

Last, look at the family-wise error rate output. In this case, it tells you the overall probability that you will make at least one false positive claim without doing any correction. As you keep adding tests, you’ll see the number shoot up from five percent to ninety percent, which can be a sobering reminder about why we’re even doing this in the first place! It makes a concrete risk metric out of something that’s otherwise an abstract statistic. We’re not playing with numbers here: we’re quantifying the likelihood of being wrong.

Whether you’re creating a business report or peer-reviewed paper, the calculator gives you exactness required for accurate reporting. It removes the guessing game from comparing many thing at once. But finally, all of this gets back to how much care is in the discipline to use such a thing rather than in the formula itself. Do you define your hypotheses prior to seeing the data? Are all the comparisons that inform your ultimate conclusions counted? And are you willing to throw away an interesting lead when the numbers prove it wrong? If so, great, but a wrong answer is worse then none at all. The math shields you from yourself, from your optimism.

Bonferroni Correction Calculator