> ## Documentation Index
> Fetch the complete documentation index at: https://docs.absurdrunning.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Import a shared route

> Bring a route shared by another runner or a race organizer into your library.

When someone shares a route with you — a friend, a race organizer, a coach — it comes as a **share link**. Importing it gets the full route into your library so you can plan around it.

## What gets transferred

A share link transfers everything about the route:

* The line, distance, and elevation.
* All checkpoints — aid stations, segment boundaries, named landmarks.
* Aid-station details — what's available, drop bag and crew access flags.
* Cutoff times if the original route has them.
* Design overrides (line color, marker styles) if the sender customized them.

What's **not** transferred: any plans built on top of the route. Plans are personal; only the underlying route is shared.

## Import the link

<Steps>
  <Step title="Get the share link">
    Either pasted directly to you (in a message, email, or DM), or scanned from a QR code on race materials.
  </Step>

  <Step title="Open the Routes page → Import">
    A dialog opens with a paste field.
  </Step>

  <Step title="Paste the link, click Import">
    The route is fetched and added to your library. Takes a couple of seconds.
  </Step>
</Steps>

## Naming conflicts

If you already have a route with the same name, the import gets a `(2)` suffix automatically (or `(3)`, `(4)`, etc.). Rename later from the route's edit page if you want a cleaner name.

## When imports go wrong

**"Share link not found or has expired."** The sender disabled sharing on their end, or the link was for an older route version that's been removed. Ask them to re-share.

**"Invalid share code format."** The link is malformed — usually a copy-paste issue. Check that you've got the full URL (it starts with `https://absurdrunning.com/r/`).

## Imported routes are yours

Once imported, the route is in your library and you can edit it freely — rename, change design, add or remove checkpoints, tweak aid-station info. Your edits don't affect the original sender's copy, and their later updates don't sync back to your copy.

If the sender pushes a meaningful update and you want it, the cleanest path is to import a fresh copy and copy over any of your own customizations.

## Next

Once a route is in your library, [build a plan around it](/get-started/first-plan).
