Jerk converter
1 m/s³ is 0.101971621298 g/s: move a jerk value between six units when ride-comfort limits come in g/s, robot motion profiles in m/s³ and an old lab sheet in feet or inches, with every step shown. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 1
- From
- m/s3
- To
- g/s
- Result
- 0.1019716213 g/s
- Converted
- 0.1019716213
- From
- m/s³
- Value ms3
- 1
A jerk converter turns one rate-of-change-of-acceleration magnitude into another unit without spreadsheet formulas or mental factor tables. Enter a finite value plus a source unit and a target unit among metres per second cubed, feet per second cubed, standard gravity per second, centimetres per second cubed, millimetres per second cubed, and inches per second cubed; the tool returns the converted jerk, the SI intermediate in m/s³, the exact unit factor applied, and step-by-step substitution lines you can paste into a report. Vehicle dynamics engineers comparing ride comfort in g/s, robotics teams checking end-effector profiles in m/s³, and students converting homework values all need the same deterministic path.
Which jerk units are supported and how conversion works
This capability converts among six everyday jerk units that dominate vehicle dynamics, elevator ride quality, robotics trajectory planning, and laboratory kinematics work. Metres per second cubed (m/s³) is the SI coherent unit and the internal hub: every conversion multiplies the input by how many metres per second cubed equal one source unit, then divides by how many metres per second cubed equal one target unit. Feet per second cubed use the international foot of exactly zero point three zero four eight metres.
Standard gravity per second uses the conventional standard gravity g₀ of exactly nine point eight zero six six five metres per second squared, so one g/s equals nine point eight zero six six five m/s³. Centimetres and millimetres per second cubed are the SI decimal submultiples zero point zero one and zero point zero zero one. Inches per second cubed use the international inch of zero point zero two five four metres.
Same-unit requests succeed and return the input magnitude with a short message that no change of unit was required.
Practical tips, limits, and when to use this landing
Prefer sending bare numbers for value when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without currency symbols or thousand separators. Round-trip checks are straightforward: convert A to B and B back to A and confirm you recover the original within the published twelve-decimal rounding.
When teaching unit analysis, pair classic examples such as one metre per second cubed to about zero point one zero one nine seven g/s, nine point eight zero six six five m/s³ to exactly one g/s, and one foot per second cubed to zero point three zero four eight m/s³. Stay inside the absolute range so intermediate metres-per-second-cubed values cannot overflow.
This landing targets people searching for a jerk converter, m/s³ to g/s, feet per second cubed, or g per second online; it is not a general length-weight-temperature unit converter, not a speed converter, and not an acceleration-only calculator.
What you can do with it
Vehicle ride comfort thresholds
Chassis and NVH teams convert measured jerk between m/s³ and g/s so comfort limits and ISO-style profiles share one numeric language in reports.
Robot trajectory planning
Motion planners convert end-effector jerk caps from SI m/s³ into ft/s³ or in/s³ when machine tools and documentation still use US customary units.
Lab and homework kinematics checks
Students and technicians convert m/s³ experiment results to cm/s³ or g/s and compare deterministic steps against hand calculations before submission.
FAQ
How is g/s defined here?
One g/s uses standard gravity g₀ = 9.80665 m/s² exactly, so one g/s equals 9.80665 m/s³ when converted through the SI hub.
Is the jerk converter free?
The browser tool is free and runs locally.
How many g/s is 1 m/s³?
1 m/s³ is 0.101971621298 g/s. The reverse is a clean figure: 9.80665 m/s³ is exactly 1 g/s, because one g/s is standard gravity gained or lost every second.
Can I convert a negative jerk?
Yes. A negative value is accepted for motion with a direction, such as braking or a reversing robot arm, and the sign is kept in the converted result.
Which jerk units can I convert between?
Six: metres, centimetres, millimetres, feet and inches per second cubed, plus standard gravity per second. Any of them can be the starting unit and any of them the target.
Related tools
For developers — API access
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.
API endpoint
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.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/conv/jerk \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1,"from":"m/s3","to":"g/s"}'const res = await fetch("https://api.kit.forhosting.com/conv/jerk", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1,
"from": "m/s3",
"to": "g/s"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/jerk",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1,
"from": "m/s3",
"to": "g/s"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/jerk", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1,"from":"m/s3","to":"g/s"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1,"from":"m/s3","to":"g/s"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/jerk", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"value": 1,
"from": "m/s3",
"to": "g/s"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.jerk",
"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.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_abs | 1000000000000 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Unknown unit names fail with a clear invalid_input error instead of silent wrong factors.
Which jerk units are supported and how conversion works
Common aliases are accepted case-insensitively: m/s3, mps3, and metres per second cubed for m/s³; ft/s3, fps3, and feet per second cubed for ft/s³; g per second and g0/s for g/s; cm/s3 and gal/s for cm/s³; mm/s3 for mm/s³; in/s3 and ips3 for in/s³. If the name is not on that list the solver rejects the request with invalid_input naming the bad field and listing supported units, so clients never guess whether a typo produced a wrong number. Negative jerk is allowed for directed motion contexts; absolute magnitude must stay within the published one-trillion limit so intermediate products remain finite in IEEE double precision on the Worker and in the browser.
How to call the API and read the response
Value must be a finite number or a strict numeric string within absolute limits of one trillion. Wire this into dashboards, mobile clients, or batch jobs that already hold a jerk reading and only need a second unit for display, ride-comfort thresholds, or regulatory comparison without shipping floating conversion tables in every app binary. Send a JSON body with three required fields: value (aliases jerk, amount, and j), from (aliases from_unit, unit_from, and source), and to (aliases to_unit, unit_to, and target). From and to must resolve to supported unit names after alias normalization. On success the response echoes the rounded input value, canonical from and to labels, result and converted set to the same rounded target magnitude, value_ms3 as the SI intermediate, unit as the target label, factor as from-to multiplier, formula as the short equation string, message as an English summary, steps as ordered substitution lines, and supported_units as the six canonical identifiers. Failed validation—missing fields, non-finite numbers, values outside absolute limits, or an unknown unit name—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item and zero marginal unit price.
Practical tips, limits, and when to use this landing
Normalize display labels on your side if you need locale-specific spellings—this API always returns the short canonical tokens m/s³, ft/s³, g/s, cm/s³, mm/s³, and in/s³ so automated tests stay stable. Prefer this capability when both endpoints are among the six supported jerk units and you need deterministic factors and step strings; if you only need to reformat a number for a locale without changing physical unit, use a number-format capability instead. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when clients deliberately probe unknown unit names.
Technical questions
Which jerk units can I convert?
Metres per second cubed (m/s³), feet per second cubed (ft/s³), standard gravity per second (g/s), centimetres per second cubed (cm/s³), millimetres per second cubed (mm/s³), and inches per second cubed (in/s³), including common aliases such as m/s3, fps3, and g per second.
What happens if I send an unknown unit name?
The API returns invalid_input, names the bad field, and lists the supported units. The failed task is not charged.
Are results deterministic across browser and API?
Yes. Handler and widget share the same lib.js solve path with fixed conversion factors and twelve-decimal rounding, so golden examples match production.