Tag: how to fix

iMessage Won’t Send on iPhone: How I Fix Green Bubbles and “Not Delivered” Errors

iMessage won’t send on iPhone and turning green or showing “Not Delivered”? Here is the exact order I work through to get blue bubbles back, usually in under two minutes.

When iMessage won’t send on my iPhone, iOS gives me one of two warnings: a red “Not Delivered” alert under the bubble, or the bubble flipping green because my phone quietly fell back to standard SMS. After years of fixing this for family members, I have learned that both signs point to the same thing. Something is blocking iMessage from reaching Apple’s servers, and the cause is almost always small.

The triggers range from a lapsed Apple ID session to a weak Wi-Fi signal, and most take under two minutes to clear. I work through the steps below in order, because the first one resolves it for me roughly nine times out of ten.

Quick Answer

Open Settings, tap Messages, and toggle iMessage off. Wait 10 seconds, then switch it back on and give it up to a minute to re-register. If the bubble is still green, confirm you are signed into your Apple ID and that your internet connection works. Most iMessage failures clear in under a minute this way.

The single most reliable fix is toggling iMessage off and on to force a fresh session.

Why does iMessage turn green or say “Not Delivered”?

A blue bubble means your message travelled over Apple’s iMessage network, end-to-end encrypted and free over Wi-Fi or cellular data. A green bubble means iOS fell back to SMS or MMS through your carrier, which may cost money and drops read receipts. A “Not Delivered” notice means the message failed entirely and reached the recipient by neither route.

What each warning sign means

The first time I saw a green bubble to my sister, I assumed iMessage was broken on my end. It was not. The colour and the error each map to a specific cause, so reading the sign correctly saves you from chasing the wrong fix.

Cause What you’ll see
iMessage disabled or signed out All bubbles turn green
No or weak internet connection “Not Delivered” or stuck “Sending…”
Recipient’s iMessage is off Green bubble (their end, not yours)
Apple server outage Multiple recipients affected at once
Device clock set incorrectly iMessage fails to authenticate

Match the sign to the table first, then jump straight to the fix that fits.

How do I toggle iMessage off and back on?

This clears a stale session token, and it is the first thing I try every single time because it works so often.

  1. Open Settings and tap Messages.
  2. Toggle iMessage off.
  3. Wait 10 seconds.
  4. Toggle iMessage back on and wait up to 60 seconds for registration to complete.

If you also use FaceTime, toggle it off and on at the same time, since it shares the same Apple ID authentication layer. When FaceTime is misbehaving too, my guide on fixing FaceTime when it won’t connect walks the same sign-in path.

Toggling iMessage forces a fresh registration with Apple and fixes most failures on its own.

What if my internet connection is the problem?

iMessage needs an active internet connection, and when my signal is weak the messages either queue up or fail silently with no obvious reason.

  1. Open Safari and load any website. If it fails, the problem is your connection, not iMessage.
  2. On Wi-Fi, go to Settings → Wi-Fi, toggle it off and back on, or move closer to your router.
  3. On cellular, switch Airplane Mode on for 15 seconds, then off.

Open Settings → Cellular, scroll down, and confirm iMessage is allowed to use cellular data. If that toggle is off, iMessage breaks the moment you leave Wi-Fi range. If pages won’t load at all, my walkthrough on Safari not loading on iPhone covers the connection-side steps.

Confirm a working data connection before blaming iMessage itself.

Should I sign out of my Apple ID and back in?

Yes, when the toggle looks fine but messages still fail, a corrupted iCloud credential is usually the culprit. Signing out and back in rebuilds it.

  1. Go to Settings → [your name].
  2. Scroll to the bottom, tap Sign Out, enter your Apple ID password, and choose to keep a local copy of your data.
  3. Return to Settings and sign back in with your Apple ID.
  4. Go to Settings → Messages and re-enable iMessage.

A fresh sign-in clears a broken credential that toggling alone cannot reach.

Why does my iPhone clock break iMessage?

iMessage uses your device clock to authenticate with Apple’s servers, so even a few minutes of drift can break the handshake. I once hit this after a long flight across time zones.

  1. Open Settings → General → Date & Time.
  2. Enable Set Automatically.
  3. If it was already on, toggle it off, wait five seconds, then turn it back on to force a fresh sync.

An accurate, auto-set clock keeps iMessage authentication from silently failing.

How do I reset network settings safely?

A network reset wipes saved Wi-Fi passwords, VPN profiles, and cellular APN settings to give iMessage a clean slate. It does not delete your photos, apps, or personal data, which is why I keep it as a later step rather than a scary last resort.

  1. Go to Settings → General → Transfer or Reset iPhone.
  2. Tap Reset → Reset Network Settings.
  3. Enter your passcode and confirm. Your iPhone will restart.
  4. Reconnect to your Wi-Fi network, then open Settings → Messages and confirm iMessage is still enabled.

Before you reset, check Apple’s System Status page to rule out a server-side outage. A red dot next to iMessage means the problem is Apple’s, not yours.

Reset the network last, and only after confirming Apple’s own servers are healthy.

Common Mistakes to Avoid

  • Messaging an email the recipient never linked to iMessage. Fix: switch to their phone number, which is far more likely to be registered.
  • Assuming a green bubble means you are being ignored. Fix: accept it usually means the recipient is on Android or has iMessage off, and the message still delivers as SMS.
  • Skipping the internet check. Fix: load a website first, because a silently dropped Wi-Fi session causes more “iMessage broken” reports than anything else.
  • Force-quitting the Messages app. Fix: toggle iMessage in Settings instead, since force-quitting can interrupt an in-progress sync.
  • Ignoring a full storage warning. Fix: free up space, because a packed iPhone can stop the Messages database from writing. My guide on freeing up iPhone storage fast shows the quickest wins.

Frequently Asked Questions

Why does iMessage say “Delivered” but they never got it?

“Delivered” means the message reached Apple’s servers and was pushed to their device, not that they opened it. For example, when my brother’s phone was powered off overnight, my texts showed “Delivered” yet sat unread until he turned it back on the next morning.

Can iMessage work without Wi-Fi?

Yes, iMessage runs over any active internet connection, including 4G and 5G cellular data. I send blue bubbles on the train every day with no Wi-Fi in sight, as long as iMessage is toggled on under Settings → Cellular.

Why do some contacts always show green bubbles?

Those bubbles are green because the recipient is on Android or has iMessage disabled on their Apple device. My one friend with a Pixel always lands as a green SMS thread, and nothing I change on my iPhone will ever turn it blue.

Does resetting network settings delete photos or apps?

No, a network reset only clears Wi-Fi passwords, VPN configurations, and cellular settings. When I reset my own iPhone last month, every photo, app, and message stayed exactly where it was.

Why does iMessage work on my iPad but not my iPhone?

Both devices must be signed into the same Apple ID with iMessage enabled separately. When mine drifted out of sync, I opened Settings → Messages → Send & Receive on the iPhone and found the wrong Apple ID listed there.

What if none of these fixes work?

Contact Apple Support or book a Genius Bar appointment, since the cause may be deeper. A persistent failure I troubleshot once traced to a carrier provisioning issue that only my mobile network could clear from their end.

Conclusion

Most iMessage failures come down to a stale session, a dropped connection, or a clock that slipped out of sync, and all three are fixable in under two minutes. Start with the toggle, work down the list, and you should be back to blue bubbles fast. If wireless sharing is also acting up, my guide on fixing AirDrop when it won’t find devices covers the same network layer.

Android Not Charging: How to Get Your Phone Powering Up Again

Android not charging? I walk through the cable swap, port cleaning, and restart steps I actually use to get a dead phone powering up again in minutes.

You plug in your Android overnight, confident it will be full by morning, then wake up to 3%. The reason “Android not charging” is one of the most-searched phone problems is that the symptom looks identical whether the cause is a worn cable, lint packed into the port, or a one-off software glitch. The good news is that most charging failures are something you can fix at home in under five minutes.

I have repaired this exact issue on my own Pixel and on a dozen friends’ Samsungs, and the cause is almost never a dead phone. Work through the checks below in order, because they run from most common to most involved, and you can stop the moment charging resumes.

Quick Answer

Plug in a different USB-C or Micro-USB cable and adapter first, since faulty cables cause most Android charging failures. If that does not help, restart the phone, wait 60 seconds, and try again with the cable connected. Most people fix the problem within these two steps alone.

Why won’t my Android charge at all?

In nearly every case I have seen, the culprit is the cheapest part of the setup: the cable. Third-party and frayed cables look fine but deliver an intermittent connection, so the phone reads it as “no power.” A clogged port, a weak power source, or a frozen charging chip cover most of the rest.

Before blaming the phone itself, rule out the cable, the port, and the wall outlet in that order.

How do I test the cable and adapter?

The charging cable is the single most common point of failure. The first time my phone “died,” I spent an hour cleaning the port before a $4 spare cable fixed it in seconds, so now I always swap the cable first.

  1. Test with a cable you know charges another device reliably.
  2. Plug the adapter straight into a wall outlet, because laptop USB ports and power strips often do not deliver enough current.
  3. If the phone charges with the new cable, throw the original away.

Use a cable rated to your phone’s charging standard. An underpowered cable charges slowly, runs hot, and wears out the connector over time.

A known-good cable plugged into a wall outlet rules out the most common cause in under a minute.

How do I clean a charging port that won’t take a cable?

Pocket lint compacts inside the USB-C or Micro-USB port over months of use and stops the cable making full contact. I shine a phone flashlight into the port first; the packed debris usually looks grey or beige and fills the back of the opening.

  1. Power the phone off completely.
  2. Use a wooden toothpick or a dry interdental brush, never metal.
  3. Gently loosen debris around the port edges and avoid the center pins.
  4. Follow with two or three short puffs of canned air held upright.
  5. Reconnect the cable and check whether it seats more firmly than before.

If the port looks visibly bent or corroded, cleaning will not help; skip ahead to the battery-health check and arrange a port replacement.

A toothpick and canned air clear the lint that blocks contact without risking the delicate pins.

Can a restart really fix charging?

Yes, and it is the step most people skip too quickly. A software crash can freeze the charging subsystem entirely, and a full restart clears that fault in about 60 seconds. I have watched a phone that “refused” to charge come right back the instant it rebooted.

  1. Hold Power, or Power and Volume Down on many models, until the restart menu appears.
  2. Tap Restart and wait for the phone to boot fully.
  3. Plug in the charger and watch for the charging indicator within 10 seconds.

A 60-second reboot resolves a surprising share of charging failures, so always try it before anything harder.

Could the power source be the problem?

A faulty wall outlet, an overloaded surge protector, or an underpowered USB hub can all block charging with no obvious sign. Unplug the adapter and test it in a different wall outlet on a separate circuit before you assume the phone is at fault.

Swap to a different wall outlet to rule out a dead socket masquerading as a dead phone.

How do I check USB mode and battery settings?

When connected to a computer, Android can quietly switch to “File transfer” mode, which trickle-charges or stops charging altogether. I have been caught by this more than once after plugging into a laptop for a quick sync.

  1. Connect to a PC, then pull down the notification shade.
  2. Tap the USB notification (“Charging this device via USB” or similar).
  3. Select Charging only, sometimes labeled “No data transfer.”

Then open Settings > Battery and confirm Battery Saver is not capping the charge at a set percentage. Samsung, Xiaomi, and some other skins include this option, and it can look exactly like a charging failure.

Forcing “Charging only” mode and checking Battery Saver fixes the cases where the phone is working as designed but not as you expected.

How do I know if an app is blocking charging?

A rogue downloaded app can interfere with power management. Safe Mode disables every third-party app without deleting anything, which isolates whether software is the cause.

  1. Hold the Power button, then long-press Power off on screen until “Reboot to safe mode” appears, and tap OK. Exact steps vary by manufacturer.
  2. Plug in the charger. If it charges normally in Safe Mode, an installed app is the culprit.
  3. Restart normally and uninstall recently added apps one at a time until charging holds.

If the phone charges in Safe Mode but not normally, a recently installed app is to blame.

What if it still won’t charge after all that?

Lithium-ion batteries degrade over hundreds of charge cycles. After two to three years of daily use, a battery may charge sporadically or refuse to charge at all.

  1. Dial *#*#4636#*#* on many Samsung, Motorola, and stock Android phones to open a hidden battery information screen.
  2. Check whether Status shows “Charging” while plugged in. If it reads “Discharging” with a cable connected, the battery or charging circuit needs professional service.
  3. Contact your phone’s manufacturer or a local repair shop. Battery replacements typically cost $30 to $80 depending on the model.

A “Discharging” reading on a plugged-in phone points to failing hardware that needs a shop, not another home fix.

Which charging speed should my Android hit?

Using the wrong adapter tier is a frequent reason charging feels broken when it is actually just very slow. This table shows what to expect from each method.

Charging Method Typical Wattage Approx. Time to Full
Standard 5W adapter 5W 3 to 4 hours
Quick Charge 3.0 / 4.0 18 to 27W 60 to 90 minutes
Super / Warp / Turbo Charge 33 to 65W 30 to 50 minutes
Laptop USB-A port 2.5 to 5W 4 to 6+ hours
Wireless Qi (standard) 5 to 15W 2 to 3 hours

See Qualcomm’s Quick Charge overview for wattage specs on QC-certified chargers.

If your phone supports fast charging but you are on a 5W brick, slow charging is expected, not a fault.

Common Mistakes to Avoid

  • Grabbing any USB-C cable nearby. A data-only cable may charge at 5W even on a 65W adapter. Fix: use the cable that shipped with your phone or one rated to the same wattage.
  • Charging through a sleeping PC. Most computers cut USB power in sleep or shutdown, so the phone slowly drains. Fix: use a wall adapter overnight.
  • Using metal to clear the port. SIM-eject pins, scissors, and paper clips permanently damage the pins. Fix: use only a wooden toothpick or interdental brush.
  • Dismissing a “Slow charging” notification. That warning means the cable or adapter does not match your charging standard. Fix: swap to a correctly rated cable and brick.
  • Skipping the restart. A reboot resolves a large share of “not charging” complaints. Fix: restart before moving on to harder steps.

Frequently Asked Questions

My Android shows the charging icon but the percentage isn’t rising. Why?

The phone is receiving some power, but apps are draining it faster than it charges. Lock the screen and turn on Airplane Mode. When my phone did this during a long navigation drive, the percentage started climbing within minutes once I locked it.

Is it safe to charge my Android overnight?

Yes, on Android 9 and later. Adaptive charging slows the rate near 80% and finishes just before your usual wake time. I leave my Pixel charging every night and its battery health is still strong after two years.

Why does my brand-new Android charge slowly?

The most likely cause is a mismatched adapter. A 5W brick on a phone that supports 33W still charges, just three times slower. I once “diagnosed” a friend’s new phone only to find she was using an old 5W charger from a previous device.

Can a software update break charging?

Rarely, but it is documented. If charging stopped right after an update, restart the phone and check Settings > System > Software update for a follow-up patch. A reader once messaged me about exactly this, and a patch released two days later fixed it.

My Android won’t turn on after the battery died completely. What should I do?

Leave it on a wall adapter, not a PC port, for at least 15 to 30 minutes before pressing power. A deeply drained lithium battery needs a slow trickle first. I have revived several “dead” phones this way after they sat empty for days.

Conclusion

A dead cable, a lint-packed port, and a software freeze all look identical from the outside, which is exactly why working through these checks in order saves both time and money. The vast majority of charging failures clear up at the cable swap or the restart. If you have tried everything and it still will not charge, a battery or port replacement is the likely next step, so book a repair before the phone goes flat for good.

If charging works again but your battery still drains too fast, my guide to Android battery draining fast covers the settings that help. Hitting other issues? See my fixes for Android apps that keep crashing and missing Android notifications too.

Chrome Crashing on Windows or Mac: How to Stop Aw, Snap and Random Closes

Chrome crashing on Windows or Mac usually traces to one bad extension, a stale cache, or a GPU conflict. Walk through six ranked fixes and get stable again today.

Chrome crashing on Windows or Mac almost always traces back to a small set of culprits: a rogue extension, a corrupted cache, a GPU driver conflict, or simply an outdated build. The first time my own copy started throwing “Aw, Snap!” on every tab, I assumed the install was beyond saving — but the real cause was a single extension that had silently updated overnight.

I have rebuilt this troubleshooting routine across dozens of Windows and Mac machines, and the order below is ranked easiest-first. Each step takes one to five minutes, and most people get a stable browser back after the first two.

Quick Answer

Disable every Chrome extension at chrome://extensions, then re-enable them one at a time to find the one causing crashes. If that does not help, clear the cache via Settings → Privacy and security → Clear browsing data (set to All time) and update Chrome at Menu → Help → About Google Chrome. These two steps fix most crashes.

Why does Chrome keep crashing in the first place?

Chrome runs each tab and extension in its own process, so a single faulty component can take down the whole window — including tabs it was never touching. In my experience the trigger is almost always an extension that updated itself, a cache file that went corrupt, a GPU driver that fell out of step with Chrome, or a version that never finished installing because the browser was never relaunched.

Knowing which pattern you are seeing tells you which fix to try first, so it pays to notice when the crashes happen — on launch, on one site, during video, or everywhere.

Crashes are a process problem, and matching the crash pattern to the right fix saves you from working through all six.

How do I find the extension that is crashing Chrome?

Extensions are the single most common crash trigger I see. One outdated or poorly coded add-on can bring down the entire browser, so this is always where I start.

  1. Type chrome://extensions in the address bar and press Enter.
  2. Toggle all extensions off using the blue switches.
  3. Restart Chrome. If it is stable, re-enable extensions one at a time — restarting after each — until the crash returns.
  4. Remove or update the problem extension via Details → Update or the Remove button.

Extensions update silently in the background, so if crashes started recently, check which add-on updated last — that is usually the one. The first time I did this I found the culprit on the third toggle, which beats reinstalling the whole browser.

Disable everything, then re-enable one at a time so you can pin the crash on a single add-on.

Will clearing the cache and cookies stop the crashes?

Often, yes. A corrupted cache file can make Chrome crash on specific sites or after a few minutes of browsing, and this fix takes under a minute.

  1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac).
  2. Set Time range to All time.
  3. Check Cached images and files and Cookies and other site data.
  4. Click Clear data, then restart Chrome.

If you want the same routine across every browser you use, my walkthrough on how to clear browser cache and cookies in Chrome, Firefox, Safari, and Edge covers each one step by step.

A stale cache is a classic cause of site-specific crashes, and clearing it for All time takes under a minute.

Could an outdated Chrome version be the problem?

Frequently. Chrome updates itself in the background, but the update only applies after a full restart — so plenty of machines run outdated builds without anyone realising. An unpatched stability bug can cause repeated crashes.

  1. Click the three-dot menu (⋮) in the top-right corner.
  2. Go to Help → About Google Chrome.
  3. Chrome checks for updates automatically on this screen. Install any available update.
  4. Click Relaunch when prompted.

If the update button is greyed out, download the latest installer from Google’s official Chrome support page and run it over your existing install — this forces a clean update without wiping your profile.

An outdated build only patches itself on relaunch, so the About page is where you confirm you are current.

Should I turn off hardware acceleration?

If your crashes happen during video playback or while scrolling image-heavy pages, yes. Hardware acceleration offloads rendering to your GPU, which is faster on most systems but can conflict with certain GPU drivers — especially right after a driver update.

  1. Open Chrome’s menu (⋮) and click Settings.
  2. Search for “hardware acceleration” in the settings search bar.
  3. Toggle Use graphics acceleration when available to Off.
  4. Click Relaunch.

The trade-off is slightly slower rendering. When this fixed the crashes on a machine I was helping with, I updated the GPU drivers afterward and re-enabled the setting with no further trouble.

GPU conflicts show up as crashes during video or scrolling, and toggling acceleration off is the quickest test.

What if I changed Chrome flags by accident?

Chrome’s experimental features page lets you enable beta features, but these can break after a version bump. If you or an extension ever touched chrome://flags, a reset is worth trying.

  1. Type chrome://flags in the address bar.
  2. Click Reset all at the top of the page.
  3. Click Relaunch.

Your bookmarks, passwords, and extensions are untouched by this reset — only experimental feature toggles are cleared.

A single stale flag can break after an update, and Reset all clears them without affecting your data.

How do I reset or reinstall Chrome without losing my data?

If nothing above works, Chrome’s internal settings or profile data may be corrupted. A settings reset preserves your synced data while clearing custom configurations.

  1. Go to Settings → Reset settings → Restore settings to their original defaults.
  2. Click Reset settings to confirm.
  3. If crashes continue, uninstall Chrome via Control Panel → Programs (Windows) or drag it to Trash (Mac), then download and reinstall a fresh copy.

If you are signed in to your Google account, bookmarks and passwords sync back automatically after reinstalling. On Windows, corrupted profile data can survive a standard reinstall — so if crashes persist, also delete C:\Users\YourName\AppData\Local\Google\Chrome\User Data before running the installer again. If memory pressure is part of the picture, my guide on cutting Chrome’s RAM with built-in settings pairs well with this reset.

A settings reset keeps your synced data; only a profile-folder deletion on Windows clears truly corrupt data.

Which fix matches your crash pattern?

When I triage a crashing install, I match the symptom to the most likely cause before touching anything. This table is the shortcut I use.

Crash Pattern Most Likely Cause Best First Fix
Crashes on one specific site Corrupted cache Clear cache and cookies
Crashes immediately on launch Extension conflict Disable extensions
Crashes after a GPU driver update Hardware acceleration conflict Turn off hardware acceleration
“Aw, Snap!” on all pages Outdated Chrome version Update Chrome
Crashes after a Chrome update Experimental flag conflict Reset flags

Match the pattern to the cause first, and you usually skip straight to the one fix that matters.

Common Mistakes to Avoid

  1. Clearing only browsing history, not cache — History and cached files are separate. Always tick Cached images and files when troubleshooting crashes; clearing history alone does nothing for this problem.
  2. Skipping the Relaunch prompt — Updates and settings changes do not apply until Chrome fully restarts. Clicking away from the prompt means the fix has not taken effect yet.
  3. Re-enabling all extensions at once — Adding them back in bulk defeats the purpose. Re-enable one at a time so you can identify the exact problem add-on.
  4. Reinstalling without removing profile data — On Windows, a standard uninstall leaves the profile folder intact. Corrupted data at C:\Users\YourName\AppData\Local\Google\Chrome\User Data will reload with the new install.
  5. Assuming Chrome is always the culprit — If other applications also freeze or crash, check that your system drive has at least 5 GB free and run a Windows SFC scan before blaming the browser.

Frequently Asked Questions

What does the “Aw, Snap!” error mean?
It means Chrome ran out of memory or the page’s renderer process crashed. Closing unused tabs, enabling Memory Saver (Settings → Performance), or disabling extensions usually clears it. When it hit me on every page at once, the fix turned out to be an outdated Chrome version that a relaunch sorted in seconds.

Does reinstalling Chrome delete my bookmarks and passwords?
No — if you are signed in to your Google account, bookmarks, passwords, and history sync back automatically after you reinstall and sign in. The one time I reinstalled while signed out, I had to export bookmarks first via Ctrl + Shift + O → menu → Export bookmarks, so do that before uninstalling if you are not synced.

Can malware cause Chrome to crash?
Yes. Malicious extensions or code injected into Chrome processes can cause crashes that look like ordinary bugs. On a machine where standard fixes did nothing, a Malwarebytes Free scan found a hijacked extension that was the real cause — so scan with Windows Defender or Malwarebytes before any reinstall.

Will trying Firefox tell me if the problem is Chrome-specific?
Yes — if the same page loads fine in Firefox but crashes Chrome, the issue is in Chrome’s configuration rather than the website. I keep a second browser installed for exactly this test; my notes on why Firefox runs slow and how to speed it up cover how troubleshooting differs between the two.

Why does Chrome crash only on certain websites?
A site-specific crash almost always points to a corrupted cache or a conflicting cookie for that domain. Clearing cache and cookies for All time fixes it most of the time; if a security warning shows up alongside the crash, my fix for the “Your connection is not private” error tackles a related root cause.

Conclusion

Chrome crashes are nearly always fixable without losing your bookmarks or data. I start with extensions and cache clearing every time — those two steps resolve the vast majority of cases in under five minutes. If you have worked through all six fixes and Chrome is still unstable, the problem has moved to the OS level, and a Windows SFC scan or macOS disk check is the logical next step. Bookmark this page so the routine is ready the next time “Aw, Snap!” appears.

Last updated: June 25, 2026

Android Apps Keep Crashing? How I Stop Force-Closes for Good

Android apps keep crashing? I walk through the exact steps I use — clear cache, free storage, update, and Safe Mode — to stop force-closes on any phone in minutes.

When Android apps keep crashing right as you reach for them, it feels like the phone is conspiring against you. I have lost count of how many times a banking app force-closed at the checkout counter, and after fixing dozens of these on my own devices and for friends, I can tell you the cause is almost always small and fixable. A factory reset is rarely the answer — most crashes trace back to a corrupted cache, low storage, or a missed update.

Below I walk through the exact order I troubleshoot in, from the 30-second fix that solves most cases to the Safe Mode trick that catches a rogue app. Whether one app force-closes or several crash at once, you will find the right step here.

Quick Answer

If an Android app keeps crashing, clear its cache first: open Settings > Apps > [App Name] > Storage > Clear Cache, then relaunch. If it still crashes, update the app in the Google Play Store and restart your phone. These three steps resolve the large majority of Android app crashes within a few minutes.

Why do Android apps crash in the first place?

Apps crash because something they depend on is broken or missing: a corrupted cache file, not enough free storage to write temporary data, an outdated app version that clashes with your OS, or a buggy system update. The first time I mapped these causes to their symptoms, troubleshooting stopped feeling like guesswork. The table below is the cheat sheet I still use.

Cause Typical symptom Fix
Corrupted cache One app crashes repeatedly Clear app cache
Outdated app Crash after an OS update Update via Play Store
Low storage Multiple apps crash Free up 1–2 GB
Bad OS update Many apps crash at once Install latest system patch
Third-party conflict Crashes stop in Safe Mode Remove recently installed apps

Match the symptom to the cause and you will know which fix to try first.

How do I clear an app’s cache to stop crashes?

Corrupted cache files are the single most common cause I see, and clearing them takes under a minute. This is always my first move.

  1. Go to Settings > Apps (or Application Manager on older devices).
  2. Tap the crashing app, then tap Storage.
  3. Tap Clear Cache, then relaunch the app.

One warning from experience: do not tap Clear Data at this stage. That wipes your login and saved settings. Clear Cache alone fixed the problem the last several times an app started force-closing on me.

Clear Cache is the fast, no-risk first step that resolves most single-app crashes.

Should I update the app before anything else?

If clearing the cache did not help, update the app next. A missed update can leave an app incompatible with your current Android version, which causes crashes on launch or mid-use — something I run into most after a system update lands.

  1. Open the Google Play Store and tap your profile icon (top right).
  2. Tap Manage apps and device, then tap Update next to the crashing app.
  3. Relaunch the app after the update finishes.

An outdated app version is a frequent crash cause, so updating early saves you time.

Could low storage be making my apps crash?

Yes — and this is the cause people overlook most. Android needs headroom to write temporary files, and when free space drops below roughly 10% of total capacity, apps start crashing. Open Settings > Storage; if you are more than 85% full, storage is the likely culprit.

  1. Tap Free up space in the Storage menu.
  2. Delete cached files, large videos, and unused apps.
  3. Aim for at least 1–2 GB free before testing the app again.

For more ways to reclaim space, my guide on how to speed up a slow Android phone targets storage directly, and the walkthrough for an Android storage full warning clears gigabytes fast.

Free up 1–2 GB and crashes caused by a full drive usually stop on their own.

What if force-stopping and restarting don’t fix it?

An app stuck in a bad memory state will not recover on its own, so force-stopping clears it completely. If that alone fails, a full reboot is the step I lean on next.

  1. Go to Settings > Apps > [App Name] and tap Force Stop.
  2. Wait 10 seconds, then reopen the app.

If force-stopping does not help, restart the phone entirely. A full reboot flushes shared system memory that a force-stop cannot reach, and it has cleared stubborn crashes for me instantly more than once. When the phone itself reboots without warning, my guide on an Android phone that keeps restarting covers the deeper causes.

Force-stop first, then reboot — together they clear most memory-related crashes.

When should I uninstall and reinstall the app?

If the installation itself is corrupted — common after a failed update or an interrupted download — only a clean reinstall will fix it. Back up any locally stored data first.

  1. Long-press the app icon and tap Uninstall, or go to Settings > Apps > [App Name] > Uninstall.
  2. Restart your phone.
  3. Search for the app in the Play Store and install it fresh.

I learned to check for cloud backup the hard way: game progress and offline downloads stored only on the device cannot be recovered once you uninstall.

A clean reinstall fixes a broken install, but back up local data before you remove the app.

How do I tell if a bad Android update is to blame?

When several unrelated apps crash at the same time, the OS is usually the culprit, not the apps. A recent Android update may have introduced a compatibility bug, and the fix is typically a follow-up patch released within days.

  1. Go to Settings > System > System Update (the path varies by manufacturer).
  2. Tap Check for Update and install anything available.
  3. Restart your phone after the update completes.

See Google’s official guide to Android updates for manufacturer-specific menu paths on Samsung, Pixel, and other devices.

Mass crashes across apps point to the OS, and the latest system patch usually cures them.

Can Safe Mode find the app that’s causing crashes?

Yes. If crashes started shortly after you installed a new app, that app may be interfering with others. Safe Mode disables all third-party apps temporarily so you can confirm the theory — it is the trick that has saved me the most diagnostic time.

  1. Hold the Power button, then press and hold Power Off until the Reboot to Safe Mode prompt appears. Tap OK.
  2. Test the crashing app in Safe Mode. If it runs fine, a third-party app is the cause.
  3. Restart normally, then uninstall recently installed apps one at a time until the crashes stop.

If crashes happen mainly when loading online content, your connection may be the real issue — my guide on an Android phone that won’t connect to Wi-Fi is the next place to look.

Safe Mode isolates a rogue third-party app so you can uninstall the real culprit.

Common Mistakes to Avoid

  • Tapping Clear Data before Clear Cache. Clear Data wipes your account and settings. Always try Clear Cache first, and only escalate if the crash continues.
  • Skipping the phone restart. Force-stopping an app is not the same as rebooting. Many crashes only clear after a full restart that flushes shared system memory.
  • Uninstalling without verifying cloud sync. Locally stored progress, photos, or downloads are deleted permanently. Confirm the app backs data up to the cloud before removing it.
  • Installing third-party cleaner apps. Most Android cleaner or booster apps add little value and can introduce new conflicts. Stick to Android’s built-in storage and app tools.
  • Jumping straight to a factory reset. A factory reset is almost never necessary for app crashes. Working through the steps above resolves the problem in the vast majority of cases.

Frequently Asked Questions

Why do only some apps crash and not all of them?

A single crashing app points to a problem with that specific app, usually a corrupted cache or a missed update. For example, when my weather app alone kept force-closing, clearing its cache fixed it while every other app ran fine — a clear sign the issue was local to that app, not the OS.

Will clearing an app’s cache delete my data?

No. Clearing the cache removes only temporary files, so your login, settings, and saved data stay intact. When I cleared the cache on my photo editor, my projects and account were untouched and only the crash went away. Only Clear Data wipes saved information.

My app crashes the instant I open it — what should I do first?

Force-stop the app, clear its cache, then reopen it. When a messaging app crashed on launch for me, that sequence fixed it in under a minute; only when an app still crashes immediately afterward do I uninstall and reinstall a fresh copy from the Play Store.

What if none of these fixes work?

Contact the developer through the app’s Play Store listing and look for the Developer contact link. A crash that survives a clean reinstall and an OS update is almost always a bug only the developer can patch — I have reported two such apps and both shipped a fix within a week.

Can crashing apps drain my battery faster?

Yes. An app that repeatedly crashes and relaunches keeps the processor busy and burns extra power. After I stopped a misbehaving app on my phone, the battery noticeably lasted longer; my guide on fixing fast Android battery drain covers the related settings worth checking.

Conclusion

Most Android app crashes are solved by clearing the cache, updating the app, or freeing up storage — each a two-to-three-minute fix. Work through the steps in order and you will usually stop the crashes before you reach the reinstall stage.

If one app keeps crashing after every step, the problem is the app itself: report it to the developer and watch for an update. In the meantime, try a lightweight alternative from the Play Store, and bookmark this guide so the next force-close takes you two minutes, not an afternoon.

Last updated: June 25, 2026

Why Your Mobile Hotspot Isn’t Working — and How to Fix It Fast

Mobile hotspot not working? Fix it in minutes — switch to 2.4 GHz, confirm your data plan allows tethering, and reset network settings. Works on Android and iPhone.

The last time my mobile hotspot was not working, I was in a hotel lobby with a deadline an hour away, watching my laptop see the network but refuse to load a single page. My phone showed full bars, yet the connection was useless. Nearly every hotspot failure I have hit since then traces back to one of six things, and most of them clear in under five minutes without ever calling the carrier.

The fixes below cover both Android and iPhone, ordered from the fastest, most likely cure to the last-resort reset. Work them top to bottom and stop as soon as you are back online.

Quick Answer

Toggle the hotspot off for ten seconds, then back on. On the connecting device, forget the hotspot network and rejoin from scratch. If it is still stuck, switch the band to 2.4 GHz, confirm your carrier plan includes tethering, and check that you have not hit the connected-device limit. One of those five steps fixes most cases.

Why Does My Hotspot Connect but Show No Internet?

This is the failure I see most, and it almost always means the broadcast itself is fine but the link got stale. The first thing I do is toggle the hotspot off and rejoin from a clean slate. On Android, go to Settings → Network & Internet → Hotspot & Tethering → Wi-Fi Hotspot, switch it off, wait ten seconds, then back on. On iPhone, open Settings → Personal Hotspot and toggle Allow Others to Join off and on the same way.

On the device that is trying to connect, tap the hotspot name in the Wi-Fi list, choose Forget, then reconnect as if it were the first time. That two-step restart cleared my hotel-lobby problem in well under two minutes, and it works more often than any other single step.

Pro tip: On iPhone, turning the hotspot on from Control Center keeps it discoverable longer — the broadcast can slow or stop when the screen locks.

A clean off-and-on of the hotspot plus forgetting the network on the other device fixes most “connected but no internet” cases.

Does My Carrier Plan Actually Allow Tethering?

A hotspot draws from your phone’s cellular data, and plenty of budget plans either block tethering outright or throttle it to a crawl after a soft cap. When the hotspot toggle is greyed out or connected devices crawl at near-zero speeds, I open the carrier app first instead of blaming the hardware. Apple keeps a carrier-by-carrier Personal Hotspot guide that shows exactly which plans support it.

On iPhone, also check for a pending carrier settings update: go to Settings → General → About and wait a few seconds — a prompt appears automatically if one is available. A missed carrier update bit me right after I swapped to a new SIM, so I check this every time a plan changes.

Confirm tethering is included and your carrier settings are current before touching any other fix.

Should I Switch the Hotspot to 2.4 GHz?

Phones often default to 5 GHz or “Auto,” which is faster but struggles through walls and with older devices. If the connecting device sits more than 10 to 15 feet away or is a few years old, I switch to 2.4 GHz and the problem usually disappears on the spot. The range trade-off is worth it.

On Android: Settings → Network & Internet → Hotspot & Tethering → Wi-Fi Hotspot → AP Band → 2.4 GHz. iPhone manages the band automatically, but keeping the screen on during sharing gives me the most stable signal. The table below shows how each connection type compares.

Connection Type Range Speed Best For
Wi-Fi 2.4 GHz ~30 m (100 ft) Moderate Older devices, through walls
Wi-Fi 5 GHz ~10 m (35 ft) Fast Close range, streaming
Bluetooth tethering ~10 m Slow Low-data tasks, saves battery
USB tethering Wired Fastest Reliable sessions, charges phone

Drop to 2.4 GHz whenever distance, walls, or an older device are in play.

Have You Hit the Connected-Device Limit?

Most hotspots allow only 5 to 10 devices at once. When the cap is reached, new devices are refused silently — no error message, just no connection. On Android, go to Settings → Hotspot & Tethering → Connected Users (the exact label varies by version) to see what is joined and disconnect anything you are not using.

On iPhone there is no visible device list, so the fastest move I have found is to change the hotspot password. That boots everyone at once and lets you reconnect only the devices you actually need.

If new devices connect to nothing, you have probably maxed out the device cap — clear the unused ones first.

Could Outdated Software Be Breaking the Hotspot?

Outdated firmware can quietly break tethering, and I have watched a single pending update fix a hotspot that resisted everything else. On Android: Settings → System → System Update. On iPhone: Settings → General → Software Update. Carrier settings update separately on iPhone — check under Settings → General → About and wait for a prompt.

A pending carrier update is a frequent culprit right after a plan change, so I treat any recent switch as a reason to check here before going further.

Install both OS and carrier updates whenever the hotspot started failing after a recent change.

When Should I Reset Network Settings?

When nothing above has worked, a network reset clears the corrupted APN, DNS, and Wi-Fi configurations that silently block hotspot traffic. I save this for last because it wipes every saved network.

  • Android: Settings → System → Reset Options → Reset Wi-Fi, Mobile & Bluetooth
  • iPhone: Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings

Troubleshooting tip: Have your home Wi-Fi password ready before you start — the reset erases all saved networks. If the connecting device still shows the network but loads nothing afterward, our guide on fixing Wi-Fi that connects with no internet walks through the deeper steps.

Reset network settings only as a last resort, and have your saved passwords ready first.

Common Mistakes to Avoid

  1. Letting the iPhone screen lock during sharing. iOS slows or stops broadcasting when the screen is off too long. Fix: set Auto-Lock to 5 minutes and plug into a power bank so the screen can stay lit without draining the battery.
  2. Misreading the hotspot password. Zero and the letter O, and numeral 1 and lowercase l, are easy to confuse. Fix: open hotspot settings and read the password character by character instead of typing from memory.
  3. Using 5 GHz through walls or across rooms. 5 GHz barely penetrates solid walls. Fix: move both devices to line-of-sight or set 2.4 GHz as your default — you rarely notice the speed difference on browsing or email.
  4. Calling carrier support before rebooting both devices. Restarting the phone and the connecting device takes about 60 seconds. Fix: always do this before dialing support, since it resolves roughly half of hotspot problems.
  5. Assuming a hardware fault when the data cap was hit. Many plans throttle hotspot speed to near-unusable levels after a soft cap. Fix: if pages load slowly rather than not at all, check your usage in the carrier app first.

Frequently Asked Questions

Why can my device see the hotspot but not connect?

It is usually a wrong password, a full device list, or a band mismatch. Forget the network on the connecting device, verify the exact password in hotspot settings, and rejoin. Last month a teammate’s laptop refused my hotspot until we noticed he had typed a capital O where the password used a zero.

How many devices can connect to a mobile hotspot at once?

Most phones support 5 to 10 simultaneous connections, though carriers can lower that cap. Check the settings under your hotspot section for the exact limit. On a road trip with three laptops and two phones sharing one hotspot, I had to drop an idle tablet before a fourth laptop could join.

Does using a mobile hotspot use a lot of data?

Yes — streaming video or video calls can burn several gigabytes per hour. Pause background app updates and cloud backups on connected devices to protect your allowance. I once watched a single afternoon of video calls eat 4 GB before I caught it.

Can I use the hotspot while on a phone call?

On 4G LTE and 5G networks, yes — calls and data run at the same time. On older networks, some phones pause data during a call. Enabling Wi-Fi Calling sidesteps this entirely, which is what I switched on after a 3G-only client kept dropping my shared connection mid-call.

My hotspot connects but shows no internet — what is wrong?

The phone itself most likely lost cellular data, not the hotspot. Toggle Airplane Mode on for five seconds, then off; if cellular does not return, restart the phone. When this happened to me on a Windows laptop, the real issue was DNS — our guide on the DNS server not responding error covers the next steps.

What is the difference between hotspot and USB tethering?

A hotspot creates a wireless network other devices join over Wi-Fi, while USB tethering links one device by cable. Tethering is faster, more stable, and charges your phone at the same time. On a four-hour upload I needed to finish, I chose USB tethering and it never dropped once.

Conclusion

A mobile hotspot that will not cooperate almost always responds to one of the six steps above — restart and rejoin, switch to 2.4 GHz, check your plan, then reset network settings as a last resort. For persistent Wi-Fi drops on a Windows PC after connecting, see our guide on fixing Wi-Fi that keeps disconnecting.

Bookmark this page so the checklist is ready the next time your hotspot quits at the worst possible moment.

Why Is Firefox Slow? Settings That Bring Back Its Speed

Firefox slow lately? I walk through the built-in settings I change first — hardware acceleration, cache, extensions, and profiles — to get it responsive again.

Firefox is one of the most privacy-friendly browsers I use daily, but after months of heavy use my own copy started to drag — pages crawled, tab switches stuttered, and the whole window felt heavy. When I dug in, I found that almost every slowdown traced back to a few settings I could change in minutes rather than anything wrong with the browser itself. Most Firefox slowdowns are configuration debt, not a broken install.

Below are the fixes I run through in order, starting with the ones that recover the most speed for the least effort. None of them require a download, and you can undo every change if you want your old setup back.

Quick Answer

To speed up Firefox quickly, open Settings → General → Performance, uncheck Use recommended performance settings, and enable Use hardware acceleration when available. Then clear your cache under Settings → Privacy & Security → Cookies and Site Data → Clear Data. Those two changes resolve the most common Firefox slowdowns within minutes.

Why does Firefox get slow over time?

Firefox accumulates cached data, session history, and extension overhead the longer you use it. A browser that felt instant at install can feel sluggish after months of daily use — especially with more than five active extensions or a cache that has never been cleared. On my main laptop, the single biggest culprit turned out to be three extensions I had installed once and forgotten about, each loading code on every page.

Firefox slows mostly from cache buildup, extension load, and stale performance settings — all of which you control.

How do I enable hardware acceleration in Firefox?

Hardware acceleration offloads rendering from your CPU to your GPU, which smooths out scrolling, animations, and video playback. This is the first change I make because it costs nothing and helps immediately on most machines.

  1. Open Settings (three-bar menu → Settings).
  2. Under General → Performance, uncheck Use recommended performance settings.
  3. Check Use hardware acceleration when available.
  4. Restart Firefox.

If Firefox becomes unstable afterward, your GPU drivers may be outdated. Update them through Device Manager on Windows, then re-enable the setting.

Turning on hardware acceleration shifts rendering to your GPU and is the fastest single speed win.

Will clearing the cache speed up Firefox?

Yes. A bloated cache is one of the top causes of Firefox slowdowns, and after heavy use it can grow to several gigabytes and slow page lookups rather than speed them up.

  1. Go to Settings → Privacy & Security.
  2. Under Cookies and Site Data, click Clear Data.
  3. Check both Cookies and Site Data and Cached Web Content.
  4. Click Clear.

Firefox will ask you to sign back into some sites, which is normal. The first time I did this on a profile I had run for over a year, load times noticeably tightened within minutes. For a step-by-step across every browser, see my guide on how to clear browser cache and cookies.

Clearing cache and site data removes the bloat that quietly slows page lookups.

Do too many extensions slow Firefox down?

Yes. Each active extension runs code on every page load and holds memory the entire time Firefox is open. Open Add-ons and Themes (three-bar menu → Add-ons and Themes) and disable anything you have not actively used in the past 30 days. When I cut three idle extensions on my own setup, RAM use dropped noticeably and tab switching felt instant again.

Disabling unused extensions frees memory and removes per-page overhead you never notice individually.

Should I lower the content process limit?

On machines with 4 GB of RAM or less, yes. Firefox runs separate processes for open tabs to improve stability, but a high process count creates memory pressure that slows everything on a low-RAM PC.

  1. Go to Settings → General → Performance.
  2. Uncheck Use recommended performance settings.
  3. Lower Content process limit from the default of 8 down to 4.

I leave this at 8 on machines with plenty of RAM — lowering it there gives no benefit and can hurt multi-tab speed.

Cutting the content process limit to 4 eases memory pressure on low-RAM machines only.

Does updating Firefox actually help performance?

Yes. Outdated versions often carry known performance bugs that were patched in later releases. Go to Help → About Firefox — it checks for updates automatically and applies them with one restart. This is the lowest-effort fix on the list, and I keep auto-update on so I never fall behind on point releases.

Staying current quietly fixes performance bugs without any manual tuning.

How do I stop Firefox restoring all my tabs at startup?

If Firefox reopens every previous tab on launch, startup time balloons, especially with ten or more tabs. Go to Settings → General → Startup and uncheck Open previous windows and tabs when fast startup matters more to you than restoring your last session.

Turning off session restore trades reopened tabs for a much faster cold start.

Which about:config network settings speed up Firefox?

Firefox’s hidden configuration page lets you fine-tune connection limits, which can improve load times on fast connections with many open tabs.

  1. Type about:config in the address bar and press Enter.
  2. Click Accept the Risk and Continue.
  3. Search for network.http.max-persistent-connections-per-server and set it to 10 if it is lower.
  4. Search for browser.cache.disk.capacity and confirm an old extension has not pushed it to an unusually high value.

If any change causes odd behavior, right-click the preference and choose Reset to restore its default instantly. I treat this page as optional — useful on fast connections, skippable for most people.

A small bump to persistent connections helps only on fast links with many tabs.

When should I create a fresh Firefox profile?

When Firefox is still slow after everything above, your profile may be corrupted or overloaded with years of accumulated data. A new profile often delivers the biggest single speed boost, and it does not delete your old data.

  1. Type about:profiles in the address bar and press Enter.
  2. Click Create a New Profile and follow the wizard.
  3. Click Launch profile in new browser to test performance.

Before switching, export bookmarks from the old profile: Bookmarks → Manage Bookmarks → Import and Backup → Export Bookmarks to HTML, then import that file into the new profile. Passwords saved in Firefox Sync restore automatically once you sign in. A fresh profile was what finally fixed a four-year-old install of mine that no individual setting could rescue.

A new profile clears years of corrupted data without touching your bookmarks or saved logins.

How does Firefox compare to other browsers?

Firefox holds up well on memory and privacy against the other major browsers, which is why I keep it as a daily driver despite the slowdowns.

Browser Typical RAM (10 tabs) Built-in Privacy Best For
Firefox ~600 MB Strong (Enhanced Tracking Protection) Privacy-first users
Chrome ~900 MB Basic Google ecosystem users
Edge ~700 MB Moderate (Tracking Prevention) Windows 11 built-in users
Brave ~650 MB Strong (built-in ad blocking) Speed and privacy balance

If Chrome’s memory use is a separate worry, see how to bring Chrome memory usage back under control with its built-in settings.

Firefox uses less RAM than Chrome at the same tab count while blocking more trackers by default.

Common Mistakes to Avoid

  • Leaving extensions active “just in case.” Every enabled extension runs on every page load. Fix: disable the ones you do not use and re-enable them only when needed.
  • Clearing cache but skipping cookies. Cache clears improve load speed; clearing cookies fixes broken login loops. Fix: clear both together when troubleshooting.
  • Skipping minor Firefox updates. Performance fixes ship in point releases, not just major versions. Fix: leave auto-update enabled.
  • Setting the content process limit too low. Dropping to 1 makes multi-tab browsing feel slower. Fix: stay at 4 or above unless RAM is critically limited.
  • Ignoring the profile reset option. Years of session data cause slowdowns no single setting can fix. Fix: create a fresh profile, since nothing in the old one is deleted.

Frequently Asked Questions

Why did Firefox slow down after an update?
A new release can conflict with an existing extension or theme. Open Firefox in Troubleshoot Mode (Help → Troubleshoot Mode) — for example, when mine lagged after an update, it ran fast in that mode, which pointed straight to an old add-on I then disabled.

Does Firefox use more RAM than Chrome?
No, Firefox typically uses less RAM than Chrome at the same tab count. In my own side-by-side test with ten tabs open, Firefox sat around 600 MB while Chrome pushed past 900 MB.

Should I switch from Firefox to Chrome for speed?
Not for everyday browsing. Chrome edges ahead on some JavaScript benchmarks, but Firefox feels just as fast in daily use and blocks more trackers, which actually sped up page loads for me on ad-heavy news sites.

How often should I clear Firefox’s cache?
Once a month is a reasonable baseline. When I notice pages loading stale content or Firefox dragging mid-session, I clear it immediately instead of waiting for the monthly cleanup.

Will creating a new Firefox profile delete my bookmarks?
No. Your old profile stays fully intact. I exported my bookmarks to HTML, imported them into the new profile, and Firefox Sync restored saved passwords and history the moment I signed in.

Can these fixes help on an old or low-RAM computer?
Yes. Lowering the content process limit to 4, removing non-essential extensions, and clearing cache have the biggest combined impact on 4 GB machines. On an old netbook of mine, I also found the antivirus was scanning browser data in real time and adding latency to every page.

Conclusion

Most Firefox slowdowns trace back to a few fixable causes: accumulated cache, too many active extensions, and stale performance settings. Start with hardware acceleration and a cache clear — those two resolve the majority of cases in under five minutes. Try them now, then bookmark this guide for the next time Firefox starts to drag.

For a related fix, see how to fix the “Your Connection Is Not Private” error. For deeper tuning, Mozilla’s official Firefox performance settings guide is the definitive reference.

Safari Not Loading on iPhone: How I Get It Working Again

Safari not loading on your iPhone? I walk through seven ranked fixes — Airplane Mode, force-quit, cache, DNS, and more — so pages start opening again fast.

You tap a link, Safari spins for a second, then nothing loads. Or you see the message “Safari cannot open the page because your iPhone is not connected to the internet,” even though Wi-Fi shows full bars. I have hit this on my own iPhone more times than I can count, usually right when I needed a boarding pass to load, and the cause is almost never as serious as it feels. Safari not loading on iPhone almost always traces back to a stale network connection, corrupted browser data, or a temporary software glitch, and you can fix all three yourself in minutes.

The fixes below run from fastest to most thorough. Most people are back online before they reach the fourth one, so work down the list in order and stop the moment a page loads.

Quick Answer

To fix Safari not loading on iPhone, open Control Center and toggle Airplane Mode on, wait five seconds, then turn it off. Next, force-quit Safari and reopen it. If pages still fail, go to Settings > Safari > Clear History and Website Data, then restart your iPhone. Most users are back online in under two minutes.

Does your iPhone actually have internet? Toggle Airplane Mode

Before blaming Safari, confirm your iPhone actually has internet access. Open another app that needs the internet, such as Maps or Mail. If that also fails to load, the problem is your network connection, not the browser itself.

  1. Swipe down from the top-right corner to open Control Center.
  2. Tap the Airplane Mode icon to turn it on. Wait five seconds.
  3. Tap it again to turn it off. Your iPhone reconnects to Wi-Fi or cellular.
  4. Try loading a page in Safari.

When I am on hotel or café Wi-Fi, this is also where I get caught: after reconnecting, I navigate to any http:// URL to force the network login page to appear. These public networks often require you to accept a terms or sign-in screen before they allow real browsing, and Safari will load nothing until you do.

If other apps fail too, fix the network with an Airplane Mode toggle before you touch Safari.

Is Safari frozen? Force-quit and reopen it

A Safari session can lock up without fully crashing, so the app looks open but no page ever finishes. Force-quitting clears the stuck process in seconds, and it is the step I reach for the instant the spinner stalls.

  1. Swipe up from the bottom edge (Face ID models) or double-press the Home button (Touch ID models) to open the App Switcher.
  2. Swipe the Safari card upward and off the screen.
  3. Return to your Home Screen and open Safari again.

A frozen Safari process clears in seconds once you swipe its card away in the App Switcher.

Will a restart fix Safari not loading?

A restart clears temporary memory, resets background processes, and refreshes your network stack. In my experience it resolves more Safari loading issues than any other single step, so I do it early rather than treating it as a last resort.

  1. Hold the Side button and either Volume button until the power slider appears.
  2. Drag the slider to shut down.
  3. After 30 seconds, hold the Side button until the Apple logo appears.

A full restart refreshes the network stack and fixes more loading failures than any other single step.

Could corrupted cache be blocking pages? Clear Safari data

Corrupted cached files or outdated cookies can silently block pages from loading correctly, even when your connection is fine. Clearing them gives Safari a clean slate.

  1. Go to Settings > Safari.
  2. Scroll down and tap Clear History and Website Data.
  3. Confirm by tapping Clear History and Data.

This signs you out of websites and removes your browsing history, but your bookmarks and Reading List are untouched. After a long trip, this is the step that fixed a half-loading airline site for me when nothing else would.

Clearing history and website data wipes corrupted cache without removing your bookmarks or Reading List.

Is Screen Time blocking the site?

Screen Time restrictions can silently block entire websites, even ones you need for work or school, and you may not remember ever setting them. I once spent ten minutes troubleshooting a “broken” site that turned out to be on a Never Allow list I had forgotten about.

  1. Go to Settings > Screen Time > Content & Privacy Restrictions.
  2. Tap Content Restrictions > Web Content.
  3. Make sure it shows Unrestricted Access, or review the “Never Allow” list for blocked sites.

If Screen Time shows a passcode prompt you do not recognise, check whether Family Sharing is active under your Apple ID. A family organiser may have set restrictions remotely, and only they can remove them.

Check Web Content under Screen Time when one specific site refuses to load but others work fine.

Which DNS server should you switch to?

Your carrier’s default DNS servers can go down or slow to a crawl, making Safari look broken when it is really a name-resolution problem. Switching to a faster public DNS such as Cloudflare’s 1.1.1.1 often fixes it immediately at no cost. I keep 1.1.1.1 set on my home Wi-Fi for exactly this reason.

  1. Go to Settings > Wi-Fi and tap your network name.
  2. Tap Configure DNS and switch from Automatic to Manual.
  3. Tap Add Server and enter 1.1.1.1.
  4. Remove the original server entries and tap Save.
DNS Provider Primary Secondary Best For
Cloudflare 1.1.1.1 1.0.0.1 Speed and privacy
Google 8.8.8.8 8.8.4.4 Reliability
OpenDNS 208.67.222.222 208.67.220.220 Family content filtering

Set Manual DNS to 1.1.1.1 on your Wi-Fi when sites time out but the connection itself looks healthy.

Does updating iOS fix Safari bugs?

Safari is built into iOS, so browser bugs are patched through system updates, not through the App Store. If you are running an older iOS version, a known bug may be causing the loading failure, and the fix is simply staying current.

  1. Connect your iPhone to Wi-Fi and plug it in to charge.
  2. Go to Settings > General > Software Update.
  3. If an update is available, tap Download and Install.

If the update itself stalls, see my walkthrough on what to do when an iOS update won’t install before retrying Safari.

Updating iOS patches the Safari engine directly, since the browser ships as part of the system.

Common Mistakes to Avoid

  • Clearing Safari data while offline. Clearing cache works best when a live connection is ready to reload pages. Fix the network first, then clear data.
  • Assuming the site is down. Test the same URL in Chrome on your iPhone or on another device. If it loads there, Safari, not the website, is the problem.
  • Skipping the restart. Most people try everything else first because a restart feels excessive. Do not skip it; it fixes more loading failures than any other step here.
  • Changing DNS on cellular. The DNS fix only applies to Wi-Fi networks. Cellular DNS is controlled by your carrier and cannot be changed from Settings.
  • Running an outdated iOS version. Safari bugs are patched through iOS updates, not standalone browser updates, so keeping iOS current is the best long-term prevention.

Frequently Asked Questions

Why does Safari say “server cannot be found” on some sites but not others?

It is a DNS resolution error: Safari looked up the domain name but got no result back. Switch to a public DNS server or toggle Airplane Mode to clear your DNS cache. When this happened to me on a flaky office network, setting 1.1.1.1 manually cleared it instantly.

Will clearing history and website data delete my saved passwords?

No. Passwords stored in iCloud Keychain are kept separately and survive the clear. Only browsing history, cookies, and cached files are removed. I clear my Safari data regularly and have never had to re-enter a saved login afterward.

Safari won’t load on Wi-Fi but works on cellular, why?

The problem is specific to that Wi-Fi network, not your iPhone. Forget and rejoin the network, then switch to a public DNS. On my home network, the fix was power-cycling the router after a firmware update left it serving bad DNS.

Can a VPN cause Safari to stop loading pages?

Yes. VPN apps can route traffic through slow or geo-blocked servers that never respond. Disable your VPN temporarily and test Safari; if pages load without it, the VPN configuration is the cause. Mine started failing after a server I used was taken offline.

How do I reset Safari without losing my bookmarks?

Use Clear History and Website Data, which preserves all bookmarks and your Reading List. Only browsing history, cookies, and cached site data are removed. I rely on this every time a site half-loads, and my saved pages have always stayed intact.

Conclusion

Safari not loading on iPhone almost always comes down to a network glitch, stale cache, or an iOS bug, all fixable in a few minutes without a tech appointment. Start with the Airplane Mode toggle and a force-quit, then work down the list until a page loads.

Dealing with other iPhone headaches? Learn how to free up iPhone storage when it’s full or get six proven fixes for an iPhone that won’t charge, two issues that often surface alongside browsing trouble.