Item logo image for ReFetch - Record & Replay Requests

ReFetch - Record & Replay Requests

ExtensionDeveloper Tools3 users
Item media 5 (screenshot) for ReFetch - Record & Replay Requests
Item media 1 (screenshot) for ReFetch - Record & Replay Requests
Item media 2 (screenshot) for ReFetch - Record & Replay Requests
Item media 3 (screenshot) for ReFetch - Record & Replay Requests
Item media 4 (screenshot) for ReFetch - Record & Replay Requests
Item media 5 (screenshot) for ReFetch - Record & Replay Requests
Item media 1 (screenshot) for ReFetch - Record & Replay Requests
Item media 1 (screenshot) for ReFetch - Record & Replay Requests
Item media 2 (screenshot) for ReFetch - Record & Replay Requests
Item media 3 (screenshot) for ReFetch - Record & Replay Requests
Item media 4 (screenshot) for ReFetch - Record & Replay Requests
Item media 5 (screenshot) for ReFetch - Record & Replay Requests

Overview

Record, inspect, filter and replay fetch, XHR and EventSource requests across all tabs as raw HTTP.

ReFetch shows you the fetch, XHR and EventSource requests that a page makes, as plain raw HTTP, and lets you edit any of them and replay it. RECORD • Recording is off by default. One click turns it on for all tabs until you turn it off or the browser restarts. While it is off, pages are left almost untouched. • Requests from all tabs go into one log that keeps the latest 3,000. They stay across page loads and after a tab is closed, until you press Clear or the browser restarts. • Turn on "This tab only" to list just the current tab's requests. Clear then removes only that tab's requests. • Incognito/private windows, if you allow the extension there, share the same log. Their requests stay after the window closes, until Clear or a browser restart. • Optional recording of document requests (page navigations and redirects). A GET document request has a "Fetch body" button that replays it from the page and opens the response as a new replayed request, since the browser doesn't expose the body of a navigation. Replaying it can have side effects, such as reusing an OAuth callback code. FILTER • Filter by method, host, URL regex, status, content type and kind. Each condition can include or exclude. • Search the list for any text in URLs, headers and bodies. Replayed requests always stay in the list. • Hidden requests are counted in the toolbar, or, with "Don't record hidden requests", not recorded at all so they don't use up the 3,000-request limit. INSPECT • Requests and responses are shown as HTTP text. Very large bodies (over 100,000 characters) show only the beginning until you press "Show all". • Bodies are pretty-printed by default: JSON (numbers and key order kept exactly), NDJSON line by line, URL-encoded form data as key = value, and XML and HTML indented. The Raw | Pretty switch in a pane header changes both panes, and the choice is remembered. Bodies that can't be formatted stay raw. Copy as, Edit, search and HAR export always use the full raw body. • Includes the headers the browser adds itself, such as cookies, as seen on the wire. • Status reads like DevTools: "200 CORS" when the server answered but CORS kept the page from reading it, "(failed)" for network errors and "(canceled)" for aborted requests. • A request still running after a second is listed as "(pending)", like in DevTools, and fills in when it finishes. • Step to the previous or next request right from the detail view. • Copy a request as a cURL command or as fetch code. • Server-sent events and streamed responses update live as data arrives. • Choose, reorder and resize list columns, add your own columns from any request or response header, and show the ID of the tab that sent each request. EDIT AND REPLAY • Edit the raw request, then replay it from the original frame, so the page's cookies and origin apply. • Headers that fetch cannot normally set (Cookie, User-Agent, Origin and similar) are applied to that one replay only. • Uploaded files are replayed byte for byte from the original request. • Write a new request from scratch and send it from the current tab's page. • If the page that sent the request is gone (its tab was closed or it moved to another origin), choose "Send from extension". The extension then sends the edited request itself, with the headers shown in the editor, Cookie included. Deleting the Cookie line sends no cookies; only a request that never had one gets the browser's normal cookies, not those of a private window. The page's CORS, cookie policy and Origin don't apply. These requests are labelled "Sent from extension". YOUR DATA STAYS WITH YOU • Recorded requests are stored only in your browser, in its local extension storage. • No servers, no accounts, no analytics. Nothing is sent to the developer or any third party. • Export the listed requests as a HAR file to open in DevTools or other tools. The file includes cookies, so share it with care. Open it as a popup or a side panel. Shortcut: Ctrl+Shift+X (Command+Shift+X on macOS). Requires Chrome 141 or later.

Details

  • Version
    0.6.0
  • Updated
    October 26, 2026
  • Offered by
    yoong
  • Size
    179KiB
  • Languages
    English
  • Developer
    Email
    tarojjack@gmail.com
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization
The developer has disclosed that it will not collect or use your data. To learn more, see the developer’s privacy policy.

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, visit the developer's support site

Google apps