Hiking elevation gain: converting a feet-based trail description to meters
I was planning an international trek using a US-written trail guide quoting elevation gain in feet, while every trail marker and local guidebook on the actual mountain used meters — converting ahead of time helped me jud
We write the way we argue on the bench: exact factor, one sharp trap, one worked example you can re-check.
I was planning an international trek using a US-written trail guide quoting elevation gain in feet, while every trail marker and local guidebook on the actual mountain used meters — converting ahead of time helped me judge the day's difficulty realistically.
Start with the exact relationship. Everything else is just arithmetic and knowing when to round.
The factor that settles arguments
This is the relationship our converters use. Screenshot it if you have to — just stop re-deriving it from a half-remembered blog post.
1 ft = 0.3048 m
Write that line once at the top of your notes. Every later arithmetic step should point back to it instead of inventing a friendlier number mid-stream.
The mistake that keeps showing up
Comparing a feet-based elevation gain figure against a meters-based one without converting, and misjudging how strenuous a hike will actually be as a result.
I still write the unit next to every intermediate value. It looks pedantic until it catches the one swap that would have shipped wrong.
- Write down the known value in ft (elevation gain).
- Confirm the target unit is really m, not a similar-looking one.
- Apply the factor: 1 ft = 0.3048 m.
- Round only at the end, to the precision your tool or spec supports.
Worked example
A trail guide describes 2,500 ft of elevation gain, and local trail markers on the mountain are all in meters.
2500 ft (elevation gain) × 0.3048 = 762 m
That's 762 m — round only to the precision your tool or spec actually needs.
If you want a second check, invert the conversion and see whether you recover the original quantity within normal rounding.
Quick reference table
| ft (elevation gain) | Calculation | m |
|---|---|---|
| 1 | 1 × 0.3048 | 0.3048 |
| 2 | 2 × 0.3048 | 0.6096 |
| 5 | 5 × 0.3048 | 1.524 |
| 10 | 10 × 0.3048 | 3.048 |
Use the table for speed once you trust the factor. Do not use it as a substitute for understanding which definition of the unit you are on.
Why the exact number matters
Elevation gain is one of the biggest predictors of how hard a hike actually feels — misjudging it by mixing units can mean being caught out on a much longer, harder day than planned.
Precision is not about showing off decimals. It is about making sure the shopping list, the machine setting, and the acceptance check are all describing the same physical quantity.
Pocket recap
Multiply feet by 0.3048 to get meters — 2,500 ft of gain is about 762 m, a solidly strenuous day hike by most standards.
Keep the converter link nearby for the next time the same debate shows up in a group chat. Re-typing the factor from memory is how the wrong cousin of a unit sneaks back in.
Try the converters mentioned in this article
FAQ
What is the exact ft (elevation gain) to m factor here?+
1 ft = 0.3048 m
Should I round partway through the calculation?+
No — carry full precision through the multiplication and round only the final answer, to the precision your tool, gauge, or spec actually supports.
What's the single biggest mistake people make with this conversion?+
Comparing a feet-based elevation gain figure against a meters-based one without converting, and misjudging how strenuous a hike will actually be as a result.
This article was written by The Turbo Unit Converter engineering desk (Applied units & field metrology) and last reviewed on 2026-07-16 against NIST SP 811 and the BIPM SI Brochure. Read our full editorial policy.