Probabilistic Sharpe Ratio (PSR): From CLT to Confidence
The PSR is the probability that the true Sharpe ratio exceeds a benchmark, derived from the Central Limit Theorem. Full derivation including the non-normality correction. The right way to report whether your Sharpe is statistically interesting.
Reporting a Sharpe of 1.5 tells the reader nothing about how confident you should be in that number. The Probabilistic Sharpe Ratio tells them. It answers a single question: given the data, what is the probability that the true Sharpe exceeds some benchmark ?
This article derives PSR from the Central Limit Theorem. The derivation is short, the intuition is sharp, and the resulting statistic is the right way to report whether your backtest is statistically interesting.
What PSR Computes
Define:
This is a probability statement about the true Sharpe. It is not the probability that your backtest will replicate. It is not the probability of outperformance in production. It is the posterior-ish probability that your estimated Sharpe exceeds the benchmark, under the assumption that the estimated Sharpe is normally distributed around the true Sharpe.
The benchmark is whatever you want to beat. Common choices: 0 (no skill), 0.5 (a typical actively managed equity strategy), 1.0 (good enough to attract institutional capital). The PSR lets you state “we are 95% confident our true Sharpe exceeds 0.5” or “we are 60% confident our true Sharpe exceeds 1.0.” Both statements are useful.
The CLT-Based Derivation
The Sharpe ratio estimator has mean (the true Sharpe) and variance . We derived the variance in the previous article:
This is the AFML / Bailey-López de Prado variance formula. The non-normality corrections come from the third and fourth central moments of returns. The factor uses Bessel’s correction.
For large enough, the Central Limit Theorem applies. The standardized Sharpe is approximately standard normal:
We want . Rearranging:
Under the CLT, the standardized quantity on the left is standard normal, so:
where and is the standard normal CDF.
That is the PSR. One formula, derived in four lines from the CLT.
Why the Benchmark Matters
PSR is monotonic in . A larger benchmark makes PSR smaller, holding the data fixed. The choice of is the choice of “what counts as success.”
For a long-short equity strategy, is usually too easy. If your strategy is net long equities, you will beat with a coin flip. to is more honest. For a market-neutral strategy, to is reasonable. For an HFT strategy with low latency, is the relevant hurdle.
The PSR does not tell you whether to deploy capital. It tells you whether your measured Sharpe is statistically distinguishable from a benchmark. Whether that distinction matters for capital allocation is a separate question.
The Gaussian Special Case
If returns are Gaussian, and . The variance simplifies:
For small (say ), the term is negligible and . The PSR reduces to:
This is the cleanest form. For and , . For , . So a one-year backtest with Sharpe 0.5 gives 94.3% confidence that the true Sharpe exceeds 0.4.
That sounds good. It is misleading without context. A 0.5 Sharpe over 1 year on a single strategy is fragile. The next year of returns could easily halve the Sharpe estimate. The PSR is unconditional on the future; it is a statement about the data already in hand.
Worked Example: Non-Gaussian Returns
Consider a short-volatility strategy with daily returns having , , mean , standard deviation , sample size (5 years daily). The Sharpe is:
Annualized: .
The standard error, including non-normality:
So . Annualized: .
PSR against benchmark 0:
That looks great. But notice: the non-normality correction added 13.4% to the standard error. If you had ignored it and used the Gaussian formula, the standard error would have been . The PSR with the Gaussian standard error would be . The difference looks small, but the corrected version is what the data supports.
PSR against benchmark 0.5:
PSR against benchmark 1.0:
A 75.2% probability that the true Sharpe exceeds 1.0. Reasonable. Worth a second look.
What PSR Does Not Capture
Three things PSR does not do, all of which matter.
No adjustment for autocorrelation. Returns with positive autocorrelation have fewer effective independent observations than the nominal . The standard error should be larger. The Haircut Sharpe article in this module derives the correction.
No adjustment for multiple testing. PSR assumes the strategy is the only one tested. If you tested 100 strategies and picked the best, the PSR is biased upward. The Deflated Sharpe Ratio, in the next article, fixes this.
No adjustment for non-stationarity. PSR assumes the data-generating process is stable. If the regime changed during the backtest period, the PSR is averaging across regimes and the standard error is wrong.
import numpy as np
from scipy.stats import norm
# Parameters
T = 1260
mu, sigma = 0.001, 0.012
gamma3, gamma4 = -1.5, 6.0
sr_daily = mu / sigma
sr_annual = sr_daily * np.sqrt(252)
# Standard error with non-normality correction
se_daily = np.sqrt((1/(T-1)) * (1 - gamma3*sr_daily + (gamma4-1)/4 * sr_daily**2))
se_annual = se_daily * np.sqrt(252)
# PSR for various benchmarks
for benchmark in [0.0, 0.5, 1.0]:
psr = norm.cdf((sr_annual - benchmark) / se_annual)
print(f"PSR(SR_b = {benchmark}): {psr:.4f}")
PSR as a Bayesian-Like Statement
PSR is technically frequentist. But it reads like a Bayesian posterior: “what is the probability that the true Sharpe exceeds the benchmark, given the data?” Under a flat prior on , the frequentist confidence interval and Bayesian credible interval coincide. PSR is the one-sided version of that.
This makes PSR intuitive to communicate. “We are 95% confident the true Sharpe exceeds 0.5” lands better than “the 95% confidence lower bound is 0.51” or “we reject at .” The math is the same; the framing matters.
Choosing the Right Benchmark
Three rules of thumb from practice:
Rule 1: Use a benchmark that reflects your opportunity cost. If you are evaluating a long-short equity strategy, the benchmark is whatever a 60/40 portfolio would deliver. If you are evaluating an HFT strategy, the benchmark is whatever your latency advantage should yield.
Rule 2: Report PSR against multiple benchmarks. A single number hides trade-offs. A table of PSR values for gives a fuller picture than .
Rule 3: Be honest about what PSR does not capture. If you tested 50 strategies, the PSR for the best one is overstated. If returns are autocorrelated, the PSR is overstated. If the data-generating process shifted mid-backtest, the PSR is meaningless.
The Right Reporting Standard
For any backtest report, the minimum standard should be:
- Reported Sharpe with frequency and sample size.
- Standard error, with non-normality correction.
- PSR against at least three benchmarks (typically 0, 0.5, 1.0).
- Adjusted Sharpe (Haircut) for autocorrelation.
- Deflated Sharpe for multiple testing.
PSR is the second item. It is what separates “we have a Sharpe of 1.3” from “we have a Sharpe of 1.3 with 75% confidence the true value exceeds 1.0.” The latter is information. The former is not.
The PSR vs the t-Test
If you have taken a statistics course, you might recognize the PSR formula as one-sided t-test. The connection is exact:
The PSR formulation:
Under Gaussian returns and the null , the standardized Sharpe is t-distributed with degrees of freedom:
For , the t-distribution is well-approximated by the standard normal. So:
where is the CDF of the t-distribution with degrees of freedom. The PSR formula in AFML uses (the normal CDF), which is the limit. For finite , the t-distribution is more accurate.
The difference between and is small for . For , the difference is about 1% in PSR. For typical backtests with , the difference is negligible. Use unless your backtest has fewer than 100 observations.
PSR Power Analysis
Power is the probability that PSR exceeds when the true Sharpe is some value . The power function:
Setting the inner probability to :
For , the expected value of the test statistic is:
The power is the probability that a normal random variable with this mean exceeds :
For , . For , , , :
So with these parameters, PSR has 64% power to reject the null that at . Not great. To get 80% power, you need the signal-to-noise ratio to be at least . With , this requires . For observations with i.i.d. Gaussian returns, . So . But wait, this is in the return-frequency Sharpe units. Annualized with :
Setting this to gives days, or about 6.2 years.
So 80% power requires 6+ years of daily data, even with a Sharpe gap of 1.0. For lower Sharpe gaps, you need more. This is why MBL (Minimum Backtest Length) is a useful planning tool. It tells you in advance whether your backtest will have enough power.
PSR for Non-Zero Benchmarks
The benchmark is not always zero. Three common choices:
(skill vs no skill): Tests whether the strategy has any positive edge. Weak test. Almost any long-biased strategy will beat 0.
= risk-free rate / volatility: Tests whether the strategy beats the risk-free rate. The implicit Sharpe is the information ratio against the risk-free asset.
= peer median: Tests whether the strategy is in the top half of similar strategies. Requires peer benchmarking data.
= strategy-specific hurdle: Tests whether the strategy meets its commercial hurdle (e.g., 1.0 Sharpe for an institutional mandate).
For each benchmark, PSR answers a different question. A strategy can pass PSR(0) = 0.99 but fail PSR(0.5) = 0.30. The first says “your strategy has edge over noise.” The second says “your strategy is unlikely to beat a 0.5 Sharpe benchmark.” Both are true; they address different concerns.
In practice, report PSR against the benchmark that matches your investment decision. If you are deciding whether to allocate capital, use a benchmark that reflects the alternative uses of that capital.
PSR with Bayesian Priors
If you have a prior on the true Sharpe, you can compute the Bayesian posterior probability that :
With a Gaussian prior and Gaussian likelihood (justified by CLT for the Sharpe), the posterior is also Gaussian:
with:
The posterior probability that is:
For a flat prior (), and . The posterior probability reduces to PSR. So PSR is the Bayesian posterior under a flat prior.
A non-flat prior lets you incorporate prior knowledge. If you have observed 100 quant strategies over 20 years and the prior mean Sharpe is 0.3 with prior standard deviation 0.4, the posterior adjusts the reported Sharpe toward 0.3. This is a form of shrinkage.
For most quant use cases, the flat-prior PSR is sufficient. The Bayesian version is useful when you have strong prior information about the strategy class.
Common PSR Mistakes
Five mistakes that appear frequently in practice:
Mistake 1: Using sample standard deviation instead of Sharpe standard error. The Sharpe standard error has the formula derived above. Using (the return standard deviation) gives PSR values that are 5-10x too small. This is the most common error.
Mistake 2: Forgetting the non-normality correction. For negatively skewed strategies, ignoring understates and overstates PSR. For typical short-vol strategies, the correction is 10-30%.
Mistake 3: Computing PSR with annual-frequency Sharpe but daily-frequency standard error. The scaling must be applied consistently. If is annualized, must be annualized too.
Mistake 4: Reporting PSR without specifying the benchmark. A bare “PSR = 0.95” is incomplete. The benchmark is half the statement. Always report .
Mistake 5: Using PSR for multiple testing correction. PSR assumes the strategy is the only one tested. For multiple testing, use the Deflated Sharpe Ratio. The PSR for the best of strategies is overstated by approximately .
When PSR Beats the Alternatives
Three situations where PSR is the right choice:
-
Single pre-specified strategy: You have one strategy with no parameter search. PSR answers “is the Sharpe statistically distinguishable from the benchmark?”
-
Communication with non-statisticians: PSR reads like a probability statement, which is intuitive. Confidence intervals and p-values require more explanation.
-
Risk budgeting: PSR quantifies the uncertainty in your Sharpe estimate. This is useful for sizing positions and setting risk limits.
For multiple testing, use DSR. For cross-validation diagnostics, use PBO. For parameter optimization diagnostics, use the Haircut Sharpe. PSR is one tool among many.
PSR and Minimum Backtest Length
The Minimum Backtest Length (MBL) formula in the next article is derived directly from PSR by inverting: given a desired PSR threshold, what is required? The connection:
This is the smallest such that PSR exceeds the threshold. For most practical cases (Sharpe gap of 0.5-1.0, ), MBL is 3-15 years of daily data. If your backtest is shorter than MBL, the PSR is unreliable. You cannot conclude that the strategy beats the benchmark.
A Closing Note on PSR’s Limitations
PSR is a useful diagnostic, but it is not a strategy validation. A PSR of 0.99 means your measured Sharpe is statistically distinguishable from the benchmark. It does not mean the strategy will perform in production. It does not account for regime shift, capacity constraints, or implementation issues. PSR is a single piece of a larger diagnostic stack.
The honest framing: PSR tells you whether to take the next step (out-of-sample testing, paper trading). It does not tell you whether to deploy capital. The decision to deploy is a separate question, requiring additional analysis that PSR cannot provide.
PSR vs the Sharpe Confidence Interval
An alternative to PSR is the Sharpe ratio confidence interval:
The PSR for benchmark is equivalent to checking whether is inside the 95% confidence interval (one-sided).
For , , (annualized):
PSR against : . The 95% CI does not contain 0.
PSR against : . The 95% CI does not contain 0.5.
PSR against : . The 95% CI contains 1.0.
The PSR gives a more nuanced view than the confidence interval. The CI says “the true Sharpe is between 0.418 and 2.182.” The PSR says “we are 75% confident the true Sharpe exceeds 1.0.” Both are valid; the PSR is more actionable.
For a single benchmark, the CI and PSR give similar information. For multiple benchmarks, the PSR is more compact (a single number per benchmark).
PSR for Short Backtests
For short backtests (T < 250 days), the CLT approximation underlying PSR is poor. The Sharpe estimator is not normally distributed. The t-distribution is more appropriate.
The t-distribution PSR:
where is the CDF of the t-distribution with degrees of freedom.
For , the t-distribution has heavier tails than the normal. The PSR is lower for the same data. For a 60-day backtest with Sharpe 0.1 (annualized: 1.6) and benchmark 0:
- Normal PSR:
- t-distribution PSR:
The difference is small for . For , the difference is more noticeable.
For very short backtests (), bootstrap confidence intervals are more reliable than either the normal or t-distribution approximations.
PSR with Heteroskedasticity
The PSR formula assumes constant volatility. If volatility changes over the backtest period (heteroskedasticity), the standard error formula needs adjustment.
For a strategy with volatility clustering, the Sharpe standard error is larger than the i.i.d. formula suggests. The PSR is correspondingly lower.
A simple adjustment: use the realized volatility in each sub-period and compute the weighted Sharpe:
This is the “exponentially weighted” Sharpe. The standard error is approximately .
For more rigorous treatment, use the GARCH(1,1) conditional variance. The Sharpe computed using conditional volatility is more efficient (lower variance) than the unconditional Sharpe.
PSR in Production
After deploying a strategy, you can compute PSR using the live returns. The live PSR should match the backtest PSR if the strategy is performing as expected.
If live PSR is significantly lower than backtest PSR, the strategy has degraded. Possible causes:
- Capacity (the strategy is now larger and harder to execute).
- Regime (the market has changed).
- Crowding (other traders have discovered the strategy).
- Decay (the edge has been arbitraged away).
For a deployed strategy, monitor live PSR. A persistent drop is a signal to investigate. A one-off drop is noise.
The Practical PSR Workflow
For a research project:
- Run backtest, compute Sharpe.
- Compute PSR against three benchmarks (0, 0.5, 1.0).
- If PSR(0) < 0.9, abandon. The strategy is not distinguishable from noise.
- If PSR(0) > 0.9 but PSR(0.5) < 0.5, the strategy has edge over zero but not over typical active strategies. Marginal.
- If PSR(0.5) > 0.9 but PSR(1.0) < 0.5, the strategy has edge over average but not over a strong benchmark. Promising.
- If PSR(1.0) > 0.9, the strategy has strong statistical support. Proceed to out-of-sample testing.
The PSR thresholds are conventions. Different shops use different cutoffs. The conservative cutoff (PSR > 0.95) is appropriate for high-stakes decisions; the permissive cutoff (PSR > 0.80) is appropriate for early-stage research.
PSR for Multi-Period Reports
For strategies with multiple backtest periods (e.g., 2008-2012, 2013-2017, 2018-2022), report PSR for each period separately and the combined PSR.
The combined PSR uses the concatenation of all returns. The PSR formula applies directly with .
The per-period PSR reveals period-specific risk. A strategy with high overall PSR but low PSR in the 2008-2012 period (financial crisis) has hidden regime risk. The per-period PSR surfaces this.
PSR and the Sharpe Ratio Test Statistic
A subtle point: the standard Sharpe ratio test statistic is . Under the null , this is approximately standard normal.
The PSR is . Substituting :
For daily and : .
This is the PSR for the daily Sharpe against benchmark 0. Annualized: , (essentially certain to exceed 0).
Wait, the substitution is for i.i.d. returns with . For non-zero , the variance formula is more complex (involves the SR itself).
The full PSR formula accounts for the dependence of on . The simplified formula is only accurate for small .
The Closing Reflection
PSR is the right tool for the question “is my Sharpe statistically distinguishable from a benchmark?” It is not the right tool for “should I deploy this strategy?” The latter requires additional analysis.
For a research report, PSR is one number among many. The full diagnostic stack is: PSR (significance), Haircut Sharpe (autocorrelation), DSR (multiple testing), MBL (sample size), PBO (overfitting), CPCV (cross-validation), capacity analysis (size), regime analysis (stability).
A strategy that passes all of these is genuinely validated. A strategy that passes some but not others needs more work. A strategy that passes none should be abandoned.
The honest quant researcher uses PSR as one input among many. The dishonest quant researcher reports PSR alone and declares victory.
References
- Bailey, D. H. and López de Prado, M. (2014). “The Deflated Sharpe Ratio: Correcting for Selection Bias, Non-Normality, and Multiple Testing.” Journal of Portfolio Management, 40(5), 94–107. §2 derives PSR.
- López de Prado, M. (2018). Advances in Financial Machine Learning, §14.7.2. Wiley. ISBN 978-1-119-48208-6.
- Lo, A. W. (2002). “The Statistics of Sharpe Ratios.” Financial Analysts Journal, 58(4), 36–52. Foundational for the variance formula.