Speed Conversion
Convert road, science, aviation, and marine speed units instantly as you type.
Convert road speed into feet traveled each second with a calculator that keeps the exact ratio behind the result. The initial direction is miles per hour to feet per second. Decimal inputs update immediately, and values stay inside the browser. Swap reverses the pair on the same page.
Feet per second appears in engineering, motion analysis, ballistics, and technical descriptions that use US customary length. The controls use ft/s, while the content spells out feet per second where that wording is clearer. Forward and reverse tables come from the shared conversion engine. Keep the unit beside every result.
Convert road, science, aviation, and marine speed units instantly as you type.
Miles per hour measures statute miles traveled during one hour. Because one mile contains 5,280 feet and one hour contains 3,600 seconds, the unit can be reduced directly to feet per second. The ft/s output is larger than the mph input for the same physical speed.
Feet per second measures feet traveled during one second and uses ft/s. It is a compound speed unit, not frames per second; the explicit ft distinguishes feet from the ambiguous abbreviation fps. This page therefore uses the unambiguous route and label.
Enter the source speed, then set mph as the starting unit and ft/s as the result. The calculator updates without a submit action. The initial selectors match the page’s road-to-feet-per-second task.
Choose Swap when a technical value starts in feet per second. Reset restores one mph and the configured direction after any experiment. Copy the result with ft/s or mph included so another reader knows which scale applies.
One mph equals exactly 22/15 ft/s because 5,280 feet divided by 3,600 seconds reduces to 22/15. Multiply mph by 22/15 to obtain feet per second. The decimal form is repeating, so the fraction is the cleaner exact relationship.
For the reverse direction, multiply ft/s by 15/22. Avoid replacing 22/15 with a short rounded decimal before the calculation, especially when the result feeds another formula. The shared engine retains the defined base factors before formatting.
These examples include low, urban, and motorway-scale values. Each uses the exact fraction before the result is rounded for display. The feet-per-second number should be about one and a half times the mph value.
A reverse example shows the reciprocal 15/22 relationship. Preserve the fractional calculation for technical work and round only the final output. Context still determines how many digits the source measurement supports.
For anyone integrating this conversion into their own project, the core logic is a single multiplication or division by the same exact fraction used above.
The snippets below use 22/15 directly rather than a rounded decimal, so results stay exact.
This JavaScript example applies the exact fraction directly to the input value.
function mphToFtPerSec(mph) {'{'}
return (mph * 22) / 15;
{'}'}
function ftPerSecToMph(ftPerSec) {'{'}
return (ftPerSec * 15) / 22;
{'}'}
// 60 mph to ft/s
mphToFtPerSec(60); // = 88Excel/Google Sheets equivalent: =A1*22/15 (forward direction) or =A1*15/22 (reverse direction).
The forward table converts values from 10 through 120 mph into feet per second. The reverse table interprets the same numeric inputs as ft/s and returns mph. Both use the shared conversion function rather than hand-entered cells.
Tables show two decimals for readability even when the exact fraction produces a repeating decimal. Use the live calculator for intermediate values or additional visible precision. A rounded table cell should not replace the exact ratio in subsequent technical calculations.
Multiply each mph value by 22/15.
mph | ft/s |
|---|---|
| 10 | 14.67 |
| 20 | 29.33 |
| 30 | 44.00 |
| 40 | 58.67 |
| 50 | 73.33 |
| 60 | 88.00 |
| 70 | 102.67 |
| 80 | 117.33 |
| 90 | 132.00 |
| 100 | 146.67 |
| 110 | 161.33 |
| 120 | 176.00 |
Multiply each ft/s value by 15/22.
ft/s | mph |
|---|---|
| 10 | 6.82 |
| 20 | 13.64 |
| 30 | 20.45 |
| 40 | 27.27 |
| 50 | 34.09 |
| 60 | 40.91 |
| 70 | 47.73 |
| 80 | 54.55 |
| 90 | 61.36 |
| 100 | 68.18 |
| 110 | 75.00 |
| 120 | 81.82 |
Using 1.47 as though it were exact introduces avoidable error; 22/15 is the exact factor. Another common problem is reading fps as frames per second, which is why this page writes ft/s and uses an unambiguous URL. State the unit in full when the audience may not know the context.
Multiplying by 15/22 in the forward direction makes the result smaller when it should be larger. Converting feet to miles without also converting seconds to hours leaves mismatched time units. Check both the direction and dimensional units.
Mistake | Effect | Check |
|---|---|---|
| Treating 1.47 as exact | Adds rounding error | Use 22/15 |
| Writing fps without context | Can mean frames per second | Use ft/s or feet per second |
| Using the reciprocal forward | Makes the result too small | Multiply mph by 22/15 |
| Converting only distance | Leaves incompatible time units | Convert miles/hour to feet/second |
The exact fraction makes this pair easy to audit independently: 5,280/3,600 reduces to 22/15. The calculator uses shared base factors that produce the same ratio, and the tables call that same code. Display rounding changes presentation, not the stored relationship.
Choose decimals according to the source measurement and final use. A speedometer reading usually does not justify many digits, while an intermediate engineering calculation may retain more. This page performs unit conversion and does not certify measurement equipment.
Frequently Asked Questions