> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/tools/compare.md).
# Compare
Compare two layers on a Felt map with a swipe divider, such as before-and-after imagery.
Compare splits the map with a divider that you drag across it. You choose which layers appear on the left, on the right, or on both sides, such as last year's imagery on one side and this year's on the other, then swipe to see what changed. Anyone who can open the map can use Compare in view or edit mode. Compare isn't available in embeds.
## Compare two layers with a swipe
1. Right-click the map and click **Compare**. A divider appears down the middle of the map, and the **Compare** panel opens.
2. In the **Compare** panel, next to each layer or layer group, click **Left of the divider**, **Both sides**, or **Right of the divider**.
3. Drag the divider across the map to swipe between the two sides.
By default, the top layer or group in the legend appears on the right, and the next one appears on the left. All other layers and the basemap appear on both sides. A layer that's turned off in the legend doesn't show on either side.
To end the comparison, click **Stop comparing** at the top of the **Compare** panel.
## Share a comparison
A comparison is visible only to you. Other people see the map as usual. To show someone your comparison, click **Copy compare link** at the top of the **Compare** panel. The link opens the map to your current view, with the same layers on each side. People who open it need access to the map. See [Share a map](/share/share-a-map.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.felt.com/tools/compare.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
