What LETFs actually do (and why 'decay' happens)

A leveraged ETF targets a multiple (e.g. 2×, 3× or -1×) of the *daily* return of an underlying index or benchmark. That target is explicitly defined for a single day; returns over multi‑day periods are the compound result of repeated daily resets and therefore are path‑dependent.

Because the fund rebalances each day to re‑establish the leverage, the sequence of daily returns (the path) matters: swings—even when the net multi‑day move is zero—can erode an LETF’s value. This is commonly called volatility drag, volatility tax, or path‑dependence.

Modeling volatility drag — quick formulas & example

Key approximate formula

If r is the underlying daily return (small), and σ² is its daily variance, a common log‑return approximation is: E[log(1+r)] ≈ E[r] − ½·σ². For an LETF with leverage L that targets L·r daily (ignoring fees/financing), the log approximation becomes: E[log(LETF)] ≈ L·E[r] − ½·L²·σ². That L² term is why volatility drag grows faster than leverage.

Worked numeric example (practical)

Assume underlying daily arithmetic mean E[r] = 0.04% (≈10% annual), daily σ = 1% (0.01). For L = 2: daily log ≈ 2·0.0004 − 0.5·4·0.0001 = 0.0008 − 0.0002 = 0.0006. Annualized ≈ 0.0006·252 ≈ 15.1% (geometric). Naively doubling the underlying geometric return would give about 17.6%—the difference is volatility drag magnified by L². For L = 3 the drag is materially larger because the variance term is multiplied by 9. These numbers ignore expense ratios, financing, spreads and swap costs, which further reduce LETF returns.

Simple path illustration: if the index goes +10% on Day 1 and −9.0909% on Day 2 (back to the start), a 2× LETF does +20% then −18.1818% → net ≈ −1.82% over two days even though the index is flat. That is path‑dependence in action.

Choosing horizons, sizing positions, and stop rules

Treat LETFs as tactical, time‑limited instruments. Use a clearly defined horizon and design sizing and stops around the expected horizon volatility rather than long‑term buy‑and‑hold assumptions.

Horizon guidance (practical ranges)

  • Intraday to 1–5 trading days: appropriate for directional tactical bets, event trades (earnings, CPI), or volatility spikes.
  • 5–30 trading days: usable with explicit re‑entry rules and frequent re‑calibration of position size; expect larger path risk.
  • >30 days: requires explicit model and active management (rebalancing or tactical switches); most retail traders should avoid passive holds beyond this without tight rules.

Sizing and stop rules — practical method

  1. Estimate expected multi‑day volatility for your chosen horizon (use historical daily σ and scale by sqrt(days)).
  2. Decide a max portfolio risk per trade (e.g., 0.5%–2% of equity) — smaller for high leverage and less experience.
  3. Compute LETF position size so that a stop (calibrated to horizon volatility) produces the chosen portfolio risk. Use cost-aware sizing (fees, spread, rollover).
  4. If the LETF is volatile (e.g., UVXY/volatility ETNs), cap position size further (consider a haircut factor).
  5. Plan how you will act if the LETF diverges from expectation before horizon (predefine time triggers and partial close rules).

Concrete example: account $50,000, max risk 1% ($500). Trading a 2× LETF with estimated 5‑day move SD ≈ 3.5% (daily σ≈1.56%). If you want a stop 2× the 5‑day SD (~7%), position size = $500 / 7% ≈ $7,143 notional. Use a trading calculator to include fees, spread, and financing to convert notional into share quantity. (TRL's Trading Calculator automates this.)

Scenario & stress-testing: step-by-step example

Before each trade, run scenario grids: base case, best case, two adverse cases (vol spike, gap down), and a liquidation/large‑gap case. Use deterministic scenarios and at least one Monte Carlo run for longer horizons.

  1. Choose horizon and leverage (e.g., 7 days, L = 3).
  2. Estimate daily mean and σ from the recent lookback (e.g., 30–90 days) and decide stress multipliers (+50% σ for stress).
  3. Build scenarios: (A) calm: mean realized, (B) trending up: same mean, low σ, (C) choppy: mean 0, σ×1.5, (D) gap: one day −15% underlying. For each scenario compute LETF path and final PnL.
  4. Record worst case and drawdown, required margin, and probability of hitting stop using either historical sampling or Monte Carlo.
  5. If worst case exceeds your tolerable loss, reduce size, tighten the stop, shorten horizon, or do not take the trade.

Step‑by‑step numeric mini‑case: 3× LETF, 7‑day base σ = 2% (7‑day scaling), stress σ = 3%. Monte Carlo 10,000 paths: estimate median return, 5th percentile, and % of paths breaching your stop. If the 5th percentile loss > planned drawdown, reduce notional. Use TRL's Scenarios and Risk‑of‑Ruin tools to produce these outputs quickly.

TRL mini-process: LETF Tactical Framework

A short, repeatable process for every LETF trade. Call this TRL LETF Tactical Framework.

  1. Signal & horizon: define the trade trigger and exact holding horizon (hours or days).
  2. Quick data pull: compute recent mean and daily σ (30/60/90d).
  3. Scenario grid: run base, choppy, gap, and trending scenarios and record worst‑case PnL and stop breach probability.
  4. Size with costs: compute position size that makes the stop = acceptable portfolio risk (include fees/financing).
  5. Execution plan: limit/stop orders, partial‑close ladder, re‑entry rules and hard time exit.
  6. Record trade in a journal with pre‑trade plan and post‑trade review.

Each step maps to a Trading Risk Lab tool: Scenarios (scenario grids), Trading Calculator (position & stop math), Multiple Entries (scale-ins), Partial Closes (multi‑target exit), Risk of Ruin (probabilities), and Trading Journal (review).

Checklist

  • Defined horizon in calendar and trading days (absolute dates).
  • Estimated daily mean and σ from recent lookback.
  • Scenario grid with at least one stress case and gap scenario.
  • Position size computed to limit portfolio loss at stop to your risk budget.
  • Planned execution (entry type, stop type, partial closes, re‑entry rules).
  • Pre‑trade liquidity check: average daily volume and expected spread at intended size.
  • Journal entry created before execution (intent + metrics to review).

Common mistakes

  • Holding LETFs as 'supercharged buy‑and‑hold' without modeling path risk — LETFs are daily instruments.
  • Sizing by naive leverage (e.g., 'I’ll buy twice as much because it’s 2×') without adjusting stop to volatility or costs.
  • Ignoring financing, swap and roll costs that particularly hit volatility products (UVXY‑style).
  • Assuming historical low volatility will persist and not stress‑testing larger σ scenarios.
  • Failing to set absolute time exits—keeping a trade open 'until it comes back' defeats the tactical intent.

What traders usually underestimate

  • How the L² scaling of variance amplifies decay: doubling leverage quadruples the variance term in the drag formula, not double it.
  • The practical impact of intraday gaps and overnight events — a single gap can overwhelm planned P&L and stop logic.
  • Liquidity and market‑microstructure risk at scale: a thinly traded LETF can generate large slippage even on small notional sizes.
  • Behavioral risk: LETF volatility encourages micromanagement; without strict rules traders tend to deviate from plan and compound losses.

How to apply this with Trading Risk Lab

Use TRL tools in the order below to run pre‑trade checks and post‑trade reviews. Links below point to Trading Risk Lab tools that automate the calculations described earlier.

  1. Run Scenarios to build your base, choppy, gap and stress grids and produce outcome tables and break‑even win rates. (Start here — this is the best tool for LETF trades.) — Trading Risk Lab Scenarios.
  2. Open Trading Calculator to convert notional into shares, include fees, spread, expected slippage, and preview P&L at stops and targets.
  3. If you plan to scale, use Multiple Entries to plan weighted average entry, total exposure and margin requirements.
  4. If you will take partial profits, use Partial Closes to build an exit ladder and preview blended return and R multiple.
  5. Run Risk of Ruin simulations for your sized plan to estimate probability of breaching account drawdown thresholds.
  6. Record the trade pre‑plan and outcome in the Trading Journal for the post‑trade audit.

Example workflow (7‑day 3× short event trade): 1) Scenarios: simulate calm, choppy and gap down with 10k Monte Carlo paths; 2) Trading Calculator: set stop at 6% and compute shares for 1% portfolio risk; 3) Multiple Entries: divide into two fills with staggered entries if liquidity is a concern; 4) Partial Closes: plan 50% at +8%, 50% at +15%; 5) Risk of Ruin: confirm ruin probability < your threshold; 6) Execute and log in Trading Journal. (Use those TRL tool pages to run each step interactively.)

Final practical notes

LETFs are neither inherently bad nor universally appropriate — they are mathematically and operationally specialized. Use them with explicit time limits, size modestly relative to account equity and stress‑test every plan. If your intention is long‑term exposure, use unlevered instruments or construct leverage with margin/futures and an active rebalancing plan that you control.

“Think of LETFs as tactical tools: plan the trade, don’t let the trade plan you.”

Try the relevant tool

Use the Scenarios for this

If you want to apply the ideas from this article in practice, the best fit is the Scenarios.

Open Scenarios