Skip to content

← All articles

Get cookies.txt LOCALLY: Scan YouTube With Your Own Login

30 October 2026 / 4 MIN READ

YouTube refuses most requests that come from a server rather than a home connection, even for public videos. That is why a plain YouTube link does not get through Blurp yet. Proper YouTube support is something we are working on. Until it lands, there is a way that works today on a paid plan: let Blurp fetch the video as you, by giving it your YouTube login as a cookies.txt file.

Before you start

  • Saved logins are part of the Pro and Max plans.
  • A cookies.txt file is a full signed-in session: treat it like a password. If you have a spare Google account, use that one rather than your main account.
  • YouTube sees the account used from Blurp's servers as well as your own browser. That is normal for this, but it is the reason a spare account is the tidier choice.

Step 1: install Get cookies.txt LOCALLY

Get cookies.txt LOCALLY is a free, open-source Chrome extension that saves a site's cookies to a file on your computer. As the name says, it does it locally: the file is written on your machine and the extension does not send it anywhere. It is not made by Blurp and Blurp has no connection to it. Install the one with exactly that name; ignore lookalikes with similar names.

Find it on the Chrome Web Store.

Get cookies.txt LOCALLY

Step 2: sign in to YouTube in a private window

  1. In Chrome, open chrome://extensions, find Get cookies.txt LOCALLY, press Details, and turn on Allow in Incognito.
  2. Open a new Incognito window and sign in to youtube.com there, with the account you want Blurp to use.

The private window is the step people skip and the one that matters most. YouTube replaces the cookies of a session that keeps browsing, so a file exported from your everyday tab usually stops working within the hour. A private window you close straight after exporting leaves the copy you saved as the only one in use.

Step 3: export the cookies

  1. With youtube.com open in that private window, click the extension's icon in the toolbar.
  2. Choose Export (the Netscape cookies.txt format, which is its default). It saves a file named something like youtube.com_cookies.txt.
  3. Close the Incognito window straight away. Do not keep browsing in it.

Step 4: save it to Blurp

  1. In Blurp, open Account and find Site logins.
  2. Add a login for youtube.com and paste in the whole contents of the file.
  3. Blurp checks that it holds a YouTube sign-in and tells you how long it is good for. Scans of youtube.com, youtu.be and m.youtube.com links then use it automatically.

If it stops working

Logins expire, and YouTube can end a session early. If a YouTube scan starts failing, export a fresh file the same way and save it over the old one. If a scan fails with "It thinks we are a robot" even with a fresh login, YouTube refused the server itself rather than the login, and that is the part of YouTube support we are still working on.

Exactly what Blurp does with your cookies

  • Uses them only to download the YouTube videos you submit for a scan, and only while that scan is fetching.
  • Never uses them to sign in as you, browse, watch, like, comment, post, subscribe, change settings, or read your messages, history or anything else in your account. Not the people who run Blurp, and not anyone else.
  • Stores them encrypted, and never shows them back, to you or anyone.
  • Never sells them, shares them, or uses them for advertising or anything unrelated to your scans.
  • Deletes them when you remove the login from your account page, or when you delete your account.

Saved site logins come with the Pro and Max plans.

See the plans