Wren SentGoogle Drive vs Dropbox for sending readings to clients.
Both tools were built for the same job: store files, share links. Neither was built for delivering a reading to a client. That is fine for occasional use. Where the differences start to matter is when this is part of how you run a practice.
Below is what actually changes between them for a reader, and what stays the same no matter which one you pick.
In this post
- The short answer
- How each one handles sharing settings
- How each one plays video on a phone
- Storage limits and what they mean for a reading practice
- The "Request access" problem
- When neither one is the right tool
- The short version
The short answer
For sharing card photos and short audio: both work fine. For sharing long video readings: Dropbox is slightly more reliable on mobile, Google Drive integrates more naturally if your client uses Gmail. Neither feels like a delivery experience that matches the reading. Both leave your client navigating a generic file interface.
If you are choosing between the two, pick whichever you already use. The friction with both is in the same places.
How each one handles sharing settings
Google Drive defaults to Restricted. This means only specific Google accounts can view, and your client has to be signed into the matching account. If they are not, they see the "Request access" screen. To make a Drive link viewable by anyone, you change the setting to "Anyone with the link." This is a manual step every time, and it is the single most missed step in Drive sharing.
Dropbox defaults to "Anyone with the link" for free accounts. The default works the way most readers expect. There is less to remember and fewer accidents. Dropbox business plans add team-only restrictions, which can quietly catch you out if you upgrade and the default changes.
This single difference accounts for a meaningful share of the client friction readers report with Drive. Drive is not worse, exactly. It just requires you to remember the setting every time.
How each one plays video on a phone
Most clients open reading links on their phones. This is where the experience diverges most.
Google Drive on mobile streams short videos reliably and longer videos unreliably. A 30-minute 1080p video frequently loads slowly, buffers, or fails to start at all. The Drive interface on mobile prioritises file management, not playback. Clients sometimes see a download prompt instead of a play button.
Dropbox on mobile streams more reliably for longer files, but pushes clients toward installing the Dropbox app. If they install it, playback is smoother. If they do not, they get a web preview that works but feels generic.
Neither is great for long video. Both are passable for short video and audio.
Storage limits and what they mean for a reading practice
Google Drive gives you 15 GB free, shared with Gmail and Google Photos. A single 30-minute 1080p video can be 2 to 5 GB. If you store readings here, the free tier fills up in roughly 5 to 10 readings. Paid plans start at 100 GB for a few dollars a month.
Dropbox gives you 2 GB free, which is enough for a few card photo galleries and short audio but will not hold even one long video. Paid plans start at 2 TB for a higher monthly cost than Drive's equivalent tier.
For a reading practice, neither free tier is enough if you record video. Drive is cheaper at the storage tier most readers actually need.
A note on retention: both services keep your files until you delete them. But links can change behaviour without warning. Drive has updated its sharing model multiple times. Dropbox killed its public folder feature in 2017, breaking every existing link. Building a delivery system on a free consumer service means accepting that the rules can change.
The "Request access" problem
This deserves its own section because it is the single most common delivery complaint readers hear from clients.
Your client opens the link. They see a blank page with a "Request access" button. They click it. The request comes to your inbox. You approve it. They reload. Now the video plays, but the moment is already gone. Whatever they were feeling when they opened the link has been replaced by the experience of being locked out.
This happens almost exclusively with Google Drive, almost always because the sharing setting was left on Restricted. The fix is to set every link to "Anyone with the link" before sending. The reason it keeps happening is that Drive defaults to Restricted and the sharing dialog buries the public option.
If you are using Drive, the workaround is to set up a dedicated folder with public sharing as the default, then save every reading into that folder. Files inherit the folder's sharing settings. This removes the manual step and prevents most "Request access" incidents.
When neither one is the right tool
Both Drive and Dropbox were built for storing and sharing files. A reading is more than a file. It is a video link alongside card photos alongside a written note alongside a personal greeting. Both services can hold these as separate items. Neither presents them as one experience.
If the delivery is part of how you want your work to be received, a tool built for that job will fit better than a tool built for file storage. A delivery page puts your name at the top, opens with a personal note, and presents everything as a single experience. Video stays on YouTube or Vimeo where it streams reliably. Audio embeds from wherever you host it. Card photos and written work sit on the page itself. The link is one URL.
This is what Wren Sent does. Drive and Dropbox are not the wrong tools, exactly. They are the tools that exist when no one has built the right one yet.
This is what Wren Sent does.
One link. Your name at the top. Their reading waiting. Embed your video and audio from where you already host them. Add card photos and a personal note. Start free, no card required.
The short version
Drive and Dropbox both work for sending files. Neither feels like a delivery experience built for a reading. The differences between them are real but small: Drive defaults to Restricted and surfaces the "Request access" screen, Dropbox defaults to public and pushes the mobile app. Pick whichever fits your existing workflow. Or pick a tool that was built for what you are actually doing.
Frequently asked