The KeepPin Browser Extension: What's Coming for Chrome and Edge

The most requested feature since KeepPin launched is a button on the pin itself, so you can save a video or image without copying a link and switching tabs. That button is being built as an extension for Chrome and Edge. It is in development and not yet released, and this article explains what it will do, what it deliberately will not do, and what to use while you wait.

What the extension will do

The idea is small on purpose. When you open a pin on Pinterest in a desktop browser with the extension installed, a KeepPin button appears near the pin. Click it, and the extension resolves the media behind that pin, then hands your browser a download. Video comes as MP4 at whatever resolution Pinterest stores, images as the original JPG or PNG, and animated pins as a GIF or a silent MP4, exactly as they do from the website today.

That is the whole feature. No sidebar, no feed of its own, no account to sign in to. The extension is a shortcut for the paste-link workflow described in the complete guide to saving Pinterest videos, removing the copy and paste steps and nothing else.

There is one thing it will not add. It will not walk a board and pull every pin at once. Board-wide saving is a different problem with different implications for creators and for Pinterest's own rules, and it is not on the roadmap.

What it will not collect

An extension runs inside your browser with more access than a website has, so this is the part worth being explicit about.

The extension will collect nothing. It will not record which pins you view, which you download, or which sites you visit. It will not set an identifier, send telemetry, or phone home for anything other than the request that resolves the pin you clicked. There is no account, so there is nothing to tie a download to a person.

This mirrors the website. KeepPin keeps no log of pasted links and stores no files, and the design that makes that true is described in how KeepPin works. The extension inherits that design rather than reinventing it, and when it reaches a store listing the permissions it asks for will be limited to acting on Pinterest pages and starting a download. If a listing ever asks for more than that, it is not ours.

Why it uses the same resolver as the website

Behind the button, the extension sends the pin URL to the same resolver the website uses. The resolver finds the pin ID, locates the MP4 or original image on Pinterest's CDN, signs a short-lived download link, and returns it. The browser then fetches the file directly from the CDN.

Sharing one resolver has practical consequences that favour you:

One parser, one set of fixes. Pinterest changes its page structure and link formats from time to time. When the website's parser is updated, the extension gets the same update without a separate release.
Same rules everywhere. Download links are signed and expire after five minutes, so an extension cannot become a source of permanent hotlinks. Private pins, secret boards and login-only content stay out of reach, because the resolver looks at Pinterest as a logged-out visitor.
Same output. The file you get through the extension is byte-for-byte what you would get by pasting the link, so the checks in the rest of the blog apply unchanged.

It also means the extension is thin. The heavy lifting is not shipped inside it, which keeps the code small and easy to audit.

Why desktop only

Extensions are a desktop feature. Chrome and Edge on Windows, Mac and Linux support them fully; the mobile versions of those browsers largely do not. Building for a platform that cannot run the code would be wasted work, and pretending otherwise would be dishonest.

There is a second reason. On a phone, the Pinterest app owns the pin, and the natural workflow is already the share sheet: tap Share, copy the link, paste it into KeepPin in the browser. That takes a few seconds and works on iPhone, iPad and Android. On a desktop, by contrast, you are already in a browser looking at a pin, so a button in that page is a genuine saving of effort. The Mac and Windows guide shows the current desktop workflow the extension is meant to shorten.

Chrome and Edge come first because they share an extension platform, so one build covers both. Other desktop browsers are not ruled out, but nothing is promised.

Where development stands

Version 1.4.0 of KeepPin, released 2026-08-20, focused on faster parsing and laid the groundwork for the extension: the resolver was restructured so that a browser extension and the website could call the same endpoints in the same way. That work is done and it already benefits the site.

The extension itself is still in development. It is not available in any store, and there is no release date to announce. When it ships, the browser extension page will say so, and the about page will list it in the version history alongside every earlier release.

Until then, one caution. Nothing calling itself a KeepPin extension is currently published by us. If you find one in a store or on a download site, do not install it. KeepPin is free and runs without installing anything, and the only place the real extension will ever be announced is keeppin.app. Questions about it can go through the contact page.

What covers the same need today

The website already does everything the extension will do; it just asks you to copy and paste. On a desktop, the fastest version of that loop is:

Open the pin and click the address bar, or use the share menu to copy the link.
Switch to the KeepPin tab and paste it into the box.
Click download and choose where the file goes.

Keeping KeepPin pinned in a tab makes step two instant. The download arrives with a header that tells the browser to save the file rather than play it, which is why it lands in your Downloads folder instead of opening inline; MDN's page on the Content-Disposition header explains that mechanism if you are curious.

The website also speaks 40 languages, including right-to-left layouts, and the extension will reuse those same translations rather than starting from English alone. The story of how that localisation was built is in KeepPin in 40 languages.