“Your Connection Is Not Private” Error: How to Fix It on Any Browser

Seeing “Your connection is not private”? Fix it in Chrome, Edge, Firefox, or Safari with six ranked steps — clock, cache, VPN, DNS — and get browsing again today.

The “Your connection is not private” error throws up a full-screen red warning and refuses to load the page you wanted. It looks alarming, but it almost always means your browser spotted a mismatch with the site’s SSL/TLS certificate — and the cause usually sits on your own device, not the website. The single most common trigger I run into is a system clock that drifted by a few hours.

I have cleared this error on dozens of laptops and phones, and the same short checklist fixes nearly all of them. The steps below work in Chrome, Edge, Firefox, and Safari across Windows, Mac, Android, and iPhone, ranked from quickest to most involved.

Quick Answer

Check your device’s date and time first, because a wrong clock causes this error more than anything else. If the clock is correct, clear your browser’s cache and cookies, then load the site in incognito mode. Still blocked? Disable your VPN or antivirus HTTPS scanning and retry. Most cases clear within two minutes.

What do the error codes actually mean?

Chrome and Edge print a sub-code beneath the main warning, and reading it points you straight to the right fix instead of guessing.

Error Code What It Means Best Starting Fix
NET::ERR_CERT_DATE_INVALID Device clock is wrong, or the site’s cert expired Fix 1 — correct date/time
NET::ERR_CERT_AUTHORITY_INVALID Certificate issuer not trusted by your browser Fix 4 — check antivirus HTTPS scanning
NET::ERR_CERT_COMMON_NAME_INVALID Domain name doesn’t match the certificate Try the www. or non-www. version of the URL
NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM Site uses outdated encryption Fix 6 — update your browser

Reading the sub-code first tells you which fix to try before you touch anything.

How do I fix the error step by step?

Work through these six fixes in order. I almost always solve it by Fix 3, but the later steps catch the stubborn cases.

Fix 1: Correct your device’s date and time

SSL certificates have a strict validity window. If your clock is wrong, even by a few hours, browsers reject perfectly valid certificates because they look expired or “not yet valid.”

  1. Windows: Right-click the taskbar clock → Adjust date/time → toggle Set time automatically off, then back on.
  2. Mac: Apple menu → System Settings → General → Date & Time → enable Set date and time automatically.
  3. iPhone: Settings → General → Date & Time → enable Set Automatically.
  4. Android: Settings → General Management → Date and Time → enable Automatic date and time.
  5. Reload the page after the clock syncs.

Pro tip: If your Windows PC keeps resetting to the wrong time after every reboot, the CMOS battery on the motherboard is likely dead — a common failure on machines more than five or six years old. I have swapped a couple of these myself, and the part costs only a few dollars.

Fix 2: Clear your browser’s cache and cookies

Stale cached certificate data can clash with an updated cert on the server. Clearing it forces a fresh TLS handshake.

  1. Press Ctrl+Shift+Del on Windows or Cmd+Shift+Del on Mac (works in Chrome, Edge, and Firefox).
  2. Set the time range to All time.
  3. Check Cached images and files and Cookies and other site data.
  4. Click Clear data, then reload the page.

Fix 3: Open an incognito or private window

Browser extensions — especially ad blockers, VPN add-ons, and security tools — can interfere with certificate validation. Incognito mode disables most extensions by default.

  1. Press Ctrl+Shift+N in Chrome or Edge, or Ctrl+Shift+P in Firefox.
  2. Navigate to the same URL.
  3. If the page loads, an extension is the culprit. Disable them one at a time at chrome://extensions or Firefox’s about:addons to find which one.

Fix 4: Disable your VPN or antivirus HTTPS scanning

Antivirus programs — including Avast, Kaspersky, ESET, and Bitdefender — intercept HTTPS connections and substitute their own certificate. If their certificate store is outdated, browsers flag every substituted cert as untrusted.

  1. Temporarily disable your VPN and reload the page.
  2. If it still fails, open your antivirus settings and find HTTPS scanning, Web Shield, or SSL filtering, then turn it off.
  3. If the page loads, update your antivirus to the latest version before re-enabling HTTPS scanning.

Troubleshooting tip: On corporate or school networks, a firewall or proxy may perform the same SSL interception. If you are on managed Wi-Fi and the error appears on every HTTPS site, contact your IT department — this is expected behavior and only they can resolve it.

Fix 5: Flush your DNS cache

A stale DNS record can route your browser to an outdated server IP, where the certificate no longer matches the domain. Flushing DNS forces a fresh lookup.

  1. Windows: Open Command Prompt as Administrator and run: ipconfig /flushdns
  2. Mac: Open Terminal and run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  3. Reload the page after the command completes.

Fix 6: Update your browser

Browser updates ship with new root certificates. An outdated browser may not recognize certificates signed by newer or recently added certificate authorities.

  1. Chrome: Three-dot menu → Help → About Google Chrome — it checks and installs updates automatically.
  2. Edge: Three-dot menu → Help and feedback → About Microsoft Edge.
  3. Firefox: Hamburger menu → Help → About Firefox.
  4. Restart the browser after updating, then retry the page.

Run the fixes top to bottom and you will clear the error before reaching the end in nearly every case.

Why does this error mean my device, not the site?

The certificate check happens locally, so a wrong clock, stale cache, or intercepting antivirus on your machine breaks the validation before the site is ever to blame. That is why the same page often loads fine on a phone right next to a laptop showing the error.

If your pages still misbehave after the certificate clears, a deeper cleanup helps. My guide on how to clear browser cache and cookies walks through every browser, and if the browser itself feels unstable, see how to stop Chrome from crashing. For the underlying mechanics, Let’s Encrypt’s documentation explains how TLS certificates are issued and validated.

The validation runs on your hardware, which is why local fixes resolve it far more often than anything on the server.

Common Mistakes to Avoid

  • Clicking “Advanced” and proceeding on unfamiliar sites. The bypass is meant for developers testing local servers. On a login, banking, or shopping page it exposes your credentials to interception. Fix: only proceed on sites you personally manage.
  • Clearing the cache with a short time range. Choosing “Last hour” or “Last 7 days” often leaves old cached certificates in place. Fix: always select All time.
  • Assuming the website is broken before checking your device. The common triggers — wrong clock, cached data, antivirus interference — are all local. Fix: rule them out before blaming the site.
  • Permanently disabling antivirus HTTPS scanning. Leaving it off removes real protection. Fix: turn it off only long enough to confirm the cause, then re-enable it or update the antivirus.
  • Dismissing the warning on public Wi-Fi. On open networks a persistent warning can signal a genuine man-in-the-middle attack. Fix: do not proceed on public Wi-Fi without a trusted VPN active.

Frequently Asked Questions

Is this error the same in Chrome, Firefox, and Edge?

Yes, it is the same underlying TLS certificate problem in all of them. Chrome and Edge say “Your connection is not private,” while Firefox says “Your connection is not secure.” Last week I hit the identical issue on the same site in both Chrome and Firefox after my laptop clock drifted, and one date fix cleared both.

Does this error mean I have been hacked?

Almost never — the vast majority of cases trace back to a local issue like a wrong clock, stale cache, or antivirus interference. A real man-in-the-middle attack would typically show NET::ERR_CERT_AUTHORITY_INVALID on a site that normally loads cleanly, which is rare on home Wi-Fi.

Can the website owner cause this error for all visitors?

Yes, an expired, misconfigured, or revoked certificate blocks every visitor until the owner renews or corrects it. I once watched a small store’s site go dark for an afternoon when its certificate lapsed, and nothing on my end could load it until they renewed.

Is it ever safe to click “Proceed to site (unsafe)”?

Only on sites you personally manage for local development or testing. For example, I bypass it on my own localhost dev server, but never on any page asking for a password, payment details, or personal information.

Why does the error appear in Firefox but not Chrome?

Firefox keeps its own certificate store, while Chrome and Edge use the Windows or macOS system store. An antivirus certificate injected into the OS store may not be trusted by Firefox, so I have seen the warning show up only in Firefox on the same machine.

Conclusion

This error is fixable in minutes without specialist knowledge: start with the clock, clear the cache, test in incognito, then work through the rest in order. If all six fixes fail, the problem is server-side and only the site owner can correct it. Next, tame your browser’s resource use with my guide to cutting Chrome’s RAM usage.

Last updated: June 25, 2026

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.

Free AI Chatbot Comparison: ChatGPT vs Gemini vs Claude

A practical free AI chatbot comparison of ChatGPT, Gemini, and Claude. Match each to writing, research, coding, or long docs and pick the right one fast.

Picking a free AI chatbot gets confusing fast, because ChatGPT, Google Gemini, and Claude all promise to answer questions, write emails, and summarize documents in seconds. After running the same tasks through all three for months, I landed on one takeaway: each tool wins a different job, so the smart move is matching the chatbot to the task instead of picking a favorite brand.

The gap only shows when you push past simple requests — asking Gemini for today’s headlines, handing Claude a 20-page report, or asking ChatGPT to debug a script. Below is how I actually split the work between them.

Quick Answer

ChatGPT is the most versatile all-rounder and the best starting point for most people. Gemini taps live Google Search, so it wins for current events and research. Claude handles long documents and careful writing better than the other two. All three are genuinely free — choose by task, not brand loyalty.

Bottom line: ChatGPT for general use, Gemini for live research, Claude for long documents.

What Does Each Free AI Chatbot Do Best?

Each chatbot has a clear sweet spot once you use them side by side. Here is how I’d describe each one after daily use.

ChatGPT (OpenAI)

ChatGPT launched the mainstream AI era and is still the one I open first. The free tier, powered by GPT-4o mini, handles writing, Q&A, coding, brainstorming, and translation with ease. You sign up free at chatgpt.com with an email address or Google account.

  • Best for: Writing, code, quick explanations, creative tasks
  • Free limit: Unlimited chats; the stronger GPT-4o model is rate-limited on free plans

The trick I rely on is opening with a role and a goal, like “You are a plain-English editor; rewrite this for a non-technical reader.” That one framing shift sharpened my results more than any other tweak. If you want this baked in permanently, our guide to ChatGPT custom instructions shows how to set it once.

ChatGPT is my default for general writing, code, and quick explanations.

Google Gemini

Gemini’s biggest free edge is live internet access. Unlike the other two on their free tiers, it pulls real-time search results, which makes it my pick for current news, prices, or anything that changes by the hour. It also plugs directly into Gmail, Google Docs, and Drive.

  • Best for: Current events, research, Google Workspace tasks
  • Free limit: Generous on the web; Gemini Advanced (paid) unlocks deeper app integrations

There is more under the hood than most people realize — I found several useful tools buried in the menus, which I cover in our roundup of Google Gemini hidden features.

Gemini is the one I reach for whenever an answer depends on fresh, live information.

Claude (Anthropic)

Claude, built by Anthropic, is my specialist for long documents. I paste in a contract, research paper, or sprawling email thread and ask it to extract key points, flag inconsistencies, or rewrite a section — it holds the thread across large inputs without drifting. It also reasons through nuanced questions more carefully than the other two in my testing.

  • Best for: Summarizing long documents, careful editing, nuanced analysis
  • Free limit: Daily message cap that resets each day

The daily cap is the main thing to plan around; our breakdown of the Claude AI free plan explains what you get and how to stretch each session.

Claude is the tool I trust most with dense, lengthy text and detailed editing.

How Do the Three Free Chatbots Compare Side by Side?

When three tools cover overlapping ground, a quick table makes the trade-offs obvious at a glance.

Feature ChatGPT (free) Gemini (free) Claude (free)
Real-time web access Limited Yes No
Long document handling Good Good Excellent
Coding assistance Excellent Good Good
Google app integration No Yes No
Mobile app available Yes Yes Yes

No single chatbot wins every row, which is exactly why I keep all three open.

Which Chatbot Should I Use for My Task?

Here is how I route each kind of job to the right tool.

Writing and creative work

Both ChatGPT and Claude shine here. I use ChatGPT for short, punchy content because it is faster, and Claude for longer, polished pieces like reports or cover letters where its more deliberate prose pays off.

Research and current information

Gemini, every time. It is the only free option with live web access, so it stays reliable for time-sensitive questions about news, events, or prices.

Coding and technical help

ChatGPT is my strongest free choice for writing, debugging, and explaining code across Python, JavaScript, SQL, and most common languages.

Reading and summarizing long texts

Claude takes the longest inputs of the three. When I have a dense report or contract to work through, it is the first tool I open.

Match the task to the tool and you sidestep most of the frustration people blame on AI.

Common Mistakes to Avoid

These are the slip-ups I see most often, plus the fix for each.

  1. Trusting every answer at face value. All three can state wrong facts confidently — a flaw called “hallucination.” The fix: verify anything important against a primary source, and our guide on how to fact-check AI answers shows my process.
  2. Using vague prompts. “Write something about marketing” produces generic mush. The fix: specify format, audience, tone, and length — more context, better output.
  3. Ignoring free plan limits. Slow or cut-off responses usually mean you hit a daily or hourly cap. The fix: switch to another chatbot or wait for the limit to reset.
  4. Pasting sensitive personal data. Never enter passwords, bank numbers, or medical records. The fix: review each service’s privacy settings before sharing anything confidential.
  5. Defaulting to one tool for everything. Each has a different sweet spot. The fix: Gemini for current events, Claude for long documents, ChatGPT for code and general writing.

Most bad AI experiences trace back to one of these five habits, not the tool itself.

Frequently Asked Questions

Is ChatGPT completely free to use?
Yes — the free tier gives unlimited conversations on GPT-4o mini with rate-limited access to the stronger GPT-4o model. For example, I draft and revise emails all day on the free plan and only brush the cap during heavy GPT-4o sessions, where ChatGPT Plus would remove most limits.

Do I need an account to use these AI chatbots?
Yes, all three require a free account. ChatGPT and Claude accept an email address or Google sign-in, while Gemini needs a Google account — when I set Gemini up, my existing Gmail login got me in with zero extra steps.

Which free AI chatbot handles privacy best?
They are close, since each lets you disable conversation history. In my own setup I turned it off in ChatGPT under Settings > Data Controls, in Claude’s Settings menu, and in Gemini through my Google account’s Activity controls, which stops chats from feeding model training.

Can I use ChatGPT, Gemini, or Claude on my phone?
Yes — all three offer free apps for Android and iPhone. I bounce between the Claude app on my phone and the browser on my laptop, and the free-plan limits are identical on both.

What happens when I hit the free usage limit?
The behavior differs by tool. ChatGPT quietly drops me to a less capable model, Claude shows a “daily limit reached” message and invites me back tomorrow, and Gemini rarely throws a visible cap on the standard free web tier.

Which free AI chatbot is best for beginners?
ChatGPT, because it is forgiving with messy prompts and covers the widest range of tasks. When I help someone new to AI, I start them on ChatGPT and only add Gemini or Claude once they hit a job that calls for live search or long documents.

Conclusion

ChatGPT is the safest starting point — versatile, fast, and capable across everyday tasks. Add Gemini when you need live search results, and reach for Claude when long documents or nuanced writing are on the table. Each one is free and takes under a minute to set up, so run a real task through all three this week and let the winning answer decide for you.

Last updated: June 25, 2026

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.