Google Drive does not natively recompress ordinary uploaded videos, photos, audio files, or PDFs. To avoid downloading files to your own computer, a connected cloud service must read each file included in the run, process it on remote infrastructure, and write the result back. That can save local disk space and manual effort, but it also makes permissions, backups, and provider behavior important.
What you can do inside Google’s products
Start with Drive’s storage view to find large items and remove obvious duplicates or obsolete exports. Converting compatible office documents to Google Docs formats can change storage behavior, but it is not a general compressor for media and PDFs. Creating a ZIP in Drive packages files; it usually does not materially shrink JPEG, MP4, MP3, or already-compressed PDFs.
How a no-download compression service works
No-download means no local download for you; it does not mean the bytes are never transferred. Read the provider’s privacy policy, scope request, retention description, and replacement behavior before proceeding.
- You sign in with Google and grant the permissions disclosed on the consent screen.
- The service identifies metadata candidates that appear supported, owned, unshared, untrashed, and editable.
- After you explicitly start a run, it downloads file content to its processing environment—not to your device.
- It creates and validates a smaller output, then updates the Drive file or skips it.
A permissions and safety checklist
- Confirm the service clearly explains why it needs Drive access.
- Keep a separate copy of files whose original quality or evidentiary value matters.
- Prefer a workflow that validates the format and verifies the output is smaller before replacement.
- Know how to revoke access from your Google account.
- Test a small sample and inspect it in your usual apps before a large run.
Using Compress.My
Compress.My first estimates potentially eligible candidate data using limited metadata. It accesses content only after you start a run. Supported images, PDFs, videos, and audio files are processed remotely; inaccessible, unsupported, non-editable, already efficient, or invalid outputs are skipped. Compression is lossy and savings vary. A free allowance is available for a small trial, while paid plans are one-time processing allowances.
When local processing is still better
Use local software when you need exact encoder settings, cannot grant a third party Drive access, have archival masters, or must visually approve every file before replacement. A cloud workflow is most useful when local storage and manual handling are the main constraints.