Postman Chrome Extension: What It Does, Setup and Add-ons Worth Pairing

Is there still a Postman Chrome extension?

Yes, but it is a companion, not Postman itself. The official Postman extension for Chrome is Postman Interceptor, and it works alongside the Postman desktop app or the Postman web app.

Postman started life as a Chrome app that opened in its own window from the browser. Google deprecated the Chrome Apps platform in 2020, and Postman now offers a desktop app and a web app instead. Old tutorials that say 'launch Postman from chrome://apps' describe something that no longer works that way.

What survived in the browser is the part that genuinely needs to live there: capturing the requests your browser makes and handing its cookies to Postman, so you can replay an authenticated call without copying tokens by hand.

What does Postman Interceptor actually do?

Interceptor watches network requests in Chrome and sends copies to Postman, and it can keep Postman's cookie jar in sync with the browser for the domains you choose. It does not send requests on its own or show responses in Chrome.

• Capture requests: record the calls a web app makes while you click through it, then save them into Postman history or a collection.
• Filter what you capture: limit capture to a URL pattern or domain, so analytics beacons and font downloads don't bury the API calls you care about.
• Sync cookies: copy session cookies for chosen domains into Postman, so requests you send from Postman carry the same logged-in session as your browser tab.
• Reuse your browser session: useful for internal tools behind single sign-on, where getting a token manually is tedious.
• Reverse-engineer a front end: see which endpoints a page calls and with what payloads, then turn them into documented requests.

If you only need to inspect traffic, Chrome DevTools already shows it. Interceptor earns its place when you want those requests inside Postman, where you can parameterise, test and share them with your team.

How do you install and connect Postman Interceptor?

Install Postman first, then the extension, then start a capture from the extension's own window. Postman renames buttons between versions, so if a label differs slightly, check the Interceptor documentation linked below.

1. Install the Postman desktop app from Postman's downloads page, or sign in to the Postman web app in Chrome.
2. In the Chrome Web Store, open the Postman Interceptor listing, confirm the publisher is Postman, and click Add to Chrome, then Add extension.
3. Pin it: click the puzzle-piece Extensions icon in the toolbar and select the pin next to Postman Interceptor.
4. Keep the Postman desktop app running or the web app open, then click the Interceptor icon in the toolbar. The message Ready to capture should appear at the bottom of the window.
5. If it says Interceptor disconnected, check that Postman is running and that you are in a workspace where you have edit access. On Linux, or in older desktop versions, Postman may ask you to install Interceptor Bridge: in Postman click Capture requests in the footer, open the Via Interceptor tab and choose Install Interceptor Bridge.
6. On the Capture Requests tab, set optional filters for methods and for domains or URLs, such as api.example.com, then click Start Capture.
7. Use the site in Chrome, then click Stop Capture. The results open in Postman, and each session is logged under History.

Postman's own Interceptor documentation covers the current version, including saving captured requests to a collection, and is the place to check if menus have moved.

How do you sync Chrome cookies into Postman?

Open the cookie sync option and add each domain whose cookies Postman should receive. After that, requests to those domains in Postman can use the browser's cookies from Postman's cookie jar.

1. Log in to the site in Chrome as you normally would.
2. Click the Interceptor icon in the toolbar and choose Sync Cookies. Wait for the Ready to sync message.
3. Enter one or more domains, for example app.example.com. Adding a domain also syncs its subdomains; add https:// in front to sync that exact domain only.
4. Click Sync Cookies. Alternatively, do this inside Postman: click Tools in the footer, choose Cookies, click Sync Cookies, then Interceptor in the desktop app.
5. Send a request that needs authentication. If it succeeds, the session is shared.
6. Click Stop Syncing when you're done, especially for production accounts.

Synced cookies are live credentials. Anyone with your Postman workspace data could, in principle, reuse them, so avoid syncing admin sessions into shared team workspaces.

For quick one-off edits you may not need sync at all. A cookie editor lets you read or change a single value in the browser, then paste it into a Postman header.

Postman extension vs desktop app vs web app: which do you need?

Most developers need the desktop app or web app to build and send requests, plus Interceptor only when capturing browser traffic or sharing a login session. The extension alone does nothing useful.

Browsers apply cross-origin (CORS) restrictions to requests sent from web pages. That is why the Postman web app asks you to use the Desktop Agent, a small local helper, for requests it could not otherwise send, and Postman recommends the desktop app for the full experience.

For a broader toolkit around API work, our extensions for developers page groups picks by task.

Which Chrome extensions pair well with Postman?

Interceptor is the core piece, and the rest of this list covers what Postman doesn't do in the browser: reading JSON in a tab, editing cookies, clearing stale sessions and changing how the browser identifies itself. Each one below is in our developer tools category.

How do you get a request from Chrome into Postman without Interceptor?

Use DevTools: copy the request as cURL and import it into Postman. It takes a few seconds and needs no extension, which makes it the better choice for a single request.

1. Open DevTools with F12 or Ctrl+Shift+I on Windows and ChromeOS, or Cmd+Option+I on Mac.
2. Go to the Network tab, reload the page and click Fetch/XHR to hide assets.
3. Right-click the request you want, choose Copy, then Copy as cURL (on Windows, pick Copy as cURL (bash)).
4. In Postman, click Import, paste the command into the text box, and confirm.
5. Postman creates a request with the method, URL, headers and body filled in. Save it to a collection.

curl 'https://api.example.com/v1/orders?limit=20' \
  -H 'accept: application/json' \
  -H 'authorization: Bearer <token>'

Why isn't Postman Interceptor capturing anything?

Usually the connection or the filter is the problem. Check that Postman shows Interceptor as connected, then widen the filter before suspecting the extension.

• Shows disconnected: make sure the Postman desktop app is running or the web app is open, that you are in a workspace where you have edit access, and that the extension is enabled at chrome://extensions. On Linux or older desktop versions, install Interceptor Bridge.
• Connected but empty: the domain or URL filter is too narrow or has a typo. Remove it, capture briefly, then narrow it again.
• Site access limited: open the extension's Details and check Site access. If it is set to specific sites, your API host must be on the list.
• Nothing in Incognito: switch on Allow in Incognito for Interceptor, or capture in a normal window.
• Wrong Chrome profile: extensions are per profile. Install Interceptor in the profile where you're logged in to the site.
• Using Edge, Firefox or Safari: Postman's documentation lists Interceptor for Chrome, Edge, Firefox and Safari, each installed from that browser's own link.
• Web app and desktop app both open: if results or cookie sync go to the wrong place, close extra Postman tabs and reconnect.

On a Chromebook, the simplest setup is the Postman web app in Chrome plus Interceptor. Installing the desktop app means using ChromeOS's Linux environment, which is a separate feature from Chromebook developer mode and doesn't require it.

What permissions does Postman Interceptor need, and is it safe?

By design, Interceptor needs deep access: it reads requests and cookies, which is its whole job. That is reasonable from the official publisher, but it is exactly why you should limit where it runs.

Read the permission prompt when you click Add to Chrome, and later review it at chrome://extensions under Details. Set Site access to On specific sites and list only your development and staging hosts, so Interceptor never touches your bank or email tabs. Our guide to Chrome permissions explains what each warning means.

Treat any extension that asks for similar access with the same care. We explain how we review listings, publishers and permissions in our methodology, and you can compare other assistant-style tools for coding in our roundup of AI tools for developers.