What people use drop. for
Each page explains one job: where the files come from, what drop. does with them and how to set it up.
By task
- One library for all your AI toolsA chart made in ChatGPT can go straight into a doc Claude is writing, without downloading it and uploading it again.
- Screenshots and recordings in pull requestsCoding agents and the CLI turn a screenshot into a markdown image for a PR, an issue or a ticket.
- Email files into your libraryForward an attachment, or point a scanner at your drop. address, and the files arrive in the library with links.
- Uploads from systems that only speak SFTPPoint an ERP export, a photo studio or a cron job at sftp.drop.media. Folder names set privacy and expiry.
- Share a private file with a link that expiresPrivate files stay off the CDN. You hand out a signed link that stops working after an hour, a day or a week.
- Run your own code when a file arrivesA signed webhook fires when a file is added, shared, deleted or expires, however it got there.
- Generate images and keep themGenerate an image from your agent, the CLI or the website. It is hosted straight away, and the prompt stays with it.
By industry
- E‑commerce and retailProduct photos from the studio over SFTP, supplier files by email, and webhooks that pass each one to your store.
- AgenciesSend work to clients privately, get screenshots into tickets, and keep each client’s files apart.
- Software teamsScreenshots in pull requests, files from CI, and one place your coding agents can save to and search.
- Operations and financeScans and invoices by email, nightly exports over SFTP, and reports shared with links that expire.
Something else in mind?
Tell us what you need