FPS to MPH Converter — Feet per Second to Miles per Hour

What does converting FPS to MPH actually do?

Feet per second (fps or ft/s) and miles per hour (mph or mi/h) both measure the same physical quantity — speed — using different combinations of distance and time. Converting between them is a unit conversion, not a calculation of anything new. The speed itself does not change; only the number used to describe it changes.

Two units exist because of scale. Feet per second gives compact, readable numbers for short distances and fast objects: a bullet at 3,000 fps, an arrow at 300 fps, a pitch at 147 fps. Miles per hour gives intuitive numbers for road travel: a 60 mph motorway limit, a 35 mph city street, a 550 mph airliner. Trying to express a motorway limit in fps (88 fps) or a bullet in mph (2,045 mph) works mathematically but loses the everyday feel that makes each unit useful in its own domain.

This converter shows the relationship four ways. The hero gauge places the value on a speedometer arc and adapts the scale to keep the needle readable. The 9-zone speed strip shows exactly which real-world band the speed falls in. The log-scale spectrum places the speed against real-world benchmarks from a slow walk to a rifle bullet. The six context cards translate the number into something you can feel — kinetic energy, fastball percentile, braking distance, Beaufort scale, Mach number, and knots.

The FPS to MPH formula (and why it is exact)

The conversion rests on two exact definitions: one mile contains exactly 5,280 feet, and one hour contains exactly 3,600 seconds. Dividing distance by time gives:

The fraction 15/22 is exact. The decimal 0.681818… repeats forever, which is why rounding it to 0.68 introduces a small error over long distances. This converter does not round the factor internally — it multiplies by 3,600 and divides by 5,280 in full double precision, then rounds only the displayed result to the precision you choose.

💡 Mental arithmetic shortcut. To go from fps to mph quickly, multiply by 2 and divide by 3, then add a little. The exact factor is 0.6818, and 2/3 is 0.6667 — close enough for a rough estimate. So 300 fps ≈ 300 × 0.6667 = 200 mph, and the exact answer is 204.55 mph. For mph to fps, multiply by 1.5 and add a touch: 60 mph × 1.5 = 90, and the exact answer is 88 fps.

The landmark conversions worth memorising

The 60 mph = 88 fps relationship is worth internalising because it appears constantly in physics problems, driving calculations, and engineering texts. It exists because 5,280 ÷ 3,600 = 22/15, and 60 × 22/15 = 88 exactly. Any speed that is a multiple of 60 mph maps to a multiple of 88 fps: 30 mph = 44 fps, 90 mph = 132 fps, 120 mph = 176 fps.

How to read the gauge

The hero gauge has three visual modes and all three show the same physical speed — the value itself. What changes is the way the scale is presented.

Needle mode is a classic speedometer arc. Color bands run from the start of the scale (walking pace) through the middle (driving speeds) to the end (ballistic speeds), and the needle sweeps across the arc from left to right as the value increases. The scale adapts automatically — at 300 fps the arc spans 0 to 400, at 3,000 fps it spans 0 to 4,000 — so the needle always sits in a readable part of the arc rather than pinned against the endpoint.

Bar mode is a horizontal spectrum. It uses the same color bands but presents them linearly, with a triangle marker above the current position. This is useful when you want to see the exact percentage position within the spectrum.

Dial mode is a circular progress arc that starts at the bottom-left (7:30 position) at value 0 and ends at the bottom-right (4:30 position) at maximum. The active portion of the arc is drawn solid while the inactive portion is semi-transparent, so you can see progress at a glance.

💡 Why three modes? The needle mode is best for reading a value against a scale. The bar mode is best for comparing against the full spectrum. The dial mode is best for getting a quick sense of "how full" the gauge is. All three are correct — pick the one that suits your mental model.

Understanding the 9-zone speed strip

The speed strip divides the entire range of possible speeds into nine categories, each corresponding to a distinct real-world context:

Understanding the log-scale spectrum

The speed spectrum is a horizontal band spanning 1 to 5,500 feet per second on a logarithmic scale. This is essential — on a linear scale, a walk at 1.5 fps and a rifle bullet at 3,000 fps would be 2,000:1 apart, which would compress every human and sports speed into less than one pixel. A logarithmic scale keeps all six decades visible at once.

The spectrum has five colour-coded zones: Human (0–30 fps), Sports (30–150 fps), Vehicle (150–400 fps), Ballistics (400–1,500 fps), and Supersonic (1,500+ fps). Markers show where common benchmarks fall (walk, jog, sprint, city, 60 mph, fastball, bow, handgun, rifle), and your current speed is marked with a pulsing indicator and tag.

The trade-off of a logarithmic scale is that equal distances represent equal ratios, not equal differences. Doubling a speed always moves the marker by the same amount regardless of where you start. This is the only way to show a 5,500:1 range on a single horizontal band.

What the six context cards compute

Each context card takes the current speed and answers a different real-world question. These are not decorative — they are the standard conversions used by practitioners in each field.

Ballistics — kinetic energy of a 55-grain projectile

The ballistic card computes kinetic energy using the standard formula E = (m × v²) / 450,437, where m is mass in grains and v is velocity in feet per second. 55 grains is a typical .223 Remington bullet weight. The result is in foot-pounds (ft-lbs), the standard unit for firearm energy in the United States. A .223 Remington at 3,000 fps produces about 1,099 ft-lbs.

Sports — percentile vs the MLB fastball distribution

The sports card compares your speed to the distribution of MLB fastball velocities, which range from about 85 mph (a slow pitch) to about 105 mph (an elite closer). The percentile is computed linearly within that range: 85 mph = 0th percentile, 95 mph = 50th percentile, 105 mph = 100th percentile.

Automotive — braking distance at 0.7g deceleration

The automotive card computes the distance required to stop from this speed assuming a constant 0.7g deceleration, which is a typical dry-road braking performance for a modern passenger car. The formula is d = v² / (2 × 0.7 × 9.81), with v in metres per second. A 60 mph car (88 fps) stops in about 52 metres (171 feet) of pure braking distance.

Weather — Beaufort wind scale

The weather card maps your speed to the 13-point Beaufort scale, the traditional maritime measure of wind intensity. Beaufort 0 is calm (under 1 mph), Beaufort 6 is a strong breeze (25–31 mph) that makes umbrellas difficult to use, Beaufort 8 is a gale (39–46 mph) that breaks twigs, and Beaufort 12 is a hurricane (73 mph and above).

Physics — Mach number, kinetic energy, crossing time

The physics card computes three values. Mach number is speed divided by the speed of sound at sea level (1,116.47 fps). Kinetic energy per kilogram is v²/2 in metres per second. Time to cross 100 metres is 100 divided by the speed in m/s.

Nautical — knots and crossing time

The nautical card computes knots (1 knot = 1 nautical mile per hour = 1.15078 mph = 1.68781 fps) and time to cross a football field (100 yards = 300 feet).

How far does that speed actually take you?

The distance visualizer on this page converts a speed into meaningful spatial comparisons. Some examples:

💡 Reality check. At 60 mph, you cover 88 feet in one second — nearly the length of a basketball court. At Mach 1 (767 mph), you cover 1,125 feet per second — over three football fields. The distance visualizer shows these numbers live as you type or drag the slider.

Deep dive: ballistics velocities in fps and mph

Muzzle velocities span a huge range, and the same bullet weight can be pushed to very different speeds depending on the cartridge and platform. Here are the standard reference velocities for common ammunition types, with both units shown:

Deep dive: sports velocities in fps and mph

⚠ Note on "fps" in broadcast sports. Broadcasters usually say "mph" for pitch and serve speed, but high-speed cameras measure in frames per second (also abbreviated "fps"). A camera recording at 1,000 fps is capturing 1,000 frames each second — completely unrelated to feet per second. If you see "fps" in a sports analytics context, always check whether it means frames or feet.

Five mistakes people make with this conversion

• Rounding the factor too early. Using 0.68 instead of 15/22 introduces an error of about 0.27% — small for a single conversion, but it compounds if you chain conversions.
• Confusing "fps" with frames per second. In video and gaming, fps means frames per second. In ballistics and physics, it means feet per second. The two are unrelated.
• Reversing the multiplication. mph = fps × 0.6818, not fps × 1.4667. The larger number is always fps, because there are more feet per second than miles per hour for the same speed.
• Assuming 60 mph is 60 fps. It is 88 fps. This is the most common sanity-check failure.
• Forgetting that mph uses statute miles. A nautical mile is 6,076 feet, not 5,280. Use the knots conversion for maritime and aviation speeds.

How accurate is this converter?

The conversion factor is exact by definition. One mile is exactly 5,280 international feet, and one hour is exactly 3,600 seconds. The ratio 3,600/5,280 simplifies to 15/22, a rational number with no rounding. The only approximation anywhere in the pipeline is the display rounding you control with the decimals selector.

Internally the tool stores values in JavaScript double-precision floating point, which has about 15–17 significant decimal digits. For any input within the tool's working range, the result is accurate well beyond the six decimals the display allows.

Privacy and data handling

Every conversion, gauge animation, chart, spectrum marker, context card calculation, and CSV export runs in your browser using vanilla JavaScript. Nothing is uploaded, logged, or stored on a server. The share link encodes the value into the URL hash, which stays on your device unless you deliberately copy it. Conversion history is stored in your browser's localStorage and can be cleared with one click.

Limitations

• The input range is 0 to 100,000 fps (about 68,181 mph). Values beyond that are rejected to keep the gauge scales readable.
• The Mach figure is a sea-level approximation and will not match the Mach number reported at altitude.
• The gauge scales adapt automatically, so tick labels change between conversions. This is deliberate — it keeps the needle in a readable part of the gauge — but two conversions cannot be compared by needle position alone.
• The context cards use fixed reference models — a 55-grain bullet, a 0.7g deceleration, the MLB fastball distribution — that are representative but not user-adjustable.
• The conversion table generator caps at 500 rows. Larger tables are better produced in a spreadsheet.

Frequently asked questions

Related converters on AIToolsPros