Some photos are missing from the timeline. Why?

The timeline is built strictly from EXIF capture time, so a frame without one cannot be placed on it and is left out rather than guessed at. Screenshots, heavily re-exported files and anything stripped of metadata are the usual cases. Those photos are still in the gallery — only this view skips them.

Either none of the photos carry GPS — many cameras have no receiver and phones drop it when location is off — or the map key isn't configured on this deployment, in which case you get the same clusters as a plain list of coordinates and counts.

In the gallery yes, on the timeline and map no. Capture metadata is only extracted from photographs today, so clips have no time or place to be plotted at.

It is exactly as exact as the camera was. We read the recorded values and never infer a time or a location — a camera with a wrong clock produces a wrong bucket, which is worth checking before a multi-camera shoot.

For hosts

Timeline & Map — the day in the order it happened

A separate view of the same gallery, grouped into time buckets and location clusters. Nobody sorts anything by hand.

Create an event All features

An evening reception in full flow, string lights overhead

Every camera stamps the frame with when it fired, and most phones add where. That metadata is already in your gallery and, delivered as one long upload-ordered grid, completely unused.

The timeline groups the event by capture time — hour by hour for a single day, day by day for anything longer than about a day and a half. The map clusters GPS-tagged frames tightly enough to separate the photos taken at the bar from the ones taken on the dance floor. A guest who wants the sangeet rather than the whole wedding goes straight there.

Operate it

The same gallery, grouped. Sections here; the timeline groups the identical set by the hour the shutter fired.

Seetha and Ram

Ashwin & Rose Studio · gallery.ashwinrose.studio

Favourites · Download · Share

Showing a sample of 1,842 photographs in All photos. Guests find themselves in any of them by face.

The gallery you hand over.

Your mark, your typography, your own web address over HTTPS — set up once, certificates handled. The sections are yours, and face search is already inside.

The InstantPix event screen, showing indexing progress, the join code and the gallery address — The event screen — indexing, the join code, and the address the gallery answers on.

How it works

01Capture time is read on the way inFrom the photo's own EXIF — the moment the shutter fired, not the moment it was uploaded.
02Photos group into bucketsHours for a same-day event, days for a multi-day one. Each bucket previews a dozen frames and expands on demand.
03GPS-tagged frames cluster on the mapClusters are about 110 m across, so distinct parts of a venue stay distinct.

At a glance

Where: Its own view, alongside the gallery
Grouping: By hour under ~36 h; by day beyond it
Map cluster size: About 110 m
Needs: EXIF capture time; GPS for the map
Video: Not placed — clips carry no capture EXIF

Availability

Live on every event.

A delivered InstantPix gallery with the studio's name, the event's sections and a photo grid — A delivered gallery: the studio’s name, the event’s sections, one grid.

Questions

Some photos are missing from the timeline. Why?: The timeline is built strictly from EXIF capture time, so a frame without one cannot be placed on it and is left out rather than guessed at. Screenshots, heavily re-exported files and anything stripped of metadata are the usual cases. Those photos are still in the gallery — only this view skips them.
Why is there no map?: Either none of the photos carry GPS — many cameras have no receiver and phones drop it when location is off — or the map key isn't configured on this deployment, in which case you get the same clusters as a plain list of coordinates and counts.
Do videos appear?: In the gallery yes, on the timeline and map no. Capture metadata is only extracted from photographs today, so clips have no time or place to be plotted at.
Is this exact?: It is exactly as exact as the camera was. We read the recorded values and never infer a time or a location — a camera with a wrong clock produces a wrong bucket, which is worth checking before a multi-camera shoot.

For hosts — more

Create an event

Back to the homepage