Relativistic Velocity Addition

Combine two signed collinear subluminal velocities using the special-relativistic velocity-addition formula.

Key facts

What it does
Combine two signed collinear subluminal velocities using the special-relativistic velocity-addition formula.
Formula
For collinear signed velocities, beta_out = (beta_v + beta_u) / (1 + beta_v beta_u), and v_out = beta_out c with c = 299792458 m/s.
You enter
Frame speed as a fraction of c · Object speed as a fraction of c
Worked example
Combining 0.5c and 0.75c gives about 0.9090909c, or 272538598.18 m/s.

A clearer path to an answer

From your question to a useful result

This page keeps the calculation transparent: define the goal, enter the matching values, inspect the method, and decide what the result means in your situation.

01

Goal

Combine two signed collinear subluminal velocities using the special-relativistic velocity-addition formula.

02

Inputs

Frame speed as a fraction of c · Object speed as a fraction of c

03

Method

For collinear signed velocities, beta_out = (beta_v + beta_u) / (1 + beta_v beta_u), and v_out = beta_out c with c = 299792458 m/s.

04

Next step

Calculate, review the assumptions below, then compare a related tool when the decision needs more context.

Relativistic Velocity Addition

Combine two signed collinear subluminal velocities using the special-relativistic velocity-addition formula.

Finite signed one-dimensional frame speed fraction.

Finite signed one-dimensional object speed fraction in the moving frame.

Result

Enter your values above and choose Calculate to see the result here.

Calculation map

Follow the path from input to answer

Ready to calculate
01

Inputs (2)

  • Frame speed as a fraction of c Ready
  • Object speed as a fraction of c Ready
02

Formula

For collinear signed velocities, beta_out = (beta_v + beta_u) / (1 + beta_v beta_u), and v_out = beta_out c with c = 299792458 m/s.

Bounded, transparent calculation

03

Result

  • Calculate to preview the result.
This diagram mirrors the calculator contract. It summarizes the declared inputs, formula, and returned outputs; it does not add a forecast or professional advice.

Recent runs

Your recent runs stay in this browser session only.

Formula, assumptions, and example

Formula: For collinear signed velocities, beta_out = (beta_v + beta_u) / (1 + beta_v beta_u), and v_out = beta_out c with c = 299792458 m/s.

This calculator combines two signed one-dimensional velocities as fractions of c using the special-relativistic velocity-addition relation. It returns the combined fraction and metres-per-second value while keeping acceleration, multidimensional vectors, and frame construction outside the model.

  • Both inputs are finite signed velocity fractions between -0.999999 and 0.999999, measured along one common line with an explicit positive direction.
  • The velocities describe the standard one-dimensional composition of inertial frames, so the denominator 1 + beta_v beta_u remains positive and the combined speed remains subluminal.
  • Acceleration history, transverse components, gravitational effects, simultaneity measurements, and navigation or equipment advice are outside the calculation.

Worked example: Combining 0.5c and 0.75c gives about 0.9090909c, or 272538598.18 m/s.

Displayed input contract

  • Frame speed as a fraction of c · minimum -0.999999 · maximum 0.999999
  • Object speed as a fraction of c · minimum -0.999999 · maximum 0.999999

The displayed limits are checked before the handler runs. Model-specific domain checks may also reject impossible or non-finite inputs.

Methodology: This calculator follows the WorldCalculate input, formula, precision, and boundary policy. Read the official methodology.

Calculator usage statistics

Usage of this calculator and related tools

This section counts anonymous successful Calculate submissions, not unique visitors. Counts and top tools appear only when trusted aggregate data is available; country analysis is shown only under the same condition and reporting threshold.

Waiting for trusted aggregate usage data.

Answer-first guide

How to use the Relativistic Velocity Addition for a real question

Combine two signed collinear subluminal velocities using the special-relativistic velocity-addition formula. Start with one clearly defined goal, enter values in the units shown, and keep the result attached to the assumptions below.

What this answers

This tool is useful when your question includes relativistic velocity addition, velocity transformation, Einstein velocity addition. It returns the outputs declared in the calculator contract rather than a live quote, approval, diagnosis, or professional sign-off.

What you enter

Frame speed as a fraction of c · Object speed as a fraction of c. Keep the same time period, unit system, and currency wherever the form requires comparable values.

How to check it

Run the worked example first, compare its output with the page's example, then change one input at a time. This makes an unexpected result easier to trace to a unit, boundary, or assumption.

Three checks before you rely on the answer

  1. Match the question. Confirm that the result means the quantity you need, not a similar-sounding percentage, balance, rate, or estimate.
  2. Match the inputs. Use the requested units and period, and read each hint before replacing the example values with your own.
  3. Read the boundary. Review the assumptions and limits. Both inputs are finite signed velocity fractions between -0.999999 and 0.999999, measured along one common line with an explicit positive direction.

Need a wider view? Browse Science Calculators or compare the related tools below. The WorldCalculate methodology explains how formulas, examples, limits, and revisions are reviewed.

How to use the Relativistic Velocity Addition

  1. Enter Frame speed as a fraction of c — Finite signed one-dimensional frame speed fraction. (c).
  2. Enter Object speed as a fraction of c — Finite signed one-dimensional object speed fraction in the moving frame. (c).
  3. Choose Calculate and read the result panel.
  4. Use Download PDF or Download Word to save a result sheet.

Formula

For collinear signed velocities, beta_out = (beta_v + beta_u) / (1 + beta_v beta_u), and v_out = beta_out c with c = 299792458 m/s.

This calculator combines two signed one-dimensional velocities as fractions of c using the special-relativistic velocity-addition relation. It returns the combined fraction and metres-per-second value while keeping acceleration, multidimensional vectors, and frame construction outside the model.

Worked example

Combining 0.5c and 0.75c gives about 0.9090909c, or 272538598.18 m/s.

Assumptions and limits

  • Both inputs are finite signed velocity fractions between -0.999999 and 0.999999, measured along one common line with an explicit positive direction.
  • The velocities describe the standard one-dimensional composition of inertial frames, so the denominator 1 + beta_v beta_u remains positive and the combined speed remains subluminal.
  • Acceleration history, transverse components, gravitational effects, simultaneity measurements, and navigation or equipment advice are outside the calculation.

Who uses this calculator?

  • Physics students learning special-relativity transformations
  • Science learners comparing classical and relativistic velocity addition
  • Teachers demonstrating signed frame and object velocities

When is it useful?

  • Combine two collinear subluminal velocities as fractions of c.
  • Compare the relativistic result with ordinary arithmetic addition.
  • Check signs, limiting behavior, and the speed-of-light boundary in one dimension.

Context and background

The model-first approach to science

Science calculators define a system, choose an equation, apply units and constants, and show the substitution. Effects outside that model remain outside the result.

Introductory science problem solving builds from measured quantities and idealized relationships. Those models are valuable for learning and first-pass estimates, while experiments and engineering decisions need additional evidence.

Research and review

How this guide was researched

Researched by , Founder and editorial researcher at WorldCalculate.

This guide follows the live calculator's declared inputs, formula, worked example, assumptions, validation boundaries, and source-backed methodology. The review date describes editorial review of the calculator explanation; it is not a promise that external facts or rates remain current.

Read the WorldCalculate research and methodology policy

WorldCalculate visual showing scientific measurements flowing through units, an equation, substitution, result, and limits for Relativistic Velocity Addition
A scientific estimate is easier to check when measurements, units, equation, assumptions, and limits remain visible together. An original science visual connecting measured inputs, units, equations, substitution, a reproducible result, and model limits. WorldCalculate original artwork; watermark included.

Ordinary arithmetic suggests that two velocities should be added directly, but that rule can produce a result faster than light when the inputs are large fractions of c. This calculator uses the special-relativistic one-dimensional relation beta_out = (beta_v + beta_u) / (1 + beta_v beta_u). It accepts two signed collinear velocity fractions, returns the combined fraction and its metres-per-second value, and keeps acceleration, transverse motion, and frame measurement details outside the page. The guide explains signs, frames, the formula, examples, limits, units, classical comparison, validation, and appropriate reporting.

Small WorldCalculate visual showing measurement, units, equation, substitution, result, and limits for Relativistic Velocity Addition
The model can be reproducible while the real-world conclusion still needs context and evidence. Compact science visual showing a checked calculation without turning it into a laboratory or safety conclusion. WorldCalculate original artwork; watermark included.

The narrow composition question

The page answers one defined question: what velocity fraction results when a frame moves at beta_v relative to a reference and an object moves at beta_u relative to that frame, with both velocities along one line? The handler applies the relativistic addition formula and then multiplies the combined fraction by the exact speed of light to show metres per second. It does not build a coordinate system, measure clocks, identify an observer, or infer the direction convention from a diagram.

This distinction is important because velocity is not just a number detached from a frame. The two input values must have the meanings stated by the contract before the formula is useful. The result is a transformation for a simple inertial, collinear setup. It is not a trajectory, an acceleration, a force, or a navigation instruction. If the physical problem includes turning, gravity, changing frames, or transverse components, additional mathematics is required.

  • Inputs are two signed velocity fractions.
  • The velocities are collinear in one dimension.
  • Output is a combined fraction and m/s value.
  • No trajectory or frame measurement is inferred.

Signed directions and a shared axis

Each field permits a positive or negative fraction because direction matters. The user must choose a positive direction along the common line before entering the values. A positive frame speed and a positive object speed point the same way under that convention. A negative value points the other way. Reversing the axis convention changes both signs and reverses the sign of the combined result, while the described physical arrangement can remain equivalent when every sign is changed consistently.

The page does not accept an angle or a vector, so it cannot resolve a velocity into components. A value such as -0.5 is not an instruction to subtract an arbitrary speed from a positive one; it is a signed input in a declared one-dimensional coordinate. Mixing a speed magnitude from one source with a signed velocity from another can change the question. Record the axis and frame meanings with any result that leaves the page.

  • Positive and negative values encode one axis direction.
  • Both inputs use the same line and sign convention.
  • Reversing the axis reverses both signs.
  • No transverse angle or vector is represented.

Why ordinary addition can fail

At everyday speeds, direct addition is often an excellent approximation because the product beta_v beta_u is extremely small. The denominator in the relativistic formula is then close to one, so the result looks like beta_v plus beta_u. At larger fractions of c, the denominator reduces the result relative to ordinary addition. This correction prevents a valid relativistic composition from exceeding the speed-of-light limit for subluminal inputs.

The difference is not an arbitrary cap applied after arithmetic. It is part of the transformation relation derived from the structure of special relativity. A common mistake is to add the two fractions directly and then clip any value above one. Clipping loses information and can hide an invalid interpretation. The proper method is to use the numerator and denominator together, then check that the resulting fraction remains strictly within the physical domain.

  • Direct addition is a low-speed approximation.
  • The denominator supplies the relativistic correction.
  • Do not add first and clip afterward.
  • The combined fraction remains below one for valid inputs.

The velocity-addition formula

The formula is beta_out = (beta_v + beta_u) divided by (1 + beta_v beta_u). Both beta values are dimensionless, so the numerator and denominator are dimensionless and the output is dimensionless. The metres-per-second result is obtained afterward by multiplying beta_out by c. This two-step display makes the formula auditable: a reader can check the fraction first, then check the unit conversion to an ordinary speed value.

For the supported ranges, each input has absolute value below one. The product cannot make the denominator zero in the ordinary same-sign or opposite-sign cases permitted by the bounds, and the handler explicitly checks that the denominator is positive. It also checks that the output magnitude remains below one. These guards make the branch behavior visible rather than relying on the user to recognize an invalid transformation from a strange numeric result.

  • The numerator adds signed fractions.
  • The denominator is 1 plus their product.
  • The output fraction is multiplied by c for m/s.
  • Denominator and subluminal checks are explicit.

A 0.5c plus 0.75c example

The catalog example uses beta_v = 0.5 and beta_u = 0.75. Ordinary addition would give 1.25c, which is not a permitted speed for a massive object in this model. Relativistic addition gives (0.5 + 0.75) divided by (1 + 0.5 x 0.75), or 1.25 divided by 1.375. The result is approximately 0.9090909c. Multiplying by 299792458 m/s gives about 272538598.18 m/s.

The example demonstrates the purpose of the denominator without asserting a practical experiment. It assumes the frame and object velocities are defined along one line and that the frames are inertial for the relation. It does not say how a frame reached 0.5c, how an object was launched at 0.75c in that frame, or how an observer would construct the measurement. The arithmetic result is valid only for the stated transformation setup.

  • Frame fraction: 0.5c.
  • Object fraction: 0.75c in the moving frame.
  • Direct sum would be 1.25c and is invalid.
  • Relativistic result: about 0.9090909c.

Opposite directions and cancellation

Signed inputs allow the formula to represent opposing motion. If the two fractions have opposite signs, the numerator can be smaller than either magnitude, and the result can be zero when the signed values cancel under the transformation. Zero output means the combined velocity is zero in the selected reference description; it does not mean the object has no energy, no momentum, or no motion in every frame. The frame definitions remain part of the interpretation.

The denominator also changes when the product is negative. This is why subtracting magnitudes by ordinary arithmetic is not a general substitute. For a clear comparison, write both signed fractions, apply the denominator, and state which frame each one belongs to. The calculator does not label one input as an observer's speed and the other as a laboratory measurement beyond the field names; the user supplies that semantic context.

  • Negative values represent the opposite axis direction.
  • Opposing motion can produce a small or zero combined result.
  • Zero in one frame does not mean zero in every frame.
  • Signed inputs must retain their frame meanings.

Low-speed and limiting behavior

When both input fractions are close to zero, the product in the denominator is negligible and the relativistic result approaches ordinary addition. This is a useful limiting check for classroom work. It does not justify using direct addition at arbitrary speeds. A formula can have a simple low-speed limit while still having important corrections in the range where the inputs are substantial fractions of c.

For same-direction inputs that approach the upper boundary from below, the combined result approaches one from below rather than crossing it. For opposite directions, the sign and magnitude depend on the full numerator and denominator. The field limits stop at 0.999999 and -0.999999, so the calculator never asks the handler to represent an exactly light-speed massive input. These endpoints are computational safeguards and model boundaries, not operating targets.

  • The result approaches ordinary addition at low speed.
  • Same-direction subluminal inputs remain subluminal.
  • The supported endpoints stop short of plus or minus c.
  • Limiting behavior is a contract check, not a trajectory claim.

Units and the exact c value

The input fractions are dimensionless ratios relative to c. The first result keeps that ratio visible with the unit label c. The second result multiplies the ratio by 299792458 metres per second and reports m/s. Because the speed of light is an exact SI-defined value, the conversion is reproducible. A source speed in kilometres per second must be converted to a fraction before it is entered, and a displayed m/s result can be divided by 1,000 for a separate km/s presentation if needed.

The page does not accept a mixture of metres per second and c as if they were interchangeable. Nor does it ask for a medium-dependent wave speed. The constant c belongs to vacuum and to the special-relativity model in the source contract. Sound, water waves, and light traveling through a material medium are different physical contexts. Unit labels should therefore remain attached whenever the result is copied.

  • Inputs are ratios to c.
  • The second result is beta_out multiplied by c.
  • c is exact in this SI contract.
  • Material-wave speeds are outside this calculator.

One-dimensional frame assumptions

The formula used here is the one-dimensional composition rule for collinear velocities. It assumes the relevant velocities lie along the same axis and that the frame relationship is the one represented by the inputs. The handler does not ask whether the frames are accelerating, rotating, gravitationally separated, or measured with synchronized clocks. Those details can matter in a complete relativity problem, but adding them without fields would make the output appear more general than it is.

A vector velocity transformation can contain transverse components and additional factors. That is not a missing branch in this page; it is a different contract. If an object moves at an angle, or if a frame changes direction, reduce the problem to a justified one-dimensional component only when the physical setup allows it. Otherwise define a separate vector model. The safest interpretation of this result is collinear special-relativistic composition, not universal velocity addition.

  • The frames are treated as inertial and collinear.
  • No acceleration or rotation is represented.
  • Transverse components require another formula.
  • The one-dimensional boundary is intentional.

Validation and numerical protection

Both fields require finite JavaScript numbers between -0.999999 and 0.999999. Numeric strings, missing values, NaN, positive or negative infinity, and out-of-range fractions are rejected. The visible form can guide ordinary entry, but direct calls still pass through the same pure-handler checks. The denominator and output magnitude receive their own finite and domain checks. This protects against a caller that supplies values outside the catalog even if the browser would normally prevent them.

The handler does not silently convert a positive speed magnitude into a signed value or reinterpret a number as metres per second. A validation error preserves the original semantic problem so it can be corrected. Near the endpoints, retaining the unrounded fraction is useful because the m/s display may hide a small difference after formatting. The calculator reports its mathematical result, not a measurement uncertainty or a clock-synchronization error.

  • Both fractions have finite signed bounds.
  • The denominator must remain positive.
  • The output magnitude must be below one.
  • Invalid units and types are not guessed or coerced.

Velocity is not kinetic energy

The combined velocity result describes a kinematic relation between frames. It does not provide kinetic energy, momentum, force, or time dilation. A mass field would be needed for an energy calculation, and a complete momentum or collision problem would need additional conservation and frame information. The existence of a high velocity fraction does not by itself specify the energy required to achieve it or the effect on an object.

This separation is useful when several relativity topics appear together. The velocity-addition page can provide one transformed velocity, while a separate kinetic-energy page can evaluate motion energy for a declared mass. Combining their outputs requires a defined frame and a reason for the combination. Do not treat the m/s row as an energy input without adding mass and the correct relativistic relation.

  • The output is velocity, not energy.
  • No mass or momentum is entered.
  • Frame transformation and energy accounting are separate.
  • A high speed does not specify a propulsion requirement.

How to report a transformed velocity

A reproducible report should name the reference direction, identify which frame moves relative to which, state beta_v and beta_u with their signs, show the numerator and denominator, and state the exact c convention. Include both the dimensionless combined fraction and the m/s presentation. If a source used another unit, record the conversion before the fraction was entered. This prevents a later reader from confusing a frame speed with an object speed or reversing the order of the transformation.

The report should also state that the formula is one-dimensional and collinear. If the values are hypothetical, call them a scenario rather than a measurement. If the setup includes acceleration, gravity, transverse motion, or a changing axis, identify those as reasons the simple result may not answer the full problem. A clear boundary makes the transformed number useful without presenting it as a navigation or equipment decision.

  • Name both frames and the positive direction.
  • Keep the signs and input meanings visible.
  • Show the denominator and c conversion.
  • State the collinear inertial-model boundary.

Common mistakes and comparison checks

Common mistakes include adding the fractions directly, clipping a result above one, dropping a negative sign, and using two velocities that do not belong to the stated frame relationship. Another mistake is putting a metres-per-second value into a field that expects a fraction of c. A simple check is to confirm that low-speed inputs behave nearly like ordinary addition and that same-direction valid inputs never produce an absolute fraction of one or more.

A second check is symmetry of the written operation: the numerator uses the two signed fractions and the denominator uses their product. Swapping the labels does not change the arithmetic in this one-dimensional formula, but changing which frame an input describes can change the physical interpretation. The calculator checks numbers, not the provenance of the frame definitions. Preserve that provenance in the surrounding explanation.

  • Do not use direct addition at high fractions of c.
  • Do not clip invalid results.
  • Check signs, frames, and units before calculation.
  • Arithmetic symmetry does not replace frame definitions.

A final scope checklist

Before accepting the output, verify that both inputs are signed fractions of c measured on one axis, that the frame relationship is stated, and that the denominator is included. Confirm that the combined fraction is below one in magnitude and that the m/s value uses the exact speed of light. Check zero, low-speed, same-direction, and opposite-direction examples when validating an implementation. These checks establish the transformation contract but do not validate a real measurement setup.

Finally, ask whether the physical question includes acceleration, gravity, transverse motion, clock synchronization, collision dynamics, energy, or navigation. If it does, define the additional model separately. The honest conclusion is that one-dimensional special-relativistic velocity addition was evaluated for two entered signed fractions. No trajectory, force, energy budget, equipment recommendation, or safety conclusion was produced.

  • Confirm the axis and frame meanings.
  • Apply the numerator and denominator together.
  • Keep fraction and m/s units visible.
  • Do not turn a kinematic relation into system advice.

Sequential transformations and frame order

A real problem may involve more than one frame transformation. This page evaluates one pair of collinear fractions in one operation. If a visitor wants to combine several transformations, each intermediate frame must be named and the order must be preserved. Applying one result as the next input can be mathematically useful when the frames match the formula's assumptions, but it is not automatically valid merely because the numbers are available. A changing frame, a reversed axis, or a velocity measured in a different convention can alter the meaning of the next operation.

The order of a sequence is therefore part of the data record even when the scalar expression looks symmetric in its two inputs. For one pair, swapping the labels leaves the arithmetic unchanged, but a chain of transformations has named source and target frames. The calculator does not store that graph or verify that an intermediate result belongs to the next frame. Keep each step, sign convention, and frame label visible outside the page. If the scenario includes acceleration or curved motion, the inertial one-dimensional formula may be only a local approximation and needs a separately reviewed treatment.

  • One operation represents one frame relationship.
  • A chain needs named intermediate frames.
  • Sequence order matters for a multi-step scenario.
  • Changing or accelerating frames require further analysis.

Checking the direction of a transformation

A reliable calculation starts by writing a sentence about the frames before writing numbers. For example, state that frame S prime moves at beta_v relative to frame S and that the object moves at beta_u in S prime. Then declare the positive direction. This preparation prevents a common error in which a speed is copied from a table without its frame or a sign is changed because the reader expects ordinary subtraction. The formula can evaluate the supplied fractions, but it cannot repair an ambiguous sentence.

A reverse or opposite-direction problem should be checked by changing the frame description, not by guessing which input should be negative. At low speed, a reasonable result may look familiar, which can hide a reversed convention. At high speed, the denominator makes the difference more visible but still does not identify the correct physical direction. Preserve the source and target labels, the sign convention, and each intermediate result when the number is used in a longer derivation or an educational explanation.

  • Write the frame relationship before entering values.
  • Declare the positive direction.
  • Do not infer signs from ordinary subtraction.
  • Keep source and target labels with the result.
  • Frame order belongs in the record.
  • A fraction is not a raw speed.

Frequently asked questions

What is the Relativistic Velocity Addition?

Combine two signed collinear subluminal velocities using the special-relativistic velocity-addition formula.

What is the formula for the Relativistic Velocity Addition?

For collinear signed velocities, beta_out = (beta_v + beta_u) / (1 + beta_v beta_u), and v_out = beta_out c with c = 299792458 m/s. This calculator combines two signed one-dimensional velocities as fractions of c using the special-relativistic velocity-addition relation. It returns the combined fraction and metres-per-second value while keeping acceleration, multidimensional vectors, and frame construction outside the model.

What do I need to use this calculator?

Enter Frame speed as a fraction of c, Object speed as a fraction of c, then choose Calculate.

What are the limits of this calculator?

Both inputs are finite signed velocity fractions between -0.999999 and 0.999999, measured along one common line with an explicit positive direction. The velocities describe the standard one-dimensional composition of inertial frames, so the denominator 1 + beta_v beta_u remains positive and the combined speed remains subluminal. Acceleration history, transverse components, gravitational effects, simultaneity measurements, and navigation or equipment advice are outside the calculation.

Methodology

This calculator is part of the WorldCalculate library. Its formula, example, assumptions, input bounds, and output formatting follow the official methodology.

Read the WorldCalculate methodology

Use this calculator as part of a bigger plan

These WorldCalculate collections connect this tool with related questions while keeping each calculation separate and transparent.

Keep this guide handy

Share this guide

Send the canonical WorldCalculate page to a classmate, client, teammate, or friend with the destination you already use.