PLAN THE TRANSFER
Send large files: check the connection, storage and limits
For a file larger than 2 MiB, first establish a suitable Direct session. Keep both devices available, check receiver storage and wait for verified completion. Direct transfer is not a promise of unlimited size or speed.
Confirm the path before sending a large file
File size changes which path is usable. The current volunteer relay limit is 2 MiB per file, so a larger file cannot use that relay as a substitute for Direct. Public Nostr rescue supports messages and control only.
Read the active path in the actual session. A separate network test can help diagnose connectivity, but it does not establish that this transfer has a working Direct connection.
Check storage, browser behavior and available time
Orylin sends encrypted chunks and checks received bytes progressively with SHA-256. That describes the transfer mechanism; it does not guarantee that every browser can receive every file size.
Check free space on the receiving device, keep both pages open and use a stable network. Browser memory, file-saving capabilities, device resources and available upload bandwidth can all affect the result. Allow the recipient time to finish saving before ending the session.
Use completion at the recipient as the handoff check
Select the source file after connecting and follow the transfer status at both ends. An accepted invitation, an open connection or a progress bar below completion is not a finished file.
Let the receiver complete the integrity check, save the file and confirm it is usable. Keep the original until that check finishes. The hash checks transferred bytes; it is not a malware scan or a guarantee about the file's origin.
Handle a disconnect without assuming success
Check the session path and the error shown on each device. If a transfer stops after a path change, restore a suitable Direct connection. Use any recovery controls actually shown by the interface; a new invitation does not by itself prove automatic resume.
For repeated failures, try a smaller non-sensitive sample to distinguish a connection problem from a capacity or saving problem. Avoid including invitation secrets or private file contents in a support report.
Questions and answers
Is there an unlimited-file-size guarantee?
No. This guide establishes the current 2 MiB volunteer-relay limit, but does not claim a universal Direct file-size maximum or unlimited support. Browser, storage and network limits still apply.
Will changing to a fallback path keep a large transfer running?
Do not assume so. Volunteer-relay files are limited to 2 MiB, and Nostr rescue carries no files. Check the session's path and transfer state.
Can I estimate a guaranteed transfer time?
No guaranteed rate is published here. Available upload and download bandwidth, path quality and device behavior determine the actual transfer time.
Connect