CoMaps

Open-source offline navigation, honestly reviewed. No marketing fluff, just what you get when you stop letting Google track your routes.

TL;DR

• What it is: A community-led, Apache-2.0 offline navigation app built on OpenStreetMap data. It’s a fork of Organic Maps, which itself forked Maps.ME before that project went ad-supported and data-hungry [1][2].
• Who it’s for: Privacy-conscious hikers, cyclists, travelers, and anyone who wants turn-by-turn navigation that works without a data connection and doesn’t phone home [1][2].
• Cost savings: Google Maps is free but collects everything you do. Apple Maps is better on privacy but iOS-only. CoMaps is free, open-source, and collects nothing — audited by Exodus to prove it [homepage].
• Key strength: Genuinely offline-first. Not “offline with degraded experience” but designed from the ground up so every function works without cellular service [1][2].
• Key weakness: 1,458 stars on Codeberg — a young fork with a small community. Map data quality depends on OpenStreetMap contributors in your region. No route planning for public transit. Not a Google Maps power-user replacement [merged profile][1].

---

What is CoMaps

CoMaps is a free, offline-first navigation app for Android and iOS built on OpenStreetMap data. The lineage matters: Maps.ME was once the gold standard for offline mobile maps. Mapsme.com was acquired, monetized, and turned into a tracking-heavy, ad-supported product. Organic Maps forked it to restore the original offline-privacy vision. CoMaps then forked Organic Maps — per its own description, because the project needed a more open governance model, not-for-profit structure, and transparent decision-making [1][2][4].

The Codeberg repository description states directly: “A community-led free & open source maps app based on OpenStreetMap data and reinforced with commitment to transparency, privacy and being not-for-profit” [1].

What this means in practice: no company owns CoMaps with an incentive to monetize your location data. Financial decisions are transparent. Development happens on Codeberg (not GitHub), and the Apache-2.0 license means anyone can fork it again without restriction [1][merged profile].

The project was independently audited by Exodus, the privacy analysis platform that scans Android apps for trackers and permissions. The homepage cites this audit as evidence of “privacy by default” [homepage]. This is a meaningful signal — Exodus findings are public and falsifiable, not a self-certification.

---

Why People Choose It

The reasons are simple and they repeat across every description of the app.

Offline without compromise. The pitch is that all functions work without mobile data — navigation, search, POI lookup, route planning. This isn’t “downloads the tile cache when connected.” You download region maps in advance and the app works entirely from local data [1][2]. For anyone who’s been caught abroad with no data roaming, or on a hiking trail where LTE doesn’t exist, this is the actual use case.

No tracking, audited. Organic Maps makes the same privacy claim, but CoMaps goes further by citing the Exodus audit [homepage]. For non-technical users who can’t read source code, third-party audits are the only credible verification. This distinguishes CoMaps from apps that make privacy claims without evidence.

Battery efficiency. Both the app description and the homepage specifically call out battery drain as a differentiator [1][2][homepage]. Navigation apps that keep a cellular modem and location services running continuously are notorious battery killers. Offline-first navigation with GPS-only can meaningfully extend battery life on long hiking or driving days, though specific numbers are not available from the sources reviewed.

Community-driven, not-for-profit. The project explicitly describes itself as not-for-profit with open financial and decision-making processes [1]. For users burned by apps that started privacy-first and pivoted after acquisition (Maps.ME being the canonical example), this governance structure is a feature, not just branding.

F-Droid availability. The app is available on F-Droid as app.comaps.fdroid [1], which matters to the subset of Android users who avoid the Google Play Store entirely. It’s also available through standard channels.

---

Features

Based on the app store descriptions and homepage:

Navigation:

• Voice-guided navigation for walking, cycling, and driving [1][2]
• Offline routing — routes calculated on-device, no server call needed [1][2]
• Downloadable regional map files with detail comparable to (and sometimes exceeding) Google Maps for outdoor use [1]

Outdoor and recreation:

• Dedicated outdoor mode with hiking trails, campsites, water sources, mountain peaks, and contour lines highlighted [1][2]
• Walking paths and cycleways rendered separately from roads [1][2]
• Track recording for logging your actual route [1][2]
• Export and import of tracks and bookmarks in KML, KMZ, and GPX formats — the standard formats used by Garmin, Komoot, and most outdoor apps [1][2]

Points of interest:

• Restaurants, gas stations, hotels, shops, and sightseeing spots [1][2]
• POI search by name, address, or category [1][2]
• Bookmark any location with a single tap [1][2]
• Offline Wikipedia article access for locations [1][2]

Urban transit:

• Subway transit layer and directions [1][2]
• Note: no full multi-modal public transit routing, which is a real gap versus Google Maps or Citymapper

Map editing:

• Built-in basic editor to contribute corrections back to OpenStreetMap [1][2]
• This is how offline maps improve over time — users fix errors directly in the app

Interface:

• Dark mode [1][2]
• The website claims 37 language versions of the app [homepage internal links]
• Available on Android 5.0+ (API 21) [1]

What it doesn’t do: There’s no street view, no real-time traffic, no business reviews, no restaurant reservations, no integration with ride-sharing, and no live location sharing. If you rely on Google Maps as a restaurant discovery and review platform, CoMaps is not that product.

---

Pricing: SaaS vs Self-Hosted Math

CoMaps doesn’t have a pricing model because it doesn’t have a business model in the traditional sense. The app is free. The Apache-2.0 license is free. There are no premium tiers, no subscription features, and no in-app purchases [merged profile][1].

The project accepts donations (the homepage links to /donate) which is how a not-for-profit open-source app sustains itself. Whether that model is durable long-term is an open question.

The actual cost comparison is privacy, not money:

App	Price	Tracking	Offline	Audit
Google Maps	$0	Extensive location history	Partial	No
Apple Maps	$0	Limited, on-device	Partial (iOS only)	No
Maps.ME (current)	$0	Ad-supported, data collected	Yes	No
Organic Maps	$0	None claimed	Yes	No
CoMaps	$0	None, Exodus-audited	Yes	Yes [homepage]

For travelers who’d otherwise pay for roaming data plans to keep Google Maps functional abroad, offline navigation has a real dollar value. A two-week trip to Europe with no roaming plan, relying on CoMaps for navigation, avoids $30–$80 in roaming costs depending on your carrier. That’s the concrete savings math for this category of tool.

Pricing data for any CoMaps commercial tier: not available — none exists.

---

Deployment Reality Check

CoMaps is a mobile application, not server software. “Deployment” means installing the app and downloading map files — the setup experience is meaningfully different from self-hosted web services.

Android install path:

• F-Droid (package app.comaps.fdroid) — for users avoiding Google Play [1]
• Google Play Store (package app.comaps) [2]
• Direct APK from Codeberg releases

iOS: Available; the homepage references iOS downloads. App Store listing details not covered in the sources reviewed.

Map file management: The main ongoing task is managing downloaded map files. Regional map packs vary in size — the app APK itself is 51–62 MB depending on version [1][2], and region maps add on top of that. For extended international travel, you’ll download multiple regions in advance over Wi-Fi. The app handles this, but users with limited phone storage need to plan which regions to keep active.

What can go sideways:

• Map data quality is uneven. In major European and North American cities, OpenStreetMap is often more detailed than Google Maps for pedestrian and cycling infrastructure. In rural areas of developing countries, coverage can be sparse. The app can’t compensate for missing upstream data.
• The project is a young fork. It had 1,458 stars on Codeberg as of the data collection date [merged profile] — a small community compared to Organic Maps or OsmAnd. Fewer contributors means slower bug fixes and feature additions.
• No iOS-specific review data was available in the sources reviewed. Android experience and iOS experience may differ.
• The subway/transit layer exists but the sources don’t detail which cities have complete coverage.

Realistic setup time: 5 minutes to install and download your home region. An evening before a trip to download destination regions and verify coverage.

---

Pros and Cons

Pros

• Genuinely offline. Not “mostly offline with some cloud calls.” Every function is designed to work without cellular service [1][2]. This is the actual promise, not a marketing hedge.
• Exodus-audited privacy. The app was independently reviewed by Exodus for trackers and permissions [homepage]. This is verifiable, not a self-certification. It also has no ads [1][2].
• Apache-2.0 license. Fully open, forkable, embeddable without restriction [merged profile][1]. This is why the Maps.ME → Organic Maps → CoMaps lineage is possible at all.
• OpenStreetMap data. OSM is often better than Google Maps for hiking trails, cycling infrastructure, and rural areas in countries with active mapping communities. Updating the map means contributing to OSM, which benefits everyone [1][2].
• GPX/KML/KMZ import and export. Interoperability with Garmin devices, Komoot, AllTrails, and any other tool that uses standard track formats [1][2].
• Not-for-profit governance. Transparent financials and decision-making [1]. No acquisition risk in the short term.
• F-Droid availability. Matters to users who’ve de-Googled their Android device [1].
• Offline Wikipedia integration. Useful for travel — you can look up context on a historical site without a data connection [1][2].

Cons

• Small community. 1,458 Codeberg stars [merged profile] is early-stage. Compare to OsmAnd which has been around since 2010. Bug fix pace and feature velocity depend on contributor count.
• No real-time traffic. Offline-first means no live traffic data. Driving in an unknown city during rush hour, you won’t know about the accident blocking the bridge.
• No multi-modal transit routing. The subway layer exists but you can’t ask “how do I get from A to B using the metro, a bus, and walking?” — that requires live schedule data [1][2].
• Map data ceiling is OpenStreetMap. In regions where OSM coverage is sparse, the app gives you sparse maps. There’s no fallback to a commercial data layer.
• No location sharing. You can’t share your live location with family or coordinate meetups the way Google Maps or Find My supports. For travelers in groups, this is a real missing feature.
• No user reviews or ratings for POIs. CoMaps shows you where the restaurant is but not whether it’s worth going to. You’re dropping back to a separate app for that.
• Young fork, uncertain governance longevity. The not-for-profit model is honest but donation-dependent. Whether the project sustains enough contributors and funding over five years is unknown.

---

Who Should Use This / Who Shouldn’t

Use CoMaps if:

• You travel internationally and want offline navigation without paying for roaming data.
• You hike, bike, or go into areas with no cellular coverage and need reliable turn-by-turn.
• You’ve decided to stop giving Google your location history and want a practical alternative for daily navigation.
• You’re already using OpenStreetMap tools (Vespucci, StreetComplete) and want a consumer-facing app in the same ecosystem.
• You need GPX track export for logging routes on Garmin or similar devices.

Skip it (use OsmAnd instead) if:

• You need deep OpenStreetMap integration with advanced routing profiles, contour line rendering, and granular display settings. OsmAnd is more powerful and has been around longer, at the cost of a steeper interface.
• You want a more mature community with faster bug fixes and documented issues.

Skip it (use Organic Maps instead) if:

• You want the same offline-privacy approach but with a larger existing user base and more public discussion about the app’s direction. Organic Maps is the parent project and has more documented usage.

Skip it (use Google Maps) if:

• You need real-time traffic, live transit schedules, business hours, user reviews, and restaurant discovery. CoMaps doesn’t compete with Google Maps as an information platform — it competes with it as a navigation tool.

Skip it (stay on Apple Maps) if:

• You’re on iOS, you trust Apple’s privacy record, and you don’t need offline navigation without any data connection. Apple Maps has significantly improved its offline mode in recent iOS versions and integrates with the Apple ecosystem.

---

Alternatives Worth Considering

Organic Maps — the parent project CoMaps forked from. Same OpenStreetMap data, same offline-first approach, same privacy posture. More stars, more users, more documentation. The split was about governance structure, not technical superiority. If CoMaps’ not-for-profit model doesn’t specifically appeal to you, Organic Maps is the safer bet for now.

OsmAnd — the power user’s OpenStreetMap app. More routing profiles (including nautical, ski, and emergency vehicle), more rendering options, more configurable than either CoMaps or Organic Maps. The interface is dense; it rewards the user who wants to tune every parameter.

Magic Earth — closed-source offline navigation with a clean interface. Free. Uses OpenStreetMap. Privacy-respecting but not audited and not open source. The pragmatic choice for users who want offline maps without the open-source setup.

Maps.ME — the ancestor. Avoid it in current form. After acquisition it became ad-supported and data-collecting. The reason CoMaps exists is because Maps.ME went this direction.

Google Maps offline — technically supports offline map downloads, but the app still calls home with your route requests and location when connected. Not a privacy alternative.

Traccar + Dawarich — relevant if your use case is self-hosted location tracking rather than navigation. The Privacy Guides forum discussion [5] covers this angle. CoMaps doesn’t do location sharing or tracking history.

---

Bottom Line

CoMaps is the most honest pitch in the offline navigation space right now: a Maps.ME-lineage app rebuilt by a community that explicitly chose not-for-profit governance and third-party privacy auditing. It doesn’t try to replace Google Maps as an information platform — it solves the specific problem of navigation that works without cellular data and doesn’t track you. The trade-offs are real: young project with a small community, no real-time traffic, no transit routing, map quality bounded by OpenStreetMap coverage in your region. But for the target user — a traveler abroad, a hiker out of signal range, or someone who made a deliberate choice to stop feeding Google their location history — the math is simple. Download the app, download your region maps over Wi-Fi, and navigate with GPS and no data connection required.

The 1,458 stars and F-Droid availability suggest an early but genuine community. Whether it grows or eventually merges back into Organic Maps depends on whether the governance split sustains enough contributors. For now, it’s a working tool that does what it says.

---

Sources

1. AndroidFreeware.net — “CoMaps - Hike, Bike, Drive Offline with Privacy (versión 2026.04.07-8-FDroid)”. https://www.androidfreeware.net/es/download-comaps-hike-bike-drive-offline-with-privacy-apk.html
2. AndroidFreeware.net — “CoMaps - Hike, Bike, Drive Offline with Privacy (versión 2025.08.31-15)”. https://www.androidfreeware.net/es/download-apk-app-comaps.html
3. AndroidFreeware.net — “GPS y mapas Viajes Código Abierto Android Apps - April, 2026”. https://www.androidfreeware.net/es/category/travel/gps-navigation-and-maps/
4. Codeberg.org — “gedankenstuecke/comaps-website: comaps.app website of CoMaps, the community-led Organic Maps fork”. https://codeberg.org/gedankenstuecke/comaps-website
5. Privacy Guides Community — “Recommended self-hosted location tracking stack?”. https://discuss.privacyguides.net/t/recommended-self-hosted-location-tracking-stack/31912

Primary sources:

• Official website: https://www.comaps.app
• Source code repository: https://codeberg.org/comaps/comaps
• Exodus privacy audit reference: https://www.comaps.app (homepage citation)
• Privacy policy: https://www.comaps.app/privacy