Who Uses FTP? Six Industries Where It's Still the Default

FTP (File Transfer Protocol) was specified in 1971 and still moves a meaningful share of the world's business files in 2026. The reason isn't nostalgia — it's installed-base inertia. Industries that built their partner workflows on FTP in the 1990s now have decades of equipment, scripts, and contractual integrations speaking the protocol. Replacing those is expensive; running the old protocol behind modern security controls is cheap. This post covers the six industries where FTP is still actively used, why each one relies on it, and where the modern alternatives have started taking over.

What FTP is good at

Three things keep FTP relevant despite its age:

• Large file support. FTP has no protocol-level file-size limit. Multi-gigabyte CAD files, raw video footage, terabyte-scale data sets — all move cleanly over FTP.
• Batch transfer. Drop a hundred files into a directory, run a single mput, and they all transfer. No per-file metadata overhead, no API rate limits.
• Universal compatibility. Every operating system, every major programming language, every enterprise integration platform speaks FTP. The protocol is everywhere.

What FTP isn't good at: encryption (plain FTP is cleartext — use SFTP or FTPS instead), modern API integration, anything that needs receipt acknowledgments or audit trails.

The six industries where FTP is still the default

1. Architecture, Engineering, and Construction (AEC)

The AEC industry runs on large files — CAD diagrams, SketchUp models, Revit BIM files, scanned blueprints. A single architectural model file is routinely 50–500 MB, and a project archive at completion is in the tens of gigabytes. Construction-team-to-subcontractor file exchange has been FTP-shaped for two decades.

Why FTP still fits: file size limits don't apply, multiple stakeholders need access to the same files, and the workflow is naturally "drop files, partners pick them up" rather than "real-time collaboration."

What's replacing it: most AEC firms have moved to either SFTP (encrypted version of the same workflow) or to cloud-collaboration platforms like BIM 360, Procore, and Autodesk Construction Cloud that combine file storage with workflow tools. Plain FTP is mostly seen on legacy projects and with smaller subcontractors who haven't upgraded.

2. Transcription, printing, and graphic design

Print shops, transcription services, and graphic-design vendors take large PDF and image files from clients and produce physical output. The workflow is "client uploads, vendor processes" — a perfect fit for FTP's drop-and-pick-up shape.

A typical print job might be a folder of 50 high-resolution PDFs at 200 MB each. Email can't carry that; consumer cloud sharing services can but with friction; FTP handles it natively with batch upload.

Why FTP still fits: large files, batch transfer, no real-time collaboration requirement, vendors already have FTP credentials set up with their regular clients.

What's replacing it: web-based upload portals (the same vendor's HTTPS upload page replacing FTP for new clients), SFTP for clients who do care about encryption, and per-vendor portals like WeTransfer Pro and Smash for vendors that have outsourced the transfer infrastructure entirely.

3. Web development and hosting

FTP was the way to deploy a website for two decades — point your FTP client at the hosting server, drag your HTML and PHP files into public_html, refresh the browser. WordPress, Drupal, classic shared-hosting workflows all assumed FTP as the deployment mechanism.

Why FTP still fits: small files, ad-hoc updates, no build pipeline needed for simple sites.

What's replacing it: Git-based deployment (GitHub Pages, Netlify, Vercel, Cloudflare Pages), container-based deployment (Docker images pushed to a registry), and managed CMS platforms that hide the file layer entirely (WordPress.com, Wix, Squarespace). Self-hosted WordPress shops on shared hosting still use FTP routinely; most other web dev has moved on. SFTP is the natural upgrade where FTP was once the default.

4. Finance, accounting, and business consulting

Financial workflows — batch tax filings, audit-firm document exchange, bank-to-bookkeeper statement uploads, ERP-to-CPA reconciliation feeds — have been FTP-shaped since well before the cloud-storage era. The audit-trail requirements (logs of every transfer, who uploaded what when) are stricter than most industries, and FTP servers with logging have answered those requirements for a long time.

Why FTP still fits: large recurring batches, partner-driven integrations, deeply embedded in audit-firm and accounting-software workflows.

What's replacing it: SFTP (the obvious upgrade — same workflow, encryption added), AS2 (for the larger banking and payments players), and increasingly platforms like Files.com that combine SFTP endpoints with enterprise audit logging in a single managed service.

5. Retail and hospitality

Retail supply-chain workflows — purchase orders to vendors, vendor catalogs back to retailers, daily inventory feeds, POS-to-headquarters sales reporting — were standardized on FTP in the 1990s and still run on it for thousands of retailers and their thousands of vendors.

Why FTP still fits: deeply embedded in the trading-partner integration mesh, every retailer's "vendor onboarding" packet documents the FTP endpoint, every vendor's accounting system knows how to push files to one.

What's replacing it: AS2 (mandatory for major retailers like Walmart and Target, with cryptographically signed receipts), modern API-based integrations for forward-leaning retailers, and SFTP as the encrypted compromise for the long tail.

6. Media distribution and broadcast

News organizations distributing weather-cam feeds, advertising agencies sending finished spots to broadcasters, post-production houses delivering edited content to clients, sports broadcasters sharing camera angles between stadiums and editing suites — all of this has been FTP-shaped for decades because the files are large (raw video is 1–10 GB per minute) and the workflow is partner-to-partner delivery.

Why FTP still fits: file size, batch delivery, deeply embedded in broadcast-industry workflows, partners across multiple organizations already have credentials.

What's replacing it: managed-file-transfer platforms with audit logging and DRM-aware controls (Aspera, Signiant, MediaSilo, Files.com), and large-file-transfer services purpose-built for media (MASV, Filemail, Frame.io for review-and-approval workflows).

Where FTP is fading

A few industries that used FTP in the 2000s have largely moved on:

• Software distribution. Open-source mirrors (Apache, GNU, Debian) still maintain anonymous FTP, but most software distribution has shifted to HTTPS, registries (npm, PyPI, GitHub Releases), and CDN-fronted downloads.
• Scientific data exchange. Some large datasets still ship on FTP (NCBI GenBank, NOAA weather data), but new datasets typically land on cloud object storage with HTTPS APIs.
• Personal file sharing. Once the only way for individuals to upload large files, this entire use case has migrated to cloud sharing (Dropbox, Drive) and consumer transfer services (WeTransfer).

When FTP makes sense to use today

If you're starting a new workflow in 2026, FTP itself is rarely the right answer — SFTP is the equivalent with encryption built in, and most clients can speak both. The cases where plain unencrypted FTP is still defensible:

• Public-mirror download. No credentials in the protocol, nothing sensitive to protect.
• IoT or industrial-equipment integration where the equipment can speak only FTP and changing it isn't practical.
• Legacy partner compatibility for a partner who can't speak SSH and won't move. (In this case FTPS — FTP wrapped in TLS — is the encrypted middle path.)

For any other case, SFTP is the default. Modern managed-file-transfer platforms support both, so the migration is usually a connection-string change.

The modern way

Files.com is the File Orchestration Platform we'd recommend for any team running FTP-shaped workflows in 2026. Whichever industry you're in, the platform supports the protocols your partners already speak — FTP, FTPS, SFTP, AS2, WebDAV — on the same backend storage:

• All five protocols on one platform. Partners on FTP, partners on SFTP, retail partners on AS2 — they all read and write the same files.
• Audit logging on every operation. Per-file, per-user, immutable trail. Drops into SOC 2 / HIPAA evidence collection.
• SOC 2 Type II and HIPAA-BAA out of the box. Compliance pre-built.
• Modern features the protocols never had. REST API, automation workflows, share links with passwords and expiry, MFA, SSO.

Start a free Files.com trial — no credit card, provisioned in about 10 minutes.

For teams that must run file-transfer infrastructure inside their own datacenter — air-gapped environments, regulated industries — the free ExaVault on-premise appliance handles the same protocols from a self-hosted VM image.

FAQ

Is FTP still used in 2026?

Yes — across architecture/construction, print and design vendors, web hosting (especially shared hosting and WordPress), finance and accounting, retail supply chains, and media distribution. The protocol's age is irrelevant when the installed base of equipment, scripts, and partner integrations all speak it.

What is FTP used for in business?

Bulk file transfer between partners, batch reporting feeds, large-file delivery (CAD models, video, design files, scanned documents), website deployment, IoT device data exchange, and any workflow where files need to be dropped at one endpoint and picked up at another on a schedule. For sensitive content, SFTP has largely replaced plain FTP.

Why do businesses still use FTP when there are newer alternatives?

Installed-base inertia. Trading-partner integrations, vendor workflows, scripted automation, embedded equipment — all built around FTP decades ago. The cost of upgrading the long tail is higher than the cost of running FTP behind enough security controls to make it tolerable. Most new design choices land on SFTP or a managed platform, but existing FTP workflows persist.

What industries depend on FTP the most?

Architecture, engineering, and construction (AEC), print and transcription services, web hosting and development, finance and accounting, retail supply chains, and media/broadcast. Each one has decades of FTP-shaped workflows that would be expensive to replace.

Is FTP secure for business use?

Plain FTP is not — credentials and file contents transit in cleartext. For business use, the modern defaults are SFTP (encrypted, single-port, SSH-based) for new deployments and FTPS (FTP wrapped in TLS) when a partner needs FTP-shaped semantics with encryption added. Plain FTP should be restricted to public-mirror or non-sensitive use cases.

What's replacing FTP in modern workflows?

For sensitive content: SFTP. For EDI partner exchange: AS2. For internal team collaboration: cloud sharing (Dropbox, Drive, OneDrive). For one-off external transfers: web-based file-transfer services or HTTPS share links. For automation: REST APIs and managed platforms that wrap the protocols behind a higher-level interface.