Compatibility · 7 min read
What "travel" actually means
Fork travel is simply how far the fork can compress before it bottoms out, measured in millimeters. A 160 mm fork can absorb more of a hit than a 140 mm fork, but that extra cushion comes with geometry trade-offs that ripple through the whole bike, not just the front wheel.
Swapping to a longer or shorter fork changes your frame's front-end height. As a rough rule of thumb, about every 20 mm of travel change shifts head angle by roughly one degree. More travel raises the front end and slackens the head angle (the bike feels more stable at speed, less eager to turn sharply); less travel does the opposite, steepening the head angle and lowering the front.
Why frame makers rate a maximum
Frame manufacturers publish a maximum fork travel rating for a reason: pushing well past it changes the bike's geometry enough to affect handling, and in some cases stresses the frame or headset in ways it wasn't designed for. Going over that published max doesn't necessarily mean instant failure, but it is a warranty-relevant line — manufacturers rate it, and running an oversized fork can complicate a warranty claim down the road.
Under-forking has limits too
It's tempting to assume a shorter fork is always "safe" since it's less aggressive than the frame's rated max, but that's not universally true. Some frames are designed around a fairly narrow travel window, and running a fork that's meaningfully shorter than what the frame was designed for can leave the geometry too steep or otherwise outside the intended range. This is why some manufacturers publish not just a maximum, but a full approved range.
Design travel vs. rated max
Separately from the hard maximum, some manufacturers also publish a "design" travel figure — the travel they actually engineered the geometry around, which may be lower than the absolute max the frame can accept. Running noticeably less travel than that design figure is a soft judgment call rather than a structural issue: the frame will happily accept a shorter fork, but the geometry will drift from what the designer intended.
Why this can't be a simple one-size-fits-all number
It might seem like you could just estimate safe travel windows from a frame's category (trail vs. enduro vs. DH) or its rear-suspension travel. In practice that guess fails often enough to be dangerous. High-pivot enduro frames are a good example: some ship stock with notably less rear-wheel travel than the fork travel they're paired with, which would trip a naive "front and rear travel should roughly match" rule even though it's the maker's own intended, tested setup. That mismatch is completely normal for that design and not a compatibility problem at all.
How BuildMyMTB checks this
Because guessing from category or rear travel produces false alarms like the high-pivot example above, the builder is deliberately conservative and only raises a flag when it has real, frame-specific data to check against:
- Rated maximum: if a fork's travel exceeds the frame's published maximum, the tool raises a warning noting it exceeds the frame's rated max — worded as "rated," not "recommended," since it's the manufacturer's own warranty-relevant figure.
- Published approved range: when a frame publishes an explicit approved minimum-to-maximum travel window, a fork outside that range in either direction is treated as an error, and the message names the range so you know exactly what's allowed.
- Under-forking without a published range: for frames that don't publish an approved minimum, the tool stays silent on shorter forks rather than guess — that's exactly the case that protects high-pivot designs like this from a false flag.
- Design travel: where a maker states a design travel figure (distinct from the rated max), running a fork more than 20 mm under that figure produces a warning, with the 20 mm itself treated as reasonable grace for a deliberately tuned build.
In short: the tool only ever errors or warns off travel numbers the frame manufacturer actually published for that specific frame. If nothing is published, it stays quiet rather than invent a rule — a missing check is safer than a wrong one.
Practical takeaways
- Check your frame's spec sheet for a maximum fork travel figure before shopping forks, not after.
- If the frame publishes an approved range rather than just a max, treat both ends of that range as real limits, not suggestions.
- Expect noticeably more or less travel than stock to change how the bike steers and feels, even if it's technically within a rated range.
- Don't assume a "reasonably close" travel number is automatically fine just because it looks similar to the frame's rear travel — check the fork spec against the frame spec directly.
Compatibility notes on this page describe what BuildMyMTB checks and are grounded in the tool's real rules. Specs vary by model and year, so always confirm against the manufacturer before you buy. This guide contains no affiliate links.