Trackserver
GPS Track Server for TrackMe, OruxMaps and others
Consider an alternative
Trackserver shows warning signs in 2026 — compare the alternatives below before installing. It runs on 400+ sites, is rated 5/5 and was last updated 1 year ago, and scores 37/100 on our health check.
- Small user base (400+ active installs)
- No update in over a year
- Only tested up to WordPress 6.8 (latest is 7.1)
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Trackserver stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| gps | #26 |
| map | >100 |
| mobile | >100 |
| track | >100 |
| tracking | >100 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 19 reviews
About Trackserver
From the official readme · v5.1.1Description
NOTE: Trackserver v5.0 contains backwards-incompatible changes and changes to client configurations are needed. Please read the release notes for more information.
Getting your GPS tracks into WordPress and publishing them has never been easier!
Trackserver is a plugin for storing and publishing GPS routes. It is a server companion to several mobile apps for location tracking, and it can display maps with your tracks on them by using a shortcode. It can also be used for live tracking, where your visitors can follow you or your users on a map.
Unlike other plugins that are about maps and tracks, Trackserver’s main focus is not the publishing, but rather the collection and storing of tracks and locations. It’s all about keeping your data to yourself. Several mobile apps and protocols are supported for getting tracks into trackserver:
- TrackMe
- MapMyTracks protocol, for example using OruxMaps, including upload functionality
- OsmAnd’s live tracking protocol
- µLogger
- GPSLogger
- PhoneTrack-Android also works with OsmAnd’s protocol (Trackserver >= 4.3)
- SendLocation
- Traccar client
- OwnTracks (experimental support)
- HTTP POST, for example using AutoShare
A shortcode [tsmap] is provided for displaying your tracks on a map. Maps are displayed using the fantastic Leaflet library and some useful Leaflet plugins are included. Maps can be viewed in full-screen on modern browsers.
To publish a map with a track in a post or a page, just include the shortcode:
[tsmap track=<id>]
See the FAQ section for more information on the shortcode’s supported attributes.
Requirements
Trackserver requires PHP 7.3 or newer and it needs both DOMDocument and SimpleXML extensions installed.
Credits
This plugin was written by Martijn Grendelman. Development is tracked on Github.
It includes some code and libraries written by other people:
- Leaflet.js by Vladimir Agafonkin and others
- Polyline encoder by Eric McConville
- Leaflet-omnivore by Mapbox
- Leaflet.fullscreen by John Firebaugh and others
- Promise-polyfill by Taylor Hakes
Installation
- Use WordPress’ built-in plugin installer, or copy the folder from the plugin archive to the
/wp-content/plugins/directory. - Activate the plugin through the ‘Plugins’ menu in WordPress.
- Configure the slugs that the plugin will listen on for location updates.
- Configure your mobile apps and start tracking!
- Use the shortcode [tsmap] to include maps and tracks in your posts and pages.
Changelog
Trackserver URLs to be used in clients are changing, introducing the Universal Slug. Read the changelog!
v5.1.1
Release date: 15 April 2025
Fixed:
* Fix for CVE-2025-30961 now actually merged.
v5.1.0
Release date: 15 April 2025
Fixed:
* Escaping issues with dynamic output (CVE-2025-30961).
* Nonce checking in the backend.
* Missing property declarations in several classes.
* Unknown function calls in TrackMe and MapMyTracks handlers.
* Coding style recommendations.
* Visibility declarations of various functions and properties.
* Illegal function use in file upload handler in the backend.
* Explicit loading of WordPress functions for file uploads.
* Double output of HTML title element in embedded maps page.
* Filename with illegal character in Leaflet Fullscreen plugin.
* Removed WP admin bar from embedded maps output.
* Silenced warning messages from GPX schema validation.
* Removed some debugging code.
* WordPress compatibility set to v6.8.
* Minimum PHP version set to 7.3.
Known bug:
* uLogger support is broken when WP permalinks are disabled.
v5.0.3
Release date: 09 January 2025
Fixed:
* XSS in the ‘tsmap’ shortcode handler (CVE-2024-12505).
* WordPress compatibility set to v6.7.
v5.0.2
Release date: 05 March 2023
Fixed:
* Regression with viewing tracks in WP backend via bulk action.
v5.0.1
Release date: 06 February 2023
Fixed:
* JS localization warning in WP backend.
v5.0
Release date: 06 February 2023
This release contains many changes. Please read these notes carefully.
BIG CHANGE: Trackserver URL change for all supported apps. Starting with v5.0, Trackserver uses a single URL slug for all supported apps. This means all users have to update the server URL in the mobile apps they use for tracking. App-specific URLs still work, but will be removed in a future version. After upgrading, visit the Trackserver Options page and look at the ‘Full URL’ lines at the top. There are two versions of the universal URL. Trackserver will tell you which URL to use in which app.
BIG CHANGE: App-specific passwords and access keys (used for TrackMe, OsmAnd and SendLocation) have been transformed into ‘App Passwords’, and are now app-independent. Existing access keys are automatically converted to App Passwords during the upgrade, and will all be valid for all supported apps, including the apps that worked with your WordPress password before (OruxMaps / MapMyTracks and OwnTracks). Your WordPress password will still work for those apps, but that may change in a future release. Switching to App Passwords is recommended, regardless of the app you use for Tracking. The main benefit is an increase in security, because your WordPress password will no longer be necessary for using Trackserver. Trackserver App Passwords can be changed often without impacting WordPress logins. As an added bonus, App Passwords also work in WordPress installs that use SSO mechanisms like OAuth2 for user logins.
Added:
* A search box on the tracks management page.
* Experimental uLogger support.
* Universal slug for all protocols that Trackserver supports.
* App passwords.
* Generic ‘GET request’ support for storing locations, used for OsmAnd and Sendlocation support.
* ‘Duplicate’ bulk action for copying tracks.
* Some useful links to Github and Trackserver home page from the Plugins page in WP admin.
Changed:
* Big code restructuring changes. The main Trackserver class has been split up in different utility classes. Each protocol that Trackserver supports now lives in its own PHP class, as do the different WP admin pages and the shortcode handling code. Abstractions for database fuctionss, and data like tracks and locations have been created.
* Rewrite parts of the MapMyTracks protocol handling, to make it more robust.
* Internalized the polyline encoder for performance improvement.
* Update Leaflet, first to v1.7.1. then via v1.8.0 to v1.9.3.
Fixed:
* Embedded maps. The previously shipped template was broken and embedded maps did not actually work.
* Include tracks without locations in the list of tracks.
* CSS improvements.
* Better TrackMe error handling.
* A bug in metadata generation for polyline output.
* A PHP error when there are no posts in the $wp_query. Thanks, @caveman99.
Removed:
* TrackMe support via the WP AJAX interface. It was never used.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Trackserver alternatives
All gps plugins →FAQ
Trackserver: quick answers
Straight answers, pulled from live WordPress.org data.
Source: WordPress.org
Is Trackserver free?
Yes. Trackserver is free to download and use from the official WordPress.org plugin directory.
Is Trackserver safe to use in 2026?
Trackserver shows warning signs in 2026 — compare the alternatives below before installing. It runs on 400+ sites, is rated 5/5 and was last updated 1 year ago, and scores 37/100 on our health check.
How many websites use Trackserver?
Trackserver is active on 400+ WordPress websites and has been downloaded 22,253 times since it launched in February 2015. It was downloaded 310 times in the last 30 days.
Does Trackserver work with WordPress 7.1?
Trackserver is officially tested up to WordPress 6.8.13, while the latest release is 7.1.5. It may still work, but try it on a staging site first.
What PHP version does Trackserver need?
Trackserver requires PHP 7.3 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Trackserver last updated?
The latest version, 5.1.1, was released on September 6, 2025 (1 year ago).
Who makes Trackserver?
Trackserver is developed and maintained by tinuzz.
What are the best alternatives to Trackserver?
The most popular alternatives to Trackserver are Geolocation (300+ installs), WP-Routes Plugin (100+ installs) and Geo2 Maps Add-on for NextGE… (80+ installs).
Powered by PageForge
One template and a spreadsheet. A real page for every search.
PageForge turns each row of a CSV into a WordPress page with its own title, URL, SEO fields and schema, built on the layout you already designed. Free on WordPress.org.
- CSV and XLSX, plus Google Sheets on Professional and Enterprise
- Its own title, URL, SEO fields and schema for every page
- Works with the block editor, Elementor, Divi and Avada
- Free on WordPress.org, no credit card


