_{If HushThreads makes Threads better for you, a coffee helps me keep testing patches and maintaining them as Threads changes.}

HushThreads is a Morphe patch bundle for Android that takes the ads out of Threads and cuts down what the app reports back to Meta. Morphe Manager applies it to the Threads app on your own phone, and the result has a HushThreads page in its settings with switches for nearly everything it does.

Sponsored posts and suggested-account cards leave your feed before Threads shows them. Shared links lose their tracking tags, and a short /share/ link becomes the post's own link. Web links open in your browser instead of Threads' own, with its click tracker skipped. You can also save photos and videos, keep your place in the feed, stop autoplay and make dark mode pure black.

The latest release is v0.0.17, with 22 patches. It's for Threads 454.0.0.54.79 on all eight APKMirror variants. What changed in each version is in the changelog.

Add to Morphe | Download a release | Browse the patches

HushThreads only comes from this repo, github.com/SysAdminDoc/HushThreads, and you add it through Morphe Manager. It's a patch bundle for Android, so it never ships a Windows program or a ready-made APK, and a site offering either one under this name isn't mine.

1. Install Morphe Manager 2.5.0 or newer.
2. Add HushThreads as a patch source: https://morphe.software/add-source?github=SysAdminDoc%2FHushThreads
3. Get Threads 454.0.0.54.79 (com.instagram.barcelona) for any architecture and screen density in the table below, on Android 9 or newer. If you're on an older Threads, update it to 454 before you patch.
4. Uninstall the stock Threads. A patched Threads can't install over Meta's signed copy. If you'd rather keep it, add Change package name (and Change app name, so you can tell them apart) and the patched one installs beside it as a second app with its own sign-in.
5. In Morphe Manager, pick that file and patch. The default selection has every patch except the five the Patches section names, so you don't need Expert mode.

To add one of those five, turn on Settings → Advanced → Expert mode in Manager before you pick the file. If you saved your own selection in Expert mode before, Manager may keep using it, so look over the list once.

HushThreads patches Threads 454 only. Each release moves to the newest stable Threads and drops the one before, so v0.0.15 is the last release for 451.0.0.51.80 and v0.0.16 is the last release for 452.0.0.50.64. If a patch can't find what it needs in your build, patching stops with a message naming it, so you don't end up with an app where that patch does nothing.

In 2027 Android developer verification reaches every certified phone (it started on 2026-09-30 in Brazil, Indonesia, Singapore and Thailand), and a patched Threads signed with your own key counts as an app from an unverified developer. You can still install it over ADB, or through Android's advanced install flow, which is a one-time setting with a one-day wait.

Release checks run on these stock bundles:

bb3c799dd07c71ae6a4c4a2a74489a6dd37302a43c741df749b6d351ac001a32  threads-454.0.0.54.79-512408621.apkm
3d5dcf74d56079751770ed2d9673b7c30f42e2932df1e43028aba5f5c6bec4de  threads-454.0.0.54.79-512408622.apkm
7d63c40f2ad4fce80542dfa8e4a6c718496e9250f27c53d6885a4cb8e78b4b47  threads-454.0.0.54.79-512408625.apkm
ce9a0cdde01928a88e859d905a710d0f5316b1a178ecb4ebe1b2e76b780afb22  threads-454.0.0.54.79-512408635.apkm
2f9516f16e8fd8cd3f2fa478c7246d3274e5a14f04109c1de4996c9fbd5f45da  threads-454.0.0.54.79-512408636.apkm
2be7500e68feb3c57c4a7996f7eeefc199f8beac246bc1fe2b9395e1badd4fb0  threads-454.0.0.54.79-512408645.apkm
e427b7e8c6e88184f839039db71d087f288a37d3a934a18465ce990af1e6c5fd  threads-454.0.0.54.79-512408647.apkm
672004103783b1c1d0f7e752f7408921c8248b52531987ffbbbd0a05b2eeb7e1  threads-454.0.0.54.79-512408648.apkm

A copy from another site may be packed differently and have another hash. HushThreads matches the Threads version name, so any 454.0.0.54.79 build works. The table lists the eight APKMirror variants checked here.

Morphe Manager signs the patched Threads with a key it makes on your phone, and Android only installs an update over your patched Threads when it carries that same key. Back it up right after your first patch. In Morphe Manager, open Settings, then System, then Import & export, then Signing key, and tap Export. Keep the Morphe.keystore file somewhere private, since anyone who has it can sign an APK your phone will accept as an update.

On a new phone, import the key before you patch anything. Reinstalling Manager or clearing its storage makes a new key, and with a different key the only way forward is to uninstall the patched Threads and sign in again.

HushThreads has 25 patches. Morphe Manager's default selection has all but five: Change app name, Change package name, Change version code, Remove share targets and Trust user-added certificates. Those five change Threads when you patch and have no switch to undo them. The first two make a second app you install beside Threads, with its own sign-in. Most of the others have a switch in HushThreads settings, and each row below says where it is and how it starts.

The switches in the Appearance section take effect after you restart Threads. A Restart row shows at the top of HushThreads settings when you flip one. Tap it and Threads reopens in HushThreads settings.

In Threads, open your profile, tap the settings button at the top and tap HushThreads, just above More settings. You can also long-press the Threads icon on your home screen and tap HushThreads, or open Threads' App info page and tap Additional settings in the app (Samsung phones call it Configure in Threads). A long press on the Threads logo at the top of your feed opens it too, even while HushThreads is paused. The logo ignores taps and holds while the feed is loading or refreshing, so wait for it to settle. With TalkBack on, the logo reads as "Threads".

Don't want all of those? Under Pause, backup and diagnostics, Settings shortcut on the app icon, Settings row in Threads' settings and Open settings from the logo each take one away. The last one that's on can't be turned off, so you always have a way back in, and App info works whichever ones you keep.

Pause at the top of the home page turns every feature off at once and keeps your choices. Settings can be saved to a file and restored, and a diagnostic report can be exported for bug reports. Reports keep counts, not your posts or links, and they leave out file paths. Look one over before you share it anyway.

If Threads crashes within a minute of starting three times in a row, HushThreads pauses itself and says why at the top of its settings. Your switches stay saved. Tap Resume and restart Threads to turn it back on. A crash in that first minute is kept, so the next diagnostic report you export shows what crashed and which switches were on. Threads has a crash guard of its own. Five quick crashes inside four hours make it delete its data, which signs you out and clears HushThreads' settings. Safe mode usually gets there first, but it can't help when the crash comes from one of the patches without a switch. If Threads keeps crashing, patch again without them.

Tap Log in with Instagram and enter your Instagram username and password. Threads can ask twice whether to save your login info. Tap Not now each time if you don't want it saved. Passkey sign-in won't work on a patched Threads, because Meta only lets its own signed copy use your passkeys. Your password still does.

If you also patch Instagram with HushGram, sign both with the same Morphe Manager key. Threads then shows your Instagram account as a tile on its login screen, and tapping it signs you in without your password. With a Root Mount install you can sign in on stock Threads first, and the mounted build keeps that session.

• Threads says your password is wrong when it isn't. Reset your Instagram password and sign in with the new one. That fixed it in issue #3.
• A feature you used stopped after updating from v0.0.12 or older. Block background-return feed refresh, Disable screenshot detection, Disable video autoplay, Max image quality and Pure black dark mode joined the default selection in v0.0.13 with their switches off. Turn yours back on in HushThreads settings.
• Instagram says "Sorry, we weren't able to load that website" when you tap a Threads post. That message is Instagram's, not a patch you're missing. The regular Instagram app only hands posts over to a Threads signed by Meta, and a patched Threads carries your Morphe Manager key instead. Opening the post from inside Threads still works, and the Links section in HushThreads settings says so when it finds Meta's Instagram on your phone. Reported in issue #8.
• Android won't install the patched app. Uninstall the stock Threads first. An update to your patched Threads needs the same signing key as the copy on your phone.
• Android says INSTALL_FAILED_NO_MATCHING_ABIS. The Threads file you patched was built for a different processor. Get the variant in the table above that matches your phone's CPU (most phones are arm64-v8a) and patch it again.
• Patching stops with a patch's name. That usually means your Threads isn't the supported build. Check the Threads version name against the table above.

Assume Meta can tell. A patched Threads is signed with your key instead of Meta's, and Threads checks that signature in places. Meta could also notice the analytics uploads that stop arriving. HushThreads doesn't post, like, follow or message for you, and it doesn't change how you sign in. Your feed still comes from Meta's servers, ads included, and the ads are removed on your phone after they arrive.

Meta's terms ask for its permission before anyone modifies its apps. I haven't heard of an account suspended over a patched Threads, but this is a young project, so that doesn't prove much. Threads runs on your Instagram account, so a Threads ban can reach it, and in one report from October 2026 a ban took the linked Instagram and Facebook accounts too. Turn on two-factor authentication before you patch. If you'd rather not risk the account you care about, try HushThreads with a spare account first.

HushThreads doesn't collect anything and has no server. The patched app goes online on HushThreads' behalf for two things only.

• A save you ask for. Tap Save in a post's menu and HushThreads fetches that post's photos or videos over HTTPS from Meta's media servers (cdninstagram.com, fbcdn.net and fbsbx.com), where Threads loads them from too. Any other address is refused. The request carries no cookie or password, even through a proxy, and any cookie the server sends back is dropped.
• The release check, which is off until you turn it on. Then it asks api.github.com for the latest release at most once a day when Threads starts, and again when you tap Check now. The request sends HushThreads/<version> as its User-Agent and carries no cookies and nothing about you or your phone. GitHub sees your IP address, as any site you visit does.

The About section and the Licenses window link to github.com, gitlab.com and www.gnu.org, and Support HushThreads at the bottom of the settings home page links to ko-fi.com. Those open in your browser, and only when you tap one.

Disable analytics points the analytics uploads it recognizes at 127.0.0.1, on a port nothing listens on, so they fail on the phone. Other telemetry isn't covered. Open links in browser hands Android only the real address behind Threads' click tracker, with tags like fbclid removed. Links to Threads, Instagram, Facebook, Messenger and Meta stay in Threads, because sign-in and Accounts Center need its session. Ads go through the same check, from the link button or a swipe up in the photo viewer, and so do the links on a lead form.

Only trust a bundle from this repo's Releases page. Each release ships SHA256SUMS.txt beside the bundle, along with a CycloneDX SBOM and a release receipt recording the Threads build every patch was checked on. Compare the .mpp hash with your download. For v0.0.17 it's:

bdcedf1a14476c9b430c0bba68ebd040e116ff798818794cd7ff512c45190b23  patches-0.0.17.mpp

On Windows, run Get-FileHash -Algorithm SHA256 .\patches-0.0.17.mpp. Inside the patched app, the About section in HushThreads settings shows the bundle's payload hash and the source it was built from.

Releases from v0.0.17 on are signed. Morphe Manager shows the signer when you add or update the source, and it should read d0d2 eda0 b978 70da. Manager remembers that key from then on and refuses an update signed by any other, or by none. The full public key is in morphe-signing.pub.

Use Issues for bugs and Discussions for questions. Include your Threads version and version code, your Morphe Manager and HushThreads versions, how you installed it, and what you expected to happen. A diagnostic report from HushThreads' settings helps a lot. A report closes once you confirm the fix works, or after a few quiet days once I've asked you something or shipped a fix.

You need JDK 21, the Android SDK and PowerShell 7.5 or newer (Windows PowerShell 5.1 works too). Set JAVA_HOME and ANDROID_HOME, or set the SDK in local.properties. GitHub Packages needs GITHUB_ACTOR and GITHUB_TOKEN with read:packages.

The checked-in wrapper uses Gradle 9.8.1. Release checks examine that build-tool version separately from the libraries carried in the bundle.

$env:HUSHTHREADS_FIXTURE_DIR = '<fixture folder>'
$env:HUSHTHREADS_DESKTOP_JAR = '<Morphe desktop JAR>'
./gradlew.bat prepareAdvisoryTool
./gradlew.bat :patches:generatePatchesList
./gradlew.bat :patches:buildAndroid
./gradlew.bat :patches:test :extensions:threads:testDebugUnitTest
./gradlew.bat :extensions:threads:lintRelease :extensions:shared:library:lintRelease
./scripts/verify-all-patches.ps1 -Apk '<Threads bundle>' -DesktopJar '<Morphe desktop JAR>' -WorkDir '<scratch folder>'

The bundle, its SHA-256 and a CycloneDX SBOM land in patches/build/release. Without HUSHTHREADS_FIXTURE_DIR, the tests that need real Threads builds skip. They run in :patches:fixtureTest, which :patches:test runs first. scripts/install-hooks.ps1 installs the push checks.

A release runs in five stages of scripts/release/release.ps1, each with -Version <version>, from a clean checkout of main. prepare dates the changelog, moves the version strings, regenerates the patch list and rewrites the README's latest-release line for you to review and commit. preflight runs the quick checks and pushes. build reruns the tests, builds the bundle, writes the receipt from one fixture run per declared build and tags the commit last. publish (with -Intro and -Update text files) creates the GitHub release and downloads each asset back to compare it, and index (with -Summary) points patches-bundle.json at it. A stage won't start before the one it follows, and one that stopped part way can be run again.

Before publishing, run scripts/walk-app.ps1 -Serial <serial> -OutDir <walk folder> under an owned device lease. It writes a patch receipt and a walk receipt. To walk that retained install again, use -SkipPatch -PatchReceipt <walk folder>/patch-receipt.json. Keep the signed APK, original vendor input and catalog at their recorded paths until publication. An unknown or different install is refused without reinstalling it.

The publish stage also needs -Walk <walk folder>/walk-receipt.json. Its catalog must match the bundle's source commit. It rechecks the APK's manifest and embedded bundle identity, the installed hashes from both ends of the walk, every named screen and any recorded problem. Old schema 1 receipts remain historical records and can't qualify a new release. -Java, -DesktopJar and -Aapt2 select the validation tools when needed.

Where things live:

• patches/src/main/kotlin/app/morphe/patches/threads/ holds the patches. AppCompatibilities.kt under patches/.../shared/compat/ names the supported Threads build, and only the newest stable one is declared.
• extensions/threads/ is the Java code that runs inside Threads, settings screen included. extensions/shared/ holds the shared library and its translations.
• patches-list.json is the generated patch catalog. patches-bundle.json is the Morphe source index and only changes at release time.

HushThreads' build, settings, diagnostics and safety checks came from Hushfacebook at c15d4f79. That code carries the notices from Hushfeed, Andrew Liang's patches, FroggoMorphePatches and the Morphe/ReVanced chain recorded in NOTICE and provenance.json.

The Threads patches are written here, and no outside Threads code is used. Hide ads hooks the feed-cache merge point that zeldrisho identified, with its own implementation. sources/threads-sources.json records the 12 other Threads patch sources that were looked at and what each one allows.

Copied code keeps its copyright, author, license and source notices, and gets a Forked from line naming the repository and commit. A notice only goes when the code it covers is gone. Outside code ships only after its source is marked adopted in the ledger with its exact commit, a compatible license, a NOTICE entry and a provenance rule, and ProvenanceTest checks the headers.

GPL-3.0, with the Morphe section 7 notices carried in NOTICE. HushThreads has no connection to Meta or to the Morphe project, and neither endorses it. Threads, Instagram and Meta are trademarks of Meta Platforms, Inc.