ForHosting KIT · Unit converters

Acceleration converter

9.80665 m/s² is exactly 1 g: the converter links m/s², ft/s², standard gravity and the gal through one exact SI bridge, then shows your value in all four units, ready for physics homework, vehicle tests or seismic logs. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Acceleration magnitude to convert
9.80665
Input acceleration unit
m_s2
Output acceleration unit
g
You get
Result
1
M per s2
9.80665
Ft per s2
32.1740485564
Standard g
1

Acceleration conversion between SI meters per second squared, imperial feet per second squared, standard gravity (g), and the gal used in geophysics is a recurring chore in mechanics homework, vehicle dynamics reports, seismic instrument calibration, and aerospace load specs. People search for an acceleration converter when they need a clean map among those four families, not a general multi-unit toolbox that also handles length and temperature. This capability accepts one finite amount plus from and to unit labels among m/s², ft/s², g, and gal, bridges every conversion through meters per second squared so results stay consistent, and returns the target value together with the same acceleration expressed in all four units. Unrecognized unit names are rejected with a clear validation error instead of silently guessing a nearby symbol.

How the acceleration converter maps SI, imperial, g and gal through m/s²

Start from the meter per second squared as the SI coherent unit of linear acceleration and express every other unit as a fixed factor into m/s². The international foot is defined as exactly zero point three zero four eight meters, so one foot per second squared is exactly zero point three zero four eight meters per second squared with no rounding choice.

Standard gravity gₙ is the conventional constant nine point eight zero six six five meters per second squared fixed by the CGPM and used throughout ISO and engineering tables; this converter always uses that conventional g, not a site-specific free-fall measurement that would change with latitude and altitude. The gal, named after Galileo and still common in gravimetry and seismology, is exactly one centimeter per second squared, which is zero point zero one meters per second squared. This calculator never mixes those paths ad hoc.

It multiplies the input amount by the factor of the source unit to reach m/s², then divides by the factor of the target unit to produce the result. Because every path shares the same intermediate, converting one standard g to feet per second squared and back, or comparing gal readings to SI meters per second squared, stays numerically consistent within ordinary floating-point precision.

The tool does not convert milligal or microgal as separate landings even though they are simple decimal scales of the gal, does not compute centripetal or angular acceleration from kinematics inputs, does not fetch local gravity models, and does not apply relativistic corrections. It answers only the algebraic acceleration unit conversion people mean when they type acceleration converter into a search bar and expect m/s², ft/s², g, and gal.

Where dedicated acceleration conversion shows up in real work

Secondary-school and college physics courses constantly assign problems that give linear acceleration on one scale and ask for another, often mixing SI m/s² with g-loads for elevators, roller coasters, and vehicle braking in the same worksheet. Automotive and aerospace teams report structural and ride loads in g while simulation tools and SI-native models expect meters per second squared, so a single conversion pass keeps test reports and finite-element inputs aligned.

Geophysics and seismic instrument workflows step between gal or milligal-scale readings and SI m/s² for cataloging without reimplementing factors in every spreadsheet. Construction and safety standards sometimes quote fall and vibration limits in feet per second squared while international datasheets use metric units. If you later need centripetal acceleration from speed and radius, general multi-category unit conversion, or density conversion, treat those as separate search intents and landings rather than overloading this acceleration converter page.

Physics homework and labs

Convert between m/s² and g for free-fall, elevator, and braking problems so SI answers and g-load wording stay consistent.

Vehicle and aerospace load reports

Map structural and ride accelerations among g, m/s², and ft/s² for test sheets, FEA inputs, and international specs.

Geophysics and sensor pipelines

Normalize gal-based gravimeter or seismic readings to SI m/s² for catalogs, APIs, and mixed telemetry tags.

What happens if I send an unrecognized unit?

The error message includes Unrecognized unit and lists the supported families so you can correct the label.

Is g local gravity or standard gravity?

Standard gravity only: gₙ = 9.80665 m/s² by convention. The converter does not use latitude, altitude, or measured free-fall values.

How does one gal relate to m/s²?

Exactly 0.01 m/s². One gal is defined as one centimeter per second squared.

What does it cost?

The browser tool is free and runs locally.

How many ft/s² is one g?

32.1740485564 ft/s². One standard g is 9.80665 m/s² and a foot is exactly 0.3048 m, so dividing the two gives that figure. The converter shows it alongside m/s² and gal automatically.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/conv/acceleration

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/conv/acceleration \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"amount":9.80665,"from":"m_s2","to":"g"}'
{
  "amount": 9.80665,
  "from": "m_s2",
  "to": "g"
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "conv.acceleration",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

What you send and what you get back from the API and browser form

Send three fields: amount, a finite number for the acceleration magnitude; from, a string naming the input unit; and to, a string naming the output unit. When a unit string is unknown the error message includes Unrecognized unit and lists the four supported families so clients can fix the label rather than guessing. Classic checks include nine point eight zero six six five meters per second squared becoming exactly one standard g, one foot per second squared becoming zero point three zero four eight meters per second squared, and one gal becoming zero point zero one meters per second squared. Both unit fields accept short keys and everyday words in any common casing, including m_s2 or m/s2 or meters per second squared, ft_s2 or ft/s2 or fps2 or feet per second squared, g or gn or gee or standard gravity, and gal or galileo or cm/s2. Missing fields, non-numeric amount strings, NaN, Infinity, and unrecognized unit labels fail with invalid_input and are not charged. On success the response echoes the cleaned amount, normalized from and to keys, the primary result in the target unit, the same acceleration as m_per_s2, ft_per_s2, standard_g, and gal with twelve significant digits of stable precision, the SI factors used, the formula string, and method m_s2_bridge. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.

Where dedicated acceleration conversion shows up in real work

Data pipelines that ingest mixed IoT or telemetry payloads with m/s2, g, and ft/s2 tags can call this capability once per reading instead of reimplementing the factors in every service. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.

Which acceleration units does this converter support?

Meters per second squared (m_s2), feet per second squared (ft_s2), standard gravity (g), and gal. Common aliases such as m/s², fps2, gee, and galileo are accepted; the response normalizes to short keys.

Read the full KIT documentation →