# FeurStagram: a patch set that strips the feed out of the real Instagram app > FeurStagram is not a third party Instagram client but a set of open source patches applied to the official Android app, removing the feed, Reels, Explore, ads and telemetry while keeping direct messages, stories and search. This looks at how the blocking works and what installing it costs you. **jean-voila/FeurStagram** — Instagram without Reels, feed or ads: an open-source, updatable Instagram app for Android that keeps DMs and stories. - Repository: https://github.com/jean-voila/FeurStagram - Website: https://jean-voila.github.io/FeurStagram/ - Stars: 1,119 · Forks: 70 - Language: Java - License: GPL-3.0 - Published: 2026-10-19 · Updated: 2026-10-19 · Language: en - Canonical page: https://hysenlabs.com/projects/jean-voila-feurstagram ## It patches Instagram, it does not replace it FeurStagram is described as Instagram without Reels, feed, Explore or ads, and the readme is careful about what that means: it is an open source patch for the official Android app that removes the feed, Reels, Explore, ads and telemetry, while keeping DMs, stories, search, notifications and profiles. So this is not a client. There is no login screen of its own, no API wrapper, no WebView shell. The actual Instagram application is installed on your phone and FeurStagram modifies it. What you get is the real app with certain surfaces removed. The project's framing of the audience is precise. It is built for people who want to keep Instagram's useful social features without the addictive parts, and the topics list the intent in the vocabulary of the attention economy: digital minimalism, digital wellbeing, distraction blocker, distraction free, doomscrolling, dopamine detox, focus, no reels, reels blocker, screen time. The origin story is in the readme too. The author built it for himself as an alternative to DFInstagram, which had not been maintained for a long time and was difficult to update, and is sharing it so others can do the same for themselves. The project is free and open source, and the author invites forks, copies, enhancements and pull requests. That last point shapes the whole trust argument, which is where the project's documentation spends most of its words. ## Every block is a runtime toggle in one APK The design decision that makes FeurStagram usable rather than an all or nothing mod is that the blocks are individual runtime toggles. The readme is explicit: all content blocks are individual runtime toggles. You long-press the Home tab at the bottom-left of the main tab bar to open the FeurStagram settings page and check or uncheck what you want blocked. A single APK covers every combination. That is a good answer to the update problem that made DFInstagram hard to maintain. If a user wants the feed gone but Explore still on, they do not need a different build. If a new Instagram version changes the layout so a particular patch no longer applies, the user can turn that specific block off and keep the rest of the app working. The keep and block table in the readme sets out the split. On the keep side there are direct messages, stories, search and profiles, and notifications. On the block side there is the endless home feed, the Reels surfaces, Explore and suggested-account recommendations, and ads, shopping preloads and telemetry. Removing shopping preloads and telemetry alongside the attention surfaces is worth noting, because it is the part of the change that is not about willpower. The preloads are the mechanism by which the app pulls in the store before the user asks for it, and the telemetry is the measurement of what the user does next. A blocker that only removed the feed would leave both in place. ## Blocking happens at the network layer, not in the interface The readme's feature table names the technique for each block, and the techniques are not all the same. The home feed is blocked by network-level blocking. Explore is blocked by network-level blocking as well. Reels is blocked by network-level blocking plus tab hiding. The following feed only option, which is off by default and toggleable, uses a feed-request header rewrite. That last entry is the interesting one, because it is a more surgical change. A header rewrite alters the request the app makes rather than removing the surface outright, which is what makes a following-only feed possible in the first place. If the app supports requesting a feed scoped to the accounts you follow, rewriting the request to ask for that scope instead of the endless one is a much better outcome than blocking the endpoint, and it explains why the option exists as a toggle rather than as a build variant. The distinction between network-level blocking and interface-level blocking is the technical heart of the project, and it is also the answer to the three alternatives the readme names. Unlike WebView-based alternatives, FeurStagram patches the real Android Instagram app. Unlike accessibility-service blockers, it does not simply react to the interface after it loads. And unlike closed-source Instagram mods, every patch is public and auditable. The accessibility-service comparison is the sharpest: a service that watches the screen and hides things runs after the content has already been fetched, whereas a network-level block means the request never happens. ## Two ways to get it, and one of them is a build script The installation section gives two options, and the second is unusual enough to be worth reading carefully. The first is the ready-to-install APK, the latest patched APK from the Releases page, installed directly. The second is DIY patching, using the toolkit to patch any Instagram version yourself. The documentation set behind those two options is in the `docs/` directory: an installation guide, a build from source guide, an FAQ, and a privacy document, alongside a contributing guide, a security policy, a `CHANGELOG.md`, a `ROADMAP.md` and a `NOTICE` file at the root. The repository layout explains what the DIY path involves. There is a `patches/` directory, which is the patch set itself, an `extensions/` directory, a `build.sh` script at the root, and a Gradle project with `gradlew`, `gradlew.bat`, `gradle.properties` and `settings.gradle.kts`. The primary language is Java. The privacy argument the project makes for building rather than downloading is specific. FeurStagram does not collect, proxy, store or transmit your credentials, it patches the official Instagram Android app to remove distracting features, the patches are open source and documented so you can inspect what is changed, and for maximum trust you can build the APK yourself instead of downloading a prebuilt release. That is a coherent position for a project whose entire value is that it modifies software you trust with your account. ## Updates are checked against GitHub on every launch A patched app has an obvious failure mode: Instagram ships a new version, the patches stop applying, and the user has a broken client. FeurStagram's answer is a release cadence and a runtime check. The readme explains that FeurStagram checks GitHub for a newer release on every launch and shows a download prompt when your build is out of date. This automatic update check is on by default and can be turned off in the FeurStagram settings page, in the Updates section. The release tags show how often that is necessary. v451-0-0-20-80 was published on 2026-10-12, v450-0-0-50-77 on 2026-10-09, and v446-0-0-49-77 on 2026-09-13, with the last push to the repository on 2026-10-17. Three releases in a month, and the numbering scheme tracks the upstream Instagram build it is patched against. There is a second channel for updates. The readme says there is a story on the official Feurstagram account every time there is an update, and that FeurStagram has moved to a new account, @feurstagram_off, with the link given, and that following that account gives a new story on each release. So there are two update paths, one in the app and one on Instagram itself, and the second is a deliberate use of the platform the project patches. It is also, worth noting, the one part of the project that requires the Instagram account to work. ## What it does not do, and what it asks of you The readme has a section on safety, and it is unusually concrete, which is appropriate for a project that asks people to install a modified copy of their social media client. The claim is that FeurStagram does not collect, proxy, store or transmit your credentials. And there is an explicit list of what it does not do: it does not bypass Instagram login, does not collect your password or session tokens, does not proxy your traffic through a third-party server, does not add tracking or analytics, does not scrape accounts, does not sell or transmit user data, and does not claim affiliation with Instagram or Meta. The caveats are in the same paragraph as the claims, and they are not small. FeurStagram is an unofficial project and is not affiliated with Instagram or Meta. It is a modified APK installed outside the Play Store, so Android may show installation warnings. Using a modified client may violate Instagram's terms of service. Use it at your own risk. That last set of sentences is the honest price of the project, and an evaluator should read it as the price rather than as fine print. The installation goes through sideloading, which means allowing installation from unknown sources and dealing with the system warnings, and the terms of service issue is an account-integrity risk that no amount of auditing the patches addresses. The support channels are GitHub issues for bugs, a Discord server for support and development discussion, an official email address, and a press kit for journalists with facts, screenshots and logos. Sponsorship is handled through GitHub Sponsors and Buy Me a Coffee. ## Where FeurStagram is the wrong tool There are three groups of people for whom this is the wrong choice, and the documentation supports each of them. The first is anyone who needs a supported install. A modified APK sideloaded outside the Play Store means the device is configured to allow installation from unknown sources, the system warns, and the app is outside the normal update and security review path. For a work phone, a device management policy, or anyone who cannot change those settings, the project is not usable at all. The second is anyone who needs the surfaces it removes. The feed, Explore, the suggested-account recommendations and the Reels surfaces are gone by default. Someone whose business depends on discovering content through Explore, or whose community lives in the feed, will find the app much less useful, and the toggles only restore what the patch set supports. The third is the account-integrity question, and this one is not a technical limit but a decision. The readme says plainly that using a modified client may violate Instagram's terms of service. For an account that represents an organisation, that is a risk to weigh against attention savings, and only the account owner can make that call. There is also a platform limit, since this is an Android project patching the Android app, and a scope limit, since it does not attempt to be a replacement client and offers no API, no multi-account management and no scheduling. For the last point on maintenance, the project is moving fast, with releases on 2026-10-09 and 2026-10-12, which is what keeping up with an upstream app requires. It is also a single author project with a Discord and a sponsorship page, so its continuity depends on one person, and the licence is GPL-3.0, which covers the patch project and the tooling, not the Instagram code it modifies. ## Conclusion FeurStagram fits an Android user who wants direct messages, stories and search from Instagram without the feed and Reels, and who is willing to sideload a modified APK and rebuild it when an update lands. It does not fit anyone who needs a Play Store install with Play Protect, a device without the ability to install unknown sources, or a workflow that depends on the feed, Explore or Reels. It is also the wrong choice for a business account where an account-integrity risk is unacceptable. Before you install, read `docs/PRIVACY.md` and the installation guide, and decide whether you would rather build the APK yourself from `build.sh` than trust a prebuilt release. ## FAQ ### What does FeurStagram do to Instagram? It patches the official Instagram Android app to remove the endless home feed, the Reels surfaces, Explore and suggested-account recommendations, plus ads, shopping preloads and telemetry, while keeping direct messages, stories, search, notifications and profiles. ### How do I install FeurStagram? There are two options: download the latest patched APK from the repository's Releases page and install it, or use the patching toolkit to patch any Instagram version yourself, with the instructions in `docs/INSTALL.md` and `docs/BUILD_FROM_SOURCE.md`. Because it is a modified APK installed outside the Play Store, Android may show installation warnings. ### Can I turn the blocking features back on? Yes. All content blocks are individual runtime toggles. You long-press the Home tab at the bottom-left of the main tab bar to open the FeurStagram settings page and check or uncheck what you want blocked, and a single APK covers every combination. ### Does FeurStagram collect my credentials or proxy my traffic? No. The project states that it does not collect, proxy, store or transmit your credentials, does not bypass Instagram login, does not proxy traffic through a third-party server and does not add tracking or analytics. For maximum trust, the documentation suggests building the APK yourself rather than downloading a prebuilt release. ### How do I get FeurStagram updates? FeurStagram checks GitHub for a newer release on every launch and prompts you to download when your build is out of date, and the check can be disabled in the settings page under Updates. There is also a story on the official @feurstagram_off account for each release. ## Sources - [jean-voila/FeurStagram on GitHub](https://github.com/jean-voila/FeurStagram) - [License: GPL-3.0](https://github.com/jean-voila/FeurStagram/blob/main/LICENSE) - [Project website](https://jean-voila.github.io/FeurStagram/) - [README](https://github.com/jean-voila/FeurStagram/blob/main/README.md) - [Releases](https://github.com/jean-voila/FeurStagram/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/jean-voila-feurstagram