PhotoShelter FTP workflow: camera upload, DAM, galleries, and routing
Separate PhotoShelter for Photographers from PhotoShelter for Brands, then map incoming FTP, galleries, DAM functions, outbound delivery, and video limits.
The short answer
PhotoShelter for Photographers can receive camera images through Incoming FTP, organize them in a gallery or collection, and support server-side outbound FTP. PhotoShelter for Brands is a separate organizational DAM product with its own upload methods. The photographer product explicitly does not support video, so capabilities must not be carried from one product family to the other.2,3,4,5
“PhotoShelter” describes two different operating models.
PhotoShelter for Photographers is the individual image-business platform: archive, portfolio, galleries, licensing, and commerce. PhotoShelter for Brands is a DAM for organizations, teams, and contributor workflows.1
A comparison that mixes their capabilities will mislead both audiences. Incoming credentials, contributor permissions, supported files, AI features, portals, and purchasing should be attributed to the correct product.
| Capability | For Photographers | For Brands |
|---|---|---|
| Primary buyer | Individual photographer/studio | Team, brand, agency, or organization |
| Incoming FTP | Dedicated user; gallery or collection target | Use Brands-specific upload documentation |
| Video | Not supported by the documented photographer product | Verify against the Brands product and plan |
| Downstream value | Client delivery, licensing, sales | Search, permissions, portals, distribution |
Incoming FTP and outbound FTP solve opposite halves of the route.
Incoming FTP is available on qualifying Photographer plans. A dedicated credential can target a gallery or collection; otherwise uploaded folder structure is reconstructed in an Incoming FTP collection.2
Outbound FTP can deliver server-side to FTP, FTPS, SFTP, and SCP destinations and continue after the photographer closes the browser or computer. That makes PhotoShelter both a destination and, for image-only workflows, a possible onward-transfer hub.3
Compare the complete workflow, not the presence of an FTP checkbox.
The important questions are who can upload, how quickly assets appear, which media types are accepted, what clients can do next, and whether the same capture must reach another destination.
Media support
The Photographer product documents images and explicitly excludes video.4
Visibility
Decide whether incoming media should enter a private collection, client gallery, or organization DAM.
Distribution
Test download, outbound delivery, permissions, and any client or talent handoff.
Fan-out
If the assignment needs PhotoShelter and another system, establish which service performs the duplication and meters it.
Frequently asked questions
Can a camera upload directly to PhotoShelter?+
Yes, when the account has Incoming FTP and the camera can reach the supplied server using compatible settings. PhotoShelter documents dedicated Incoming FTP credentials and gallery or collection targeting.2
Does PhotoShelter for Photographers support video?+
No. Its supported-file documentation explicitly says video is not supported. Do not generalize PhotoShelter for Brands video capabilities to the photographer product.4
Is PhotoShelter a Camera to Anywhere competitor or destination?+
It can be either, depending on the job. It can own the ingest-through-gallery workflow for an image business, or serve as one destination in a route that also delivers to client storage, review, and archive.
Sources
Sources were last reviewed on . Vendor interfaces and documentation can change; follow the linked source and re-test the exact production workflow.
- 01PhotoShelterPhotoShelter master brand and product families ↗
- 02PhotoShelterIncoming FTP ↗
- 03PhotoShelterExporting images via outbound FTP ↗
- 04PhotoShelterSupported file types ↗
- 05PhotoShelterPhotoShelter for Brands upload methods ↗