Support

The extension mounts its buttons into the platform interface as you navigate. If they are missing:

• Open the toolbar popup. It classifies the page you are on and lists what should be available there. If it says nothing is available, you are on a page type the extension does not handle.
• Reload the tab. A hard navigation re-runs the injection from a clean state.
• Confirm the extension is enabled at chrome://extensions and that the page is instagram.com or facebook.com, not a mirror or an embedded view.
• If the popup lists an action but no button appears in the page, the platform has probably changed its markup. Report it — that is a real bug and it needs a fix in the selectors.

Large archives are where rate limiting shows up. The extension already backs off and retries on 429 and 5xx responses, but the platform can still refuse for a while.

• Open Settings and lower parallel downloads. The default is 4; try 2, or 1 for a very large profile.
• Wait a few minutes before retrying. A refusal is usually temporary.
• A toast reporting that some files could not be downloaded is expected behaviour, not a crash: unreachable items are skipped and counted, and the zip still contains everything that did arrive.

The resolver tries several routes and deliberately refuses to hand back a low-resolution thumbnail. If nothing original-resolution is reachable it reports a failure instead of pretending. Check that you can see the profile while signed in; a private account you do not follow has nothing to fetch.

The seen-state blocker is off by default, so check the Privacy section of Settings first. Even switched on, it is best effort: it drops the requests it can observe, but a view can register through a path it does not see. Treat it as a reduction, not a guarantee.

Bugs go to GitHub issues. Useful reports include the extension version (currently 2.0.0), your browser and its version, the page type you were on, what you clicked, and what happened instead. Do not paste cookies, tokens or session identifiers into an issue.

For anything you would rather not post publicly, including data deletion requests, email [email protected].

Open an issue on the repository. Requests for platforms other than Instagram and Facebook are out of scope: each platform needs its own endpoint handling and its own maintenance burden when it changes, and two are already enough.