2 items
Yoink cookies from any host onto your localhost or staging tabs for testing. Yoink copies cookies from any source host (staging, QA, prod) onto your localhost and staging tabs automatically — so you can test against a real authenticated session, without ever opening DevTools. ✦ How it works Add one or more source hosts in the popup — where cookies come from (e.g. https://app.staging.example.com) Open a destination tab — localhost and 127.0.0.1 work out of the box; add your own staging hosts with * wildcards (e.g. app-*.staging.example.com) Yoink automatically copies all cookies from the source hosts to that origin on every page load A small toast in the top-right corner shows you what was copied ✦ Features • Custom destinations — sync onto any host, not just localhost; wildcard patterns cover every staging subdomain at once (app-*.staging.example.com) • Multiple source hosts — yoink from staging, QA, and prod independently • Per-host & per-destination pause — silence a specific entry without removing it • Global pause — disable the whole extension with one toggle • Optional on-page panel — a clean floating widget on your synced pages (off by default) • Smart input — Tab-completes the source field with the hostname of your currently active tab • Incognito support — works across normal and incognito cookie stores • Status-colored toolbar icon — green when active, amber when paused, gray when idle • Zero network — cookies never leave the browser; everything happens via the Chrome cookies API ✦ Why Modern web apps depend on auth cookies. Testing a local build — or a freshly spun-up staging environment — against real data usually means manually copying cookies through DevTools, for every cookie, every refresh, every team member. Yoink does it in one click. ✦ Privacy Yoink does not collect, transmit, or store any data outside your browser. No analytics, no telemetry, no remote servers. Cookies move directly between Chrome's local cookie stores. ✦ Notes • Secure cookies cannot be set on http://localhost — use https://localhost if you need them • __Host- / __Secure- prefixed cookies have strict rules and may not transfer • Source code: https://github.com/ilyasudakov/yoink
Jul 3, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.