I built WebWarp because Chrome's Local Overrides never finished the job

Frontend developers and quality assurance engineers frequently encounter the need to modify a single response on a live website — whether it's a script, CSS file, JSON payload or other resource. They are often advised to use Chrome's Local Overrides feature in DevTools. While this works initially, problems arise when the browser profile is reloaded, the scope needs to be URL-specific, or the setup must be shared with a teammate.

Paid tools like Requestly exist, but they often come with enterprise pricing starting at $10–15/user/mo. WebWarp, created by the author, aims to solve these problems by allowing users to swap only the response they need without impacting the entire application. It keeps the live application, real backend, and user session intact, only modifying the targeted response.

The tool supports URL matching, local file mapping (JS, CSS, HTML, images, fonts), per-file URL scoping with query and cookie conditions, live reload and auto-reapplication, and injection profiles for team sharing. WebWarp offers a Chrome, Edge, and Firefox companion extension, and operates without requiring any proxy configuration or deployment queue.

There are no additional steps needed to set it up each session. A comparison shows WebWarp provides more advanced features than DevTools Local Overrides at no cost. The author recommends using DevTools Local Overrides for occasional endpoint mocking in Chrome, but suggests WebWarp for teams requiring shared rule sets, scoped conditions, and cross-browser coverage.

For such use cases, WebWarp offers a founder lifetime deal for $99, or a $19–38/mo subscription for Requestly. The founder has launched a 14-day free trial for monthly plans, with plans to charge users from the start. The founder is available to answer questions in the comments section.