Feet per second to miles per hour
One international mile contains exactly 5,280 international feet and one hour contains 3,600 seconds. Therefore mph = ft/s × 3,600 ÷ 5,280 = ft/s × 15/22, approximately ft/s × 0.6818181818. Reverse with ft/s = mph × 22/15.
This is a compound-unit conversion: feet become miles while seconds become hours. Converting only distance or only time is incomplete. A positive ft/s value should produce a smaller mph number because one foot per second is less than one mile per hour.
The symbols must keep their time denominators: ft/s, mph, and m/s. A foot or meter alone is a distance, not a speed. Unit-aware labels are especially important in datasets where values may be plausible under more than one convention.
The international foot definition used here replaced older local or survey-foot conventions for general modern measurement. Historical engineering, mapping, or archival records may identify a different foot. Preserve their metadata and use the required definition instead of silently applying the international factor to every legacy value.
Feet per second to meters per second
The international foot is exactly 0.3048 meter, and the time denominator remains one second. Use m/s = ft/s × 0.3048. Reverse with ft/s = m/s ÷ 0.3048. The factor is exact, although a measured source speed may be rounded or uncertain.
A quick check uses 10 ft/s ≈ 3.05 m/s. Keep the exact 0.3048 factor during calculation and round only the final display. Do not confuse m/s with m/s²: the first describes speed or velocity magnitude, while the second describes acceleration.
Useful reference values include 22 ft/s = exactly 15 mph and 44 ft/s = exactly 30 mph. The fraction 15/22 makes these checks immediate. For metric comparison, 100 ft/s equals exactly 30.48 m/s. Benchmarks verify scale but should not replace direct calculation from the original source.
Three worked speed examples
Input: 10 ft/s. Formula: mph = ft/s × 15/22. Calculation: 10 × 15 ÷ 22 = 6.818181818…. Result: about 6.82 mph. Interpretation: only the unit changes; the underlying rate remains the same.
Input: 25 ft/s. Formula: m/s = ft/s × 0.3048. Calculation: 25 × 0.3048 = 7.62. Result: exactly 7.62 m/s. Interpretation: the exact factor does not imply that the original observation was exact.
Input: 88 ft/s. Formula: mph = ft/s × 15/22. Calculation: 88 × 15 ÷ 22 = 60. Result: exactly 60 mph, also 26.8224 m/s. Interpretation: this reference point provides a useful reverse check for both target units.
Input: 1 ft/s. Formula: mph = ft/s × 15/22; m/s = ft/s × 0.3048. Calculation: 15/22 = 0.681818… and 1 × 0.3048 = 0.3048. Result: about 0.682 mph and exactly 0.3048 m/s. Interpretation: this baseline can verify a conversion table.
Input: 44 ft/s. Formula: mph = ft/s × 15/22. Calculation: 44 × 15 ÷ 22 = 30. Result: exactly 30 mph, or 13.4112 m/s. Interpretation: both target numbers describe the same scalar rate, and neither supplies direction or measurement context.
Speed, velocity, and measurement context
Speed is a nonnegative scalar magnitude; velocity also contains direction. Negative ft/s can represent a component along a chosen axis, but a converter cannot determine the coordinate convention or whether a sign is an error. Preserve the source's directional and reference-frame information.
Air speed, ground speed, conveyor speed, flow velocity, object speed, and sensor-derived rate can describe different physical contexts. Conversion does not account for wind, current, slip, calibration, acceleration, or measurement method. Correct units do not make unlike measurements directly comparable.
Combining motion components requires vector mathematics. A vertical component and horizontal component cannot generally be added as plain speeds; direction and axes matter. Converting each component is valid, but finding a resultant magnitude or path requires an appropriate physical model beyond scalar unit conversion.
Relative speed also requires context. Two objects moving in the same direction or opposite directions do not have one relative rate determined by converting either speed alone. Their directions and chosen reference frame must be included. Unit conversion is valid for each input, but the later physical calculation is a separate step.
Average and instantaneous values
Average speed equals total distance divided by total elapsed time. Instantaneous speed describes a moment or short sampling interval. A single ft/s value cannot reveal stops, changing motion, peak values, or the path used to produce an average.
If distance and time are available, normalize their units before division and state whether stopped time is included. The Speed Converter translates an already stated rate; it does not reconstruct motion, calculate acceleration, or validate instrument data.
Travel time under constant speed can be estimated only when distance uses compatible units and assumptions are explicit. Real motion may include acceleration, pauses, route changes, or constraints. A converted ft/s value does not prove that constant speed was maintained and should not be used alone for operational planning.
Frame rate is another separate concept. Feet traveled per second is a physical rate, while frames per second counts images or samples per second. They share the letters fps in informal writing, so spell out the intended unit. A video value of 60 fps cannot be converted to mph without a distance-per-frame relationship.
Precision, code, and reverse checks
Use unrounded values for chained calculations. Converting ft/s to rounded mph and then deriving another unit can accumulate display error. A direct conversion from the original source is preferable. Match displayed decimals to the measurement and purpose rather than exposing every calculator digit.
Software should attach units to variables, define factors relative to a consistent base, and test zero, known reference points, inverse directions, and range limits. A numerically plausible output is still wrong if a value labeled mph was treated as ft/s.
Dimensional cancellation verifies the mph formula: ft/s × 3,600 s/h × 1 mi/5,280 ft leaves mi/h. Writing units alongside factors makes an inverted ratio visible. It also documents why the recurring multiplier is derived rather than an arbitrary approximation.
A zero rate converts to zero in every supported speed unit. Infinity, missing values, and nonnumeric text are not ordinary finite speeds and require validation. Negative signed values may be useful as vector components, but the sign should not be removed automatically. The data owner must determine whether it represents direction or an error.
Using the Speed Converter safely
Select ft/s as the source and mph or m/s as the target. The converter also supports km/h and knots. Check that mph is about 0.682 times ft/s and m/s is exactly 0.3048 times ft/s, then reverse the unrounded result when needed.
The converter does not determine operating limits, stopping distance, structural loads, weather effects, safe machinery settings, or legal speed. Follow official rules, calibrated instruments, equipment manuals, engineering analysis, and qualified guidance for safety-critical decisions.
Examples here are neutral unit demonstrations, not performance recommendations. High-speed equipment, industrial processes, transport, and experiments can involve hazards and specialized standards. Use guards, procedures, qualified engineering review, and governing limits. A correct numeric conversion cannot assess the safety of a system or activity.