2026-09-24

Google Photos’ “storage saver” only resizes video above 1080p — by Google’s own wording, everything at or under that backs up at full size

The "storage full" notice reads like it's about too many photos. It usually isn't. A single minute of phone video, even compressed for sharing, runs to tens of megabytes — a thousand photos rarely add up to what a few dozen video clips do. And the fix most people reach for first — turning on Google Photos' "Storage saver" backup option — does far less than its name implies, in a way Google's own support page states plainly if you read past the first sentence.

The 15GB is one pool, and video shares it with everything else

Google's own "How your Google storage works" support page opens with the number itself: "Each Google Account includes up to 15 GB of storage, which is shared across Gmail, Google Drive, and Google Photos." That's not three separate allowances — a long phone video backed up to Photos, a video file sitting in Drive, and a large video attachment stuck in a Gmail message all draw down the same 15GB, and hitting the ceiling from any one of them blocks the other two as well.

"Storage saver" draws its line at exactly 1080p — and stops there

Google Photos' own "Choose the backup quality of your photos & videos" page describes what its space-saving option actually does to video, in one sentence each for the two settings: Storage saver — "Videos higher than 1080p will be resized to high-definition 1080p. A video with 1080p or less will look close to the original." — against Original quality — "Photos and videos are stored in the same resolution that you took them with no change to their quality." Read together, that means Storage saver's entire effect on video is a one-time check against a single threshold. A 4K recording gets pulled down to 1080p. A video that was already recorded at 1080p or below — which is still how a lot of phones default, and how most screen recordings and downloaded clips already are — passes through untouched, at whatever bitrate and file size it already had.

What "over quota" actually threatens, on Google's own timeline

The same support page spells out what happens next, not just that uploads get blocked. Crossing the 15GB line first stops new activity — no new files in Drive, no new backups in Photos, and it can affect sending and receiving mail in Gmail. Left over quota for two years, Google's own wording is that "all of your content in your Google Account may be removed" — across Gmail, Drive and Photos together, not just the service that pushed the account over. Google states it will try to give warning first — it will "attempt to give you ample notice (at least three months) before your content may be deleted" — but the underlying number that got the account there in the first place is usually video, quietly accumulating in the background of an automatic phone backup nobody's looked at closely.

Where a lossless trim and a lower-bitrate export actually help

NearVid can't change Google's quota, its notice period, or what Storage saver decides to resize — none of that runs on Google's side is something a browser tool can reach into. What it can do is shrink a video before it's ever handed to any of those three services. Trim performs a lossless stream copy — the container is re-packaged around new start and end points without decoding or re-encoding the video — so cutting a long phone recording down to the part actually worth keeping removes the rest of its bytes entirely, in roughly the time it takes to read the result rather than the time a real re-render would cost. Convert to WebM (VP8 + Vorbis, this build's ffmpeg.wasm core) or Convert to MP4 (H.264 + AAC through the browser's own WebCodecs encoder, where available) both offer a High/Medium/Low bitrate choice with an estimated output size shown before committing to the export — useful specifically for video that's already 1080p or under, since that's exactly the case Storage saver's own resize leaves alone. A phone clip recorded at 1080p and re-encoded at NearVid's "Low" bitrate setting is smaller going into the backup than the same clip left at its original bitrate, regardless of what Google's own resolution check does or doesn't do to it.

What this doesn't do

Trim and convert only affect a file before it leaves the device — neither one reaches into an account's existing Google Photos library to shrink what's already backed up; recovering space there means Google's own tools (deleting or downloading originals) or the manual work of pulling a file back down, re-exporting it, and re-uploading it. Converting doesn't touch resolution either — there's no width or scale option on the MP4/WebM path in this build, unlike its GIF export, so a 4K file processed through NearVid stays 4K, just at a smaller bitrate; it's Storage saver, on Google's side, that actually performs the resize down to 1080p for anything above that line. And nothing here changes the 15GB figure itself, the two-year clock, or the three-month notice — those are Google's policy, not a video file's problem to solve.

The honest summary

Google's own support pages draw two separate lines: Storage saver resizes video only above 1080p, and the shared 15GB across Gmail, Drive and Photos is one pool with a two-year, at-least-three-month- notice removal policy if it stays over quota. A lossless trim and a lower-bitrate convert, done entirely on-device before a video goes anywhere, shrink exactly the files that automatic resize doesn't touch — without changing anything about how Google's own storage rules work.