umap-project.org

Yes. uMap is free and open-source, and it is maintained by a community of contributors rather than a single company. The project describes itself as "free (as in speech and beer)," meaning both the source code and the hosted service are available at no cost. It has been free and open-source since day one, has been improved for more than 10 years, and has 60+ contributors to its codebase.

What "free" means here

uMap uses the phrase "free (as in speech and beer)" to cover two separate ideas:

• Free as in speech — the software is open-source, so you can inspect, reuse, and contribute to the code.
• Free as in beer — using it costs nothing.

The project's stated philosophy leans toward long-term, minimalist code, which is part of why it has stayed maintainable over a decade of development.

Who maintains uMap

uMap is run by a community of contributors, not a single vendor. The evidence on the project site points to:

• 60+ contributors to the codebase
• More than 3,000 issues already discussed
• An active community and an up-to-date Docker image for self-hosting
• Sponsors who support development

The project also publishes a full changelog and commit history, so you can see ongoing activity rather than taking the "maintained" claim on faith. At the time of the source material, the latest release was 3.4.2 (2025-11-26) and the latest commit was dated 2025-12-02.

Signals that it is actively used

Adoption numbers on the site give a sense of scale:

How to support it

If you want to contribute to uMap's development, the project lists a "Support uMap's development" section and names its sponsors. The site also links to GitHub, a forum, and technical documentation — the usual entry points for code contributions, bug reports, and community help.

Practical takeaway

If your concern is lock-in or cost, uMap's model addresses both: the code is open-source, the hosted instances are free to use, and the Docker image means you can run your own instance. If your concern is longevity, the 10+ year history, active commit log, and contributor count are the relevant evidence — though, as with any community project, continuity depends on that community staying active.

uMap is one software project, but it is offered through several instances run by different OpenStreetMap organisations. The main practical differences shown on the project site are anonymous usage and real-time collaboration: the DE instance (OpenStreetMap Germany) has anonymous usage activated and real-time collaboration activated; the CH instance (OpenStreetMap Switzerland) and the FR instance (OpenStreetMap France) both have anonymous usage activated but real-time collaboration deactivated. If you need several people editing the same map live, DE is the instance to pick; if you only need to create and publish a map, any of the three works.

The three instances side by side

All three are presented in the same “Choose an instance” window on umap-project.org, so the choice is made before you start building, not after.

What each difference actually means

Anonymous usage

On all three instances anonymous usage is activated. In practice this means you can start creating a map without first registering an account — the site’s own user quotes describe uMap as a tool that “doesn’t require any account” and lets you build an interactive map through a graphical interface without coding. This is a property shared by DE, CH and FR, so it is not a reason to prefer one over another.

Real-time collaboration

This is the only functional difference the site flags between the instances. Real-time collaboration is the feature that lets two or more people work on the same map at the same time — the instance chooser illustrates it with a “two people side by side” icon for DE, and a “person with a cross in the background” for CH and FR.

• Choose DE if your use case involves a group editing one map simultaneously — for example a classroom exercise, a workshop, or a team mapping session.
• Choose CH or FR if you are working alone or your collaborators can take turns; you lose live co-editing but keep everything else.

How to choose

1. Decide whether live multi-user editing is required for your map.
2. If yes, select the DE instance in the “Choose an instance” window.
3. If no, pick the instance closest to your context — CH for Switzerland-related work, FR for France-related work — or simply the one you prefer, since anonymous creation is available on all three.
4. Proceed to “Create a map” on the instance you selected.

What is the same across instances

The underlying uMap project is the same everywhere. It is described as free “as in speech and beer”, open-source since day one, with 10+ years of improvements, 60+ contributors, and a current release of 3.4.2 (2025-11-26). The site reports 190,194 user accounts, 1,561,209 maps created, and 9,890 edited maps per week across the project. Feature-wise, the documented use cases — drawing lines and polygons, importing information layers, heatmaps, clustering, and slideshow storytelling with photos, text, sound and video — are capabilities of uMap itself rather than of a specific instance.

A note on hosting and continuity

Because DE, CH and FR are run by different OpenStreetMap organisations, the instance you choose also determines who operates the server your map lives on. The site does not state service-level guarantees, storage limits, or long-term retention policies for any instance, so if a map is business-critical, verify the current terms with the operator of that instance before relying on it.

uMap is best suited to tasks where you need to place data on a map, draw on top of OpenStreetMap background layers, and publish the result on your own website without writing code. The project's own examples cover five recurring patterns: drawing lines and polygons, importing existing data layers, showing density with heatmaps, handling large point sets with clustering, and telling a sequenced story with the slideshow feature. If your task fits one of those shapes, uMap is a reasonable fit; if you need heavy spatial analysis or custom basemaps, it is not.

Drawing lines and polygons

The simplest use case is marking areas or routes by hand. uMap supports drawing lines and polygons directly on the map, which the project illustrates with a solar-panel suitability example: outlining roofs that have potential for solar panel sites.

This works well when:

• The set of features is small enough to draw manually.
• You want to annotate an area rather than compute anything from it.
• The map is meant to be read by people, not processed by another system.

Importing information layers

uMap lets you import data layers and place them on top of a tile layer. The project's example is a city's public transportation network, and a second example overlays imported data and drawings on a tile layer to make a flooding hazards plan easier to understand.

The pattern here is: take data you already have, load it as a layer, then add drawings or notes on top so the combination is more legible than either part alone. This is the use case to pick when your source data already exists in a file or service and you mainly need to present it in geographic context.

Representing density with heatmaps

When the question is "where is this concentrated?" rather than "where exactly is each item?", a heatmap is the right representation. uMap's example maps pubs in a given neighborhood to show density.

Use a heatmap when:

• Individual points matter less than the overall distribution.
• You have enough points that plotting each one would be unreadable.
• The audience needs a quick visual impression of concentration.

Handling many points with clustering

The project describes the cluster feature as the answer to having too much information to display: points are revealed step by step as you zoom in. This is the complement to the heatmap case — you keep the individual points, but only show them at zoom levels where they are readable.

Choose clustering over a heatmap when the identity and position of each individual point still matter to the reader.

Telling a story with the slideshow feature

uMap's slideshow feature lets you insert photos, texts, sounds, and videos and display them in a specific order. This turns a map from a static reference into a guided sequence, useful for walkthroughs, field reports, or narrative explanations where the order of what the reader sees is part of the point.

Choosing between these use cases

What to check before committing

uMap is described as free and open-source, maintained by a community of contributors, with anonymous usage available on its instances. That lowers the barrier for trying any of the use cases above. What the source material does not establish is anything about limits on data volume, storage, or long-term hosting guarantees, so for a map that must stay online and unchanged for years, verify those conditions on the instance you plan to use before you build on it.

uMap is a free, open-source web tool for building custom interactive maps on top of OpenStreetMap background layers and embedding them in your own website. You can start creating a map anonymously — no account required — and the project reports over 1.9 million user accounts and more than 1.5 million maps created. It suits people who want to draw, import, and publish map data without writing code.

What uMap actually is

uMap is a software project, not a single website. It is maintained by a community of contributors and has been free and open-source since it started, with 10+ years of improvements and 60+ code contributors. The latest release noted on the project page is 3.4.2 (2025-11-26), and the code lives on GitHub with 1,400+ stars.

Because it is open-source software, it runs on multiple instances rather than one central service. The project page lists several, each with different capabilities:

If real-time collaboration matters to you, that difference between instances is the deciding factor. Otherwise, anonymous usage is available across all three listed instances.

What you can do with it

The project describes a range of use cases, all built around drawing or importing data onto a map:

• Draw lines and polygons — for example, marking roofs with potential solar panel sites.
• Import information layers — such as a city's public transportation network, or data drawn on top of a tile layer to make a flooding hazards plan easier to understand.
• Show density with a heatmap — for example, pubs within a given neighborhood.
• Handle crowded data with clustering — the cluster feature displays points step by step as you zoom in, so a dense dataset stays readable.
• Tell a story with a slideshow — insert photos, texts, sounds, and videos and display them in a specific order.

The project's own framing is that no coding is needed: you create your interactive map through a graphical interface. One quoted user describes it as easy to get started with, reactive, and not requiring an account, and notes it allows interesting collaborative work with students.

Who it fits, and who it doesn't

uMap is a good fit if you want a quick, no-code way to put custom points, lines, or imported layers on an OpenStreetMap base and embed the result on a site. It is also a reasonable choice if you value open-source software with an active community — the project notes more than 3,000 issues already discussed, an up-to-date Docker image, and a philosophy oriented toward long-term, minimalist code.

It is a weaker fit if you need guaranteed real-time collaboration on every instance, since that depends on which server you pick. And because it is community-maintained rather than a commercial product, you should treat support and hosting as community resources: the project points to its documentation, forum, and GitHub for help and development.

How to get started

1. Open the uMap site and choose Create a map, or pick an instance first if you need real-time collaboration (uMap DE) or a specific regional server.
2. Start building — anonymous usage is activated, so you can begin without registering.
3. Add your content: draw lines and polygons directly, or import an information layer, then layer on heatmaps, clustering, or a slideshow as needed.
4. Embed the finished map on your own website.

If you want to support the project or dig into how it works, the project page links to its documentation, forum, GitHub repository, and a sponsorship section.

uMap lets you build a custom map on top of OpenStreetMap background layers and embed it on your own website, without writing code. You can start creating a map anonymously — no account required — and the interface is a graphical one, so markers, lines, polygons, and imported data layers are added by clicking rather than coding. The steps below cover choosing an instance, building the map, importing data, and embedding the result.

Choose an instance and start a map

uMap is run on several public instances. The homepage presents a choice of servers, and the one you pick determines whether real-time collaboration is available:

If you want several people editing the same map live, choose the main instance where real-time collaboration is activated. Otherwise any instance works for anonymous, single-editor use.

From the homepage, select Create a map to open the editor. Because anonymous usage is activated, you can begin immediately; creating an account is optional but useful if you want to keep and manage your maps over time.

Add markers, lines, and polygons

Inside the editor, the base layer is OpenStreetMap. You draw on top of it using the built-in drawing tools:

• Markers for points of interest.
• Lines for routes or linear features.
• Polygons for areas.

A documented example is drawing lines and polygons to find roofs with potential solar panel sites — the polygon marks the roof area, and the geometry is what makes the map useful rather than just a picture.

Import data layers and overlay them

Beyond hand-drawing, uMap supports importing information layers and placing them over the tile layer. The project shows several use cases:

• Importing the public transportation network for a city.
• Importing data and drawing on top of a tile layer to make a flooding hazards plan more understandable.
• Using a heatmap to represent densities (the example given is pubs in a neighborhood).
• Using the cluster feature when there is too much information to display at once, so points appear step by step as you zoom in.

If your dataset is dense, reach for clustering or a heatmap instead of plotting every point individually.

Tell a story with the slideshow feature

uMap includes a slideshow feature that lets you insert photos, texts, sounds, and videos and display them in a specific order. This turns a plain map into a guided narrative — useful for walking a viewer through a sequence of locations rather than presenting everything at once.

Embed the map on your website

uMap is designed so you can integrate the maps you build on your own website. Once your map is ready, use the embed option in the editor to generate the code for your site. The project's own description states that uMap "lets you quickly build custom maps with OpenStreetMap's background layers and integrate them on your own website," and the interface is graphical, so no coding is needed to produce the map itself.

What to know before you rely on it

• It is free and open-source, described as "free (as in speech and beer)," maintained by a community of contributors, with 10+ years of improvements and 60+ contributors to the codebase.
• Scale is real: the project reports 190,194 user accounts, 1,561,209 maps created, and 9,890 edited maps per week.
• It is actively developed: the latest release listed is 3.4.2 (2025-11-26), with commits as recent as 2025-12-02 and 1,400+ GitHub stars.
• Support and documentation exist: the site links to documentation, a forum, and GitHub, and notes sponsors and a way to support development.

If you need live multi-user editing, confirm you are on an instance where real-time collaboration is activated before inviting collaborators.