GTFS·X vs. National RTAP GTFS Builder

National RTAP's GTFS Builder is the most widely used free GTFS authoring tool for small US transit agencies, and it's been the right answer for hundreds of rural and tribal operators. Calling it a competitor misses the point — it's the tool that proved small agencies could do this themselves at all. GTFS·X is the fast, free GTFS editor for the next generation of small-agency staff who'd rather work in a browser than in Excel — and for agencies that want some of the analyses (cost, demographic coverage, Title VI) without leaving the editing tool.

This page is the honest comparison. If you're a 10-vehicle rural operator producing a feed once a year for FTA reporting, RTAP GTFS Builder is probably still the right answer. If you're a 30-vehicle small-urban or a rural agency adding Flex, the calculus shifts.

Quick comparison

Where RTAP GTFS Builder is genuinely better

A few categories where RTAP has the cleaner answer:

• Excel-native teams. If your staff already lives in Excel and the existing workflow is "open the spreadsheet, update three cells, save, generate the zip," there is no upside to switching. Excel is the right tool for a workflow that's already in Excel.
• No internet dependency. RTAP GTFS Builder is a local Excel file. You can work on it offline at a desk that doesn't have reliable broadband. GTFS·X requires a working browser connection (though it does support offline editing once the page is loaded).
• Federally vetted, no-procurement option. National RTAP is a USDOT-funded program; the tool comes with FTA imprimatur. Some agencies that have to clear procurement for any cloud tool can use RTAP without that paperwork; GTFS·X is a private product and may need a software approval step at agencies with strict IT policies.
• Phone-and-chat human support. RTAP staffs a help line. GTFS·X doesn't, at the free tier; we offer docs and a community forum, plus included support on paid tiers.

If any of those four points describe your situation, you're better off with RTAP.

Where GTFS·X is genuinely better

Four categories:

• Map-based editing. Drawing a route by snapping to roads on a map is faster than typing latitude/longitude into a spreadsheet. For an agency with 20+ routes or with curvy alignments, the time savings is hours per feed update.
• GTFS-Flex. RTAP GTFS Builder doesn't support GTFS-Flex. If you operate demand-response, microtransit, or deviated fixed-route and want it discoverable in the trip planner ecosystem, you need a tool that can author Flex zones, stop groups, and booking rules. GTFS·X does this; RTAP doesn't.
• Continuous validation. The validator runs against your edits as you make them in GTFS·X. Errors surface inline with jump-to-entity links, and you can't export a feed that won't pass the canonical validator. RTAP validates at export — if you've made an error somewhere, you find out after you've built ten unrelated changes.
• Analyses for grant reporting and Title VI. Cost estimation, demographic coverage by route, and Title VI service-equity analysis are built into the editor at the Pro and Team tiers. These are the deliverables that justify "we should have a real tool" for many agencies — once you've spent two weeks pulling ACS data and writing a Title VI memo by hand, paying $199/mo for a tool that does it automatically is an obvious trade.

Which one fits your agency?

Choose RTAP GTFS Builder if you:

• Operate fewer than 15 vehicles on fixed-route only, no Flex
• Update your feed 1–2 times per year
• Have an Excel-native team
• Need a no-procurement, federally-vetted free tool
• Want the option of calling a help line

Choose GTFS·X if you:

• Operate fixed-route + Flex (or want to add Flex)
• Want to draw routes on a map instead of typing coordinates
• Update your feed 4+ times per year and want a stable hosted URL
• Need Title VI, demographic coverage, or cost analysis for grant work
• Have multiple staff working on the feed and want collaboration

A few specific points of confusion worth clearing up

"RTAP added GTFS·X to their Resources list." Yes. National RTAP listed GTFS·X on their Technology Tools page as one of the GTFS authoring options. That's not an endorsement, just an acknowledgment that both tools exist and serve overlapping needs. Pick the one that fits your workflow.

"Is RTAP GTFS Builder being deprecated?" No. National RTAP continues to support and update the tool. It is not going away. If you're using it and it's working for you, you don't need to switch.

"Can I migrate from RTAP GTFS Builder to GTFS·X?" Yes. Export a GTFS zip from RTAP GTFS Builder and import it into GTFS·X. The import handles all standard GTFS files. You'll need to redo Flex zones (RTAP doesn't have any) but everything else round-trips.

"Will my feed look different in trip planners if I switch?" No. Both tools produce standards-compliant GTFS that the canonical validator accepts. Trip planners can't tell which tool produced the feed; they just consume the data.

FAQ

Is GTFS·X really free? Yes — the editor and export are free for anyone, no signup. Paid tiers ($49/mo, $199/mo, $500/yr hosted) add feed management, analyses, and hosted publishing.

Can I use both tools? Yes. Some agencies use RTAP for fixed-route and GTFS·X for Flex. The two tools produce compatible output if you're careful about agency_id and feed merging.

What if my IT department won't approve a third-party cloud tool? GTFS·X runs entirely in your browser — no data leaves your computer until you choose to export or save. If "the data lives on our IT-approved laptop only" is the requirement, GTFS·X meets it. If "no cloud SaaS" is the requirement, RTAP's local Excel file is the cleaner answer.

Does GTFS·X support the same fare structures as GTFS Builder? Yes, plus fares v2. Both tools handle flat fares, zone-based fares, and multiple fare categories. GTFS·X also supports the v2 fare model (fare_products / fare_leg_rules) for agencies that need transfer rules or distance-based pricing.

Try GTFS·X at gtfsx.com — no signup, browser-based, free editor and export.