Skip to content
Ask Claude about any Chrome extension, answered with Ext Watch data. See how →
Developer Tools extension

Loupewire: HTTP Request Inspector, Header Editor and Masked HAR Export

Capture traffic from every tab in one window, apply header rules, mask secrets and export HAR. All on-device, no accounts.

by https://getmarkview.com/ · 3 listings

Add to RadarChrome Web Store Free plan tracks 1 extension · no card
extwatch.com/extensions/loupewire-http-request-inspector-header-editor-and-masked-ha-dkoclbklglebhboiodckkicoajbcmbjd
Loupewirehttps://getmarkview.com/ · Developer ToolsMedium access
Users
24
#11,895 of 31,198 in category
Rating
5.00
4 ratings · median 4.63
Version
1.2.0
362 KiB · Manifest V3
Access
Medium53/100
4 permissions + every website
From the store listing

Screenshots

5 images from the publisher · use the arrows or pick one · swipe or pick one

Loupewire: HTTP Request Inspector, Header Editor and Masked HAR Export screenshot 1Loupewire: HTTP Request Inspector, Header Editor and Masked HAR Export screenshot 2Loupewire: HTTP Request Inspector, Header Editor and Masked HAR Export screenshot 3Loupewire: HTTP Request Inspector, Header Editor and Masked HAR Export screenshot 4Loupewire: HTTP Request Inspector, Header Editor and Masked HAR Export screenshot 5
1 / 5

Description

As written by the publisher on the store

Loupewire opens one window that records the HTTP requests every tab and popup makes, so a flow that crosses several pages - a login that bounces through a redirect chain, a payment step that opens a verification window, a vendor checkout - reads as one list. Select any request to see its headers, cookies, form data and body, timing and redirect chain. Everything runs on your device.

  • 🔍 CAPTURE ACROSS EVERY TAB
  • One tracker window records every tab and popup in the browser window it belongs to
  • Or narrow it to one tab and every tab or popup opened from it, so a login or checkout flow is recorded without the rest of the browser
  • Request and response headers, cookies, form data, request bodies, timing, redirect chain, resource type and server IP
  • Requests that were blocked or failed appear in the list with the reason
  • When the browser's site access setting hides some sites from the extension, the tracker says so and gives access back in one click
  • Open the tracker in its own window or as an ordinary browser tab, and move it between the two from its header without losing what it captured
  • 📥 RESPONSE BODIES
  • Turn on response-body capture for a site, and the bodies of that page's own fetch and XHR calls appear beside each request, masked like every other value
  • A site covers its subdomains. Capture starts with the next page load, and nothing runs on a site you have not turned on
  • On a site you turn on, a script observes the page's calls without changing them, receives nothing from the extension, and is removed when the tracker closes
  • Import a HAR saved from DevTools to read every body it recorded, masked on screen and in the file you export again. The imported file is held in memory and never stored
  • A request without a body says why: a page that read its response as a stream, a call made by a worker, a request that is not a fetch or XHR call
  • 🛡️ MASKING, ON SCREEN AND IN THE FILE
  • Add a pattern such as authorization or session, and every matching value shows only its first and last characters
  • In a JSON body, a pattern that names a key masks every value beneath that key
  • A built-in preset covers the common secret-bearing header and field names and is on by default
  • Masking is applied as the row is drawn, and there is no reveal button - a screenshot of the panel is already safe to attach
  • 📤 EXPORT AND COPY, ALREADY REDACTED
  • Export as HAR 1.2, what vendors, developers and every network tool read, with response bodies where a request has one
  • Export as Loupewire JSON, which keeps what HAR has nowhere to put: each redirect leg, partial records, and how a multipart field was read
  • Choose what goes in: everything captured, only the rows you selected, or only what the filter shows. A file holding part of a session says so inside itself
  • Copy one request as redacted text, or as a redacted cURL command, for a ticket or a chat message
  • ✏️ REQUEST HEADER RULES, WITHOUT A PROXY
  • Set a request header on every request whose URL matches a filter, for a staging API or a feature flag
  • Rules are applied by the browser's own declarative rule engine, and the captured request shows the header exactly as it was sent
  • Headers that belong to the connection itself, such as Host or Content-Length, are allowed and flagged with a warning
  • Rules last while the tracker window is open and stop when it closes
  • 🎯 NARROW IT DOWN
  • Track and Skip patterns decide what is recorded, for the session or for every window
  • Filter the table by url, method, status, date and cache state, combined with & and |
  • Block requests by pattern to see how a page behaves when an endpoint is unavailable
  • Find text inside the request you have open
  • Pause and resume; clear everything, the selected rows, or the rows currently shown
  • Select several rows and export or clear only those
  • 🌍 INTERFACE
  • Available in 8 languages, including right-to-left interfaces that mirror as a whole
  • Light, dark, or following the system, with a switch in the tracker header
  • 🔒 ON-DEVICE, AND NOTHING ELSE
  • Captured headers, cookies, bodies and URLs, and any HAR you import, stay in the tracker window and are never written to disk unless you export them
  • Your patterns, rules, settings and the sites you turned body capture on for are stored in the browser's local extension storage
  • The extension makes no network requests of its own
  • No account, no telemetry, no analytics, no crash reporting

⚠️ WHAT IT DOES NOT DO
Response bodies are captured only for the page's own fetch and XHR calls, on the sites you turn on. A body the page reads as a stream, a request made by a worker or service worker, and page loads, images and scripts have none in the live capture; save a HAR with DevTools and import it to read those. Loupewire does not attach a debugger to your tabs.

  • 🚀 QUICK START
  • Install, then click the Loupewire icon in the toolbar
  • The tracker window opens and starts recording straight away
  • Browse in any tab of that window - rows appear as requests are made
  • Select a request to read its headers, then Export to attach a masked HAR to a ticket
  • 📞 SUPPORT
  • Guides: https://loupewire.com/guides/
  • Support: https://loupewire.com/support/
  • GitHub: https://github.com/loupewire/loupewire-support
  • 🔗 LINKS
  • Website: https://loupewire.com/
  • Privacy Policy: https://loupewire.com/privacy-policy/
  • Terms: https://loupewire.com/terms/

Ratings and reviews

Split of the 1 written reviews we hold
Reviews on the store
5.004 ratings on the store
1 written review we hold
5 ★100.0%1
4 ★0.0%0
3 ★0.0%0
2 ★0.0%0
1 ★0.0%0
Tinh Hoa Cổ Học

Does exactly what I needed, nothing more and nothing less.

Radar

Track Loupewire on Radar

This page shows the listing as it is today. Add it to Radar and get one email when it changes.

  • Users and rating
  • Store text and screenshots
  • Permissions it asks for
Free plan tracks 1 extension · no card
Ext Watch Radar watchlist cards showing tracked extensions with users, rating, version and latest store change
Guide

Loupewire, in plain words

What it is, what to use instead, what it can access and how to fix it.

At a glance

Loupewire at a glance

Loupewire: HTTP Request Inspector, Header Editor and Masked HAR Export is a Developer Tools extension by https://getmarkview.com/ with 24 users. Chrome Web Store users rate it 5.00 out of 5 from 4 ratings, which is still a small sample. By users it sits in the top half of Developer Tools extensions.

By users
#11,895of 31,198 in Developer Tools
Rating
5.00category median 4.63
Access
Medium53 of 100

Loupewire alternatives

Popular in Developer Tools · users as the store shows them
Loupewire245.00 ★
GoFullPage - Full Page Screen Capture11M4.9 ★TouchEn PC보안 확장8M1.2 ★TrendAI™ Toolbar for Enterprise7M1.2 ★SentinelOne6M1.4 ★React Developer Tools5M3.5 ★
Permissions

Is Loupewire safe?

Loupewire asks for 4 permissions and access to every website. 2 of them give wide access.

Permissions show what it could do, not what it does. See the full permission list.

53/ 100Medium access
Loupewire4 permissions · 2 wide
  • <all_urls>Read and change data on every website
  • webRequestWatch the web traffic your browser sends

Every permission Loupewire asks for

4 permissions + every website · 2 sensitive · Medium access overall

Sites

  • Read and change data on every website<all_urls>

Browser permissions · 4

  • Watch the web traffic your browser sendswebRequest
  • Block or redirect requests with set rulesdeclarativeNetRequest
  • Save its own settingsstorage
  • Run its code on pages it can accessscripting

Sensitive marks access that reaches your data or other sites. The access level is a 0 to 100 score of all of it: under 25 is Low, 60 and up is High.

Troubleshooting

Loupewire not working?

What recent reviews say

Store reviews from the last 90 days
1recent reviews, none with 1 or 2 stars
1–2 stars 3–5 stars

Common fixes

Try them in this order
  1. 1Update Chrome and the extension
  2. 2Turn it off and on in chrome://extensions
  3. 3Reload the page
  4. 4Turn other extensions off in case two clash

Still stuck? Contact the maker or try an alternative.

297,753 Chrome extensions in one place

Know when a listing changes

Track any extension on Radar: users, rating, permissions and store text, with one email when something moves.

No credit card neededFree ExplorerAsk Claude about any extension