## How to Plan a Bikepacking Route in Seven Stages Here is how to plan a bikepacking route, end to end: choose the shape of the trip, choose an app, draw the line, verify every segment, budget the days, map water and camp, then load the file onto a device you can follow and carry a fallback. Seven stages. Drawing the line is the easy one. Most route-planning advice stops at the tutorial — here is where to click, here is how to export. That is the half a router already does for you. **The hard half is that a routing engine will happily draw a magenta line down a Forest Service road that has been gated for years, or across a creek with no bridge.** The engine does not know. It is reading a database. We would put it plainly: the most common cause of a ruined bikepacking trip is not a mechanical and it is not the weather. It is a route nobody checked. Everything below is organized around that — draw, then verify, then budget, then load, then carry a fallback. **1. Shape** — days, loop or point-to-point, and how you get to the start. Decide this before you open a map. **2. App** — pick one planning tool and learn it properly. Three subscriptions and no fluency is the worst outcome. **3. Draw** — build the file, snapping to roads where the router behaves and drawing manually where it does not. **4. Verify** — every unpaved segment gets checked against satellite imagery and a second source. This is the stage people skip. **5. Budget** — set daily distance from load, surface and climbing, not from what you ride at home unloaded. **6. Resources** — waypoint every water source, store and campsite, then check which ones are seasonal. **7. Load and back up** — offline maps downloaded and tested, route on the device, and one copy that does not need a battery. ## Start With the Shape of the Trip, Not the Map The shape is three decisions: how many days you actually have on the bike, whether the route is a loop or a point-to-point, and how you reach the start and leave the finish. Every one of those constrains the map more than the map constrains them. A loop needs no shuttle and no second car, which is why most weekend routes are loops. A point-to-point usually rides better — you never repeat ground — but it needs a train, a shuttle or a friend. An out-and-back is the least fashionable and the most forgiving: turn around at any point and you still had a trip. **The most common mistake here is picking the route first and discovering the logistics afterward.** A gorgeous 180-mile point-to-point is not a three-day trip if the finish town has no bus and you left the car 180 miles away. Decide the shape, then look for routes that fit it. If this is your first trip, our guide to [planning your first bikepacking trip](/posts/your-first-bikepacking-trip-planning) covers the pre-map decisions in more depth, and the [best beginner bikepacking routes in the US](/posts/best-beginner-bikepacking-routes-us) are worth riding before you design your own. ### The worked example Throughout this guide we will plan one hypothetical trip: **a three-day gravel loop out of a small national forest gateway town.** Friday afternoon start, two nights out, back to the car Sunday evening, one small town on route for resupply. The loop is invented for the example — we are not describing a ride we did, and none of the numbers below are measurements. They are planning assumptions, which is what you will be working with too. ## Choosing Your Route Planning and Navigation App We compare [the best bikepacking navigation apps](/posts/best-bikepacking-navigation-apps) in detail elsewhere in this series, but the short version is that three tools cover almost everyone, and the differences that matter are about layers and exports, not about which map looks nicer. **Ride with GPS** is the strongest general-purpose drawing tool for mixed road and gravel. [BIKEPACKING.com's route planning guide](https://bikepacking.com/plan/route-planning-guide/) calls it "our favorite amongst this grouping," specifically for its toolset and basemap layers. On its [plans page](https://ridewithgps.com/pricing), as of September 2026, the free Starter tier does not include downloadable offline maps or turn-by-turn voice navigation — both begin at the Basic tier. [Ride with GPS's Premium page](https://ridewithgps.com/premium) lists climb-aware estimated ride times, extra map layers and custom spoken cues as Premium features; heatmaps start earlier, with 7- and 30-day mobile heatmaps on the Basic tier and full global and all-time access at Premium. **Komoot** is the better tool for discovery and for staged trips. [Komoot's Premium page](https://www.komoot.com/premium) describes a multi-day planner that splits a route into daily stages, plus sport-specific map layers and weather on route. Its [2026 feature releases](https://support.komoot.com/hc/en-us/articles/10621431252250-All-komoot-Feature-Releases-2026) note that you can download an arbitrary area of the map by selecting it in the viewport, with Premium or the World Pack. **Gaia GPS** is the one we reach for when land ownership and terrain matter more than turn-by-turn. Its map catalog is the selling point; [Gaia's help center states that downloading maps for offline use requires a Premium Membership](https://help.gaiagps.com/hc/en-us/articles/360047131513-Download-Maps-for-Offline-Use). The tradeoff is honest: none of these is free once you leave cell coverage. **The mistake is collecting subscriptions instead of fluency.** Pick the tool whose export and offline behavior you understand cold, and use the others as free second opinions in the browser. ## Building the Route File Itself Now the drawing. If you have never thought about [how to build a GPX route](/posts/how-to-build-gpx-route-bikepacking) beyond clicking "export," it is worth knowing what is actually inside the file, because devices treat the parts differently. A GPX file can hold three kinds of thing. Per [the GPX format specification](https://en.wikipedia.org/wiki/GPS_Exchange_Format), a **track** is an ordered list of points describing a path — a dense breadcrumb; a **route** is an ordered list of waypoints leading to a destination — a sparse "go via here, then here"; and a **waypoint** is a single point of interest. For bikepacking you almost always want the dense version: a track that says exactly where the line goes, plus separate waypoints for water, camp and resupply. Draw with the auto-router where it behaves and take manual control where it does not. BIKEPACKING.com's guide describes the failure and the fix: when the routing tool will not complete a line and instead reroutes around, "simply click UNDO, and then use the DRAW LINES tool to manually bridge the gap," and notes that [this often happens at water crossings](https://bikepacking.com/plan/route-planning-guide/). **A router that refuses to connect two segments is frequently telling you something true about the ground.** Before you export, read the elevation profile once, slowly. Look for climbs stacked at the end of a day, and for flat sections that are flat because the route follows a river — which often means gates, private land or a washed-out crossing. We build one file per riding day rather than one file for the whole trip, named plainly, like `day1-forest-loop.gpx`. Multi-day tracks make on-device progress and remaining-distance readouts far less useful, and a single corrupt file cannot cost you the whole trip. ## Surfaces: What the Map Says vs What You Ride This is the section that separates a good route from a bad one, and it is the one people skip. The problem with finding real gravel is that "unpaved" covers everything from smooth county road to a boulder-strewn wash, and the map often cannot tell you which. OpenStreetMap — the data behind most cycling routers — does try. The [OSM wiki's bicycle page](https://wiki.openstreetmap.org/wiki/Bicycle) says `surface`, `smoothness`, `tracktype`, `mtb:scale` and `incline` should be used to indicate whether a way suits bicycles, and it admits the core difficulty directly: bicycle routers find it hard to suggest tracks and paths because "a wide range of conditions (path surface, incline) can make them unsuitable for some or all types of bicycles." The tags are also uneven. [OSM's smoothness key](https://wiki.openstreetmap.org/wiki/Key:smoothness) runs from `excellent` down through `bad`, `very_bad`, `horrible`, `very_horrible` and `impassable`, and the wiki notes that part of the community objected to the key over a lack of verifiability. [Tracktype](https://wiki.openstreetmap.org/wiki/Key:tracktype) describes firmness rather than shape. In practice a segment is often tagged only `surface=unpaved`, which tells you nothing you did not already assume. So verify with pictures. BIKEPACKING.com puts the rule bluntly — "just because a route shows up on one map or aerial doesn't mean it's actually there or is viable" — and notes that [the satellite layer is indispensable for identifying unpaved tracks](https://bikepacking.com/plan/route-planning-guide/), because forest roads are frequently missing from OSM layers and trails are frequently missing from the standard map layer. Popularity data is a useful third opinion with real limits. [Strava's heatmap](https://stories.strava.com/articles/strava-routes-and-heatmap-how-to-find-new-places-to-go) shows where people ride, with more heat where more people go. Which end of the scale looks brighter depends on the basemap: [Strava's own guide](https://support.strava.com/en-us/articles/16046277-a-guide-to-strava-heatmaps) says darker shades mean more heat on Light and Winter maps, and that the relationship flips on Dark, Satellite and Hybrid maps. The [OpenStreetMap wiki's page on Strava data](https://wiki.openstreetmap.org/wiki/Strava) is blunt about what heat does not prove: it "does not necessarily mean that access on that location is legal for the general public," it does not tell you the surface or difficulty, and because the data covers the past year, "if a trail was recently closed, it will still show heat for some time." Heat means somebody went there. It does not mean you may, or that you can. On our hypothetical loop, the segment worth real time is the 11-mile unpaved link between the two forest roads: satellite view at maximum zoom, a bridge check at each stream crossing, a look for the ruts and shadows that mean doubletrack rather than graded road, and a search for a trip report from anyone at all. ## Legal Access and Seasonal Closures A line can be rideable and still be closed. On national forest land, [the Forest Service's motor vehicle use maps](https://www.fs.usda.gov/r06/giffordpinchot/maps-guides/motor-vehicle-use-map-mvum) show which roads are legally open and include seasonal and wildlife closures — and forests warn that [open and close dates are subject to change without notice and can be condition-based](https://www.fs.usda.gov/r05/sierra/maps-guides) due to weather and safety. MVUMs govern motor vehicles rather than bicycles, so they are not a bicycle permission slip. What they are is an early-warning system: a road shown with a seasonal closure has a gate, a snowline, a mud season or a wildlife window attached to it, and that gate does not care what you are riding. So call the ranger district office about the specific roads you are relying on, especially in spring and late fall, and check whether the route crosses private inholdings — checkerboard ownership in the West puts private parcels inside what looks like continuous public forest. On a route with a single unpaved link between two road systems, a closure on that link is not a detour — it is a reroute of everything after it. When your plan depends on one segment, verify that segment twice and know your bypass before you leave. ## How Far to Plan Each Day The honest answer to how many miles per day to plan is that it depends on load, surface and climbing far more than on fitness. Published figures are useful as starting assumptions, not as predictions. The clearest published numbers we know come from the [Adventure Cycling Association](https://www.adventurecycling.org/blog/find-the-perfect-distance-for-your-tour/), which says a physically fit rider carrying under 20 pounds of gear — a supported-touring load — can average 60 miles a day on pavement, that with 35 to 50 pounds the average "might drop to 50 miles per day," and that the figure moves with terrain. For a first loaded tour it recommends planning "maybe one-half to two-thirds of what you already know you can ride comfortably," and a rest day for every 10 days of riding. Its [guided-tour difficulty ratings](https://www.adventurecycling.org/guided-tours/difficulty-ratings/) put the introductory level at 35 miles a day and under, on gentle terrain with less than 1,500 feet of climbing. Those are pavement-flavored numbers. **We plan gravel days at meaningfully less than the pavement equivalent** — chunky surfaces, gates, navigation stops and refilling water all eat time that a mileage figure does not show. Treat that as our planning heuristic, not a measurement. Three things to build into the number: - **Daylight, not hours.** Count backward from sunset, subtract 45 minutes for making camp, and stop planning there. - **Front-load the easy day.** Day one carries the most food and water and the least acclimatization. - **Climbing as a second axis.** A 40-mile day with 5,000 feet of gravel climbing is a bigger day than 60 flat miles. For our three-day loop, we would sketch 40 miles on Friday afternoon into evening, 55 on Saturday, and 40 back to the car on Sunday — then check that Saturday's climbing is not stacked in the last 10 miles. If those numbers feel optimistic for your current riding, that is a training question rather than a planning one, and our guide to [bikepacking fitness training](/posts/bikepacking-fitness-training) is the better place to start. ## Water, Resupply and Camp on the Map Do a separate pass over the route for mapping water and camp spots, once the line is final. Ride it in your head at planning speed and ask, at every point: where does the next liter come from, where does the next meal come from, and where do I sleep if today goes badly. **Water first, because it is the one that hurts.** Waypoint every source — spigots, campground taps, streams, stores — then work out the longest dry gap in miles and in hours. That gap sets your carrying capacity, not your comfort preference. Assume any natural source needs treating; our comparison of [water filtration systems for bikepacking](/posts/water-filtration-systems-bikepacking) covers what to carry. Mapped water is not guaranteed water. OpenStreetMap even encodes the problem: the [drinking water tag documentation](https://wiki.openstreetmap.org/wiki/Tag:amenity=drinking_water) notes that `seasonal=yes` marks a source that is turned off or removed for winter. A campground tap mapped in July is not a tap in October. Where a source is critical, find a second confirmation — a recent trip report, or a phone call to whoever manages the site. Resupply is a scheduling problem more than a mapping one: a store that exists is not a store that is open when you arrive on a Sunday afternoon. Plan to carry through at least one failed resupply; our [bikepacking resupply guide](/posts/bikepacking-resupply-guide) covers how. For camp, get the legal question right before the scenic one. [Apache-Sitgreaves National Forests' dispersed camping guidelines](https://www.fs.usda.gov/r03/apache-sitgreaves/recreation/dispersed-camping-guidelines) are typical of Forest Service rules: no more than 14 days in a 30-day period, campsites placed at least 100 feet from any stream or other water source, and sites kept within 300 feet of a roadway. Rules genuinely vary between forests and districts, and that page says the best way to find out where dispersed camping is allowed is to contact the nearest district office. We mark a primary camp and a bail-out camp roughly 8 to 10 miles earlier on every day. It costs nothing at the planning desk and converts "we have to make it" into "we have options" at 7 pm. For choosing between marked spots on the ground, our notes on [stealth camping and camp security](/posts/camp-security-stealth-camping-bikepacking) apply. ## Phone or Dedicated Device There is nothing wrong with phone-only navigation, and anyone who tells you otherwise is selling a bike computer. It works with conditions attached, and the conditions are the whole argument. A modern phone has the better screen, the better map rendering, and the app you planned in. What it does not have is a purpose-built power budget or a mount designed for washboard. Screen-on GPS navigation is one of the most expensive things a phone can do, and a phone that dies at 4 pm is also your camera, your emergency call and your resupply research. Dedicated computers trade screen quality for endurance and durability. Garmin's own support material for the Edge 1050 [gives up to 20 hours of battery life in demanding use and up to 60 hours in battery saver mode](https://support.garmin.com/en-US/?faq=l25CfzjwKp5qWhs98Youb9) — figures that assume specific settings, but that indicate the category difference. A dedicated unit also fails in useful ways: it is not carrying your text messages, and dropping it does not end the trip. Our position: **the phone is the planning and backup device, and a dedicated unit earns its price once your days are longer than your phone's battery honestly lasts.** Going phone-only is legitimate, with a mandatory accessory list — rigid mount, waterproof case, power plan. Start with our guide to [GPS navigation devices for bikepacking](/posts/gps-navigation-devices-bikepacking), then [portable chargers for your phone and GPS](/posts/navigating-with-power-the-best-portable-charger-for-your-phone-and-gps) for the part most people underestimate. ## Making It Work Without a Cell Signal There is nothing advanced about offline maps for bikepacking. They are the feature. A navigation app without downloaded map tiles becomes a blue dot on a grey background about 20 minutes after you leave town. Every major app puts this behind a paid tier, so budget for it. [Gaia GPS requires a Premium Membership to download maps for offline use](https://help.gaiagps.com/hc/en-us/articles/360047131513-Download-Maps-for-Offline-Use), and as of Android v2026.3 and iOS v2026.4 [its offline snap-to-trail routing data downloads automatically with offline maps](https://help.gaiagps.com/hc/en-us/articles/4406144762135-Offline-Snap-to-Trail-Routing). Komoot's area download by viewport selection [requires Premium or the World Pack](https://support.komoot.com/hc/en-us/articles/10621431252250-All-komoot-Feature-Releases-2026). Ride with GPS puts offline map downloads at [the Basic tier and above](https://ridewithgps.com/pricing). Download more than the corridor. A 2-mile-wide strip around your line is useless the moment you need to find a road that is not on your route — which is precisely when you need a map. We download the county or the forest, not the track. File size is the tradeoff, and it is adjustable. Gaia's own guidance on downloading large areas is to [reduce the zoom level to make a smaller file](https://blog.gaiagps.com/how-to-download-an-entire-state-map/), with maximum detail around 1:12,000. Less zoom means less storage and less detail on the ground. Put the phone in airplane mode at home, open the app cold, and navigate the route. Pan off the corridor. Zoom in on the trickiest junction. If anything renders grey, you found it in your kitchen instead of at a five-way junction at dusk. We consider this the single highest-value ten minutes in the whole planning process. ## Getting the Route onto Your Device The stage where a fully verified route dies of a file-transfer problem in a trailhead parking lot is loading a GPX onto a Garmin, Wahoo or Coros. Do it at home, then confirm the route actually opens on the device. **Garmin.** The reliable path is importing the GPX into Garmin Connect on web or mobile and syncing it to the head unit wirelessly, which also normalizes the file. Riders on [Garmin's own forums](https://forums.garmin.com/sports-fitness/cycling/f/edge-1030-plus/230983/importing-courses-into-newfiles) describe the direct alternative: connect the unit by USB, drop the file into the NewFiles folder, and restart the device, which converts it into a course. ``` /Garmin/NewFiles/day1-forest-loop.gpx ``` **Wahoo.** [Wahoo's support documentation](https://support.wahoofitness.com/hc/en-us/articles/115000368190-Sync-download-third-party-routes-to-ELEMNT-computers) describes linking a third-party account — Komoot, Ride with GPS, Strava or Trailforks — to your Wahoo account in the ELEMNT app, then syncing routes in bulk over Wi-Fi or one at a time over Bluetooth. For a one-off file, [Wahoo also documents importing a GPX, TCX or FIT file](https://support.wahoofitness.com/hc/en-us/articles/20582927265042-Import-and-delete-routes-to-ELEMNT-computers) by opening it into the ELEMNT app from your phone's downloads. **Coros.** Download the GPX on your phone and open it with the COROS app, then sync. [COROS advises keeping routes under 2,000 kilometers, under 100 MB and fewer than 200 waypoints](https://support.coros.com/hc/en-us/articles/26895703330196-Downloading-and-Syncing-Routes-to-DURA) for reliable processing — a real argument for splitting a long trip into daily files. Then check the device screen: correct day, correct total distance, correct start point. If the distance is wrong, the file is wrong. For the unit itself, our roundup of the [best cycling computers for bikepacking](/posts/best-cycling-computers-bikepacking) covers the tradeoffs. ## The Analog Backup There is nothing nostalgic about a paper map and compass backup. It is the only navigation system on your bike that does not share a failure mode with the others — one crash, one soaked phone, one dead battery bank, and every electronic copy of your route can go at once. Free is available. [USGS US Topo maps](https://www.usgs.gov/programs/national-geospatial-program/us-topo-maps-america) are modeled on the classic 7.5-minute, 1:24,000-scale quadrangles, published as geospatial PDFs and produced from national GIS databases. USGS says the program historically followed a three-year production cycle and that beginning in 2026 it updates maps based on changes in the underlying data instead. Current and historical maps download free from [topoView](https://ngmdb.usgs.gov/topoview/). A national forest visitor map bought at a ranger station is often the better single sheet for a gravel loop, because the whole forest road network fits on one page. That update cadence is also the limitation. **Paper will not tell you which fork of a doubletrack the route takes.** What it tells you is the shape of the terrain — which drainage you are in, which way the water runs, where the highway is — and that is exactly the information you need when the electronics are gone. Carry a compass, know the local declination, and write a cue card for each day: junction numbers, mileages between turns, water points, and the bearing to the nearest paved road. Ours lives in a plastic bag in a frame bag pocket and weighs nothing. Two copies of your route, one of which needs no battery. That is the whole rule. ## When It All Goes Wrong Good off-route recovery starts before you are off route, with two decisions made at the desk: where your bail-out points are, and what you will do when the device disagrees with the ground. Know what your unit does automatically. The [Edge 1050 owner's manual](https://www8.garmin.com/manuals/webhelp/GUID-08ACA9FC-DEE6-4C8D-8A95-F62181C512E9/EN-US/GUID-62C3249E-F56E-467B-A9DA-83D907CDF4E6.html) says you can choose Pause Navigation until you are back on course, or Re-route to pick from suggestions, and that the first rerouting suggestion is the shortest route back to the course and begins automatically after 10 seconds. That default is fine on a road ride. On a gravel loop, the shortest route back to the line can mean re-climbing a pass, or a road that does not exist. Know that it fires, and know how to stop it. The field procedure we would use is deliberately boring: 1. **Stop and mark the point.** Drop a waypoint where you are before you experiment. A known point you can return to is worth more than the ten minutes it costs. 2. **Find the last place you were certain.** Not the last turn you remember — the last junction you positively identified. 3. **Backtrack rather than improvise.** Cutting cross-country toward the line is how a wrong turn becomes a night out. 4. **Reassess the day, not the mile.** If recovery costs two hours, the plan is now a shorter day, and the bail-out camp you waypointed is the answer. The escalation ladder matters too. Being lost is not an emergency until it is combined with something else — darkness, cold, injury, no water. Our guide to [emergency communication with no cell signal](/posts/emergency-communication-no-cell-signal) covers what actually works out there, and our comparison of [satellite messengers for bikepacking](/posts/best-satellite-messengers-bikepacking) covers the devices. The broader decision framework lives in our [complete bikepacking safety guide](/posts/bikepacking-safety-complete-guide). ## If You Only Do Three Things If the full workflow is more than you have time for this week, these three carry most of the value: 1. **Verify every unpaved segment against satellite imagery and one other source.** Zoom to maximum, check each stream crossing for a bridge, and look for a trip report. This is the step that prevents the trip-ruining surprise. 2. **Download offline maps wider than your route, then test them in airplane mode at home.** Ten minutes in the kitchen, cold app, panning off the corridor. 3. **Carry the route in two forms, one of which needs no battery.** Device plus a printed map and a cue card. They fail independently, which is the entire point. ## The Route Nobody Checked Route planning looks like a drawing exercise and is actually an editing exercise. The line takes twenty minutes. The verification — surfaces, closures, water, the gap between the map and the ground — is the work, and it decides whether day two is a good day or a five-hour improvisation. Nothing here requires expensive software or a rare skill. It requires being willing to distrust a magenta line that a computer drew for you, and to spend an evening proving it before you spend three days living inside it. ## Explore the full series - [Best Bikepacking Navigation Apps: Komoot, Ride with GPS, Gaia GPS and OsmAnd Compared](/posts/best-bikepacking-navigation-apps) — Komoot, Ride with GPS, Gaia GPS, OsmAnd and Organic Maps compared by what each one is bad at. - [How to Build a GPX Route for Bikepacking: Create, Edit, Split and Merge](/posts/how-to-build-gpx-route-bikepacking) — Track vs route, splitting a file into days, merging, reversing, and cleaning up someone else’s GPX.

gps-devices

Bikepacking Route Planning and Navigation: The Complete Guide