Why Notion Map View Only Shows 100 Pins (And What to Do About It)

The Notion Map View pin limit is 100 items per view, enforced by Notion at render time. If your database has more than 100 places, the extra rows still exist in the database but are hidden from the map until you apply filters or split them across additional views. There is no native way to raise the cap, no export of the rendered map, and no public link that shows all your pins on one screen.

Notion released Map View on November 17, 2025 as part of Notion 3.1, alongside the new Place property. The feature works well for short trips, a list of favorite shops, or a regional office expansion plan. It falls apart the moment your dataset crosses three digits. This post documents the exact limit, why Notion designed it that way, the official workarounds, and the database-first path that removes the ceiling entirely.

What the 100-pin limit actually means

Notion's official Map View help page states it plainly: "Up to 100 items can be shown in map view at one time." The cap applies per view, not per database. A database with 4,800 restaurants is fine to store in Notion — the API and the underlying table can hold tens of thousands of rows — but the Map View itself will silently render only 100 of them.

The behavior is not a warning or an error. The map loads, the pins appear, and unless you count them you will not notice that 4,700 places are missing from the map. Filtering and sorting on a Place property is text-based: you can filter by text contained in the place's name or address, and you can sort alphabetically. There is no native filter for "within 5 km of point X" or "items 101-200." If your data does not have a clean text field to filter on, the cap becomes a hard ceiling.

For a long-form treatment of how the underlying Place property works, see our complete guide to the Notion Place property.

What you can and cannot do inside the view

• Conditional coloring: Yes. Pin color can be driven by a Select or Status property — useful for categorizing visited vs. wishlist locations.
• Map height: Four sizes (Small, Medium, Large, Extra Large). No fullscreen view of the embedded map.
• Sharing: Public link sharing works only at the Notion page level. There is no standalone, map-only URL.
• Embed: A Notion page with a Map View can be embedded in another Notion page. There is no public iframe code for a third-party site.
• Export: Map View does not export as an interactive map. The underlying database exports to CSV, Markdown, or HTML only — the same options as any other Notion view.

Why Notion shipped the cap at 100

Notion's Map View renders client-side in the browser using a third-party geocoding provider. Loading 5,000 markers in a browser tab — without clustering, lazy-loading, or vector tiles — would freeze the UI, especially on mobile. Notion's product philosophy has always been "good enough for most users," not "best in class for power users." 100 pins covers a typical itinerary, a real-estate portfolio of a single agent, or a small chain of stores.

There is also an architectural reason. Notion Pages stream blocks as you scroll, and a database view is one block. Forcing the renderer to load every pin in a 10,000-row database every time someone opens the page would conflict with the 15% page-load speedup Notion announced in the 3.1 release. A 100-item cap keeps the view fast by design.

Finally, Notion sells paid plans — Plus, Business, Enterprise — where the differentiation is collaboration, AI, and admin tooling, not raw mapping power. Native Map View is a "complete enough" feature for personal and team use. Heavy mapping workloads were never the target.

The official workarounds — and where they break

Notion's help page suggests two paths when your database exceeds 100 places: "narrow down your list using filters, or splitting items across additional views." Both work for a while.

Filters are fine if your data already has a natural slicing dimension. A travel database with a Country property can show one map per country. A real-estate database with a Status (Active, Pending, Sold) can show three views. The friction shows up when you want one map of everything — a single shareable view that proves you have 800 ramen shops cataloged. You cannot build that with native Map View at any price tier.

Multiple views lets you stack maps inside one page: "North America," "Europe," "Asia." Each view is a separate render, each capped at 100. You can pile up 50 views to cover 5,000 pins, but every view needs its own filter logic, every reader scrolls through 50 maps to find one location, and the map embed code (which Notion does not actually expose publicly) is per-view, not per-database.

The Notion API exposes Map View as a supported view type since the 3.1 release, but the API returns the database rows — not the rendered map. If you want to surface all your pins on one screen, you have to render them yourself.

How NotionToMaps removes the ceiling

NotionToMaps connects to your Notion database via OAuth, reads every row with a Place property, and renders all of them on a single Leaflet map. No 100-pin cap. Clustering kicks in at low zoom levels so 5,000 markers stay responsive on mobile. The map gets a public URL like notiontomaps.com/map/{database_id} that you can share with anyone — no Notion account needed on the viewer's side.

The same database can be exported in one click to KML for Google Earth, GPX for GPS devices, GeoJSON for web mapping, or CSV for spreadsheets. The four export formats are documented side-by-side in our KML vs GPX vs GeoJSON vs CSV breakdown. For a deeper look at how teams use a NotionToMaps URL as a phone home-screen app, see the Notion travel guide on your phone walkthrough.

Notion Map View vs NotionToMaps

Workflows where the 100-pin cap silently breaks things

The pin cap is dangerous precisely because it does not raise an error. A few real scenarios where users hit the wall without realizing it:

• Travel databases over multi-month trips. A 6-month around-the-world trip easily logs 200-400 locations. The first 100 alphabetical entries render; everything from "M" onward goes missing.
• Restaurant bucket lists in major cities. Anyone who has been collecting restaurant recommendations for more than a year ends up with 150-300 places.
• Real estate portfolios at any agency level above solo. A team of five agents covering one metro routinely tracks 400+ active and pending listings.
• Sales territory mapping with even modest account loads. 150 accounts is a small territory for a B2B SaaS rep.
• Photographers tracking shoot locations across a region. A photographer's location database typically grows past 100 within a year.

The same pattern that hit users of Google's free mapping tool — documented in our Google My Maps 2,000-location limit breakdown, the top-traffic post on this blog — is now hitting Notion users much earlier, at 100 instead of 2,000. The fix is the same: keep the database in the tool where you actually edit it (Notion), and render the map somewhere that scales.

If you are starting fresh, our getting started with Notion places guide walks through the property setup before you hit any limit. If you already have 500+ rows and need a public-facing map this week, the path is simpler: connect to NotionToMaps, send the link.

Frequently asked questions

How many pins can Notion Map View display at once?

Notion Map View displays up to 100 pins per view. The limit is documented on Notion's official Map View help page. Databases can store far more — the cap applies only to the rendered map, not to storage.

Can I increase the 100-pin limit in Notion Map View?

No. There is no setting on any Notion plan — Free, Plus, Business, or Enterprise — that raises the 100-pin cap. The official workaround is to use filters or split items across additional views. Each additional view is also capped at 100.

Does Notion Map View work on public pages?

Yes, but with caveats. A Notion page set to "Share to web" will render the Map View to public visitors. The view is still capped at 100 pins, the page URL is shared (not a map-only URL), and visitors cannot filter or interact beyond clicking pins.

Can I export the Notion Map View as KML or GPX?

No. Notion exports databases to CSV, Markdown, or HTML only. The map itself does not export as KML, GPX, or GeoJSON. To export those formats, connect the database to a tool like NotionToMaps that reads the Place property and converts it.

When did Notion launch Map View?

November 17, 2025, as part of the Notion 3.1 release. The same release introduced the Place property type, two-way sync between Notion Calendar and databases, and API support for map view as a queryable view type.

Sources

• Notion Help Center — Map view
• Notion 3.1 release notes (November 17, 2025)
• Notion Developers — Changelog