Turn your list of summits, trails, and viewpoints into a beautiful, interactive map — no coding required.

PeakMaps is a WordPress plugin built for hiking blogs, outdoor clubs, tourism sites, and anyone who wants to showcase peaks, trails, and points of interest on a real, interactive map. Add a searchable database of locations, complete with GPX tracks and elevation profiles — then drop it into any page or post with a Gutenberg block or shortcode.

PeakMaps is completely free, with no peak-count cap, no expiring features, and no upgrade popups. PeakMaps Pro is a separate, optional add-on for sites that want Norwegian topographic maps (Kartverket), custom marker styles, extra data fields, on-map tools, GPX downloads, and bulk CSV import/export.

See it in action: demo table | demo map

What PeakMaps does

Add peaks to your own dedicated database, attach GPX tracks, and PeakMaps takes care of the rest: rendering them on interactive Leaflet maps, generating a sortable and filterable table, calculating elevation profiles — all without a single line of code. Place as many maps and tables as you like, anywhere on your site, each with its own filters and settings.

🗺️ Interactive map

Built on Leaflet — fast, lightweight, and mobile-friendly.
Marker clustering keeps busy maps clean at lower zoom levels.
Background layers: OpenStreetMap and OpenTopoMap, with an easy switcher for visitors.
Fullscreen mode for an immersive map view.
Smooth touch and pinch-zoom on mobile.

🏔️ GPX tracks and elevation profiles

Attach a GPX track to any peak and it renders on the map automatically — the map zooms to show the whole track.
The peaks the track passes are marked in the elevation profile, with their names.
A map button colours the track by steepness, like the elevation profile.
Map and profile work together: point at the track on the map to see that spot in the elevation profile, or click the profile to zoom the map there.
Optional distance markers and direction arrows along the track, switched on and off by visitors with a «km» button on the map.
Elevation profile charts with interactive hover tooltips — elevation and distance at any point along the track.
Ascent/descent totals, min/max elevation, total distance calculated automatically, plus an optional estimated walking time.
Optionally coloured by steepness (0–5 % up to 35 %+), with the gradient in the hover tooltip; start and finish are marked on the map.
Secure GPX proxy built in — tracks hosted anywhere load smoothly without CORS issues.
Each track’s length and total ascent are stored with the peak, and the admin warns you when a GPX file can’t be read or never comes near its peak (usually the wrong file).

📊 Smart, filterable table

Fully sortable and searchable — sort by name, elevation, track length, ascent, municipality, county, visited date, and more.
Live filtering by municipality, county, elevation range, track length (e.g. hikes under 10 km), free-text search, and visited status — no page reload.
Pagination with configurable results per page.
Optional row-number column and configurable column selection per instance.

🗄️ Your own peak database

A dedicated, purpose-built database — not repurposed WordPress posts — for fast, clean querying at any scale, with no upper limit.
Visited/completed tracking — doubles as a personal or club peak-bagging log.
Show/hide individual peaks without deleting their data.
Full admin interface: search, filter, sort, bulk-edit, bulk-delete, and duplicate entries.

🌍 Built for real-world use

Works via Gutenberg blocks (with live editor preview) or classic shortcodes ([peakmaps_map] and [peakmaps_table]).
Norwegian Bokmål translation included; standard WordPress i18n for adding more languages.
Automatic cache clearing on settings changes, compatible with WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache, and WP-Optimize.
Assets load only on pages that actually contain a map or table.

PeakMaps Pro

PeakMaps Pro is a separate, optional add-on that extends the free plugin without removing anything from it. Pro adds:

🇳🇴 Norwegian Kartverket maps
Norway’s official topographic map, raster map, and nautical chart as additional background layers. When a Kartverket layer is active, Pro also refines elevation profiles against Kartverket’s own terrain model for extra accuracy.

🎨 Custom marker styles
Choose from circular, square, triangular, diamond, or star markers in any colour — or upload your own custom marker image.

📝 Five custom extra fields
Add up to five fields with labels you choose — difficulty, parking notes, permit info, or anything your project needs. Supports wildcards (*, ?), exclusion (!), and numeric comparisons (>, <, >=, <=) in filters.

🛠️ On-map tools
A distance-measuring tool and a «find my position» GPS button for visitors browsing on mobile.

⬇️ GPX download
Let visitors download GPX files, with an optional terms/consent dialog.

📥 CSV import and export
Bulk-load or update peaks from a spreadsheet, with insert mode (add new entries) and update mode (fill in missing fields on existing ones). Export your full peak database to CSV at any time — perfect for backups or editing in Excel.

Find out more about PeakMaps Pro

Perfect for

Hiking and outdoor blogs documenting summits, trails, and viewpoints
Tourism boards and destination sites showcasing regional attractions
Hiking clubs maintaining a shared, browsable peak list
Personal peak-bagging logs for trackers working through a summit list

Source Code

This plugin’s own frontend script, assets/js/nu_script.js, is shipped as a whitespace-minified build for faster loading. Its full human-readable source — same code, same behavior, just formatted — is included in this plugin at assets/src/nu_script.js. No bundler, transpiler, or other build step is used beyond whitespace minification; regenerating the minified file from the source is a single pass through any standard JS minifier.

All other JavaScript and CSS files written for this plugin (everything under assets/js/ and assets/css/ not listed below) are already shipped in their normal, unminified, human-readable form — no separate source is needed for those.

Bundled third-party libraries (Leaflet, Leaflet.markercluster, Leaflet.fullscreen, Leaflet.UTM) are minified as distributed upstream; each file includes a header comment with its name, license, and source repository URL. GPXParser.js (MIT) is included in readable form with a few PeakMaps fixes, listed in its header comment.

External services

PeakMaps connects to the following services. Nothing is sent to any of them unless a map is shown, or a peak with a GPX link is saved or recalculated.

Map tiles — requested by the visitor’s browser when a map is shown

The browser asks the tile provider of the background map in use for the image tiles of the area in view. Each request carries only what any image request carries: the tile coordinates and zoom level, plus the browser’s normal request data (IP address, user agent). No peak data, site content or personal data is sent.

OpenTopoMap — the default background map, a topographic map built on OpenStreetMap data. Tiles from tile.opentopomap.org. Usage policy · OpenStreetMap privacy policy (OpenTopoMap does not publish a separate one)
OpenStreetMap — the second background map in the layer switcher. Tiles from tile.openstreetmap.org. Tile usage policy · Privacy policy
Esri (satellite, topographic) and CARTO (light, dark) — part of the plugin’s layer list, but only shown when an add-on such as PeakMaps Pro switches them on. Tiles from server.arcgisonline.com and basemaps.cartocdn.com. Esri: Terms of use · Privacy policy. CARTO: Terms of use · Privacy policy

GPX files — requested by this site’s server

For the map: GPX files hosted on another site are fetched through this site’s own proxy, so the browser can draw them. The proxy only fetches URLs that exactly match a GPX link saved on a peak in this site’s database.
For track statistics: when a peak is saved, imported or recalculated, the server reads its GPX file (and the detailed «F» variant next to it, if there is one) to work out length, ascent, steepness and distance above 1000 m. A file on this site is read straight from disk; a file elsewhere is requested from the address given in the peak’s GPX link.

Which third party, if any, receives a GPX request depends only on where the site owner hosts the files; the plugin’s author runs no server involved in any of this.