Send large files. Keep the originals.
Upload videos, photo collections and project files, then send a download link. Start with 5 GB free, follow the transfer progress, and verify the file before your client opens it.
Check space and delivery limits first
A file must fit the available account and workspace storage, as well as any workspace file-size, member or file-type rules. Your upload method can add its own limits. Leave room for the rest of the project; the storage indicator is not a reservation.
Free includes 5 GB storage, up to 5 active share links, expiry up to 7 days and 10 GB of share-link downloads per day. The download allowance applies across links; reaching it pauses downloads until the window resets.
Check the allowances and storage plans before arranging a large delivery.
Upload, verify, deliver
Upload
Choose the workspace and folder, then select your source files. Larger web uploads use multipart transfer; storage and workspace rules still apply.
Verify
Wait for Done, then open the stored file and check its name, size and contents. Keep the original until verification succeeds.
Deliver
Create a share link with the access settings you need. Public-link recipients can download without an account, subject to those settings and allowances.
See the transfer workflow
Illustrative flows for a browser upload and public share link. They show the steps, not a measured transfer or a speed guarantee.
Scroll each diagram sideways to see every step.
Uploading a large video file
CHUNKEDRecovering an interrupted multipart upload
RECOVERYSharing a file with a password-protected link
SHAREDAn interruption is a state to check
Keep the source unchanged. Before adding it again, inspect its queue row and destination so you do not create an unnecessary second upload.
The tab is still open
Restore the connection. If a row shows Error and Retry is available, retry that row. Storage, permission and file-type errors need their stated cause resolved first.
The page was refreshed
An Interrupted row needs Resume and the unchanged original file. A retained Error row may first need Retry all failed. The browser saved queue information, not permission to read your source again.
Multipart recovery asks the server which parts remain available. Smaller single-request uploads restart. Keep the browser open and the device awake until Done; recovery is not guaranteed after a session expires or browser records are cleared. Follow the network recovery guide or refresh recovery guide for the exact controls.
Built for large file workflows
Resumable Uploads
Multipart uploads can reuse parts still recorded by the server. After a refresh, reselect the unchanged source file to recover an interrupted row.
Parallel Chunking
In the web app, files larger than 50 MiB use 10 MiB parts with up to four parts in flight per file. Other clients use their own transfer settings. See S3 multipart guidance.
Choose your protection
HTTPS protects transfers in transit. A share-link password controls access; Vault adds client-side encryption through its separate file and sharing workflow.
Know your allowances
No per-GB egress bill does not mean unlimited downloads. Free share links have a shared daily download allowance; check the current limits before a delivery.
Instant Share Links
Set a password, expiry and download count. Check access in a signed-out browser before sending a public link. Explore sharing controls.
Cloud-to-Cloud
Import straight from Google Drive, or paste a link and let our servers fetch it.
Who uses dosya.dev transfers?
Video & Post-Production
Send exports and project assets with a clear delivery note. Follow the video delivery guide.
Photography
Separate client-ready images from working originals. Plan a full-resolution gallery handoff.
DJs & Music Producers
Label mixes, masters and stems so the recipient can find the intended version. See the audio delivery checklist.
Small Creative Teams
Collect incoming assets with a file request, then use a separate share link for the approved delivery.
Before you send the client a link
Try this with one small, non-confidential sample before a full project.
1. Confirm the destination
Check the account, workspace, folder and available space before adding the file. Keep your original copy.
2. Verify the result
Wait for Done; 100% byte progress alone is not completion. Check the stored name and size. Open or download it; use a checksum when byte-for-byte integrity matters.
3. Test recipient access
Create the link and choose its password, expiry and download count. Test it while signed out. Test downloads use the link count and Free download allowance, so leave enough remaining for the recipient.
4. Send a useful handoff
Include the filename, version, expected size and delivery deadline. Share a password separately when used, and keep an independent backup.
Large file transfer questions
How do I send a large file with Dosya?
Create an account, select the destination workspace and folder, and upload the file. Wait for Done, check the stored result, then create a share link. Open the link in a signed-out browser to check the recipient experience before sending it. Allow for the test when setting a download count.
What is the maximum file size?
Dosya does not add a fixed per-file cap to each plan. Your effective limit depends on remaining storage, workspace and member restrictions, the upload method and any credential limits. A plan's total storage is not a promise that every file of that size can be uploaded.
Can I send large files for free?
Free includes 5 GB of storage, up to 5 active share links, expiry up to 7 days and 10 GB of share-link downloads per day. Those are separate allowances: multiple recipients can use the daily download allowance even when you stored a file only once.
Does the recipient need a Dosya account?
A public share-link recipient can download without signing up. They still need the link password if you set one, and the link must be within its expiry, download count and applicable download allowance. Private sharing has different access requirements.
Will my upload resume after I close the browser?
After a refresh or reopen, the browser needs you to reselect the unchanged original file. An Interrupted row offers Resume. Multipart recovery can reuse parts still recorded by the server; a small single-request upload restarts. A retained Error row after reload may need Retry all failed before Resume becomes available. Sessions and browser records are not kept indefinitely.
How long will a large transfer take?
It depends on file size, your upload connection, recipient download connection, device and service conditions. The progress display helps you monitor the active transfer, but it is not a guaranteed finish time. Keep the device awake and verify completion before promising delivery.
Does a password-protected link mean end-to-end encryption?
A link password controls access to that share. It does not turn an ordinary file into a Vault-encrypted file. Vault has a separate encryption, recovery and sharing workflow; choose it deliberately when you need client-side encryption.