Large file transfer · for anyone with a lot of data
You have the data. The line is the bottleneck.
Large data over ordinary internet is slow, stalls, and starts again from zero; FTP and consumer tools cap out. Boita is a dedicated fast path that uses your whole line over any distance and verifies every byte — with links, portals and automation around it. In the desktop app, a dropped connection picks up where it stopped.
Uses the whole line
UDP-based acceleration with its own rate control. Throughput climbs once and holds, instead of collapsing at every lost packet the way TCP does — whatever the distance.
Parallel sessions
A single big job runs as several sessions at once — 45 Mbps each, 10 on Pro, 50 on Scale, 100 or more on Enterprise — so one transfer can use the whole connection.
Resumes in the desktop app
In the desktop app, a dropped link, a closed laptop or a reboot picks up where it stopped by itself, and completed files are never re-sent. From a browser or the phone app, an interrupted transfer starts again, so use the desktop app for large files.
Verifies every byte
A checksum is recorded for every file at transfer time and shown on the receipt, so a delivery is checked rather than assumed.
No made-up numbers. Each card is a mechanism in the product; the calculator below shows what they add up to on your line.
Speed calculator
How long would your next transfer take?
Set the size, your connection and where the other end is. The typical-upload figure is a textbook model of TCP over that route, so you can see exactly what we assume; the Boita figure is your line rate; your plan’s sessions (45 Mbps each) are the ceiling — and because one file moves in one session, the planner on /calculators asks how the job is shaped, which changes the answer more than the plan does.
With Boita
4 h 27 min
at your line rate, parallel sessions
Typical upload
20 d 9 h
4 TCP streams, modelled 9.1 Mbps
Time saved
20 d 4 h
Faster by
110×
Honest assumptions: Boita is modelled at your full line rate with no per-GB throttling; the far end and your plan’s session allowance are the real ceilings. The typical upload gets 4 parallel TCP streams with loss-based congestion control (the Mathis model), capped at your line. Real services vary; distance and loss still hurt them, and never help.
Proof
Numbers you can check, not numbers we made up.
Speed receipts
Every finished transfer says how big, how long and how fast — and what a typical upload over that route would have done, from a stated model of TCP. The ceiling is arithmetic: 45 Mbps per session times your plan’s sessions (10 on Pro = 450 Mbps, 50 on Scale = 2.25 Gbps, 100+ on Enterprise), capped by your own line. Sessions are per file, so that ceiling is what a job of many files reaches; one large file moves in one session at 45 Mbps, the same on Pro, Scale and Enterprise.
How receipts are computed →Load-tested in the open
Measured on production on 21 September 2026 with the same client customers use: 40 Mbps per session over 10 000 small files, 791 Mbps up and 847 Mbps down from one machine with 20 sessions, 120 sessions from ten machines with zero failures, two hours of continuous transfers without a fault. The harness and every result file are in the repository; the numbers, including where it broke, are on the Trust page.
See the measurements →Status you can check
status.boita.io checks every component from outside our network every 30 to 60 seconds, announces incidents and maintenance, and is the source for the uptime SLA and its automatic credits on Scale and Enterprise.
Open the status page →Security reviewed, dated
A second-reviewer security pass over everything shipped in the week to 21 September 2026, with a failing test written for each finding before the fix. The controls, what is live and what is in progress, are on the Security and Trust pages.
Read the security page →
Who uses it
Not an industry. A situation.
Boita is for anyone who moves a lot of data and has hit the bottleneck. These are the situations people arrive with; each page works the example through with the plan’s real speed figures.
A 400 GB sequencing run to a collaborator
From the instrument PC to a lab on another continent, with a checksum on every file so the reanalysis starts from the same bytes.
FASTQ · BAM · microscopy stacks
Read the use case
Nightly off-site copies from a NAS
A headless agent on the box, a watch folder that sends only after hours, a second site filled by a download watch folder.
File server · NAS · archives
Read the use case
Render outputs to a client, as they finish
Frames leave the farm the moment they stop changing; the client opens a page with the sequence as one row and a receipt when they download.
EXR · DPX · ProRes · caches
Read the use case
Imaging studies between sites
DICOM series and whole-slide images to a reading centre or a trial sponsor, with verified recipients, an audit log and previews switched off.
DICOM · whole-slide · NIfTI
Read the use case
Tonight’s build to QA and the publisher
A watch folder on the build machine, one link per platform build, and a dashboard that shows who pulled it.
Builds · packages · symbols
Read the use case
Satellite and drone imagery to customers
Thousands of tiles per acquisition, checksummed, delivered to a link or straight into the customer’s own bucket.
GeoTIFF · COG · LAS · SAR
Read the use case
CAD assemblies and BIM models to partners
Whole folder trees with references intact, versions kept when a file is replaced, portals for suppliers to send parts in.
Assemblies · IFC · point clouds · CFD
Read the use case
Training sets to the cloud and back
Millions of small files or a few huge shards, from the CLI in a pipeline, into your own S3-compatible bucket.
Datasets · shards · checkpoints
Read the use case
An episode to a broadcaster before the cut-off
Mezzanine packages that hold line rate over distance, with a receipt that proves what landed and when.
IMF · MXF · mezzanine
Read the use case
Print-ready artwork to the press
A portal with the job number and file rules so it arrives right the first time, and approval on the delivery page.
PDF/X · layered artwork · dielines
Read the use case
A survey week out of a site office
Terabytes of captures pushed out overnight by the desktop app on a laptop on a mediocre link, resuming every time it drops.
LAS · orthomosaics · photogrammetry
Read the use case
Evidence sets to counsel
Forensic images and document sets with a checksum, a verified recipient and an audit trail for the matter file.
E01 · PST · document sets
Read the use case
Something else? All use cases · Solutions by need · Tell us what you move.
Product
One engine. Everything around it.
Transport, integrity and encryption come from the same accelerated engine whether you send from the browser, the desktop app, a watch folder, the agent or the CLI; the desktop app also resumes an interrupted transfer where it stopped. The product is what sits on top: links, portals, review, projects, automation, insights and the controls an auditor asks for.
Send
Share links, receipts, expiry, passwords
Explore
Drive
Storage, versions, search, members
Explore
Portals
Request links with forms and deadlines
Explore
Review
Sign-off on any file: PDFs, CAD, images, imaging, video
Explore
Projects & search
Jobs, tags, custom fields, files at scale
Explore
Automations
Rules, email-in, chat notifications
Explore
Insights
Time to open, client reports, bandwidth
Explore
Enterprise
SSO, SCIM, SIEM, holds, watermarks, archive
Explore
How it works
Three steps, and the engine does the hard part.
Boita adds the product around an accelerated transfer engine: accounts, links, portals, review, automation, receipts and billing. The engine does transport, integrity and encryption, and in the desktop app it resumes an interrupted transfer where it stopped.
- 01
Point Boita at the data
Drop files in the browser or the desktop app, point a watch folder at a folder that fills up, run the CLI from a script, or send a portal link so someone else can send to you.
- 02
The fast path moves it
The transfer runs as parallel sessions over UDP-based acceleration that holds your line rate whatever the distance. Drop the network and the desktop app resumes where it stopped.
- 03
It lands, verified, and everyone knows
Every file arrives with a checksum recorded on the server. Recipients open a page with nothing to install, you see who downloaded what, and rules, webhooks and chat notifications tell the rest of your systems.
If your network blocks UDP
First choice
UDP-based acceleration
Full speed, parallel sessions, and resume in the desktop app.
Automatic fallback
HTTPS path
Slower, still encrypted; the app tells you which path you are on so IT knows what to open.
Nothing to install
Browser path
Recipients and portal uploaders move files in the browser over HTTPS, where an interrupted transfer starts again; the page offers the free desktop app for full speed and resume on very large sends.
What’s new
Full changelog2026-10-11 · web · desktop · mobile
Where an interrupted transfer picks up, said plainly
Resume is a desktop-app feature. In the desktop app, an interrupted upload or download picks up exactly where it stopped. From a browser — including share links and upload links — or from the phone app, an interrupted transfer starts again from the beginning; files that had already finished stay finished. For large files, use the desktop app.
2026-09-25 · web · api
Thumbnails, a search index that keeps up, and a long list of smaller honesties
Thumbnails work. Photos, PDFs and video all get a preview in the file list now — none of them did before, because the component that fetches a file for rendering could not write where it needed to and gave up without saying so. Nothing about your files changed; they simply have pictures now.
2026-09-23 · web · mobile · api
Delete your account whenever you want, and send files straight from your phone
You can delete your account yourself, from the app or the web, without asking us. It removes your sign-in, your devices, your two-factor setup and your personal details straight away. A workspace only you belong to closes with it; one other people are working in has to be handed over first, so nobody loses their files because a colleague left. Invoices already issued are kept, because tax law requires it — boita.io/delete-account says exactly what stays and why.
Pricing
Flat plans in your currency (INR). Nothing per GB.
Four plans sized by storage, share retention and seats. Downloads and re-downloads are free on every plan. Prices are flat per month and billed in Indian rupee (INR, default).
Is Boita only for media and post-production?
No. Boita is for anyone who moves a lot of data and has hit the bottleneck: labs sending sequencing runs, hospitals moving imaging studies, engineering teams exchanging CAD and BIM models, satellite and drone operators, ML teams moving datasets, IT teams doing off-site copies, game studios shipping builds, print houses receiving artwork — and yes, studios delivering renders and episodes. The engine, the links, the portals and the automation are the same; only the examples change.
How is Boita faster than a normal upload?
Ordinary uploads run over TCP, which slows down every time a packet is lost and never recovers the distance to a far-away server. Boita moves data with an accelerated transfer engine over UDP with its own rate control, so a transfer climbs to your line rate and stays there whether the other end is across town or across an ocean. Big jobs also run as several parallel sessions: 45 Mbps per session, 10 sessions on Pro (450 Mbps), 50 on Scale (2.25 Gbps), 100 or more on Enterprise.
Do I need to install anything?
Not to start. The web app uploads and downloads in the browser, and recipients and portal uploaders need nothing installed either. For full speed, resume and watch folders, install the free desktop app (macOS, Windows, Linux) or the headless agent on a server; both carry the transfer engine, so there is no second client to keep updated.
What happens if my connection drops mid-transfer?
In the desktop app, it resumes on its own at the exact byte when the connection, the computer or the app comes back; completed files are never re-sent. From a browser or the phone app, an interrupted transfer starts again (files that already finished stay finished), so use the desktop app for large files.
What happens on a slow connection?
Boita uses whatever line you have; the plan sets the ceiling, not the floor. If your network blocks UDP, transfers fall back to an HTTPS path automatically and the app says which path you are on. On a 2G or 3G connection the delivery, portal and Files pages offer a low-bandwidth mode that switches off previews, covers and animations so the page and the link still work.
Do recipients need an account or a licence?
No. Recipients open a share page, see the files and download in the browser with nothing to install. The page offers the free desktop app for full speed and resume on very large deliveries.
Do you charge for downloads?
No. Plans are flat monthly amounts, billed in your local currency (INR in India). We do not charge per GB downloaded, and re-downloads are free. If storage overage ever applies it is shown before it happens, never after.
Where is my data stored?
In India: files, the transfer server, the application and the database run in Google Cloud, Mumbai, with encrypted backups in Mumbai and Singapore. The Trust page lists every location and sub-processor. Regional nodes elsewhere are available on request for Enterprise; a self-managed node in your own AWS account is also possible with our Terraform module.
Is there a mobile app?
Yes — Boita for iPhone and Android: your dashboard, files and search, share links with receipts, upload portals, review and approval, transfers, automations, members and security. "Send from my computer" lets you pick files on your Mac or PC from the phone and have the desktop app send them on the fast path. Uploads straight from the phone go over HTTPS at standard speed.
Next step
Try it on your next transfer, or ask a person first.
Your first delivery is free.
Create a workspace, upload, send a link. Free is 10 GB with no card; Pro and Scale are flat monthly plans in your currency. Teams moving terabytes a month can ask for a guided pilot.