Open-source project
davidarroyo1234/InstagramUnfollowers avatar
davidarroyo1234/InstagramUnfollowers

InstagramUnfollowers: a browser console script that finds non-followers

Check if people follows you back on Instagram.

5,053 stars460 forksHTMLMIT

At a glance

What is it?
InstagramUnfollowers is an MIT-licensed Preact tool you paste into the Instagram web console to list accounts that do not follow you back. It keeps its whitelist locally in the browser, needs no install for end users, and ships no server component.
Who is it for?
Adopt it if you want a read-only inventory of non-followers from your own logged-in browser session and you are comfortable pasting minified code into a developer console. Do not adopt it if you need unattended runs, mobile without a console-capable browser, or any guarantee about how Instagram will treat the request pattern.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly HTML, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • davidarroyo1234/InstagramUnfollowers5,053 ★ · +176
Star history
Repository2026-09-232026-11-15
davidarroyo1234/InstagramUnfollowers4.9k5.1k

176 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What InstagramUnfollowers actually answers

The question it answers is narrow and specific: which accounts do you follow that do not follow you back. It is not a follower-growth dashboard, not an analytics product, and not a scheduling tool. The README describes it as a tool that lets you see who does not follow you back, and the interface is built around a single scan plus a result list you can act on with checkboxes.

The intended user is someone who already has the Instagram web session open and is willing to open a developer console. That is the whole onboarding. There is no account to create, no OAuth screen, and the README states all data is stored locally with no external servers. For an engineer evaluating it, that means the trust boundary is your own browser tab and whatever Instagram itself logs about the requests.

The whitelist is the part that makes it usable rather than a one-off script. You click a profile image to protect an account, and the list persists between sessions because the whitelist has local persistence. That is a real design decision: it survives a page reload, but it does not survive a different browser profile or a cleared site-data wipe unless you exported it first.

How the scan works and why results appear late

The mechanism is a client-side fetch loop, not a server job. You paste the built script into the console on instagram.com, press Enter, and click Run Scan. The README says accounts now appear on screen in real time as batches are fetched from Instagram, and completed scans are cached locally so a previous audit can be reloaded without new API calls.

The README also says the tool pauses and retries with exponential cooldowns if Instagram returns HTTP 429 or HTTP 400 (feedback_required), and that expanded page limits support accounts with tens of thousands of followers.

Customizable timing settings exist specifically to avoid rate limits, exposed through the Settings button. That is an admission built into the UI: the default pace is a guess, and the correct value depends on your account size and how Instagram is responding that day. Treat the timing controls as the main operational knob, not a cosmetic preference.

Running it on desktop without installing anything

The README frames this as browser-based with no downloads or installations. The distribution model is a hosted page that holds the built script, and you copy it rather than cloning the repository. The steps below follow the README's desktop usage section.

Open the tool page and copy the code:

bash
# README step 1 and 2: open the hosted tool page
# https://davidarroyo1234.github.io/InstagramUnfollowers/
# then press the COPY button

Log in to Instagram in the same browser, then open the developer console. The README gives these shortcuts:

bash
# Windows
Ctrl + Shift + J

# Mac OS
⌘ + ⌥ + I

Paste the copied code into the console and press Enter. Click Run Scan to start scanning, or Load previous scan to open saved results; accounts appear live as the scan runs. From there, click a profile image to whitelist that account, and use the checkboxes to select the accounts you want to unfollow.

Whitelist management lives in Settings, and the README describes four operations: Export saves the whitelist as a JSON backup file, Import restores or merges whitelisted users from a file, Paste bulk-pastes usernames into the whitelist, and Clear removes all users from the whitelist. The README states the whitelist persists between sessions automatically. Export it before you rely on it, because the browser-local copy is the only one the tool keeps.

On Android, the README points to Eruda Android Browser. You download the latest release of that browser, open Instagram web through it, and follow the same steps, with the console available from the eruda icon.

Where it breaks down

The largest limitation is the console itself. This is not a browser extension, so it does not run in the background, does not schedule anything, and does not survive closing the tab. Every scan is a manual session you start by pasting code. If your workflow needs a weekly unattended report, this is the wrong shape of tool and no setting changes that.

Second, a scan still depends on how Instagram responds: the README says the tool halts the unfollow queue if Instagram returns feedback_required, and a safe lock prevents accidental unfollows if a scan is interrupted.

Third, request pacing is partly manual: customizable timings let you control request pacing to match your account safety preferences, alongside automatic backoff on HTTP 429 or 400 responses. An aggressive value is the obvious way to get throttled on your own account.

Fourth, the whitelist is browser-local. Switching machines, switching browsers, or clearing site data loses it. Export and Import exist for exactly this reason, and the README describes Import as able to restore or merge, so the recovery path exists but depends on you having made the file.

Compared with a browser extension

The obvious alternative category is an Instagram unfollower browser extension. The difference is architectural, not cosmetic. An extension installs into the browser once, gets its own UI surface, and can persist across sessions without you pasting anything. InstagramUnfollowers instead ships as code you paste into a console on each run, which is why the README can say it requires no downloads or installations.

That trade cuts both ways. Pasting code means there is no extension store review, no extension permissions to grant, and no background process you have to trust between sessions. It also means there is no persistent actor: the tool only exists while the tab does. If you want something that sits quietly and reports, an extension is the better fit. If you want a one-off audit where you can read the flow yourself before running it, the paste model is more inspectable.

A second alternative is doing it by hand: open your following list, open your followers list, and compare. That is free, needs no code, and is completely impractical past a few dozen accounts. The tool's value is entirely in automating a diff that is tedious rather than difficult.

Building it yourself and what the build actually does

If you want to modify the tool rather than run the hosted copy, the repository is a webpack project with TypeScript and Preact. The README lists Node 16+, 18+ or 20+, and the repository carries an .nvmrc file. The package.json confirms the toolchain: webpack 5, ts-loader, sass, eslint, and preact as the only runtime dependency.

The build script is two steps chained together:

bash
npm run build

That runs webpack-build in production mode, then update-index, which is a node script that injects dist/dist.js into public/index.html. The README lists npm install, npm run build, and npm run build-dev for a dev server with live reload, and says not to edit public/index.html manually because GitHub Actions regenerates it. The build-dev script runs the build and then starts webpack serve in development mode.

One practical note for anyone auditing the hosted page: the artifact you paste is the output of this pipeline, minified by webpack in production mode. The README's instruction to copy code from the hosted page means you are running compressed output, not the readable source in src/. If you want to read what you are about to execute, build it from source and paste that instead.

Licence, maintenance and upgrade cost

The project is MIT licensed, with the LICENSE file holding the full terms. For an engineer, the practical implication is that you can fork it, strip the UI, and keep the scanning logic inside your own tooling without a copyleft obligation. This is not legal advice, and MIT covers the code, not your relationship with Instagram.

The repository is not archived, and the last push was on 2026-10-31, which is recent enough that the project is not abandoned. The repository has no published GitHub releases, so distribution appears to be the hosted page plus the master branch rather than tagged versions. That matters for upgrades: if you depend on the hosted page, you get whatever master currently builds to, with no version pin to hold. If you depend on a fork, you own the merge work, and the moving parts are the webpack config, the TypeScript sources, and the update-index script that rewrites the HTML entry point.

The upgrade cost is therefore low in dependency terms, since preact is the only runtime package, and higher in attention terms, because the tool's behaviour depends on Instagram's API responses rather than on its own release cadence. A change on Instagram's side is not something a version bump in package.json can address.

Editorial conclusion

Adopt it if you want a read-only inventory of non-followers from your own logged-in browser session and you are comfortable pasting minified code into a developer console. Do not adopt it if you need unattended runs, mobile without a console-capable browser, or any guarantee about how Instagram will treat the request pattern. Before trusting a scan, open the Settings panel and confirm the timing values and export the whitelist once to a JSON file.

Frequently asked questions

How do I know my unfollowers on Instagram with InstagramUnfollowers?

Open the hosted tool page, press COPY, log in to Instagram, paste the code into the developer console, press Enter, and click Run Scan. The README states accounts appear live on screen as batches are fetched, and completed scans are cached locally so they can be reloaded instantly.

How do I use InstagramUnfollowers on desktop?

The README lists the steps as copying the code from the hosted page, logging in to Instagram, opening the console with Ctrl + Shift + J on Windows or ⌘ + ⌥ + I on Mac OS, pasting the code, pressing Enter, and clicking Run Scan. After the scan you whitelist accounts by clicking their profile image and select others with checkboxes.

Is InstagramUnfollowers safe?

The README states that all data is processed locally in your browser and that no credentials or data are sent to external servers. It also lists account-protection features: full Instagram Web headers, an action-block guard that halts the unfollow queue on feedback_required, and automatic backoff on HTTP 429 or 400 responses.

What is InstagramUnfollowers?

It is an MIT-licensed, browser-based tool that shows which accounts you follow do not follow you back. The README describes it as requiring no downloads or installations for end users, since you copy the code from a hosted page and paste it into the Instagram web console.

Can people see who you unfollowed on Instagram when I use this tool?

InstagramUnfollowers only scans your following and followers lists and lets you select accounts to unfollow; what other users can see about an unfollow is up to Instagram, not this tool.

Official sources

  1. davidarroyo1234/InstagramUnfollowers on GitHub
  2. Issues
  3. License: MIT
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/davidarroyo1234-instagramunfollowers.svg)](https://hysenlabs.com/projects/davidarroyo1234-instagramunfollowers)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/davidarroyo1234-instagramunfollowers.svg)](https://hysenlabs.com/projects/davidarroyo1234-instagramunfollowers)

Was this useful?