ProductsSecure file delivery

ArcShare

Resumable transfer + web tools · Private product

A self-hosted file-delivery product built around a simple code-based handoff, then expanded with resumable large transfers, encryption, requests, conversions, and browser-native download reliability.

Private workspace · explore the interface and workflow below.

Actual UI · sample dataArcShare
ArcShare staging two safe sample files with upload and share controls
Actual file workspace · safe sample files staged for upload
ArcShare completed local image conversion with output size and download controls
Actual browser conversion · published demo image processed locally

Inside the product

How it works

  1. Stage files or a folder and choose expiry, download limits, and access controls.

  2. Upload through a resumable transfer and share the resulting link or code.

  3. The recipient redeems the handoff and explicitly saves the file; network completion and local finalization are separate states.

  4. Use file requests or browser tools, including HEIC conversion, when the handoff needs preparation.

What it solves

The first mile of file sharing is easy. The hard part is keeping transfers understandable when files become huge, connections fail, encryption is enabled, recipients do not have accounts, and conversion or local finalization becomes a separate state.

Capabilities

  • Code-based send and receive without forcing the recipient through an account wall
  • Resumable large-file paths designed for hundreds-of-gigabytes transfers without payload-sized final copies
  • Encrypted download flows, expiry controls, file requests, URL intake, and explicit transfer states
  • Web tools including iPhone HEIC/HEIF conversion before upload or as a standalone conversion task

Where it gets hard

  • A browser transfer can finish network I/O before the local file is actually finalized
  • Multi-gigabyte retries have to resume without duplicating the payload in memory or on disk
  • Encryption, conversion, upload, ready, expired, and failed are different states
  • Simple recipient UX has to survive serious transfer and storage constraints underneath

In the loop

This product does not need AI to be useful. Reliability, resumability, encryption, conversion, and a clear transfer state machine do the important work.

The sender chooses what to share, expiry and access controls, while the recipient explicitly redeems the handoff and saves the file.

Actual product interfaces. Captions identify local previews and sample data. Screenshots do not expose private workspaces or production records.

Start a build

Start with a real workflow

Bring the idea.

If this is close to the product you need, tell us what is different. We will build the version that fits the work.

Start a Build