---
title: "My style change isn't appearing on the map"
description: "Find out why a style change does not show on the map. The Style tab only applies changes after you click Save, and a few other causes can stop it."
seo:
title: "Style change not appearing"
sidebar:
label: "Style change not appearing"
---
You changed a style, but the map looks the same. The usual cause: changes on the `Style` tab don't apply until you click the save button at the bottom. Closing the panel or switching tabs first discards the changes.
This page covers the common reasons a style change doesn't appear. They apply to point, line, and polygon layers alike unless a section says otherwise.
Work through the checks in this order. Each one has its own section below.
## You haven't clicked the save button
Unlike most other settings in MangoMap, the `Style` tab uses an explicit save. Every control on the tab — colour, classification, symbol, opacity, zoom range, per-row customisation — waits until you click the save button at the bottom of the panel:
- **Vector layers** (point, line, polygon): the button is labelled `Save`.
- **Raster and WMS layers**: the button is labelled `Save Style`.
**Fix**: scroll to the bottom of the `Style` tab and click the save button. It shows `Saving…` while it saves.
If you've already closed the layer settings, your changes are lost — re-open the layer and redo them.
## You're outside the layer's zoom-visibility range
The `Visibility` slider on the Style tab restricts which zoom levels the layer renders at. If you're viewing the map outside the slider's range, the layer is invisible regardless of any style change. The range includes both ends: a layer set to `14`–`18` shows at zoom 18 and hides above it.
**Fix**: open the Style tab, check the `Visibility` slider's range, and either zoom the map into the range or extend the range. See [How to set the zoom range a layer is visible at](/docs/styling-layers/set-layer-zoom-visibility).
A symptom: you see the legend swatch update but the map shows nothing for that layer.
## The layer's visibility eye is off
If the layer-panel eye icon for the layer is off, the layer is hidden everywhere — your style change applies but isn't visible. The legend's eye icon does the same per-session.
**Fix**: open the layer panel from the map toolbar (`Manage layers`), find the layer, and click its eye icon to toggle visibility. For the persistent vs. per-session distinction, see [How the layer panel works in MangoMap](/docs/managing-layers/concepts-layer-panel).
## Another layer draws on top of it
Layers higher in the layer panel draw on top of layers below them. A polygon layer with an opaque fill hides every point, line, and polygon under it. A thick line layer can hide points on the same streets.
**Fix**: drag the layer you changed above the layer that covers it. Or lower the covering polygon layer's fill opacity. See [How to reorder layers on the map](/docs/managing-layers/reorder-layers).
## The features fall in a hidden or unexpected category or class break
When you colour by a text field, features whose value has no row of its own use the `Other` row. Features with no value use the `Null` row. If either row is hidden, those features don't draw. When you colour by a numeric field, features with no value don't draw. With class breaks, features below the lowest class break don't draw either. Features above the highest class break take its colour.
This works the same for markers, lines, and polygon fills.
**Fix**:
- **Text field (categories)** — expand `Customise categories` and check that the features' values are listed and not hidden. If a value is missing, pick the field again to rebuild the list.
- **Numeric field (class breaks)** — expand `Customise Class Breaks` and check the lowest range. Change the classification method, or lower the start of the first class break. See [My classification produced empty buckets or weird breaks](/docs/styling-layers/troubleshoot-classification-empty-buckets).
## Still not appearing
If none of these explains it, check:
- **Permission to edit the map** — if your role is `Viewer` or your access group has only `View` on the map, the Style tab shows the controls disabled. Contact the map owner or an admin.
- **The wrong layer** — multi-layer maps make it easy to style the wrong layer. The layer name is shown at the top of the settings panel; double-check it.
Then refresh the page (you lose unsaved changes) and try again. If the change still doesn't appear, report it to MangoMap support.
## Related troubleshooting
- [My classification produced empty buckets or weird breaks](/docs/styling-layers/troubleshoot-classification-empty-buckets)
- [My colour ramp is the wrong way round](/docs/styling-layers/troubleshoot-colour-ramp-reversed)
If you've already closed the layer settings, your changes are lost — re-open the layer and redo them.
## You're outside the layer's zoom-visibility range
The `Visibility` slider on the Style tab restricts which zoom levels the layer renders at. If you're viewing the map outside the slider's range, the layer is invisible regardless of any style change. The range includes both ends: a layer set to `14`–`18` shows at zoom 18 and hides above it.
**Fix**: open the Style tab, check the `Visibility` slider's range, and either zoom the map into the range or extend the range. See [How to set the zoom range a layer is visible at](/docs/styling-layers/set-layer-zoom-visibility).
A symptom: you see the legend swatch update but the map shows nothing for that layer.
## The layer's visibility eye is off
If the layer-panel eye icon for the layer is off, the layer is hidden everywhere — your style change applies but isn't visible. The legend's eye icon does the same per-session.
**Fix**: open the layer panel from the map toolbar (`Manage layers`), find the layer, and click its eye icon to toggle visibility. For the persistent vs. per-session distinction, see [How the layer panel works in MangoMap](/docs/managing-layers/concepts-layer-panel).
## Another layer draws on top of it
Layers higher in the layer panel draw on top of layers below them. A polygon layer with an opaque fill hides every point, line, and polygon under it. A thick line layer can hide points on the same streets.
**Fix**: drag the layer you changed above the layer that covers it. Or lower the covering polygon layer's fill opacity. See [How to reorder layers on the map](/docs/managing-layers/reorder-layers).
## The features fall in a hidden or unexpected category or class break
When you colour by a text field, features whose value has no row of its own use the `Other` row. Features with no value use the `Null` row. If either row is hidden, those features don't draw. When you colour by a numeric field, features with no value don't draw. With class breaks, features below the lowest class break don't draw either. Features above the highest class break take its colour.
This works the same for markers, lines, and polygon fills.
**Fix**:
- **Text field (categories)** — expand `Customise categories` and check that the features' values are listed and not hidden. If a value is missing, pick the field again to rebuild the list.
- **Numeric field (class breaks)** — expand `Customise Class Breaks` and check the lowest range. Change the classification method, or lower the start of the first class break. See [My classification produced empty buckets or weird breaks](/docs/styling-layers/troubleshoot-classification-empty-buckets).
## Still not appearing
If none of these explains it, check:
- **Permission to edit the map** — if your role is `Viewer` or your access group has only `View` on the map, the Style tab shows the controls disabled. Contact the map owner or an admin.
- **The wrong layer** — multi-layer maps make it easy to style the wrong layer. The layer name is shown at the top of the settings panel; double-check it.
Then refresh the page (you lose unsaved changes) and try again. If the change still doesn't appear, report it to MangoMap support.
## Related troubleshooting
- [My classification produced empty buckets or weird breaks](/docs/styling-layers/troubleshoot-classification-empty-buckets)
- [My colour ramp is the wrong way round](/docs/styling-layers/troubleshoot-colour-ramp-reversed)