One editable recipe
Save query keys and values once, then independently enable only the transformations needed for the current URL.
ReqKit keeps the developer utilities you reach for every day in one focused Chrome popup—without analytics, accounts, or a developer-operated backend.
One saved URL recipe and exact-host header rules cover the common workflow while keeping every action visible and reversible.
Save query keys and values once, then independently enable only the transformations needed for the current URL.
Move the original path, query, and fragment into a configured query key before applying the enabled parameters.
Create, pause, edit, and remove request headers for HTTPS hostnames you explicitly approve through Chrome.
Settings stay in the current Chrome profile. ReqKit has no analytics, remote code, account system, or developer server.
ReqKit prefills the active tab URL but leaves it editable. Enabled recipe parameters merge into the query string while the path and fragment remain intact.
Header rules use Chrome's optional site permission prompt. Active conflicts are surfaced before a rule can silently replace another value.
The current URL and hostname are detected after you invoke the popup.
Toggle saved query parameters or manage a header rule for an approved host.
Open the transformed URL or let Chrome apply enabled headers to matching requests.
ReqKit's source, permissions, storage behavior, and complete privacy policy are public. Query strings and headers may still be logged by destinations, so use only authorized systems and test data.
Until the Chrome Web Store listing is live, clone the repository and load the extension directory through Chrome's developer mode.
Open the GitHub repositorychrome://extensionsextension directory.