You already have a travel log. It's your camera roll.

The awkward moment in day tracking is the beginning. You install something in July, and the rule you care about looks back 180 days — or a whole tax year. The app knows nothing about January.

So you try to reconstruct it. Here is what people reach for, and why each one falls short.

Passport stamps

Incomplete by design. Internal Schengen borders were never stamped, so a train from Vienna to Prague leaves no trace. And since 10 April 2026 the EU records entries and exits digitally instead of stamping at all, so recent trips will not be in there either.

Boarding passes and booking emails

Better, but they record intent rather than presence. A cancelled flight looks identical to a taken one. A trip extended by four days shows the original return. And they say nothing about the drive across a land border in the middle.

Memory and a spreadsheet

This is what most people actually do, and it fails in a specific direction: you remember trips, not days. The long holiday is easy. The Tuesday-to-Thursday work trip in February is the one that goes missing — and those are exactly the days that accumulate.

The archive nobody thinks of

Meanwhile there is a dated, place-stamped record of your movements sitting on your phone, built without you noticing. Most photos carry the moment they were taken, and many carry the coordinates too.

Track Country Days can read that. Scan From Photos walks your library, takes the capture date from each photo and works out which country the coordinates fall in, then writes those days into your history as visits you can edit like any other.

Two details matter. The capture date comes from the photo's own metadata, not the file's modified date — so photos copied between devices still carry the day they were actually taken. And the country matching runs against a boundary map bundled inside the app, entirely offline: a bulk scan never sends thousands of coordinates to a geocoding service.

What it cannot do, plainly

A photo without location data gives a date but no place, so it cannot mark a day. Days you simply did not take a photo leave gaps. And a scan reconstructs where you were when you had a camera out, which is not the same as everywhere you were.

We would rather say that than oversell it. A gap in your history is honest; a guess presented as a fact is not, and in day counting a confident wrong number is worse than an obvious hole.

The one place we do guess — and label it

There is a single exception, and it is opt-in. If you turn on filling missing days, the scan will infer the days between two photos in the same place — the reasoning being that if you photographed Lisbon on the 3rd and the 9th, you were probably in Portugal on the 6th.

Those days are marked Estimated, shown differently on the calendar, and can be cleared in bulk without touching anything else. You should never be unable to tell which of your days are recorded and which are inferred.

Worth doing once

A scan is a one-off. Run it when you install, get a year of history in a couple of minutes instead of an evening with a calendar, correct whatever looks wrong, and let automatic tracking take it from there.

As always: this is day tracking, not immigration or tax advice. We count the days — what they mean for your circumstances is a question for a professional.