Cross-Platform File Sharing: Transfer Between Any Device

Cross-platform file sharing is a solved problem the moment you stop relying on platform-native tools. AirDrop (Apple-only), Quick Share (Google and Samsung), Nearby Sharing (Windows-only), and iMessage all fail at the boundary. A browser link works on every operating system shipped in the last decade, because HTTP and TLS are the common language. Upload the file once, paste the URL in any chat app, and a Linux user at a CLI, an Android user on 4G, and a macOS user at a hotel Wi-Fi can all pull the same bytes.

The interop problem browser links solve

When a Windows laptop sends to an iPhone, neither AirDrop, AirPlay, nor SMB works natively. The usual fallbacks: email (capped at 25 MB), iCloud for Windows (flaky, requires Apple ID), or third-party app installs on both ends. All add friction.

A link-based transfer collapses the problem into three steps: the sender uploads to a URL, the recipient hits the URL and downloads. No identity federation, no mDNS discovery, no protocol mismatch. The file travels over HTTPS (TLS 1.3 since 2018), which every modern OS supports by default.

What has to work on every platform

A genuinely cross-platform file transfer needs:

Browser upload using the File API (spec: HTML Living Standard) — works in Safari 12+, Chrome 38+, Firefox 50+, Edge 79+.
Chunked resumable uploads for flaky connections. Implemented via Range requests over HTTP/2.
Cross-OS filename handling: NTFS allows characters Linux doesn't (and vice versa). The service needs to sanitise or preserve UTF-8 consistently.
Archive format recipients can open: .zip is the lingua franca. .tar.gz is Linux/macOS but needs 7-Zip or WinRAR on Windows. .rar is pay-software on macOS by default.
End-to-end encryption that the browser can do itself: Web Crypto API crypto.subtle is present in every tier-one browser since 2017.

The platforms and their quirks

macOS (Sonoma, Sequoia): Finder creates __MACOSX and .DS_Store files inside zips. Use zip -X from Terminal or a "clean zip" app to strip them before sending. Recipients on Windows see junk otherwise.

Windows 11: still refuses filenames with :, *, ?, ", <, >, |. Unicode is fine, but trailing spaces in filenames break. Downloads go to %USERPROFILE%\Downloads and SmartScreen may flag an archive's .exe.

Linux (Ubuntu, Fedora, Arch): case-sensitive filesystem. Photo.jpg and photo.jpg coexist. When zipping on macOS (case-insensitive by default) for Linux delivery, beware accidental name collisions.

iOS/iPadOS: the Files app opens common archives but prefers .zip. Third-party apps like Documents by Readdle handle .7z and .rar.

Android: the Files by Google app extracts .zip, but needs RAR or 7-Zip installs for others. Scoped storage since Android 11 restricts where files land.

Chrome OS: any archive the Files app recognises — .zip, .rar, .tar, .gz. Drag-and-drop from Files to a browser tab just works.

One upload, every recipient — the math

A single-pass upload at 100 Mbps for a 5 GB file takes about 7 minutes. A multi-recipient scenario (four recipients on four OSes) with individual peer-to-peer transfers would take 4× that on the slowest uplink — plus coordination. The link approach sends the file once to a server and lets each recipient pull it at their own pace, including overnight when the sender's computer is closed.

End-to-end encryption across all of them

Client-side encryption with AES-256-GCM works identically in Safari on iPad, Chrome on Android, Edge on Windows, Firefox on Linux, and Safari on macOS. The Web Crypto API is standardised (W3C Web Cryptography API, Recommendation 2017). A password typed into the browser becomes a 256-bit key via PBKDF2-HMAC-SHA256. The file is encrypted in 5 MB chunks, each with a unique 96-bit IV and a 128-bit authentication tag. The server never sees plaintext.

HexaTransfer is built on exactly this pipeline. An Android artist can send an encrypted 8 GB project to a Linux animator — same code path, same ciphertext format.

Links beat every native sharing tool

| Native tool | Who it works for | Who it excludes | | --- | --- | --- | | AirDrop | Apple ↔ Apple | Everyone else | | Quick Share | Android ↔ ChromeOS, some Windows | iOS, Linux, older Macs | | Nearby Sharing | Windows 10/11 ↔ Windows | Everyone else | | SMB/Windows Share | Same LAN | Remote recipients | | Bluetooth OBEX | Any | Too slow above 20 MB | | A shared link | Every browser | Nobody |

Filename and encoding pitfalls

UTF-8 is the only safe encoding. Send a filename with accented characters from macOS using NFC normalisation (which macOS does not — macOS uses NFD on APFS for HFS+ compatibility). A Windows recipient might see café.pdf rendered as cafe\u0301.pdf and refuse to open it. A good transfer service re-normalises to NFC and sanitises disallowed characters for Windows before storing.

Spaces, emojis, and non-Latin scripts (日本語, العربية, русский) all survive a browser-based transfer because the server stores the raw UTF-8 bytes and the download preserves them via the Content-Disposition: attachment; filename*=UTF-8''... header (RFC 6266).

Realistic cross-platform scenarios

Architect on Windows sends a 400 MB .rvt Revit model to a client on macOS reviewing in Enscape: browser upload, download, Archicad-to-Revit converter runs on either side.
Video team on Linux Ubuntu edits in DaVinci Resolve, needs to hand a 6 GB .drp project to a colourist on Windows: export the project to a .zip, upload, colourist pulls on any OS.
Photographer on iPad exports 12 GB of RAW .cr3 files, sends to a retoucher on an M3 MacBook: upload from iPad Safari, retoucher downloads in macOS Safari, all original metadata preserved.

Comparison of truly cross-platform tools

| Service | Max size | E2E encryption | No-account recipient | Resume on drop | | --- | --- | --- | --- | --- | | WeTransfer Free | 2 GB | No | Yes | No | | Smash | Unlimited | No | Yes | Partial | | SwissTransfer | 50 GB | Password-protected at rest | Yes | Yes | | Dropbox Transfer | 100 GB (Pro) | No | Yes | Yes | | HexaTransfer | 10 GB | AES-256-GCM in-browser | Yes | Yes |

The beauty of cross-platform is that the sender and recipient don't need to agree on anything. They just need a browser.

Try it at hexatransfer.com — free, no account, 10 GB max.