Kindred Reels is now Kindred Scenes. Same app, same films, and your old links still work.

How it's built

What happens to your photos and videos between adding them and watching the film.

  1. You add photos and videos
    From your phone, Google Photos, or family you invite
  2. Each one gets a close look
    Google's Gemini
  3. The timeline is built
    25 steps, most of them plain code
  4. You make it yours
    Order, music, theme, pace
  5. The film is made
    FFmpeg on Google Cloud Run
  6. You watch and share
    720p to 4K
The whole trip, from your camera roll to the finished film
Step 1

Every photo gets a close look

Each new photo goes straight from your browser to private storage on Google Cloud. A worker on Cloud Run makes smaller copies and shows it once to Google's Gemini, which notes the faces, where the eye should go, a caption, what kind of photo it is and how strong a shot it is.

Two hikers walking up a grassy ridge with mountains behind
2 faces found, focus point
Caption
Two hikers reach the ridge above the clouds.
Kind
People
Setting
Outdoors
Quality
Good
How strong a shot it is
Subject
7
Engagement
8
Composition
8
Moment
7
Upright, nothing to rotate
An illustration of the notes kept for one photo

A photo is turned only when exactly one way up looks right, because a wrong rotation is worse than none. Each photo also gets an embedding: 1,408 numbers that sum up how it looks. Photos that look alike get similar numbers, which is how near-duplicates are found later.

Step 1, for video

Finding the moment in a video

A video goes to its own service on Cloud Run. It pulls a frame every two seconds (every four after the first minute), and Whisper, an open-source speech model, writes a transcript. A model then picks the most memorable moment and never cuts mid-sentence.

chosen moment, 8 sWhat the model sees: a frame every 2 sWhat Whisper hearsspeechspeech
A 30 second video: frames every 2 seconds, the speech Whisper heard, and the moment chosen

Usually that is one clip of five to ten seconds, sometimes two or three, sometimes none. The video is kept whole and trimmed only when the film is made.

Step 2

Working out when each photo and video was taken

Getting the order right matters most. Each photo's or video's date comes from the best source it has:

  1. 1
    A date you typed in
    Always wins
  2. 2
    The camera's own date
    Unless it clearly belongs to a scan
  3. 3
    A date in the file name
    Like 20260720_203724.jpg, but never a chat app save
  4. 4
    The model's best guess
    From clothes, color, film grain, faces
An old black and white family photo
summer 1923

A print scanned last spring carries last spring's date. When the camera date and the picture disagree by decades, the picture wins.

When a whole batch of file names claims the same minute, as a bulk save or a chat export does, the batch counts as undated. When a phone and a camera disagree about the time zone, the camera's clock is shifted to match.

Step 3

Setting aside the doubles and the blurry ones

The same file uploaded twice is kept once. Near-duplicates are found from the embeddings, with a cut-off worked out from each project's own photos, and a model keeps one of each group.

Near-duplicate
Kept
Near-duplicate
Too blurry

Three shots a second apart, 0.97 and 0.95 alike.

Near-duplicates keep one shot; a photo too blurry to use is set aside

Nothing is deleted. Everything left out waits in a Not Included panel with its reason, one drag away from coming back.

Step 4

Building the timeline

Building a timeline takes 25 steps. Only 8 of them can ask a model anything. The rest are plain code, because code gives the same answer every time.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
  • Plain code (14)
  • Can ask a Gemini model (8)
  • Image embeddings (2)
  • Face matching (tributes only) (1)
The 25 steps, in order

Chapters come from the gaps in time, not from a model. The pause that counts as a break is set per project, never under 45 minutes, and chapters are balanced by how long they play on screen. A larger Gemini model plans chapters only when you ask for chapters by theme or write your own.

overnight gapovernight gapDay oneDay twoDay three
A three-day trip splits at the nights

Inside each chapter a model looks at the photos and clips, at most 100 at a time, and picks the strongest, sometimes fewer than asked. One more call titles all the chapters together. Every chapter plays in date order, give or take ten minutes. If a model call fails, plain code takes over and the timeline still gets built.

Step 4, for tributes

Finding the person a tribute is for

A tribute is about one person, sometimes two. It is the only place faces are matched to a person, and only after the project's owner agrees.

The owner adds up to ten clear photos of the person. Amazon Rekognition turns the largest face in each into a template and, when the timeline is built, checks each candidate photo against them.

Reference photos, up to 10
The owner agreed first
Checked against the project's photos
1960s99.7%
1970snot him
1970s99.7%
1980s99.7%
1980snot him
2010s100%
From our founder's parents' tribute: reference photos of his father, and the photos Rekognition found him in across six decades, with its similarity scores

Photos without the person go to Not Included. Photos with no date you can trust are dated by how old the person looks, or by their era. The step that picks photos knows who is in each one. The templates are deleted with the person, the project or the account.

Step 5

Your turn: changing anything you like

The timeline is a first draft. Drag a photo or clip in from Not Included, drag one out, or drag to reorder photos and whole chapters.

Timeline
Into the valley
The lake at last
Not Included
Blurry
Near-duplicate
Not picked
Bringing a photo back from Not Included into a chapter

You can rename chapters, add one, pick the cover, turn on title cards, add a section after the credits for outtakes, and set the pace: relaxed, normal or fast. On every plan, family and friends can add their own photos and videos. On the Tribute plan they can also record a voice memory about any photo.

Step 5, music

Music that fits each chapter

Every song and every chapter is tagged with one mood (happy, upbeat, gentle or easygoing). Plain code gives each chapter a random song of its mood that is long enough, so two films rarely open on the same song. No song repeats until the library runs out.

Day oneUpbeatDay twoEasygoingDay threeHappytwo songs, 1 s crossfade
  • Happy
  • Upbeat
  • Gentle
  • Easygoing
A trip of three chapters, each with music of its own mood

You can swap any song, set its volume per chapter, or upload music you have the rights to. Photos are never squeezed to fit the music.

Step 5, the look

Themes

The title card, chapter cards and credits follow a theme. There are 12, in 4 groups (Any Occasion, Vacation, Celebration and Quiet & Reflective), and the picker previews each one with your own title and photo.

Alps Road Trip 2026 and Our 50th Anniversary are made from stock photos and clips.

Any Occasion
TimelessModern MinimalPure MinimalCinematicPhoto Album
Vacation
PostcardSummit
Celebration
Playful BirthdayGolden HourGatsby Gold
Quiet & Reflective
LinenSoft Light
The three sample videos' title cards, each in a different theme, and every theme by group
Step 6

Making the film

The film is made on Google Cloud Run Jobs, one run per film, so no film waits for another. Each photo, clip and card is rendered as its own piece, many at once, then joined with FFmpeg.

Every photo moves. The camera reads where the faces are and picks one of four moves, with a zoom of about 10 percent, like a slow breath.

starts here
ends on the whole photo
  • One or two people, faces large
    Zoom in toward them
  • A group, or faces small
    Start close, pull back
  • No people, a detail
    Zoom in on the subject
  • No people, a place
    Pan toward the subject
The faces here are small, so the camera starts close on the two hikers and pulls back

Cuts land on the beat. beat_this, a beat tracker from Johannes Kepler University in Linz, marks every beat and bar. Chapters with a voice recording keep an even pace instead.

The song's beats and bars (beat_this)Photos, each a whole number of bars
Photos last whole bars at the normal pace and whole beats at the fast pace, so every cut falls on a beat
Step 6, the sound

Mixing voices, clips and music

A clip's sound is judged twice: by Whisper, which hears speech, and by the model that watched it, which knows a toast from a gust of wind. Together they set how loud the clip plays.

Someone is talking or singing
Music
15%
Clip
100%
Cheering, fireworks, a crowd
Music
60%
Clip
40%
Wind, traffic, a TV
Music
85%
Clip
25%
Silent clip
Music
100%
Clip
0%
How loud the music and the clip play, by what is in the clip

Family members record voice memories from a link, with no account. While someone speaks the music dips to 15 percent, and every voice is leveled a little above it.

Your photos and videos

What happens to your data

Stored privately in the United States

Your photos, videos and films sit in private Google Cloud storage in Virginia, behind links that expire within a day and a half. Account records are with Amazon Web Services, also in Virginia. The Gemini analysis may run outside the US.

Nothing is generated

Models return words and numbers, never pictures. The film uses only frames you uploaded.

Your photos stay as they are

Only two changes: iPhone HEIC files become JPEG, and a sideways photo is saved upright.

Faces are named only in tributes

Elsewhere, faces are only located so the camera can frame them. Matching needs the owner to agree first.

A safety check on every photo

Google's screening runs on every photo and video. Anything it blocks stays out of the film.

Delete it all yourself

One button on your account page deletes your projects, photos, videos, recordings, films and any face data.

The full details are in the privacy policy.

Two clouds

Where each part runs

The website, the API and your account live on Amazon Web Services. The heavy media work runs on Google Cloud, next to Gemini. The numbers follow one film from upload to playback.

Your browser loads the website from Amazon CloudFront and talks to the API on AWS Lambda, which keeps projects in Amazon DynamoDB, signs people in with Amazon Cognito and, for tributes, matches faces with Amazon Rekognition. Photos and videos go straight from the browser to private storage on Google Cloud. Photo processing and clip analysis run on Cloud Run and ask Gemini on Vertex AI what is in each picture. The renderer runs on Cloud Run Jobs and saves the finished film to private storage, which the browser plays through a signed link.

  • Your browser
    The app, on a phone or a computer
    Steps 1, 5
Amazon Web Services
  • The website
    Amazon CloudFront
  • The API and background jobs
    AWS Lambda
    Steps 2, 3, 4
  • Sign-in
    Amazon Cognito
  • Projects and timelines
    Amazon DynamoDB
  • Face matching, tributes only
    Amazon Rekognition
    Steps 3
Google Cloud
  • Private media storage
    Cloud Storage, signed links
    Steps 1, 2, 4
  • Photo processing
    Cloud Run
    Steps 2
  • Clip analysis
    Cloud Run
    Steps 2
  • Gemini
    Vertex AI
    Steps 2, 3
  • The renderer
    Cloud Run Jobs
    Steps 4
  • Finished films
    Cloud Storage, signed links
    Steps 4, 5
  1. 1Upload. Your browser sends each photo and video straight to private storage on Google Cloud, through a signed link for that one file.
  2. 2A close look. Photo processing and clip analysis, both on Cloud Run, ask Gemini what is in each picture.
  3. 3The timeline. Create Timeline runs as a background job on Lambda, asking Gemini where judgment is needed and, for a tribute, Rekognition.
  4. 4The film. Create Video starts one renderer run on Cloud Run Jobs, which saves the finished film to private storage.
  5. 5Watch. Your browser plays the film through a signed link that expires.
The website and API on Amazon Web Services, the media work on Google Cloud
The parts list

What it runs on

ReactNode.js on AWS LambdaAmazon DynamoDBAmazon CloudFrontAmazon RekognitionGoogle Cloud Run and Cloud Run JobsGoogle Cloud StorageGoogle Gemini on Vertex AIGoogle multimodal embeddingsWhisperPythonFFmpegOpenCVPyTorchbeat_thisPlaywright and Chromium

Kindred Scenes is built by a small team. You can read more about us on the About page, or see the simple version of all this on How It Works.

See it on your own photos and videos

Free during the beta. No credit card.

Make your first film