> 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/layers/legend.md).
# Legend
Choose which layers appear in a Felt map's legend, rename categories, and add captions and layer metadata so people understand your map.
The legend is the panel on the left of a map. It lists layers and explains their colors and symbols. Felt builds it as you add and style layers. You can choose which layers appear, rename categories, and add captions. To turn a layer off or on, hover over it and click **Hide** (the eye icon) or **Show**.
The panel has two tabs. The **Legend** tab is what people viewing the map see. The **List** tab, shown in edit mode, lists every layer, layer group, and annotation so you can order and group them. See [Organize layers](/layers/organize-layers.md).
## Customize the legend
Each layer's legend settings are in the **Legend** section of its **Style** tab. Click **Edit map**, select the layer in the legend, and open the **Legend** section.
| Setting | What it does |
| ------------ | ------------------------------------------------------------------------------------------------------------ |
| **Show** | Shows or hides the layer in the legend. The layer stays on the map either way. |
| **Display** | **Standard** shows the layer's name with its swatches and category names. **Name only** shows just the name. |
| **Contents** | Opens the **Legend contents** panel, where you rename categories or classes and reorder categories. |
| **Caption** | Adds a line of text under the layer's name, such as the data's source or date. |
A layer with a Simple style shows just its name. A layer styled by an attribute, such as with Categories or Color range, lists each category or class. See [Choose a visualization type](/styling/style-vector-layers.md#choose-a-visualization-type).
A layer group has its own **Legend** section, with **Show**, **Caption**, and **Type**, which sets how people switch between its layers. See [Layer groups](/layers/organize-layers.md#layer-groups).
### Rename and reorder categories in the legend
Renaming a category changes the legend without changing your data, for example to show `Residential` for the value `RES`.
1. In the layer's **Legend** section, click the field next to **Contents**. The **Legend contents** panel opens.
2. Click a category or class name and enter the new name.
3. Optional: For a Categories style, drag a category up or down to change its place in the legend.
You can also rename and reorder categories in the **Set categories** panel, which opens when you click the **Showing** field in the style editor. See [Categories](/styling/style-vector-layers.md#categories).
### Hide a layer from the legend
Hide a layer from the legend to keep it on the map without a visibility control, such as a reference layer that should always show.
1. In edit mode, select the layer in the legend.
2. In the **Style** tab, open the **Legend** section.
3. Turn off **Show**.
To hide a whole group, turn off **Show** in the group's **Legend** section. If a layer is missing from the legend, check **Show** on both the layer and its group.
## Edit layer metadata
Layer metadata tells people where a layer's data comes from and how they can use it. Each part shows in a different place:
* Description, source, and license show when people viewing the map click **View info** next to the layer in the legend.
* Attribution shows in the map's credits in the bottom-left corner, and in **View info**.
1. In edit mode, click the layer's **···** menu in the legend.
2. Click **Actions** > **Edit metadata**.
3. Enter the details, then click **Done**.
## Use the legend to explore the map
Anyone viewing a map, even without an account, can use the legend to explore it:
* To turn a layer or group off or on, hover over it and click **Hide** (the eye icon) or **Show**.
* To show one layer and hide the rest, click the layer's **···** menu and click **Show only this**, or **Option**-click its eye icon (Mac) or **Alt**-click it (Windows). **Option**-click or **Alt**-click the same icon again to bring the other layers back.
* To zoom to a layer, double-click it in the legend.
Outside edit mode, your changes to layer visibility last only for your session. In edit mode, they change what everyone sees.
In edit mode, select several layers to style them together: **Shift**-click to select a range, or **Cmd**-click (Mac) or **Ctrl**-click (Windows) to add layers one at a time. See [Style multiple layers at once](/styling/style-vector-layers.md#style-multiple-layers-at-once). To hide or show the selected layers, press **H**.
## Show or hide the legend panel
To hide or show the legend panel, open the **Felt** menu and click **View** > **Legend**.
You can't move or resize the legend. An embed can hide the legend, and in an embed with a title, people viewing the map can click **Collapse legend** next to the title. See [Embed settings](/share/embed-a-map.md#embed-settings).
---
# 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/layers/legend.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.
