Does switching from meters to feet change your elevation gain?

The short answer

Switching a unit setting does not re-measure a route, recalculate its climb, or touch the elevation readings a hike was built from. Gain is calculated once, by adding up every uphill step between consecutive points along the recorded track, and that running total is fixed the moment the hike ends. Meters and feet are both just that one total, converted and rounded for whichever unit is currently selected. Toggle the setting and the label and the rounded figure change — the climb itself, and the data describing it, has not moved at all.

What the unit setting is actually doing

A unit preference is an instruction about display, not about recording. It tells the app which conversion to apply and which word to print after the number — meters or feet for elevation gain, the same way it decides kilometers or miles for distance. None of that reaches back into the elevation readings a route is built from, which is why switching the setting works exactly the same way on a hike from months ago as on one you just finished: there is no recalculating to do, only a different label going on a number that was already sitting there.

Why a round number in one unit looks odd in the other

One meter is 3.28084 feet — not 3, not 3.5, not any convenient fraction. That awkward figure is the entire reason a climb can look tidy in one unit and messy in the other. Meters come out of the metric system; feet come out of an older system of measurement, and nobody ever reconciled the two into a clean ratio afterward, so converting between them almost always leaves a remainder.

• 100 m ≈ 328 ft
• 300 m ≈ 984 ft
• 1,000 m ≈ 3,281 ft
• 500 ft ≈ 152 m
• 1,000 ft ≈ 305 m

A hike that comes out to a round number of meters climbed will, in nearly every case, land on an odd number of feet, and the reverse holds just as often. There is no elevation gain, short of rare coincidence, that converts cleanly in both directions at once. A total that looks strange after switching units has not lost accuracy — it has simply run into a conversion factor that never behaves.

The same mismatch shows up in distance, for the same reason

Distance runs into an almost identical problem switching between miles and kilometers, since a mile is 1.60934 kilometers — another ratio with no clean fraction behind it, covered on its own in the guide to switching between miles and kilometers. Elevation gain and distance are different measurements, built from different parts of a route, but they land in the same place here because both are single totals being converted through an awkward real-world ratio rather than a round one. Neither total is wrong for looking messy in a second unit; the messiness is just what an honest conversion of a real number looks like.

Things that trip people up

• Assuming a climb that reads as a decimal in feet is somehow less accurate than one that reads as a clean number in meters — a hike showing 984 ft climbed as exactly as precisely as one showing 300 m. They are the same climb, in two different units.
• Looking at the elevation profile after switching units and expecting its shape to change — it does not. The curve is the same climb; only the numbers along its axis are relabeled.
• Comparing a yearly gain total kept in meters against one kept in feet without converting one of them first — the two figures are not comparable until they share a unit.
• Treating a quick mental conversion, like dividing by three, as equivalent to the real one — 3.28084 is not 3, and the gap between the shortcut and the real conversion grows as the climb gets bigger.

Where TrailCam fits in

TrailCam draws elevation gain as a profile under the map for every route, in meters or feet depending on which you prefer, and that choice applies the same way to a hike recorded last year as to one you just finished — nothing about the recorded climb changes when you switch it. The route it comes from can be exported as GPX 1.1, which always stores elevation in meters regardless of your display setting, as part of the optional TrailCam Pro upgrade; the app itself is free to download.