File Drop: Turn a Local File Into a Direct Link

What a file drop is

A file drop is the shortest path between a local file and a public web link. Traditional cloud storage services ask you to create an account, verify an email address, install desktop utilities, and organize files into folders. A file drop strips away those intermediate steps.

The core idea is simple: you drag an asset in, and a URL comes out. Nothing sits in between. It serves the need for a quick file share when you want to send an image, archive, or code asset to a coworker, post a screenshot to a forum, or embed an asset in a chat channel without friction.

Drop a file, get a link

The process on yoink.zip takes three steps:

1. Open yoink.zip in your web browser. You do not need an account. Optional Google sign-in is available, but it is never required to upload or download files.
2. Select your file or drag it directly onto the upload area. The API enforces a declared 5 GiB per-file limit, and presigned browser upload sessions remain valid for 15 minutes while the transfer finishes. Common image formats like JPG, PNG, GIF, and WebP are supported alongside general files.
3. Copy the resulting URL once the upload completes.

Every file you upload receives a direct address on files.yoink.zip. This link serves raw file bytes with the correct content type. There is no download splash page, no interstitial advertising, and no countdown timer.

Because it is a direct hotlink, you can drop a file, get a link, and immediately paste it anywhere direct URLs work. It displays inside HTML img tags, Markdown files, forum BBCode, and Discord embeds. GET and HEAD requests are open to all origins, making the links usable directly in web projects, CSS, or scripts.

What a file drop is not

A quick file drop service is designed for distribution, not persistent management. Understanding what it does not do prevents data loss.

First, it is not a backup service or a replacement for local storage. Yoink offers no promised file lifetime. If you drop a file, you must keep your original copy on your local machine.

Second, it is not a synchronization tool or collaborative workspace. There are no folder views, no directory listings, and no file versioning tools. Once uploaded, a file cannot be edited in place.

Third, it is not private storage. Anyone who possesses the link can fetch the file. There are no access controls, passwords, or per-user permissions. File links return an X-Robots-Tag: noindex HTTP header to prevent search engines from indexing the URLs, but the link itself remains completely public to anyone who receives it.

Finally, there is no self-service remote deletion. You cannot delete an object once the upload finishes.

Keep track of what you dropped

Because Yoink does not force you into an account, there is no remote management console or file library tied to your profile across multiple machines.

Instead, the browser interface uses local storage on your current device to remember only the last 5 uploads. This list provides a temporary buffer so you can copy a link you just generated if your clipboard cleared.

That list is strictly local to that single browser on that single device. If you clear your site data, switch to a phone, or upload six files in a row, earlier items vanish from the interface.

If a link matters to you or needs to be referenced later, copy the address immediately and store it in your own notes, issue tracker, or codebase. The platform delivers the link, but organizing and preserving that link is up to you.