Feet Per Second Calculator

What Feet per Second Measures and Where It Shows Up

Feet per second, written fps or ft/s, counts how many feet something covers in one second. It is the natural speed unit for anything that moves too fast for miles per hour to feel meaningful: a baseball pitch, an arrow, a paintball pellet, water through a pipe, or a bullet.

The unit survives because the foot is still a legal US unit under American law, and its metric size is fixed by international agreement. The NIST conversion factor page gives the exact definition: 1 foot = 0.3048 meter, with no rounding. That single constant is the backbone of every conversion on this page.

Fields and ranges use fps as a safety limit. Most paintball fields chronograph markers at 300 fps or below, and archery ranges talk about arrow speed in fps because a bow shooting 300 fps covers 100 feet in a third of a second. Highway engineers, by contrast, work in mph and convert to fps only for stopping distance math, where 60 mph becomes exactly 88 fps.

The Exact Conversion Factors, Straight from NIST

Four exact relationships drive every conversion this calculator does. They are not approximations, so the results are as precise as the numbers you type in.

First, 1 foot = 0.3048 meter exactly, from the NIST Handbook 44 definition of the international foot. Second, 1 mile = 5,280 feet exactly, so 1 mile = 5,280 x 0.3048 = 1,609.344 meters exactly. Third, 1 hour = 3,600 seconds, which turns a per hour rate into a per second rate. Fourth, the international nautical mile is 1,852 meters exactly per the BIPM SI Brochure, so 1 knot = 1,852 meters per 3,600 seconds.

Combine the first three and you get the mph bridge: 1 mph = 5,280 feet per 3,600 seconds = 1.466667 fps. In the other direction, 1 fps = 3,600 / 5,280 mph = 0.681818 mph. The knot bridge works the same way: 1 knot = 1.852 km/h = 0.514444 m/s = 1.687810 fps.

Watch out for one trap. Before 2023, US surveying used a slightly longer survey foot of 0.304800609601 meters. NIST retired that unit on January 1, 2023, and this calculator uses only the international foot of 0.3048 meters, the same one every modern conversion table and the NIST Handbook 44 Appendix C now specify.

Conversion Formulas You Can Run by Hand

To go from fps to another unit, multiply by the matching factor. To come back, divide by it. The full set, exact where noted:

mph = fps x 3,600 / 5,280, which is fps x 0.681818.
km/h = fps x 0.3048 x 3.6, so km/h = fps x 1.09728 exactly.
m/s = fps x 0.3048 exactly.
knots = fps x 0.3048 x 3.6 / 1.852, which is fps x 0.592484.

Run one by hand. A hockey slap shot at 100 fps: mph = 100 x 0.681818 = 68.1818 mph, km/h = 100 x 1.09728 = 109.728 km/h, m/s = 30.48, knots = 59.2484. Flip it around: a car at 60 mph moves at 60 x 1.466667 = 88 fps, which is the number traffic engineers plug into stopping distance charts.

The km/h factor is worth memorizing because it is exact and easy: 1.09728. Multiply any fps value by 1.09728 and you have km/h with no other steps. A pellet at 500 fps is 500 x 1.09728 = 548.64 km/h.

A Reference Table of Common Speeds

The table lists speeds that come up in sports, ballistics, and driving, with every unit the calculator outputs plus the pace each speed implies over a mile and a kilometer. Pace is written minutes:seconds.

Two rows anchor the whole table. The 88 fps row is 60 mph, the highway speed that appears in driver education stopping distance problems. The 300 fps row is the paintball field cap, which reads as 204.5455 mph or 329.184 km/h, faster than any highway speed because the pellet is tiny and slows down within a few dozen feet.

Notice how pace behaves. At 100 fps you cover a mile in 52.8 seconds, a pace no human runner can hold, because world record mile pace is around 14 fps. The pace columns are what make fps concrete: they turn an abstract speed into a time you can feel.

Pace: Turning Speed into Minutes and Seconds

Pace is the reciprocal of speed, expressed as time per distance. In formulas: seconds per mile = 5,280 / fps, and seconds per kilometer = 1,000 / (fps x 0.3048) = 3,280.84 / fps. Divide by 60 to get minutes and seconds.

Work an example. At 88 fps, seconds per mile = 5,280 / 88 = 60, so the pace is 1:00.0 per mile. At 100 fps, seconds per mile = 5,280 / 100 = 52.8, which is 0:52.8 per mile, and seconds per kilometer = 3,280.84 / 100 = 32.8, or 0:32.8 per km.

The calculator formats pace as minutes:seconds.tenths, so 528 seconds reads as 8:48.0 rather than 8.8 minutes. That matches how runners and drivers read split times, and it avoids the confusion between 8.8 minutes and 8 minutes 48 seconds.

Worked Examples: Speed from Distance and Time

The calculator has a second mode for the reverse problem: you know how far and how long, and want the speed. The formula is fps = feet / seconds, and every other unit follows from it.

Example one. A pitcher throws a ball that travels 60.5 feet, the mound to plate distance, in 0.42 seconds. Speed = 60.5 / 0.42 = 144.0476 fps, which is 144.0476 x 0.681818 = 98.2143 mph. That is a big league fastball.

Example two. A car covers a quarter mile, 1,320 feet, in 14 seconds. Speed = 1,320 / 14 = 94.2857 fps = 64.2857 mph. Both directions land on the same answer because the factors are exact.

The third mode answers the distance question: feet = fps x seconds. A car at 60 mph, which is 88 fps, covers 88 x 3 = 264 feet during a 3 second glance at a phone, about three quarters of the length of a football field. That number is why distracted driving laws exist.

When to Use fps Instead of mph or m/s

Each speed unit has a home turf, and picking the right one makes the number meaningful. Miles per hour fits anything that takes minutes to cover a mile: cars, trains, cyclists. Meters per second fits physics homework and SI based engineering, because it drops straight into kinetic energy and momentum formulas without conversion.

Feet per second fits the gap in between: speeds high enough that mph feels abstract but distances short enough to measure in feet. A fastball crossing the plate, an arrow leaving a bow, water jetting from a nozzle, or a projectile in a ballistics table all read more naturally in fps. A 100 mph fastball is 146.667 fps, and a batter has about 0.41 seconds to react, a number you can feel because it is less than half a second. On the road, the same instinct explains why the NHTSA speeding page frames crash risk in stopping distance rather than top speed.

Use knots only on water or in the air. One knot is 1.852 km/h exactly, so a 30 knot boat is 50.6333 fps. Converting knot speeds to fps rarely helps, but the calculator includes it so a wind speed or boat log entry can be checked against a land based limit.

Whatever unit you start in, the calculator keeps all six outputs in sync, so a value entered in any one unit updates the other five, the pace per mile, and the pace per kilometer at once.

Common Mistakes and Rounding Traps

The most common error is treating 1.466667 as a rounded number. It is the exact decimal form of 5,280 / 3,600 = 22/15, a repeating decimal. Carrying 1.467 through a long chain of calculations drifts from the exact answer. The calculator uses the fraction form internally, so 60 mph always lands on exactly 88 fps, never 87.9998.

Second, people confuse the international foot with the old US survey foot. The survey foot was 0.304800609601 meters, about 2 parts per million longer, and NIST retired it for new work starting January 1, 2023. If an old surveying document quotes a speed or distance, check which foot it used before converting.

Third, pace and speed get swapped. A pace of 8 minutes per mile is a speed of 5,280 / 480 = 11 fps, while 8 fps is a pace of 11 minutes per mile. The larger the speed, the smaller the pace, because one is the reciprocal of the other.

Fourth, knot confusion. A knot is one nautical mile per hour, and the nautical mile is 1,852 meters, not 1,853 or 6,076 feet. The exact chain is 1 knot = 1,852 meters per 3,600 seconds = 0.514444 m/s = 1.687810 fps, and the calculator uses those exact values rather than the rough 1.688 shortcut.