altersend is a free, open source file management & sync project written in TypeScript and released under Apache-2.0. It has 2,253 GitHub stars, 146 forks and 24 open issues, and was last pushed 23 hours ago. On this registry it ranks #40 of 85 tracked projects in File Management & Sync, with 5 head-to-head comparisons available.

What is altersend?

AlterSend is a free, open-source, cross-platform file-transfer application for people who need to send files directly between devices over the internet, with end-to-end encryption, no accounts, no cloud storage and no size limit.

What it is

AlterSend is a TypeScript application, licensed under Apache-2.0, with apps for macOS, Windows, Linux, iOS and Android. It transfers files peer-to-peer, and its topic list names hole-punching, peer-to-peer networking and decentralization. The README describes a workflow in which the sender and receiver open AlterSend on both devices, and a recipient without the app can open a share link at app.altersend.com and download directly from the sender. The project is also listed on GitHub with 2,253 stars, 146 forks and 24 open issues.

The concrete problem is the upload step imposed by cloud storage and transfer services. The README asks why someone would use WeTransfer, Dropbox or Google Drive when files can go straight to the recipient, and it states that AlterSend has no cloud storage: files go directly between devices and nothing is uploaded or stored on a server. It also removes account requirements, since no signup, login or email address is needed, and it supports transfers from a 100 MB photo to a 500 GB video archive without a size limit.

Key capabilities

  • Direct peer-to-peer file transfer with no size limit, described in the README as handling a 100 MB photo or a 500 GB video archive in the same experience.
  • End-to-end encryption, with the README stating that only the user's devices can read the files.
  • No accounts, signup, login or email address required.
  • Browser-based receiving through a share link at app.altersend.com, so the recipient can download from the sender without installing the app.
  • Device pairing that lets a user pair a device once and then send to it without scanning or typing a code each time.
  • Cross-platform apps for macOS, Windows, Linux, iOS and Android, with the same code path on a local network or across continents.
  • Distribution through brew install --cask altersend, the AUR packages altersend-bin and altersend-git, a Flatpak manifest at flatpak/com.altersend.AlterSend.yaml, and release builds including EXE, DMG, AppImage and APK.

Who uses it and how

  • Individuals sending large media or archives, such as a 100 MB photo or a 500 GB video archive, without waiting for an upload to cloud storage.
  • Recipients who do not want to install an app can open a share link at app.altersend.com and download directly from the sender.
  • People who work across platforms, such as a macOS desktop and an Android phone, can pair a device once and then send to it without scanning or typing a code each time.
  • Collaborators on a local network or across continents use the same code path, according to the README.
  • Privacy-focused users who do not want accounts, signup, login or an email address can use the app without those requirements.

Getting started

Download the latest release from altersend.com/download, the Microsoft Store, Google Play, the App Store, or the GitHub releases for EXE, DMG, AppImage and APK builds. On macOS, install with brew install --cask altersend; on Arch Linux, use the AUR packages altersend-bin or altersend-git; Linux Flatpak users can build the included flatpak/com.altersend.AlterSend.yaml manifest.

How it compares

The README explicitly asks why a user would choose WeTransfer, Dropbox or Google Drive when files can go straight to the recipient. Those named services are cloud storage or transfer products, whereas AlterSend keeps files on the devices and does not upload or store them on a server. AlterSend is free and open source under Apache-2.0; the supplied facts do not provide licence or pricing details for the named services, so the comparison rests on the upload step, accounts and data ownership.

When to use it — and when not to

Use it when the sender and recipient can both be available for a direct transfer and when avoiding cloud storage, accounts and size limits matters more than asynchronous delivery. It is a poor fit for anyone who needs a recipient to download later while the sender is offline, because there is no cloud copy. Recipients without the app rely on the hosted browser receiver at app.altersend.com, and the facts do not describe a self-hosted replacement for that receiver; building from source covers the app, not a server deployment.

project readme (upstream, from github) — read inline



File transfer without the cloud storage.

Files go directly between your devices — end-to-end encrypted, no accounts, nothing stored, no limits.

License Platforms

Website · Download · Discord · X



Contents

About

AlterSend is a free, open-source app for sending files directly between your devices, with no cloud storage and no uploads. Files transfer P2P with no size limit and are end-to-end encrypted.

Why use WeTransfer, Dropbox, or Google Drive when you can send files straight to the recipient, instantly and privately, with no upload step?

Features

  • No accounts — no signup, no login, no email address required
  • No cloud storage — files go directly between devices; nothing is ever uploaded or stored on a server
  • Receive in a browser — recipients open a share link at app.altersend.com and download straight from the sender, no install
  • End-to-end encrypted — only your devices can read your files, always
  • No size limit P2P — send a 100 MB photo or a 500 GB video archive, same experience
  • Pair your devices — pair a device once, then send to it without scanning or typing a code each time
  • Cross-platform — macOS, Windows, Linux, iOS, Android
  • Works everywhere — local network or across continents, same code path
  • Multi-language — fully translated UI, available in 13 languages
  • Open source — Apache-2.0, audit every line yourself

Download

Get the latest release from altersend.com/download or directly from the table below.

Platform Download
Windows Microsoft Store (signed) · EXE installer
macOS DMG — Apple Silicon · DMG — Intel · Homebrew
Linux AppImage · Flatpak
Android Google Play · APK
iOS App Store

macOS Homebrew

You can also install AlterSend on macOS using Homebrew:

brew install --cask altersend

Linux Flatpak

You can build and install the included Flatpak manifest yourself (needs flatpak-builder):

git clone https://github.com/denislupookov/altersend.git && cd altersend
flatpak-builder --user --install --install-deps-from=flathub --force-clean build-dir flatpak/com.altersend.AlterSend.yaml

Arch Linux

AlterSend is available in the AUR as two packages: altersend-bin for official release binaries and altersend-git for the latest Git changes compiled from source.

yay -S altersend-bin
yay -S altersend-git

How it works

  1. Open AlterSend on both devices
  2. One device shows a join code (or QR)
  3. The other scans or types it
  4. Files transfer directly — peer to peer
   ┌──────────┐                                  ┌──────────┐
   │ Device A │ ◄─── direct, E2E encrypted ────► │ Device B │
   └──────────┘                                  └──────────┘
      │    ▲                                        ▲    │
      │    └───── discovery via Hyperswarm DHT ─────┘    │
      │             (hash of join code only)             │
      │                                                  │
      │            ┌───────────────────────┐             │
      └──────────► │ Relay (fallback only) │ ◄───────────┘
                   │ forwards encrypted    │
                   │ bytes it can't read   │
                   └───────────────────────┘

Under the hood

AlterSend is built on Hyperswarm, a Kademlia DHT at its core. Behind those four steps:

  1. A random 32-byte key is generated for each transfer (crypto.randomBytes(32)). That 64-char hex string is the join code you share.
  2. Peers rendezvous on a hash of that key, not the key itself. Both sides compute the same discovery key — a BLAKE2b hash derived from the join code — and join the DHT on that. The raw key never leaves your device, only its hash is published.
  3. Public bootstrap nodes are the only entry point. A handful of them get peers onto the DHT. After that, no central server is involved in discovery. Most transfers are direct peer-to-peer; when a direct connection can't be established — usually because both peers are behind symmetric NAT (for example both on a VPN) — the transfer falls back to a relay that forwards the already-encrypted stream between them without ever seeing file contents. It's on by default and can be turned off in Settings → Relay.
  4. The connection is end-to-end encrypted. Peers connect over a Noise-encrypted socket. The sender reads each file straight off disk in chunks and hashes every one with BLAKE2b; the receiver checks the hash and writes the chunk at its offset in the destination file.

Pair once, skip the code. You can pair devices you own so future transfers go straight through — no code to scan or type. Pairing only stores a public device key, the secret stays in your OS keychain, and a paired device is recognized without exposing your identity to anyone else. See docs/architecture.md for the full design.


For developers

Prerequisites

  • Node.js 20+
  • npm 10+
  • Xcode (iOS) or Android Studio (Android)

Setup

git clone https://github.com/denislupookov/altersend.git
cd altersend
npm install

cp apps/desktop/.env.example apps/desktop/.env
cp apps/mobile/.env.example apps/mobile/.env

Run

npm run dev
npm run mobile:start

Build

npm run desktop:build

Platform installers (.dmg, .exe, .AppImage) are produced by the release CI workflow — trigger manually from the Actions tab.

Project structure

apps/
  desktop/    Electron app — main + renderer + Bare worklet
  mobile/     React Native / Expo app
  web/        Browser receiver
packages/
  core/       P2P protocol — Hyperswarm, transfer orchestration, RPC
  drive/      Chunked file transfer — reads and writes files in place
  domain/     State management — Zustand store, business logic
  components/ Cross-platform UI — React Strict DOM + Tailwind
  locales/   Shared locale metadata, i18next setup, and catalogs
docs/
  architecture.md   Full system overview
  i18n.md           Translation workflow and locale coverage

See docs/architecture.md for data flow and inter-process boundaries.

Internationalization

Desktop and mobile share translation catalogs through @altersend/locales, currently covering 13 locales. See docs/i18n.md for the translation workflow.

Tech stack

Electron · React Native · Expo · Bare · Hyperswarm · Protomux · React Strict DOM · Tailwind · Zustand

Crash reporting

Crash reporting via Sentry is opt-in and off by default.


Contributors

Contributors

Contributing

Pull requests welcome. See CONTRIBUTING.md for setup, code style, and the PR process.

Security

Found a vulnerability? Follow the disclosure process in SECURITY.md — please don't open a public issue.

License

Apache-2.0 © AlterSend

Frequently asked questions

Is altersend free to use?

altersend is open source under the Apache-2.0 licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does altersend do?

Send files directly between devices over the internet - no cloud storage, no size limits.

What is altersend written in?

altersend is primarily written in TypeScript. Its source is publicly available at https://github.com/denislupookov/altersend, and it has 2,253 GitHub stars.