# InstaEclipse: Instagram Controls for Rooted and LSPatch Devices

> InstaEclipse is an LSPosed and LSPatch module that adds configurable Instagram privacy, download, appearance, feed, and distraction controls. It is aimed at users who accept module maintenance and Instagram update risk, not at users seeking a standalone Instagram client.

**ReSo7200/InstaEclipse** — An Instagram Xposed module with features like Developer Options, Ghost Mode, Ad-Free browsing, and Distraction-Free Mode.

- Repository: https://github.com/ReSo7200/InstaEclipse
- Website: https://t.me/InstaEclipse
- Stars: 1,613 · Forks: 103
- Language: Java
- License: GPL-3.0
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/reso7200-instaeclipse

## InstaEclipse Runtime Scope

InstaEclipse changes Instagram behavior from inside the app rather than replacing Instagram with a separate client. The README identifies it as an LSPosed module for rooted devices and an LSPatch module for devices without root. After the module is enabled, a long press on Instagram's search icon opens the settings sheet. Most feature changes take effect without a restart, which makes the module practical for small adjustments such as hiding feed suggestions, changing theme colors, or blocking ad units.

The project is intended for Android users who want control over Instagram's interface and some of its client-side behavior. Its feature set includes Ghost Mode, privacy controls for direct messages, media downloads, custom themes, clean-feed filtering, and ad or analytics suppression. It is not an official Meta product and the README explicitly says the project is not affiliated with Meta or Instagram. That distinction matters because the module depends on internal app behavior and can become incompatible when Instagram changes its code.

## DexKit Class Discovery

The documented technical mechanism is runtime discovery through DexKit. Instead of relying on one fixed set of Instagram class and method names, InstaEclipse uses DexKit to locate the classes and methods it needs when Instagram launches. The README says this gives the module a better chance of surviving code rearrangement in an Instagram update than a module tied to fixed names.

That approach is a mitigation, not a guarantee. The documentation states that the module will not survive every update untouched. Runtime discovery can locate a target after a structural change, but it cannot guarantee that Instagram has preserved the behavior, data structure, permission flow, or screen context required by every feature. A module update may still be needed when Instagram introduces a larger interface change. This is the central engineering trade-off: dynamic lookup reduces one class of breakage while leaving feature-level compatibility dependent on the current Instagram build.

The repository's primary language is Java, and its top-level layout includes the Android application under `app/`, Gradle build files, `settings.gradle`, `gradle.properties`, and the Gradle wrappers. The small companion app is part of the distribution. It provides module status, live logs, settings backup, and the theme editor. Those companion functions matter when runtime lookup or a feature fails, because the documentation gives the user a place to inspect status and logs rather than only a collection of switches.

## Ghost Mode and Direct Message Controls

Ghost Mode is the most consequential group of switches because it changes account activity signals and the handling of private or disappearing content. The README lists controls to hide DM read receipts, hide typing indicators, hide story views, hide live presence, bypass screenshot detection in direct messages, allow screenshots where Instagram blocks them, open view-once media without marking it as seen, retain view-once and view-twice media, and keep disappearing messages. A Quick Toggle is documented as a way to flip the listed controls together.

The Privacy and DMs section adds a passcode or fingerprint gate for the whole app or only the inbox, hiding selected chats, retaining copies of messages that another person unsends, and freezing the user's last-seen status. These are client-side module behaviors, so the account and server may still impose their own rules. The README does not explain how Instagram accounts the hidden actions on the server, whether every feature works across account configurations, or how the module handles conflicts with Instagram's own privacy settings.

There is also a clear operational risk. A switch that prevents a read receipt or typing indicator changes what the other person sees, but it does not make the action private in every sense. The module does not document a server-side guarantee, a formal threat model, or a policy for account restrictions. Users should treat these controls as configurable client behavior rather than as a promise that every trace is removed.

## Downloads, Caching, and Instagram Media

The media section is more concrete than the privacy controls because it names the supported objects and operations. InstaEclipse can download single photos, full carousels, reels, stories, profile pictures, and viewed Instants. It can also copy direct CDN links for a post, reel, or individual carousel slide. The documented folder controls include a custom download directory, username subfolders, and timestamped filenames.

The 24h story cache is a separate mechanism from ordinary downloading. Viewed stories are kept for one day so that deleted or expired stories can potentially be reopened or saved. The README says these cached stories are organized into per-username folders. This feature introduces local storage and retention implications that differ from downloading a file intentionally. The documentation does not state cache size, encryption, maximum file count, behavior when storage is full, or how cache data is removed. It also does not explain whether cached stories remain accessible after the app is reinstalled or after device storage is cleared.

The companion app's settings backup and live logs may help with diagnosing media failures, but the README does not specify the backup file format or whether downloaded media is included in a backup. The documented distinction matters: settings backup should not be read as a media archive unless the project says so.

## Appearance, Clean Feed, and Ad Controls

Appearance changes are applied through the in-app settings, with theme colors live-applying without a restart. Users can select built-in presets or configure background, surface, text, accent, and icon colors. Custom `.ttf` and `.otf` fonts can be loaded and applied across the app, including chats and captions. A custom emoji font can also be installed. The README specifically notes that font and emoji changes apply the next time Instagram starts, so the apparent live behavior differs by feature.

The Clean Feed section removes suggested posts, suggested reels, other non-followed feed material, Threads cross-promotion, and Meta AI entry points in search, the composer, and reel more-options controls. The Ads and analytics section documents blocking sponsored posts and ad units, cutting analytics and telemetry calls, and disabling tracking links. The README excerpt ends while describing the last feature, so the complete tracking-link behavior cannot be confirmed from the available text.

These controls are filters or hooks inside the Instagram client, not a replacement recommendation system. Filtering suggested content does not change who follows whom, and disabling telemetry calls cannot establish that no network request occurs elsewhere. The documentation does not promise complete removal of all sponsored content, all analytics, or every tracking path. It also does not define a way to whitelist individual ads or restore a hidden feed section through the documented interface, so users should inspect the menus before relying on a particular control.

## Installation Path and First Configuration

The README does not provide a complete device-by-device installation tutorial or exact commands for enabling the module. It states that InstaEclipse is available through the GitHub release page and identifies the required environments as rooted LSPosed and no-root LSPatch. It does not document a package name, APK installation command, LSPosed activation sequence, LSPatch patching sequence, or compatibility matrix for Instagram and Android versions.

Because the available project documentation omits those exact steps, this article does not invent an `adb install` command or an activation sequence. The practical first use described by the README is to obtain the release, place the module into the supported LSPosed or LSPatch environment, enable it for Instagram, and open Instagram. A long press on the search icon should open the InstaEclipse settings sheet. Start with one low-impact setting, such as a theme change or feed suggestion filter, then confirm that the menu remains usable before enabling Ghost Mode or media caching.

The companion app should be used to check module status and read live logs. Those are the documented diagnostic entry points. The README does not say whether the companion app is required for every feature, so its exact role beyond status, logs, backup, and theme editing should not be expanded beyond the documented scope.

## Compatibility and Maintenance Boundaries

InstaEclipse is not archived, and the last push was on 2026-09-15. Recent releases include v0.7.0 on 2026-09-13, v0.6.0 on 2026-07-08, and v0.5.2 on 2026-05-10. These facts indicate recent repository activity, but they do not establish compatibility with every Instagram release. The repository's own README makes the narrower point that DexKit can reduce breakage from renamed classes and methods, while some Instagram updates can still defeat features.

The Apache-2.0 license provides the project's stated licensing framework. The README points to a separate `DISCLAIMER.md`, and the project identifies itself as personal and educational. The available documentation does not state whether the module is signed, how updates are distributed, whether releases include source changes, or what migration process applies to settings across versions. Those omissions limit upgrade planning.

A serious limitation is that the module alters a third-party application at runtime. Instagram updates can change behavior, permissions, screens, and internal method structures. A successful installation therefore does not guarantee that every switch works. The appropriate maintenance cost is periodic compatibility checking against the installed Instagram version, plus occasional module upgrades and configuration review. The README does not document a stable API for external integrations or a rollback procedure for an incompatible module release.

## InstaEclipse Compared With Official Instagram Controls

InstaEclipse adds client-side toggles such as hiding DM indicators, preserving disappearing media, caching viewed stories, filtering feed suggestions, and applying a custom theme.

InstaEclipse takes a different approach through an LSPosed or LSPatch module. It instruments the installed Instagram client and searches for target code at runtime with DexKit. That creates a larger compatibility surface than using the official settings, because the module depends on both the Android modification environment and Instagram's internal implementation. It also introduces documented features such as local story caching and options affecting client-side activity indicators.

The official client is therefore the better choice when supported behavior and predictable account handling matter more than additional controls. InstaEclipse is more relevant when the user specifically values the documented module features and accepts the possibility of breakage after Instagram updates. Neither approach should be described as a guarantee about server-side privacy.

## Conclusion

InstaEclipse is appropriate for an Android user who wants in-app Instagram controls, can work with LSPosed or LSPatch, and is prepared to handle module compatibility after Instagram updates. It is unsuitable for users who need an official client, cannot use a modified module environment, or want behavior supported by Meta rather than through runtime instrumentation. Verify the compatible Instagram versions and the specific features required before adopting it, then check whether the module remains enabled after each Instagram release.

## FAQ

### What is InstaEclipse and who is it for?

InstaEclipse is an LSPosed and LSPatch module that adds configurable controls to Instagram. It is for Android users who want client-side privacy, media, appearance, and feed modifications and can use either a rooted LSPosed environment or no-root LSPatch.

### Does InstaEclipse require root access?

The README describes two supported environments: LSPosed for rooted devices and LSPatch for devices without root. It does not provide a complete installation procedure or compatibility matrix for either environment.

### How do I open the InstaEclipse settings menu?

After the module is enabled, the README says a long press on the search icon inside Instagram opens the settings sheet. Most feature changes take effect without a restart, although custom fonts and emoji apply the next time Instagram starts.

### What happens when Instagram updates?

InstaEclipse uses DexKit to find Instagram classes and methods at runtime instead of relying only on fixed names. The README says this helps when Instagram rearranges its code, but also states that the module will not survive every update untouched.

### What is the 24h story cache in InstaEclipse?

The cache keeps viewed stories for a day so deleted or expired stories can potentially be reopened or saved. The README says cached stories are sorted into per-username folders, but does not document cache size, encryption, or deletion behavior.

## Sources

- [License: Apache-2.0](https://github.com/ReSo7200/InstaEclipse/blob/main/LICENSE)
- [Project website](https://t.me/InstaEclipse)
- [README](https://github.com/ReSo7200/InstaEclipse/blob/main/README.md)
- [Releases](https://github.com/ReSo7200/InstaEclipse/releases)
- [ReSo7200/InstaEclipse on GitHub](https://github.com/ReSo7200/InstaEclipse)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/reso7200-instaeclipse
