Google Drive & Dropbox Photo Shares

July 4, 2026

Share link vs "Save image preview"

Handoff

Metadata

Risk

Drive/Dropbox file download

Preserved

Low if already stripped

Google Photos sync

May transcode

Medium - use Drive file

Dropbox preview save

Sometimes re-encode

Avoid for masters

iCloud link confusion

HEIC surprises

Convert + strip

Always download the original file from Drive/Dropbox - not a browser preview right-click save that might grab a transcode.

Version history traps

Collaborators re-upload unclean v1 while you cleaned v2 . Instagram gets the wrong file. Use dated folders (2026-07-04_Social_Ready) and restrict edit access on archive trees.

Pair checker on downloaded file after Drive fetch - confirms sync did not swap versions.

Team SOP snippet

Retoucher strips → uploads to Client/Instagram/Ready/
Social downloads → optional checker spot → Instagram direct
Ban intermediate WhatsApp/Telegram unless emergency

Contrast messy messenger path: WhatsApp before Instagram .

Batch folders for carousel drops

Zip or folder-share 30 slides once; social batch-downloads, runs remover only if retoucher flag says "raw." Prefer retoucher-delivered cleaned sets to save time.

Verify cloud-downloaded files on the metadata checker before Instagram upload when handoff chain involves multiple editors.

Permission levels and accidental overwrite

Editor role collaborators can overwrite Social_Ready with raw exports - use Commenter for social managers or separate Ready folder with upload-only policy.

Dropbox Smart Sync placeholders

Smart Sync online-only files may confuse batch remover file picker - ensure local hydrate before strip session.

Client review vs publish tree

Client review folder keeps marked PDF proofs ; publish tree is JPG only - never upload review exports with embedded audit XMP to Instagram.

Google Drive virus scan delay

Large batch zip triggers scan delay - social manager waits for Ready flag before download; grabbing early partial zip misses slides.

Version history and backup traps

Drive version history can restore pre-strip files - social teams pin the cleaned version in changelog comments. Restoring v3 while v5 was cleaned sends dirty bytes back; name Social_Ready versions explicitly. Backup restores can resurrect pre-SOP masters - re-run checker on Social_Ready before resuming Instagram posts.

Add a README.txt in Social_Ready stating "upload these bytes only" - reduces contractor confusion more than another Slack reminder the day before launch.

Download masters, strip, then upload via the Instagram AI Info hub .

Schedulers ( Later / Buffer ) re-fetching the wrong asset: Later & Buffer file re-wrap .

See Disclaimer .