Acceleration Converter

What linear acceleration units describe

Linear acceleration measures how quickly velocity changes over time. The unit changes the scale used to report that change, but it does not change the motion itself.

That is why one acceleration can be written as m/s², ft/s², Gal, mGal, or g and still describe the same change in velocity. The converter simply re-expresses the same physical rate in a different unit family.

For most physics and engineering equations, metres per second squared is the clean SI base form. A converter is helpful because real-world sources do not stay in that one format: vehicle tests often use g or mph/s, seismology and gravimetry often use Gal or mGal, and imperial specifications may still report ft/s² or in/s².

Why the sign can matter

Acceleration is a vector quantity, so positive and negative values depend on the axis convention you choose. In road, motion-control, and test contexts, a negative value is often used to represent braking or acceleration opposite to the chosen positive direction.

This converter preserves the sign so a deceleration value stays negative after unit translation. It does not decide which direction should count as positive in your system.

That distinction matters because people often say “deceleration” when they really mean a negative acceleration along one chosen axis. If your chosen positive direction is backwards instead of forwards, the exact same physical event could carry the opposite sign in your notes. The calculator keeps the sign you entered and leaves the coordinate convention to you.

Which acceleration units are most useful in practice

Use m/s² when you want the clean SI form expected by most physics, dynamics, and controls equations. Use g when you want a human-readable comparison with Earth-normal loading, such as launch, braking, or ride-comfort discussions.

Use Gal, mGal, or µGal when you are dealing with gravity surveys, seismology, or very small acceleration changes that would look awkward if you wrote them only in m/s². One mGal is one-thousandth of a Gal, and one microgal is one-millionth of a Gal, so the smaller units are useful when rounding in m/s² would hide meaningful variation.

Use ft/s², in/s², or yd/s² when your design notes or legacy specifications are imperial. Use km/h/s, km/h², mph/s, or kn/s when the audience thinks in transport or vehicle-speed terms rather than in pure SI base units.

How to read the conversion factor shown in the calculator

The result now includes the exact source-unit factor used to reach the SI base value. For example, a g-force entry is multiplied by 9.80665 to reach m/s², while a microgal entry is multiplied by 0.00000001.

That conversion-factor trace helps when you are checking a worksheet, spreadsheet, simulation input, or lab note and need to show how the acceleration unit converter moved from the source unit to the target unit. All displayed outputs are then derived from the same m/s² base value, which keeps signs and magnitudes consistent across m/s², g, ft/s², Gal, mGal, µGal, mph/s, and knot/s.

Transport-rate units are not interchangeable

A common source of mistakes is treating km/h/s and km/h² as if they were the same notation. They are both acceleration units, but they describe different-sized changes because one changes speed per second and the other changes speed per hour.

The same warning applies to mph/s and other transport-style notations. A value expressed in miles per hour per second is much larger than the same number written as miles per hour squared, because the denominator time scale is different.

This calculator keeps those transport-style units explicit so you can translate them cleanly into m/s², g, or ft/s² before using them in equations, specifications, or reports.

Worked example: converting a braking deceleration

Suppose a vehicle test report states a braking deceleration of 0.8 g and you need the value in m/s² and ft/s² for a simulation that uses those units. Enter 0.8 in the converter and select g as the source unit.

The converter multiplies 0.8 by the standard-gravity constant 9.80665 to get 7.8453 m/s². It then divides that SI base value by the foot-per-second-squared factor 0.3048, yielding 25.7327 ft/s². Both outputs preserve the original magnitude without changing the sign.

If the test report had recorded the braking value as negative (for example, -0.8 g to indicate deceleration), you would enter -0.8 instead. The outputs would read -7.8453 m/s² and -25.7327 ft/s², keeping the directional information intact for your simulation.

You can extend the same example into transport notation. The same 7.8453 m/s² is 28.2431 km/h/s, about 17.5494 mph/s, and 784.532 Gal. Those alternative forms are useful when the receiving document, test rig, or discipline uses a different reporting style than the source document.

Common use cases across industries

Automotive engineers frequently convert between g, m/s², ft/s², and mph/s when translating brake-test or launch-performance data between suppliers, simulation software, and public-facing documents. Aerospace teams use the same approach when comparing ascent loads or manoeuvre profiles reported in different unit systems.

In geophysics and seismology, the Galileo and milligal are standard units for reporting gravitational anomalies and some forms of ground acceleration. Converting them to m/s² is routine when feeding those readings into structural, physics, or controls models that expect SI input.

Transport planners and marine or aviation teams may encounter acceleration expressed as km/h/s or kn/s. A converter helps when those rates need to be compared against g-based comfort thresholds or inserted into a broader kinematics worksheet.

What this converter does not solve

Unit conversion alone does not tell you force, stopping distance, travel distance, or final speed. Those outcomes depend on additional assumptions such as mass, elapsed time, and the motion model you are using.

The page also does not substitute local gravity for standard gravity. When you convert to or from g, it uses the standard reference value 9.80665 m/s² so results stay consistent with engineering and standards-based reporting.

Use this page to translate an acceleration value cleanly, then move to a separate kinematics or dynamics calculation when you need a full answer.