How KeepPin Works: No Accounts, No Storage, No Copies

A downloader that keeps no files sounds like a contradiction. Where does the video come from if not from the downloader's own disk? This article walks through what happens between pasting a pin link and seeing a file in your downloads folder, so the answers to "do you store my videos" and "do you log what I paste" are not just promises but consequences of the design.

Three requests, one file

Every download is three separate requests to KeepPin, each with a narrow job.

1. Parse the pin

You paste a pin URL and press the button. KeepPin's server fetches that pin's page from Pinterest the same way a logged-out visitor would, reads the data embedded in it and extracts the addresses of the media: the video renditions if it is a video pin, the original image if it is not. What comes back to your browser is a small description of the pin: a title, a thumbnail and one or more options to download.

No media is transferred in this step. The server has read a web page, not a video. If the pin is private, deleted or behind a login, this is where the process stops, because there is nothing for an anonymous visitor to read.

2. Sign a link

When you pick an option, the server produces a download URL. That URL contains the CDN address of the file, an expiry time five minutes ahead, and a signature computed over both. The signature means two things: nobody can alter the address to point somewhere else, and nobody can extend the expiry. If either is changed, the signature no longer matches and the link is refused.

3. Stream the file

Your browser opens the signed link. The server checks the signature, checks that the expiry has not passed and checks that the address belongs to one of the allowed Pinterest CDN hosts. Then it opens a connection to that CDN address and passes the bytes straight through to your browser as they arrive, adding a Content-Disposition header so the browser saves the response as a file instead of playing it inline.

That is the whole path. The complete guide to saving Pinterest videos covers what to do with the file afterwards; this article stays on what happens before it lands.

Why streaming means nothing is stored

The intuitive model of a download site is a warehouse: fetch the file, store it, hand out copies. KeepPin is closer to a pipe. During step three the server holds only the chunk of the file currently passing through it. It never writes the file to disk, never keeps a finished copy and never builds up a library of videos other people have requested.

The practical consequence is that there is no cache to fill, no old files to purge and nothing to leak. If the same pin is requested twice, it is fetched from Pinterest twice. That costs a little bandwidth and buys a service with no stored media at all.

It also explains why the file you receive is exactly what Pinterest serves. There is no re-encoding stage because there is no stored intermediate to re-encode. The article on why a properly downloaded Pinterest video has no watermark follows that thread further.

What is logged and what is not

KeepPin has no accounts, so there is no user record to attach a request to. It keeps no log of the pin links you paste. The parse step reads the URL, does its job and moves on; the URL is not written to a history table.

Two mechanisms do exist, and it is fair to describe them.

Rate limits. A script could point thousands of requests at the service and either overload it or use it to hammer Pinterest. To prevent that, the service limits how many requests a single client can make in a short period. This needs to know that requests are arriving quickly, not which pins they were for.

Ordinary web server operation. Like any site, KeepPin has to handle HTTP requests, which means it receives your IP address and browser identification in the course of serving pages. The privacy policy describes this in full. The point of this article is narrower: the content of what you download and the links you paste are not kept.

Why links expire after five minutes

A signed link that lasted forever would be a permanent shortcut through KeepPin to a Pinterest file. It could be pasted into a forum, embedded in another site or bookmarked, and every visit would route the file through KeepPin's servers again. That is a form of hotlinking, and it is unfair both to the service and to creators whose work would be redistributed under an address that hides where it came from.

Five minutes is long enough to press the download button, even on a slow connection, and short enough that a link cannot be used as a stable address. In practice you will only notice the limit if you parse a pin, walk away and come back later. The fix is to paste the pin URL again and get a fresh link, which takes a few seconds. The article on why KeepPin links last five minutes covers this in more detail, including why bookmarking a download link never works.

One distinction is worth keeping straight. The pin URL, on pinterest.com, is stable and safe to save anywhere. The download URL, on keeppin.app, is a temporary ticket. Keep the first, discard the second.

Why only Pinterest's CDN

Step three refuses any address that is not on i.pinimg.com, v1.pinimg.com, v.pinimg.com or s.pinimg.com. These are the hosts Pinterest uses to serve images and video. The restriction stops KeepPin from being used as a general-purpose proxy for fetching arbitrary files from arbitrary sites, and it guarantees that whatever streams through the service originated on Pinterest's own infrastructure.

If you are curious what those hosts are and how their paths are laid out, the article on where Pinterest actually stores your pins explains the split between the Pinterest application and its content delivery network.

Copyright requests when nothing is stored

Because no file is kept, a copyright complaint does not lead to a file being deleted; there is nothing to delete. Instead, the pin URLs named in a valid notice are added to a block list, and the parse step refuses them from then on.

Notices go to [email protected] and are handled within 48 hours. What counts as a valid notice, and what to include, is set out in the DMCA policy. Blocking a pin on KeepPin does not remove it from Pinterest; that has to go through Pinterest's own copyright process, since KeepPin is independent and not affiliated with Pinterest.

What this design cannot do

The same choices that make the service simple also set its limits.

It cannot reach private pins, secret boards, login-only content or deleted pins, because step one reads Pinterest as an anonymous visitor.
It cannot improve quality. The renditions Pinterest stores are the ceiling, and a pass-through cannot add pixels that were never there.
It cannot save a whole board in one go. Each pin is parsed on its own.
It cannot keep a link alive past five minutes, for the reasons above.

None of these are settings that could be flipped. They follow from a service that reads, signs and streams, and stops there.