Tools
Debug
Clear cookies, storage, caches and service workers for the open site only, hard reload, and optimize its images to WebP or AVIF in your browser with Pickode.
Updated October 20, 2026
Debug clears the stored data of the site open in the tab, without touching any other site, and reloads it without cache. With Pro it also optimizes the page’s images into lighter files. Use it when you’re testing changes and want to be sure you’re seeing the latest version.
Clear one site’s data
-
Open Pickode on the site you’re working on and choose Debug. You see what’s stored, with counts.
-
Pick what to clear: cookies, local and session storage, IndexedDB, Cache Storage, service workers or HTTP cache.
-
Confirm when asked: removing cookies always asks for confirmation.
-
Reload the page without cache to see the changes you just deployed.
You stay logged in on every other site: only the site in the tab is affected.
What Debug can clear
| Data | Notes |
|---|---|
| Cookies | Always with confirmation |
| Local and session storage | Of the open site |
| IndexedDB, Cache Storage | Of the open site |
| Service workers | Of the open site |
| HTTP cache | Not per site in Firefox (see limits) |
Optimize images (Pro)
-
In Debug, open the image optimizer on the page you want to lighten.
-
Choose the format (WebP or JPEG, or AVIF where your browser can encode it) and a quality between 50 and 95.
-
Check the before/after and the saving for each image. Images are resized to the displayed size × screen density, never upscaled.
-
Download everything as a ZIP with a CSV.
Everything happens in your browser: no image is uploaded anywhere.
Free vs Pro
| Free | Pro | |
|---|---|---|
| Clear site data, with counts | ✓ | ✓ |
| Hard reload | ✓ | ✓ |
| Optimize images (WebP/AVIF, resize, ZIP) | — | ✓ |
The browsingData permission
Debug uses the browsingData permission only to clear the data of the site open in the tab, and only when you ask. See Privacy.
Related
Still stuck?Contact us