Trip Countdown Planner

Save every upcoming trip, watch a live countdown to departure, jot unlimited notes per trip, and keep a permanent travel history — all stored locally in your browser.

0 ongoing
0 upcoming
0 past
Loading your trips…

About Trip Countdown Planner

The Trip Countdown Planner is a permanent home for every trip you've ever planned. Save a trip, watch a live days-and-hours countdown to departure, write as many notes as you like for each one (flight numbers, hotel confirmations, packing reminders, restaurant ideas), and the whole list stays in your browser — no account, no sign-in, no server.

Past trips don't disappear when the date passes — they move to a "Past" section so you keep a permanent travel history. Export the lot to a JSON file whenever you want a backup, and import it again on a new device or after clearing cookies.

How to Use Trip Countdown Planner

  1. 1
    Add a trip. Tap "Add trip" and fill in a name, destination, and departure date. Return date is optional — leave it blank for one-way or single-day trips.
  2. 2
    Watch the countdown. Each trip card shows a live countdown to departure (or to return, if the trip is ongoing). The numbers refresh every 30 seconds.
  3. 3
    Add notes. Tap the notes button on any trip card to expand it. Each trip can hold unlimited notes — confirmation codes, things to pack, restaurants to try, anything.
  4. 4
    Edit or delete. Use Edit to change dates or rename a trip. Delete removes the trip and all its notes (with a confirmation). Notes can be deleted individually inside the expanded card.
  5. 5
    Review history. Past trips move automatically to the "Past" section. The countdown turns into "X days ago" so you can see at a glance when each trip was.
  6. 6
    Export a backup. Tap Export to download a JSON file with every trip and every note. Keep it on cloud storage, email it to yourself, whatever — it's a complete, portable copy.
  7. 7
    Import to a new device. On a new browser or device, tap Import and choose the JSON file. Trips and notes are merged into anything already there — duplicates with the same ID are updated, not duplicated.

Frequently Asked Questions

Where are my trips stored?

Everything is saved in your browser's IndexedDB — a local database tied to this device and this browser. Nothing is sent to a server. That's good for privacy, but it means trips don't automatically sync between devices or browsers. Use Export + Import to move data manually.

Will I lose my data if I clear cookies?

"Clear cookies" alone usually preserves IndexedDB. "Clear site data" or "Clear all browsing data, including site storage" will wipe it. Export a backup before doing either — Export gives you a single JSON file you can re-import any time.

How many trips and notes can I save?

In practice, thousands. Browsers give IndexedDB roughly 50–500 MB without prompting; each trip and note is a few bytes, so even a heavy traveller with 500 trips and 20 notes per trip wouldn't dent the quota.

Why doesn't the countdown count seconds?

A second-by-second tick is great for "departure in 4 hours" — useless for "departure in 87 days." The planner refreshes every 30 seconds, which is plenty for minute precision without thrashing the page. If you want a second-precision countdown in the final 24 hours, use a dedicated countdown timer.

What does Import do with duplicates?

Each trip and note has a unique ID. On import, items with an ID already present are overwritten with the imported version; brand-new IDs are added. That means importing the same backup twice produces no duplicates — and re-importing a slightly newer backup correctly updates the older copies.

Can I share a trip with another person?

Not directly — the planner is single-user by design. The simplest workaround is to Export, then send the JSON file (email, message, cloud drive). The other person opens this page on their device, taps Import, and the trip plus its notes are in their planner. You can also edit the JSON to include only one trip if you don't want to share the rest.

What format is the export file in?

Plain JSON. It's human-readable, opens in any text editor, and follows the shape { version, exportedAt, trips: [...], notes: [...] }. Trips contain id, name, destination, departureDate, optional returnDate, and timestamps. Notes contain id, tripId, text, and a created timestamp. The format is stable — exports made today will import fine on future versions.

Is anything sent to a server?

No. Trip names, destinations, dates, and notes never leave your device. The page loads HTML/CSS/JS from our server but no trip data is uploaded — there's no account system and no analytics for what you type.