Video Authoring with Google Photos

Turning a folder of photos into a shareable video — and why I moved the source of truth off Google

16-04-2019

Contents

I built my first slideshow-video for a family birthday in about four minutes on my phone, sitting in a car park, and it looked genuinely good. That’s the pitch for Google Photos’ video tool in one sentence: it is the fastest way to turn a pile of stills into something with music and motion that you’d actually send to relatives. It is also, quietly, a lock-in machine — the free unlimited storage that once made it a no-brainer ended in June 2021, and the “movie” you assemble lives inside Google’s walls until you export it. So this is two posts in one: how to make the video, and how to keep the source photos somewhere you control. <h2 id="what-google-photos-is-now-honestly">What Google Photos is now, honestly</h2><div class="ad-unit ad-in-article" aria-label="Advertisement"> Advertisement <ins class="adsbygoogle" style="display:block;text-align:center" data-ad-client="ca-pub-3726833845844946" data-ad-slot="3291553914" data-ad-format="auto" data-full-width-responsive="true"></ins> <script>(adsbygoogle = window.adsbygoogle || []).push({});</script> </div> Google Photos launched at Google I/O 2015 with the killer feature of free, unlimited storage for “High quality” (lightly compressed) uploads. That deal is gone. On 1 June 2021 Google closed it: anything you upload after that date counts against the 15 GB shared across Gmail, Drive and Photos, and beyond that you’re paying for Google One. Content uploaded in High quality before that cut-off is grandfathered and still doesn’t count, which is a detail worth knowing if you’re an old account. What remains excellent is the automatic organisation and the creation tools. Photos still groups your library by date, place and — via machine learning — the faces and things in the images, and it uses that to power its video features. It runs on Android and iOS and in any browser at <a href="https://photos.google.com/">photos.google.com</a>. The point I keep coming back to is that all of this is convenience layered on top of Google’s copy of your memories. The convenience is real. The dependency is also real. <h2 id="the-2026-video-editor">The 2026 video editor</h2> If you last used this feature years ago, it has been overhauled. Google rolled out a redesigned mobile video editor in late 2025 with a single universal timeline that spans multiple clips, and a highlight video template flow that does the automatic-assembly trick: you pick a template, select photos and clips, and it cuts them to the beat of a soundtrack with text overlays baked in. Two paths, depending on how much control you want: <ul> <li>Highlight video (fast). In the Create tab, choose Highlight video, pick a template, feed it your selection, and let it auto-cut to music. This is the successor to the old “movie” feature and the descendants of those preset styles — big city, 8mm, documentary and friends — now live as templates. Great for “make me something shareable now”.</li> <li>Manual video editor (control). Open the redesigned editor and work on the universal timeline: trim clips, reorder, add still images with their own duration, drop text with proper fonts and colours, and pull a soundtrack from Photos’ built-in music library organised by mood.</li> </ul> The music matters more than people expect. The app re-cuts the sequence to fit the track you choose, so swapping the song genuinely changes the pacing and feel of the finished piece, not just the audio. <h3 id="getting-a-good-result-out-of-the-auto-tool">Getting a good result out of the auto tool</h3> A few habits make the automatic assembly noticeably better. Curate before you start — feed it fifteen strong images rather than eighty mediocre ones, because the algorithm respects your selection and won’t rescue a weak set. Put the visually strongest shot first; templates tend to lead with your first pick, and that frame sets the tone. Mix in a couple of short video clips among the stills, because motion breaks up a wall of static images and the beat-matching has something to cut against. And when the auto-cut lands a transition on the wrong frame — it will, occasionally — drop into the manual editor and nudge that one clip rather than regenerating the whole thing and losing your other tweaks. The text tools are more capable than they used to be. You can overlay titles with real font, colour and background-style choices, which is enough to caption a trip or label a year without exporting to a desktop app. It’s not motion-graphics territory, but for “Summer 2025” over the opening shot it’s exactly right. <h2 id="where-this-fits-against-a-proper-editor">Where this fits against a proper editor</h2><div class="ad-unit ad-in-article" aria-label="Advertisement"> Advertisement <ins class="adsbygoogle" style="display:block;text-align:center" data-ad-client="ca-pub-3726833845844946" data-ad-slot="3291553914" data-ad-format="auto" data-full-width-responsive="true"></ins> <script>(adsbygoogle = window.adsbygoogle || []).push({});</script> </div> Be clear-eyed about what this is. Google Photos’ video tool is a convenience editor: fast, phone-native, and template-driven. It deliberately hides the controls a serious editor exposes — you don’t get frame-accurate colour grading, multi-track audio mixing, keyframed transitions, or precise export settings. For a birthday montage or a holiday recap that’s a feature, not a limitation; the whole appeal is that you finish in minutes. The moment you want any of those missing controls, the workflow changes. Export a rough cut from Photos if it’s useful as a storyboard, but do the real work from your full-resolution masters in a dedicated editor — DaVinci Resolve is free and runs on Linux, which is where I do anything I actually care about. That hybrid split is the sensible one: Photos for the quick shareable version, a real editor for the keepsake, and your own storage holding the originals that feed both. There’s a wider pattern here that I keep bumping into. Google’s tools are superb at the last mile — the share, the quick edit, the “make me something now” — precisely because they sit on top of a copy of your data that they fully control. The instant convenience and the lock-in are the same mechanism viewed from two angles. Enjoy the convenience; refuse the lock-in by keeping custody of the raw material. <h2 id="formats-and-the-quality-ceiling-you-should-plan-around">Formats and the quality ceiling you should plan around</h2> Google Photos ingests a wide spread of formats — common stills (<code>jpg</code>, <code>png</code>, <code>webp</code>, <code>heic</code>, <code>gif</code>) plus a long list of RAW files (<code>cr2</code>, <code>nef</code>, <code>dng</code>, <code>arw</code>, <code>raf</code> and more), and the usual video containers (<code>mp4</code>, <code>mov</code>, <code>m4v</code>, <code>mkv</code>, <code>avi</code>, <code>3gp</code>, <code>mts</code>). So getting material in is rarely the problem. Getting quality out is the part to plan around. If your account uploads in “Storage saver” (the compressed tier, formerly “High quality”), stills are capped around 16 MP and video around 1080p, with visible compression on close inspection. That’s fine for a phone-to-phone share; it’s not fine if this is your only copy of a once-in-a-lifetime clip. The exported highlight video is a rendered file — re-compressed again on top of already-compressed sources — so treat the Google Photos version as the shareable derivative, never the master. Keep your masters at full resolution elsewhere. Which brings us to the actual point. <h2 id="keep-the-originals-on-your-own-server">Keep the originals on your own server</h2> Here’s my genuinely-held opinion after years of doing this: use Google Photos for what it’s brilliant at — instant sharing and clever video assembly — but do not let it be the only home for the photos themselves. The moment a subscription lapses, a policy changes, or an account gets locked, “all my memories” becomes “all my memories, hostage”. I’ve written the fuller argument for pulling this kind of thing in-house in <a href="/story/your-photos-your-server-self-hosting-immich/">your photos, your server: self-hosting Immich</a>, and the same custody logic that makes me self-host files in <a href="/story/build-your-own-google-drive-nextcloud-on-linux/">build your own Google Drive with Nextcloud</a> applies here in spades. The pragmatic middle ground: mirror your Google Photos library down to storage you own, on a schedule. <code>rclone</code> speaks to Google Photos and will pull your media to a local disk or a self-hosted store. A minimal setup after <code>rclone config</code> creates a remote: <div class="highlight"><div class="chroma"> <table class="lntable"><tr><td class="lntd"> <pre tabindex="0" class="chroma"><code>1 2 3 4 5 6 7 8 </code></pre></td> <td class="lntd"> <pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># one-time: create a remote called "gphotos" of type "google photos" rclone config # pull everything into a dated, read-only-friendly local mirror rclone copy gphotos:media/all ./gphotos-mirror \ --progress \ --transfers 4 \ --tpslimit 5 </code></pre></td></tr></table> </div> </div>Then fold that directory into whatever backup routine you already run — mine ends up on a NAS and an off-site copy. A tidy <code>cron</code> line keeps it honest: <div class="highlight"><div class="chroma"> <table class="lntable"><tr><td class="lntd"> <pre tabindex="0" class="chroma"><code>1 2 </code></pre></td> <td class="lntd"> <pre tabindex="0" class="chroma"><code class="language-gdscript3" data-lang="gdscript3"># 03:15 nightly: refresh the mirror, then let the normal backup job sweep it up 15 3 * * * rclone copy gphotos:media/all /srv/photos/gphotos-mirror --transfers 4 --tpslimit 5 >> /var/log/gphotos-mirror.log 2>&1 </code></pre></td></tr></table> </div> </div>Now Google Photos is a lens onto your library and a convenient place to build videos, not the vault. <h2 id="troubleshooting-the-annoyances">Troubleshooting the annoyances</h2> The exported movie looks softer than the source. Expected — it’s re-encoded, possibly twice if your uploads were already compressed. Build the shareable version in Photos, but edit anything you care about from full-resolution masters in a real editor. Export at the highest quality Photos offers and don’t up-scale afterwards. Highlight video templates aren’t showing up. These features roll out gradually and are Android-first. Update the app, and if it’s still missing, the feature simply hasn’t reached your account or platform yet — there’s no hidden switch to flip. <code>rclone</code> throws quota or rate-limit errors. The Google Photos API is rate-limited and, notably, <code>rclone</code> cannot always fetch original-resolution files or full metadata through it, and Google has tightened API access over time. Keep <code>--tpslimit</code> low, expect the mirror to be your safety copy rather than a bit-perfect archive, and treat the true masters as the files you kept before they ever went to Google. Music you added vanishes when you share off-platform. Licensed tracks from Photos’ library are tied to the Photos context. Export the rendered video (which bakes the audio in) rather than relying on the in-app version if you’re moving it elsewhere. The video looks fine on your phone but wrong on a TV. Highlight videos are composed for a phone-shaped frame, and casting a vertical composition to a widescreen TV pillarboxes it with black bars either side. If the target is a big screen, build from landscape source clips and check the aspect ratio in the manual editor before you export, rather than discovering it in front of the family at Christmas. An old shared movie link stopped working. Shared links point at Google’s copy, so if the underlying account changes plan, hits a storage limit, or the item is removed, the link dies. This is the lock-in made concrete — and the reason the exported file living on your own storage is the version that actually lasts. <h2 id="is-it-worth-it">Is it worth it?</h2> For making a quick, good-looking highlight video from your phone’s camera roll, Google Photos is hard to beat and I use it without hesitation — the 2026 editor is genuinely nice, the auto-cut-to-music trick still delights, and it costs nothing to try. As a place to store the only copy of your memories, I’d steer you firmly away. The free ride ended in 2021, the quality tiers compress what you feed them, and everything you build lives inside Google until you export it. So: enjoy the tool, share the videos, and keep the originals on hardware you own. Use Google Photos for the last mile, not the vault. That combination gives you the convenience with none of the hostage situation — which, after years of watching services change their terms, is the only arrangement I trust.

Written by Smarc

Founder and editor of vo.rs. A lifelong tinkerer who self-hosts far more than is sensible, hardens Linux boxes for fun, and prods the latest AI tools to see what they can really do. The how-to guides here are the notes Smarc wishes had existed the first time round.

Tagged#google-photos #video #selfhosting #backup #photos

Video Authoring with Google Photos

Turning a folder of photos into a shareable video — and why I moved the source of truth off Google

Related Content

Borg vs Restic: Painless Encrypted Backups You'll Actually Run

Your Photos, Your Server: Escaping Google with Self-Hosted Immich

ZFS for Mortals: Snapshots, Scrubs, and Surviving a Dead Disk

Unity3D on Arch Linux