Local Overrides is Chrome's built-in way to fake a response. It is great for quick edits and awkward for everything else. Here is exactly where the line is.
The short version
Local Overrides saves a response to disk and serves your edited copy on reload.
It cannot change status codes, add latency, patch one field of a changing payload, or share mocks with a team.
Use Overrides for one-off UI tweaks and an interceptor for repeatable API scenarios.
How Local Overrides works
Open DevTools, go to Network, right-click a request and choose Override content (or Override headers).
The first time, pick a local folder and allow DevTools to access it.
Edit the saved file in the Sources panel and reload: Chrome serves your copy.
Overrides persist per origin and path in that folder. Files show a purple dot in the Network panel when they are being overridden.
Where Local Overrides falls short
Need
Local Overrides
ProxyCeptor
Change response JSON
Yes (whole file)
Yes (whole body or deep merge)
Change status code (500, 401, 429)
No
Yes
Add latency
No (throttling is global)
Yes, per URL pattern
Patch one field and keep the rest live
No, the file is a frozen copy
Yes (merge-json)
Wildcard or regex URL matching
Limited
Yes
Redirect to another host
No
Yes
Share with QA or teammates
Copy the folder by hand
Export or cloud workspace
Use on a Smart TV
No
Yes (SDK)
A practical split
Use Local Overrides when you want to tweak CSS, a script or one static response for a few minutes on your own machine. Use a proxy interceptor when you need an API scenario you will run again, such as an error state, a slow endpoint, an expired token or a feature flag, or when someone else needs to see the same thing.
Frequently asked questions
Can Chrome DevTools mock an API response?
Yes, with Local Overrides you can replace the body and headers of a response with a local file. It cannot change the status code or add delay.
Why is my Local Override not applied?
Common causes: DevTools is closed (overrides only apply while it is open), the folder permission was revoked, the URL has a changing query string, or the request is served by a service worker.
Can I throttle only one request in Chrome?
Not with built-in throttling, which slows the whole page. A per-URL delay rule in ProxyCeptor affects only the matched endpoint.
Vimal builds the front-end and runs the search and campaign side of ProxyCeptor, which means he cares about how a page feels and how people find it. He writes code-first guides for developers: the snippet comes before the theory, and the loading spinner gets a fair trial. Expect practical steps, honest opinions about browsers and a soft spot for a well-behaved fetch call.
Manifest V3 removed blocking webRequest, leaving developers wondering how to modify response bodies. Here is why declarativeNetRequest cannot touch payloads and how modern interceptors bypass the limitation.