What Happened: Instagram keeps crashing in recurring waves, and the current one hits Samsung Galaxy and other Android phones at launch and mid-scroll. Most waves start on Meta’s servers, not on your phone, which is why clearing the cache so often does nothing. The fix that works depends on which of five crash patterns you have.

Instagram keeps crashing for thousands of people at a time, in waves that arrive every couple of months like clockwork. The current wave is heavy on Samsung Galaxy phones, S23 and S24 Ultra owners especially, with the app closing the moment it opens or dying mid-scroll in Reels.

The standard advice is to clear the cache, restart the phone, and reinstall. Plenty of people in the middle of a crash wave have done all three and watched the app crash again on the very next launch. One reinstall attempt can even make things worse, kicking you into a loop where Instagram logs you out every single time you log back in.

There is a reason the usual fixes fail, and it lives on Meta’s side of the connection. I’ll walk through what causes these waves, how to tell whether the problem is your phone or Instagram itself, and the specific fix for each crash pattern, including the ones where the right move is to do nothing at all.

Why Does Instagram Keep Crashing in Waves

Instagram keeps crashing in waves because Meta changes the app’s behavior remotely about 15 times more often than it ships visible updates, so one bad server-side switch can break millions of phones overnight without any new download.

The explanation rarely makes it into fix guides. What surprised me digging into Meta’s own engineering paper on its MobileConfig remote configuration system is the sheer scale of it, more than 4,300 remote configurations and 26,000 individual parameters steering the app. Engineers flip those switches from the server, and configuration changes ship roughly 15 times more often than code changes.

That math answers the question users keep asking during every wave: “the last update was days ago, so why did it break today?” What changed was a server-side setting, and your phone obeyed it the next time the app phoned home. No download was involved.

Meta also tests these switches on live users at a scale that surprises people. The same paper describes canary tests that route a configuration change to as much as half of the entire user base for four hours to catch subtle bugs. If you crash during one of those windows and your friend with the same phone does not, you were probably in the test group.

One more wrinkle matters here. Fetching fresh settings at startup would add about 2.5 seconds of launch delay, so the app deliberately boots on slightly stale cached settings and updates them in the background.

That design choice is why a broken app sometimes runs fine for a few seconds and then dies. It is also why Meta keeps an emergency push mechanism, used about once a quarter, that can force the app to restart itself on billions of devices. The same staged-rollout machinery sits behind other sudden behavior shifts, like the ones covered in the Explore page reset guide.

Is the Crash Coming From Your Phone or From Instagram

The fastest diagnosis is a two-device test. If Instagram also misbehaves on your browser at instagram.com or on a second device, the problem is on Meta’s side and no amount of phone cleanup will fix it.

The way I triage this is symptom-first, because each crash pattern points at a different cause. Crashing in step with thousands of strangers means a config wave. Crashing alone means something local, usually storage, an ancient install, or a beta build.

Symptom	Likely cause	Fix
App worked yesterday, now crashes at launch for you and many others	Server-side configuration wave	Wait it out, keep the app updated, confirm scope on a second device
Crashes only when scrolling or watching Reels	Beta build, low RAM, or the iOS 26.2 touch bug	Leave the beta, restart, then apply the iPhone fixes below
Galaxy S24 crashes when you like a comment inside a Reel	Known device-specific bug	Avoid the action until a patch lands, report it in-app
Logged out every time after a reinstall	Account state desync between Meta’s databases	Stop retrying, use the 24 to 48 hour reset trick below
Single-image drafts vanish while Reels drafts save fine	Draft-saving bug first reported in April 2026	Use carousel or Reel drafts, back up content outside the app

Two of those rows deserve a quick flag. If comments will not load at the same time the app is crashing, that is one more vote for a server-side wave, and the comments not loading guide shows the same cross-platform test. And if you want the deeper version of the outage-or-me protocol, the is TikTok down diagnostic applies to Instagram almost line for line.

How to Fix Instagram Crashing on Android

The Android fix order is cache, beta status, storage, then a careful reinstall. Run them in that order because the early steps are free and the last one can cost you your drafts.

The current wave is Android-heavy for a reason. Meta’s own data shows about 75 percent of Android devices running its apps have hardware comparable to a 2015 flagship or older, and roughly 1 percent of installs are running app versions more than 987 days old. Old hardware plus ancient versions is where crash waves bite hardest.

From my testing, this is the sequence worth running on any Android phone, Samsung included:

1. Clear the cache at Settings > Apps > Instagram > Storage > Clear Cache. This deletes nothing important, your photos and DMs live on Instagram’s servers.
2. Check whether you are in the beta. Open the Play Store, search Instagram, and scroll to the beta section. Leave the program, then update to the standard build. Beta exits fix a large share of Reels-specific crashes.
3. Free up storage until at least 10 to 20 percent of the phone is empty. Instagram gets unstable on full phones, and Reels are the most memory-hungry surface in the app.
4. Restart the phone after a recent system patch. The April 2026 Samsung security patch broke background services for several big apps on Galaxy hardware, and a restart after patching clears most of those conflicts.
5. Reinstall only as a last resort. Uninstalling permanently deletes every locally saved draft, and during this wave some reinstalls have triggered the logout loop covered two sections down.

If the phone is older or low on RAM, anything under 3GB struggles with Reels, the smarter long-term move is Instagram Lite. It is a fraction of the size and skips most of the heavy rendering that crashes budget hardware.

How to Fix Instagram Crashing or Freezing on iPhone

iPhone crashes in 2026 mostly trace to iOS 26.2’s touch handling bug and to power-saving settings throttling the app, not to the cache.

The strangest failure mode on iPhone is Reels that stop responding to vertical swipes on iPhone 16 and 17 models. That one has a name, the Touch Handshake bug in iOS 26.2, and it is a firmware-level problem rather than an Instagram bug. The app gets blamed because Reels is where fast swiping happens.

Fix	Where it lives	When to use it
Force restart	Press Volume Up, Volume Down, then hold the Side button about 15 seconds	Frozen scrolling or unresponsive touch in Reels
Offload App	Settings > General > iPhone Storage > Instagram > Offload App	iOS has no clear-cache button, this is the equivalent without deleting your login
Reduce Transparency	Settings > Accessibility > Display & Text Size	UI lag and stutter on newer iPhones running iOS 26
Turn off Adaptive Power	Settings > Battery	Jerky Reels scrolling, the setting throttles the GPU to save battery
Most Compatible camera format	Settings > Camera > Formats > Most Compatible	Crashes that happen while uploading photos or video

What I’d recommend for upload crashes specifically is dropping export resolution before blaming the app. Pushing 4K at 120fps through Instagram’s uploader strains it badly, and 1080p at 60fps uploads survive the same network conditions with room to spare.

What to Do When Reinstalling Logs You Out Over and Over

The logout loop after a reinstall is usually a database desync on Meta’s side, and the counterintuitive fix is to stop logging in and wait one to two days.

This one frustrates people more than the crashes themselves. The pattern got a nickname in early 2026, the zombie state, because Meta’s review system marks the account as fine while the login servers keep reading a stale copy that says otherwise. Your password is fine, and so is your account; two of Meta’s databases are out of step about you.

Hammering the login screen makes it worse by tripping rate limits. The way I’d play it instead: log in once through your linked Facebook account if you have one, and if that fails, request a password reset email but wait 24 to 48 hours before clicking the link. The delay gives Meta’s database clusters time to sync, so the reset lands on an account both systems agree exists.

If the loop survives all of that for more than three days, the nuclear option is a formal data access request under GDPR or CCPA through Meta’s privacy center. Those requests route to a different internal team and have a track record of forcing stuck accounts back into sync. Anyone who suspects the lockout is more than a glitch should read the hacked account recovery guide before doing anything else.

How Do Creators Protect Drafts and Deadlines During a Crash Wave

Drafts are local files that die with the install, so the protection strategy is finishing content outside Instagram and treating the app as an upload button only.

The most expensive mistake during a crash wave is reflex-uninstalling with a week of drafts inside. Uninstalling wipes every local draft permanently, and there is no recovery path. On top of that, a separate bug from April 2026 makes single-image drafts silently fail to save even when Reels and carousel drafts work fine.

The creators who sail through these waves all run the same playbook, and it is the one I’d set up before the next wave rather than during it. Edit and store everything in an external editor, keep finished exports in your camera roll or cloud storage, and post through Meta Business Suite in a desktop browser whenever the app is unstable.

The browser path runs on separate infrastructure from the mobile app and usually survives app-side waves untouched. Stories deserve the same caution, since upload failures spike during waves, as covered in the story upload troubleshooting guide.

Before: The app crashes the night a sponsored Reel is due. The creator clears the cache, reinstalls, loses 12 drafts including the sponsor’s edit, then gets stuck in the logout loop with a deadline gone.

After: The same crash hits, but the finished Reel lives in the camera roll and a cloud folder. The creator posts it from Meta Business Suite on a laptop in five minutes, offloads the app instead of deleting it, and waits out the wave with every draft intact.

Quick Takeaways

• Instagram crash waves are mostly server-side. Meta flips remote settings 15 times more often than it ships app updates, which is why phones break with no new download.

• Diagnose scope first. If instagram.com or a second device shows the same problem, skip the phone cleanup, nothing local is broken.

• On Android, leave the beta program and keep 10 to 20 percent storage free before considering a reinstall. On iPhone, offload the app and turn off Adaptive Power.

• Never uninstall with drafts inside, they are local files and deletion is permanent. Reinstalls during a wave can also trigger a 24 to 48 hour logout loop.

• Keep finished content outside the app and post through Meta Business Suite on the web when the app is unstable.