Velocity Addition Interactive Calculator

At speeds that get close to light speed, classical velocity addition fails—that's why adding two velocities of 0.9c doesn't give you 1.8c. You actually get 0.9945c. Special relativity uses a different formula to make sure nothing can go faster than light, no matter how you combine velocities. This calculator lets you see what happens when you plug in two velocities (as fractions of c) for anything involving high-speed objects—like in particle physics labs, relativistic astrophysics, or even planning trajectories for deep-space probes. You'll find the formula, a practical example, edge cases, and a FAQ for troubleshooting.

What is relativistic velocity addition?

This is the right tool for combining speeds when working with anything moving fast enough for relativity to matter. Instead of simple addition, the formula keeps the result below c every time.

Simple Explanation

If you're riding a train and throw a ball forward, you just add your speed and the ball's in basic physics. But at high speeds, nature just doesn't work like that. Relativistic velocity addition is the correction that stops you from ever getting a result above light speed, no matter how much you try to add.

📐 Browse all 1000+ Interactive Calculators

Reference Diagram

Velocity Addition Calculator

How to Use This Calculator

1. Select a Calculation Mode from the dropdown — choose between solving for combined velocity, an individual velocity, Lorentz factor, or rapidity addition.
2. Enter Velocity 1 (u) and Velocity 2 (v) as fractions of c — for example, 0.6 means 60% of the speed of light.
3. Confirm the Speed of Light value (default is 299,792,458 m/s) or set it to 1 if working in natural units.
4. Click Calculate to see your result.

<> Embed this calculator → <> Embed this animation calculator →

Velocity Addition Equations

The formula below lets you work out the combined velocity if you have two speeds that are significant compared to c.

Simple Example

A spacecraft moves at 0.6c relative to Earth. It fires a probe forward at 0.8c relative to itself.

u = 0.6, v = 0.8
u' = (0.6 + 0.8) / (1 + 0.6 × 0.8) = 1.4 / 1.48 = 0.9459c

Classical addition would predict 1.4c — impossible. The relativistic result is 0.9459c, safely below light speed.

Theory and Practical Applications

Fundamental Physics of Relativistic Velocity Addition

This formula comes directly out of the real math of special relativity. In basic, pre-relativity physics, velocities just stack: your object's velocity plus your platform's velocity equals the object's velocity relative to the ground. That works fine at low speeds, but once you're anywhere near c, that approach gives you nonsense—sometimes even numbers above c. The extra denominator (1 + uv/c²) prevents this problem. It's not just a fudge factor; it's what pops out of the Lorentz transformations. For values of u and v much lower than c, the correction is so tiny it doesn't affect normal calculations, so classical addition holds up for everyday use. But get anywhere close to light speed and this nonlinearity gets obvious; you can't cheat the limit, no matter how fast both things are going.

The idea of rapidity matters if you're working deep in this territory. Unlike velocity, rapidities add in a straightforward, linear way. That's why you often see rapidity in theoretical discussions and particle physics—the algebra just works out cleaner, especially when you're combining lots of velocities at high γ. In rapidity space, calculations are much less fiddly because you aren't running into limits and floating-point errors from stacking velocities close to c.

Particle Physics and Collider Experiments

In high-energy particle colliders, practically everything runs into relativistic effects—there's no ignoring it. For example, protons in the LHC zip around at almost c (γ ≈ 7460). If you did the math classically, two head-on protons would have a closing speed of nearly 2c. Relativity's formula puts the real number safely just below c, which matches what every decent detector actually measures. Whenever you reconstruct a particle's momentum across frame changes, use the relativistic formula or you'll wreck your calculations. Get it wrong, and the data (and expensive experiment) simply don't make sense.

Secondary particles produced from collisions will have different velocities depending on which reference frame you're interested in. Say you care about how fast a pion is moving relative to the detector, but you only know its velocity in the center-of-mass frame—the only reliable way to bridge those is this relativistic sum. Misusing classical addition gives errors that can totally throw off further analysis steps.

Astrophysical Jets and Superluminal Motion

Plasma jets from black holes and similar sources often reach Lorentz factors over 10 (v ≈ 0.995c). Observers sometimes see components moving faster than light across the sky, but that's not real—it comes from combining projection effects and relativity. If you want the actual material's velocities, especially when mixing different motion directions (like bulk jets vs. turbulence within the jet), you have to use relativistic velocity addition. It's not optional; the alternative is results that contradict every physical observation.

For instance, if a jet is headed toward us at 0.98c and has internal motions of 0.3c, stacking those gives you a maximal forward velocity of 0.9937c in the larger frame. Go classical here and you get a physically meaningless number above c—easy to spot as an error, but still a common mistake in naive calculations. Backward-moving eddies also combine per the formula, not straight subtraction.

Spacecraft Navigation and Interstellar Mission Planning

Modern spacecraft don't travel anywhere near relativistic speeds. But if you're working on theoretical studies—say, planning a lightsail mission designed to reach 0.2c—the difference between classical and relativistic addition actually starts to matter, especially if you combine several maneuvers or want accurate timing for long journeys.

If your probe gets a velocity boost from both its own engine and a gravitational assist, you need to use the relativistic formula to sum the speeds. Even at "low" relativistic speeds around 0.15c + 0.08c, the correction isn't always visually obvious, but over long voyages it accumulates. That leads to sensible mission and navigation planning—skip this step and your arrival time or communication synchronization could be off by months or more.

Worked Example: Cosmic Ray Cascade in Earth's Atmosphere

Suppose you're looking at a cosmic ray proton hitting the atmosphere at 10²⁰ eV. The Lorentz factor is huge (γ = 10¹¹). After collision, you get secondary particles like charged pions. If a pion is moving at 0.87c in the collision frame, you'll need the relativistic math to get its velocity in the Earth's rest frame.

Step 1: Identify the reference frames

Frame S: Earth rest frame
Frame S': Center-of-mass frame of the collision
The center-of-mass frame is moving at nearly c relative to Earth because of the cosmic ray's energy.

Step 2: Given values

v = 0.999999999992c (center-of-mass velocity relative to Earth)
u = 0.87c (pion velocity in center-of-mass frame)

Step 3: Apply relativistic velocity addition

u' = (u + v) / (1 + uv)
u' = (0.87 + 0.999999999992) / (1 + 0.87 × 0.999999999992)
u' = 1.869999999992 / (1 + 0.869999999993)
u' = 1.869999999992 / 1.869999999993
u' = 0.9999999999995c

Step 4: Convert to absolute velocity and compute Lorentz factor

u'_absolute = 0.9999999999995 × 299,792,458 m/s = 299,792,457.9985 m/s
β = 0.9999999999995
γ = 1/√(1 - β²) = 1/√(0.000000000001) = 1,000,000

Step 5: Classical comparison

Classical addition: u'_classical = 0.87c + 0.999999999992c = 1.869999999992c
That's not possible and should always be a red flag when it comes up.

Step 6: Physical implications

The pion's relativistic momentum: p = γmu' = 1,000,000 × 139.57 MeV/c² × 0.9999999999995c ≈ 1.396 × 10¹⁴ eV/c
Time dilation factor means that the pion's laboratory-frame lifetime is much longer than in its own rest frame—this matches what is seen in air shower experiments.

Edge Cases and Computational Considerations

When you work with velocities very close to c, numerical errors get amplified. Summing numbers extremely close to 1, you lose precision—don't be surprised if calculations start showing artifacts. If you need very high γ, use enough floating-point precision to get trustworthy results.

Rapidity is often a better parameter for these ranges. Rapidities add directly, and switching to velocity at the very end avoids many floating-point headaches. If you're building a simulation with particles at high speed, this can save you a lot of debugging grief.

If the velocities are in opposite directions, just use a negative sign for one input. The formula automatically handles it and gives you the right direction and magnitude. Watch out for user inputs that try to put v/c above 1; that's not physical and outputs won't mean anything.

Frequently Asked Questions