Reference
Ingest methods
Every way files can enter ZenTransfer, with auth, behavior, and billing notes.
Last updated 2026-05-25
On this page
ZenTransfer accepts uploads from many sources. They behave differently in two key ways: does the upload trigger auto fan-out and what authentication is required.
Method matrix¶
| Method | Triggers auto fan-out? | Auth | Notes |
|---|---|---|---|
| Camera FTP | Yes | FTP credentials | Primary field workflow |
| Camera FTPS | Yes | FTP credentials | Encrypted variant |
| Camera SFTP | Yes | FTP credentials | SSH variant, port 2222 |
| HTTP upload | Yes | Basic or Bearer | Scripts and integrations |
| ZenTransfer Desktop (Upload mode) | Yes | Account login | SD/CF card import, folder upload |
| Mobile apps (iOS/Android) | Yes | Account login | Photo library upload |
| Browser dropzone | Yes | Web session | On the dashboard |
| Guest upload link | Yes | Guest link token | Third-party contributors |
| Drag-drop into the Browser | No | Web session | Files held for culling; deliver via Transfer panel |
| API upload | Yes | OAuth bearer token | Custom integrations |
What "auto fan-out" means¶
Methods marked Yes deliver the file to every enabled destination on your account automatically. Methods marked No (drag-drop into the Browser) hold the file for culling; you choose destinations explicitly via the Transfer panel.
This distinction is the most-asked support question — see Core concepts.
Per-method detail¶
Camera FTP/FTPS/SFTP¶
The primary field method. Configure the camera once with the host, credentials, and protocol. See:
HTTP upload¶
Standard POST/PUT to an upload endpoint with Basic Auth or Bearer token. The dashboard shows ready-made curl examples.
Use cases:
- Scripts that move files from a watch folder
- Custom integrations
- Backups from servers
Desktop app (Upload mode)¶
The Desktop app pushes files from your computer to ZenTransfer over its own protocol. Same pipeline as FTP. See Desktop app.
Mobile apps¶
The iOS, iPadOS, and Android apps upload directly from your phone's photo library. See Mobile apps.
Browser dropzone¶
Drag-and-drop a file (or many files) onto your dashboard. Authenticated by your web session.
Guest upload link¶
A tokenized URL that anyone can use to upload. See Guest uploads.
Drag-drop into the Browser¶
Drag files (or a folder) into the Browser. Files arrive in your workspace but do not auto-deliver. Use for cull-then-transfer workflows.
API upload¶
Programmatic upload via the OAuth API. See API and webhooks.
What happens after ingest¶
Files that enter via any auto-transfer path go through:
- Thumbnail / preview generation
- Resize (if enabled)
- Clear metadata (if enabled)
- Active metadata template applied
- Rename template applied
- Fan-out to all enabled destinations in parallel
- History log entry per destination
See Resize and watermarks and Metadata templates.
Billing impact¶
Ingest is free. Billing happens at delivery — one successful transfer to one destination = one billable event. See Billing and limits.
Related reading¶
- Destinations matrix — every delivery target
- Core concepts — ingest vs delivery