1. Your feed
Or drag the zip onto this box.
Choose a feed, then click Check feed.
Result
A worked example
The "example with errors" button loads a made-up four-stop bus line with seventeen kinds of problem planted in it. Among them:
agency_timezone=America/Chicgo: a misspelt time zone. Every time in the feed is read in that zone, so a consumer cannot place any trip in time.- Stop
LIBat 0,0 and stopPARKat latitude -87.62, longitude 41.89: a missing position written as zeros, and a swapped pair that lands the stop in the Southern Ocean, 14,831 km from the others. - Trip
1-0700leaves stop 2 at 07:03 and reaches stop 3 at 07:02, and has no times at its last stop. - Trip
1-0800runs on serviceWKND, which no calendar defines, so it never runs; trip9-0900belongs to a route that does not exist. - The only calendar ended on 2024-12-31, so the whole feed shows no service today.
Each one comes back with its file, line and the rule it breaks. The same checks on four real published feeds, and what they found, are in the list of every check.
What it checks, and what it leaves out
- Files: agency, routes, trips, stop_times, stops (unless locations.geojson), and calendar or calendar_dates; files at the zip's root, not in a folder; file and field names in the right case.
- Values: times (HH:MM:SS, past 24:00 allowed), dates, colours, IANA time zones, URLs, emails, language codes, coordinates and every enum in the files below.
- Keys and references: unique IDs; every trip's route, service and shape; every stop time's trip and stop; parent stations of the right type; agencies on routes when there is more than one.
- Stop times: stop_sequence unique per trip; times at the first and last stop; arrival before departure; no time earlier than the stop before; shape_dist_traveled never going down.
- Calendar: the first and last date with service, a warning under 7 days left and a note under 30 (the reference's publishing practice), days in the next 30 with no service at all, and a feed_info end date that disagrees with the calendar.
- Sanity limits this tool sets (the reference has none): straight-line speed between consecutive stops above 150 km/h for a bus (other modes in the list), stops over 100 km from the rest, platforms over 1 km from their station, route text colour below 3:1 contrast.
- Not checked yet: fares (v1 and v2), transfers, pathways and levels, flex (locations.geojson, booking rules), translations, stops far from their trip's shape, and block overlaps. Use the MobilityData GTFS Validator for the complete rule set before you submit a feed.
Check every export in CI
cli.mjs is the same engine for a terminal or a CI job, with no dependencies (Node 20 or newer). It reads the zip from disk and sends nothing anywhere.
node cli.mjs gtfs.zip # exit 1 if there are errors
node cli.mjs gtfs.zip --strict # warnings fail too
node cli.mjs gtfs/ --json # a folder of .txt files, machine-readable
node cli.mjs gtfs.zip --today=2026-12-01
A 2.6-million-stop-time feed (TriMet's, 210 MB unzipped) takes about 8 seconds in Node. In a browser tab the same feed needs a few hundred MB of memory; for feeds that size the CLI is the better fit.
Common questions
Why does a trip planner show no service from my GTFS feed?
The most common reason is that the feed has expired: every service_id in calendar.txt has an end_date in the past, so no trip runs on today's date. The checker reports the last date with any service and warns when it is less than 7 days away, the minimum the GTFS reference asks for.
What does the checker look at?
The required files and fields; every value's type (times, dates, colours, time zones, URLs, coordinates, enums); unique keys; references between trips, routes, stops, shapes, services and agencies; the order of stop times within each trip; the calendar's coverage of the next 30 days; and two sanity checks the reference does not set: straight-line speeds between stops above a per-mode ceiling, and stops hundreds of kilometres from the rest of the feed.
Is my feed uploaded?
No. The zip is opened in this browser tab with the browser's own decompression, and a test in the code asserts the page and the engine make no network calls.
Does a clean result mean Google Maps or another app will accept the feed?
No. Each consumer has its own rules and review. This tool checks the feed against the published GTFS Schedule Reference and a few sanity limits, and tells you which rule each finding comes from.
How is this different from the MobilityData validator?
The MobilityData GTFS Validator is the canonical, much larger rule set, and the right tool before you submit a feed. This checker covers fewer rules but runs instantly in a browser tab or as a zero-dependency Node script, with no install, account or upload, which suits a quick check on every export or a CI step.