Travel Itinerary Builder

Arrange travel, stays and activities with explicit time zones and overlap checks.

On-device No sign-up Free to use

Build itinerary files controls

?

Each entry needs type, title, start/end ISO times with explicit UTC offsets, and IANA zoneStart. zoneEnd defaults to zoneStart. Travel also needs from and to.

Drop your file here

or choose one from your device

One file · .json

    Processed in your browser. Your inputs stay on this device.

    Showing an example. Change the fields, then use build itinerary files to update it.

    Result

    Showing an example.

    Plan a train trip, hotel stay and museum visit in one time zone.

    Entries sort by their UTC start times; the museum visit inside the hotel stay is allowed and the three plans export as calendar events.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/travel-itinerary-builder · 20 November 2026

    Was this helpful?

    How to use Travel Itinerary Builder

    1. Enter travel, stay or activity entries in the JSON editor. Each needs type, title, start, end and zoneStart. Travel also needs from and to; zoneEnd defaults to zoneStart. Optional notes are included in exports.
    2. Use ISO date/time values with an explicit offset, such as 2026-10-22T09:00+01:00, and a matching IANA zone such as Europe/London. For a trip between zones, enter each endpoint with its own zone and offset.
    3. Read Chronological itinerary and time conflicts. Entries sort by their UTC start instant; end must be later than start. Fix mismatched dates or offsets before exporting.
    4. Review the reported overlaps and the checking limits below. Every stay/non-stay pair is skipped; a clear result is not a check of connections, check-in times or travel feasibility.
    5. Download travel-itinerary.json to reopen later, travel-itinerary.html for a printable table, or travel-itinerary.ics for a calendar. Check imported event times in the intended calendar app.
    6. To reopen a saved project, select it under JSON itinerary to import. That file replaces editor input for the run. Enter the printable title separately; the JSON project does not save that title.

    Example: Travel Itinerary Builder

    Plan a train trip, hotel stay and museum visit in one time zone.

    You add
    Use the sample 22 October 2026 London train, stay and activity records with +01:00 offsets.
    You get
    Entries sort by their UTC start times; the museum visit inside the hotel stay is allowed and the three plans export as calendar events.

    Supported inputs and limits

    • Use 1 to 200 entries.
    • The JSON editor allows 1,000,000 characters and an imported file at most 1,000,000 bytes.
    • Entry titles and departure/arrival places allow 200 characters, zone names 80 and notes 2,000.
    • The printable itinerary title allows 150 characters.
    • Imports accept an entry array or an exported object containing entries.
    More details

    Each start/end time needs an explicit UTC offset matching the entered zone according to this browser's time-zone data.

    An outdated browser or operating system may have outdated rules.

    Overlap checking reports stay/stay pairs and any overlapping travel/activity pair.

    It skips every pair containing one stay and one non-stay, even when the other entry extends outside the stay.

    End-to-start touching is not an overlap.

    Calendar events use UTC instants and retain the entered zones in their descriptions.

    No bookings, route feasibility, transfer allowances, travel restrictions or current transport schedules are checked.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    Questions about Travel Itinerary Builder

    Why must the offset match the time zone?

    The offset identifies an instant and the IANA zone checks its local date and time. A mismatch is refused rather than silently changing your plan. Rules come from your browser, so keep its software and operating system current.

    Does a hotel stay conflict with a museum visit?

    The checker ignores all stay/activity and stay/travel overlaps, whether or not the other entry is wholly inside the stay. It reports overlapping stays and overlaps among travel and activity entries. Review arrival, departure and check-in times yourself.

    Does the calendar export make bookings?

    No. The ICS file contains events to import into a calendar; it does not contact hotels, carriers or booking services.

    Page updated · Project managed by Tony Hines · Report a problem with Travel Itinerary Builder