jean-voila/FeurStagram
Instagram without Reels, feed or ads: an open-source, updatable Instagram app for Android that keeps DMs and stories.
About jean-voila/FeurStagram
jean-voila/FeurStagram is an open-source project on GitHub, mainly written in Java. Instagram without Reels, feed or ads: an open-source, updatable Instagram app for Android that keeps DMs and stories. It currently holds 1,380 stars and 84 forks with 35 open issues, and was last pushed on 2026-11-15 (repository created 2025-12-30).
Project Overview
Git Homed tracks it on the Today's Trending board, currently at rank #66 with 70 new stars today.
GitHub Repository Details
README
Feurstagram
Instagram without Reels, feed, Explore or ads.
Feurstagram is Instagram without Reels: an open-source patch for the official Android app that removes the feed, Reels, Explore and ads, while keeping DMs, stories, search, notifications and profiles.
Download APK · Install · Build from source · FAQ · Privacy · Support · Buy me a coffee · Issues
What it keeps and blocks
| Keep using Instagram for | Remove or block | |--------------------------|-----------------| | Direct Messages | Endless Home feed | | Stories | Reels surfaces | | Search and profiles | Explore and suggested-account recommendations | | Notifications | Ads and suggested content |
Preview
Is it safe?
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.
For maximum trust, you can build the APK yourself instead of downloading a prebuilt release.
That said, 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.
What Feurstagram does NOT do
Feurstagram does not:
- bypass Instagram login;
- collect your password or session tokens;
- proxy your traffic through a third-party server;
- add tracking or analytics;
- scrape accounts;
- sell or transmit user data;
- claim affiliation with Instagram or Meta.
Why Feurstagram?
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.
Unlike closed-source Instagram mods, every patch is public and auditable.
Feurstagram is built for people who want to keep Instagram's useful social features without the addictive parts.
I built this project for myself as an alternative to DFInstagram which hasn't been maintained for a long time and was difficult to update. I'm sharing it so others can do the same for themselves.
This project is entirely free and open-source. Feel free to fork, copy, enhance, or submit pull requests - do whatever you want with it!
Documentation
How do I get notified when there is a new update ?
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 (Updates section).
There is also a story on the official Feurstagram account every time there is an update. Feurstagram has moved to a new account, @feurstagram_off:
- https://www.instagram.com/feurstagram_off/
Community
Join the Discord server to get support, follow updates, and discuss development:
- https://discord.gg/Z9QvMw8s76
Contact
Official email: [email protected]. Journalists can find facts, screenshots and logos in the press kit.
Installation
You have two options:
1. Ready-to-install APK - Grab the latest patched APK from the Releases page and install it directly 2. DIY Patching - Use the toolkit below to patch any Instagram version yourself
What Gets Disabled
All content blocks are individual runtime toggles — tap the Feurstagram icon at the top of your profile, next to the menu (or long-press the Home tab, the first icon of the bar if you hid Home, Messages in Quoicouview mode; on tablets, the same icons in the side rail) to open the Feurstagram settings page and check/uncheck what you want blocked. A single APK covers every combination.
| Feature | Default | Toggleable | How | |---------|---------|------------|-----| | Home Feed | Blocked | Yes | Response filtering | | Following feed only | Off | Yes | Feed-request header rewrite | | Explore | Blocked | Yes | Response filtering | | Reels | Blocked | Yes | Response filtering + Tab hidden | | Stories | Visible | Yes | Response filtering | | Suggested accounts | Blocked | Yes | Response filtering + feed-parse filtering | | Instants (+ button in DMs) | Blocked | Yes | View visibility hidden | | Notes (text bubbles above DMs) | Blocked | Yes | Row removed from the inbox list | | Ads | Blocked | Yes | Response filtering + feed-parse filtering | | Threads button (profile header) | Hidden | Yes | View visibility hidden | | Analytics & telemetry | Native | No | Instagram requests preserved | | Shopping / commerce preloads | Native | No | Instagram requests preserved |
Following feed only is a softer alternative to blocking the Home Feed entirely: leave the feed unblocked and turn this on to get a chronological feed of just the accounts you follow, with the recommended/ranked posts dropped.
What Still Works
| Feature | Status | |---------|--------| | Direct Messages | Works | | Profile | Works | | Reels in DMs | Works | | Search | Works | | Notifications | Works | | Deep links | Works |
Settings Page
Tap the Feurstagram icon (the diamond at the top of your own profile, just left of the ☰ menu). A red dot on it means a new Feurstagram release is out; the settings then open on an "Update available" row. The former gesture still works: long-press the Home tab (or, if you hid the Home icon, the first icon left on the bar). A full-screen, scrollable settings page opens — Material 3 Expressive, monochrome, and padded to fit around system bars and cutouts on any device. It starts on an overview: one row per section, with Instagram's own outline icon and a one-line summary of that section's current state (for example "3 of 10 hidden"). Tapping a row opens the section's page in the same window, with a back arrow; Back returns to the overview. The sections are:
- Experimental feature: Quoicouview mode (off by default) — Messages becomes
- Blocked surfaces — toggles for Home Feed, Explore, Reels, Stories,
- Navigation bar — show or hide each bottom-bar icon (Home, Search, Reels,
- Feed — Following feed only: restrict the Home Feed to accounts you
- Display and popups — Force dark (disable HDR) (on by default): stops Instagram
- Landing page — choose which surface the app jumps to on cold start
- Updates — after an update, the first launch shows a What's new card with
- Support — opens the project's GitHub Sponsors page.
- Permanent lock and Done buttons pinned at the bottom so they stay
Changes persist across restarts (stored in SharedPreferences
feurstagram_prefs).
Once you change any setting, the page can only be left by restarting: both Done and Back clear the cache and relaunch, so a changed block can never leave the app in a half-applied state with stale content still loaded. If you open the page and change nothing, Back simply closes it.
Permanent lock
The permanent lock freezes your restrictions for this installation. It only prevents relaxing them: you can still make settings stricter (turn a block on), but you cannot turn a block back off without reinstalling. It also freezes Following feed only once it is on, so the ranked feed cannot come back.
The freeze is captured per settings session, not the instant you flip a switch. When you open the settings page, Feurstagram snapshots which surfaces are currently blocked; only those stay frozen. A surface you turn on by mistake during a session can still be turned back off until you tap Done — Done clears the cache and restarts, which bakes the new state in as the next snapshot. This means a stray tap on a surface (e.g. Stories) is recoverable within the same session instead of forcing a reinstall.
Requirements
- JDK 21 and the Android SDK (
ANDROID_HOMEset, build-tools installed) - A GitHub token with the
read:packagesscope in~/.gradle/gradle.properties,
gpr.user=
gpr.key=
Build from source
1. Download an Instagram APK from APKMirror (arm64-v8a recommended).
2. Build and apply:
./build.sh instagram.apk
Add --clone to install Feurstagram alongside a stock Instagram (separate
package and data), and --install to push it to a connected device:
./build.sh instagram.apk --clone --install
The signed result is written to feurstagram.apk.
Project structure
Feurstagram/
├── build.sh # Build the bundle and apply it to an APK
├── patches/ # Patches (Kotlin): where to inject, by fingerprint
│ └── src/main/kotlin/com/feurstagram/patches/
│ ├── network/ # Response filtering + feed-item filter + following-feed
│ ├── settings/ # Settings entry points (tab bar) + Back history
│ ├── quoicouview/ # Stories tray as a row of the Direct inbox
│ ├── signature/ # Signing-cert trust bypass (deep links)
│ ├── display/ # Force SDR (disable Instagram's forced HDR window)
│ ├── debug/ # ADB settings bridge (dev only, --debug)
│ └── clone/ # Side-by-side package/label rename
└── extensions/ # Runtime code (Java), compiled and merged in
└── .../com/feurstagram/extension/
├── Block.java # URI blocking rules + feed-item type filter
├── LimitFeed.java # Following-feed header rewrite
├── Config.java # SharedPreferences toggles + permanent lock
├── Settings.java # Settings dialog
├── Display.java # Window colour-mode control (Force dark / SDR)
├── Hiders.java # Nav-tab / Notes / Instants hiders + landing redirect
├── HiddenTabSwipeSkipper.java # Keeps swipes off hidden tabs' pages
├── Quoicouview.java # Quoicouview mode: inbox row hooks + story launch
├── StoriesTrayRow.java # The inbox row type that holds the stories tray
├── QuoicouviewIntro.java # One-time card presenting Quoicouview mode
├── DebugBridge.java # Dev-only ADB bridge over the settings (--debug builds)
└── UpdateChecker.java # On-launch GitHub release check
Design
Feurstagram's own screens follow Material 3 Expressive in a monochrome dark scheme — white is the only accent, and everything is built in code because the mod has no resources of its own. The tokens, shapes, type scale, component rules and the window-inset requirements are written down in docs/DESIGN.md; read it before changing or adding any UI.
Signing
The bundle is signed during build.sh. Set FEURSTAGRAM_KEYSTORE_PASS (and
optionally FEURSTAGRAM_KEY_PASS) to sign with feurstagram.keystore;
otherwise a throwaway keystore is generated. Reuse the same keystore across
builds to install updates without uninstalling first.
Debugging
Blocked requests surface as java.io.IOException: Blocked by Feurstagram in
logcat:
adb logcat | grep "Blocked by Feurstagram"
How It Works
Patches locate their injection points by fingerprint (matching code by stable traits like class names, strings and method shapes) rather than by obfuscated names, so they keep applying across Instagram updates. The runtime logic lives in compiled extension classes that are merged into the app.
Settings Hook
A fingerprint matches the main tab-bar binder and injects a watcher on it. The watcher adds a Feurstagram button to the header of the user's own profile (the one with the "Create" button on its left), just before the menu button, and puts it back on any layout pass where Instagram rebuilt the header; it carries the red update dot. It also resolves the tab ids viaResources.getIdentifier(...), grabs the Home tab (or the first
visible tab when Home is hidden) once laid out, and installs a long-press
listener. Either one
opens a full-screen Material dark page: content toggles plus a landing-page
selector, all backed by SharedPreferences (feurstagram_prefs). The same
hook installs the navigation-tab/Notes/Instants hiders, the hidden-tab swipe
skipper and the cold-start landing-page redirect.
Quoicouview mode
When Quoicouview is enabled or Notes are blocked, the Direct inbox uses Instagram's view-based list renderer, including on accounts assigned the fully Compose inbox. The renderer choice is applied both to view setup and data delivery. The list uses anIgRecyclerViewAdapter: a list of models, each drawn by
the row type registered for its class. The patch registers one more row type,
StoriesTrayRow, in every such adapter (it is made a subclass of Instagram's
obfuscated row and holder base classes at patch time), and hooks the adapter's
list updates so the inbox's list gets the stories row right after its search
bar (the search bar's obfuscated list models are found at patch time). The row holds the
feed's own stories tray: Instagram keeps every tab's page alive, so the feed
keeps the tray up to date while it is drawn in the inbox. A tap opens the story
exactly as on Home, growing out of the avatar and shrinking back into it on
close: the feed tray controller's "is the feed visible" checks accept the tray
in the inbox, and the controller, a lifecycle listener of the feed fragment,
follows the inbox's resume and pause instead, together with its data controller.
Returning to Messages runs Instagram's client-side story sort, and pulling to
refresh also requests new stories. The viewer is added over the
inbox rather than replacing it, so closing it does not wait for the inbox to be
rebuilt. The feed header's notifications
button is moved to the inbox header the same way. The story camera is the swipe
navigation's panel left of the tab pages, which Instagram only turns on, and only
lets a swipe from the main page reach, while Home is the current tab: both "is
Home current" checks of the tab controller accept Messages, and the tab pager
tells the swipe navigation it cannot scroll onto the hidden pages left of
Messages, so the tray's "Your story" (+) and a swipe to the right open the camera. A third patch keeps the hidden
Home out of the tab Back history. Instagram has several main layouts, picked per
account and sometimes per launch: the mode answers the override they all read
first, so it always gets the one with a tab pager and a Messages tab. The pager's
pages load when first shown, so the feed's page is told to load right away, for
launches that do not start on Home.
Content response filtering
Instagram sends requests through its own Tigon transport, with its own authentication, parameters, scheduling and retries. Feurstagram no longer throws a network error to hide a surface. After a successful response arrives, an incremental JSON filter empties the root content lists for surfaces the user blocked, retaining metadata and security messages. Pagination flags for an emptied surface are disabled locally to avoid repeated automatic load-more requests. The full response still crosses the network; it is not displayed, and media URLs removed from the response are not fetched just to imitate a view.The filter handles UTF-8, nested objects, escaped strings and arbitrary transport chunk boundaries without buffering a full response. Non-success HTTP responses pass through unchanged. Parse hooks also suppress home feed units and story-tray entries.
Logging, seen events, uploads, statistics, security notices and commerce requests now follow Instagram's native behavior. Blocking content therefore no longer saves the API traffic associated with loading it, and Instagram telemetry is no longer blocked. Feurstagram adds no synthetic views, interactions, heartbeat requests or background polling. This change does not establish why an account was restricted, and does not guarantee protection from restrictions.
Feed Item Filtering
Endpoint selection alone cannot separate ads and "suggested" units that Instagram injects inline into the Home Feed payload — they arrive inside the normal/feed/timeline/ response, not on a separate URL. A second fingerprint matches
the feed-item JSON deserialiser (by the stable wire-format type tokens like
clips_netego and the parseFromJson method name) and rewrites a blocked
unit's type token to an invalid one. Instagram's own parser then routes it to
its "unknown FeedItem type" branch and drops it — no crash. Ad/promo units are
gated on the Ads toggle, suggested/netego units on the Suggested
accounts toggle.
Following Feed Only
A fingerprint matches the main-feed request class (by its debug-string shape) and rewrites the request'spagination_source header from the recommended feed
to following, so the Home Feed returns only accounts you follow. The header
field is obfuscated, so it is resolved dynamically each build rather than
hardcoded. Gated on the Following feed only toggle.
Deep-link signature bypass
Instagram checks that the running APK is signed by Meta before it follows a deep link into its own content. A re-signed FeurStagram build fails that check, so shared links (posts, reels, profiles) silently dropped to the home feed. A patch forces Instagram's signing-certificate trust checks to always pass, so it treats the build as genuine and deep links resolve normally. It matches on a stable error string rather than obfuscated names, so it needs no per-version maintenance. Fixes #36 and #106.Force SDR display
Instagram switches its window into HDR mode at runtime (server-gated per account), which lifts the black floor on HDR OLED panels and leaves the flat dark UI looking washed out for no benefit. A patch reroutes every window colour-mode change through an extension helper that pins the window to SDR when the Force dark toggle is on (default), keeping blacks deep; turning it off passes Instagram's original colour mode through untouched. It hooks the frameworkWindow.setColorMode call, so it too needs no per-version maintenance.
Suggested accounts mixed into the story tray are not a separate request: they arrive as
reel_type: "suggested_user" entries of the tray response itself. A parse-layer hook drops
them when Suggested accounts is blocked, the same way feed ads are filtered.
`/discover/surf