Hi! When a Mac computer works only after restart, it usually means something is getting “stuck” over time — often after sleep/wake, after long uptime, or after a background app loads. A restart clears temporary state, so it can look like the reboot “fixes everything,” but it’s really a clue about where to look.

I’ll keep this safe: we’ll focus on diagnostics and low-risk checks (no Terminal commands, no deleting files, no aggressive “cleaners”). The goal is to narrow it down to a pattern like sleep issues, login items, Wi-Fi/Bluetooth, low disk space, or a specific app/device conflict.

Quick questions — answer any you can:
1) What exactly “doesn’t work” until you restart: internet, apps, keyboard/trackpad, external monitor, sound, Finder, or the whole Mac freezing?
2) Does it happen after the Mac wakes from sleep, or even if it stays awake?
3) Which macOS version are you on (Ventura / Sonoma / Sequoia), and when did this start?

That’s helpful — your description sounds like a “works after reboot, then gradually degrades” pattern. Two big branches to test (without changing anything):

Branch A: network-related (Wi-Fi/DNS/VPN/proxy). Symptoms: Safari/Mail can’t reach anything, but apps “open.” Restart resets network services and reconnects cleanly.
Branch B: system load or stuck process (memory pressure, runaway background app, cloud sync, login helper). Symptoms: Finder slow, beachballs, apps lag — restart clears the jam temporarily.

Let’s start from symptoms (since that’s clearest): when it happens, can you tell me which of these matches best?
• “No internet” (websites won’t open anywhere), but the Mac is otherwise responsive
• “Everything feels slow” (Finder, switching apps, beachball), plus internet issues
• “Only certain apps break” (example: Safari and Mail, but other apps are fine)

Also: are you using any of these (even occasionally): VPN, ad-blocking DNS apps, antivirus, “cleaner” tools, or corporate work profiles? Those are common culprits for “Mac internet works only after restart.”

The “after sleep” detail is huge. A lot of Mac sleep/wake issues show up exactly like that: the Mac wakes, but a network service, VPN tunnel, or a background helper doesn’t come back cleanly — and then everything feels off until a restart.

Let’s do two safe, observe-only checks next time it happens (no fixing yet, just evidence). This helps avoid guesswork and makes the page Bing-friendly because it’s based on real signals, not generic tips.

Safe check A — Is Wi-Fi still “connected”?
When Safari says pages can’t load, click the Wi-Fi icon: does it still show connected to your network, or does it look connected-but-not-working (still shows bars, but nothing loads)?

Safe check B — Activity Monitor snapshot (this often reveals why the Mac needs restarting):
Open Activity Monitor → look at CPU and Memory. Tell me:
• top 1–3 CPU processes when it’s acting up
• whether Memory Pressure is green/yellow/red

While we’re here: VPN + Google Drive + waking from sleep is a classic “pile-up.” We’re not blaming them — just noting they’re common in “Mac keeps needing to restart” scenarios.

Related (same style, symptom-first): Mac Wi-Fi keeps disconnecting — safe checks and Mac slow after sleep — what to look for.

Great detail. “Wi-Fi connected but nothing loads” + “VPN sometimes helps” points strongly toward a network path issue (DNS, VPN/proxy rules, or a service that didn’t resume after sleep). And seeing kernel_task spike at times can happen when the system is managing heat, drivers, or device wake events — not automatically a disaster, but it’s another clue that sleep/wake is involved.

Here’s a safe way to narrow it down without “doing fixes” yet:

Question set (different order, because your symptoms are network-first):
1) When it breaks, do all browsers fail (Safari and Chrome/Firefox), or mainly Safari?
2) Does Messages/iMessage send, and does App Store load? (This helps distinguish DNS vs general connectivity.)
3) Do you ever see a captive portal / sign-in page on that Wi-Fi (school Wi-Fi often does this after sleep)?

Low-risk check C — Network settings “read only”:
In System Settings → Network → Wi-Fi → Details, look for anything unusual like a configured Proxy or custom DNS. Don’t change anything yet — just tell me if you see it enabled.

Related (helps explain the “connected but no internet” pattern): Mac connected to Wi-Fi but no internet — diagnosis.

If multiple browsers fail, that’s almost never “a Safari problem.” And if Messages sometimes works while web + App Store struggle, DNS is a strong suspect. DNS issues can feel exactly like: “Mac internet works only after restart” — because the reboot refreshes caches, renegotiates network routes, and rebuilds the connection cleanly.

We still won’t change settings here, but we can do two very safe clarifying checks that don’t touch your files or system stability:

Safe check D — Timing and trigger map (this is surprisingly powerful):
For 1 day, note when it breaks and what happened just before: woke from sleep, VPN on/off, Google Drive syncing, switching Wi-Fi networks, plugging in a dock, etc. If the failure happens within minutes of waking, that’s a sleep/wake networking resume clue.

Safe check E — Does switching Wi-Fi off/on recover it?
Next time it breaks, try turning Wi-Fi off for 10 seconds, then back on (no restart). Tell me if that restores browsing. If it does, it supports “network service stuck after sleep.” If it doesn’t, the issue may be DNS/VPN rules persisting until reboot.

Optional diagnostic (still safe): Safe Mode once. Safe Mode loads fewer third-party helpers. If the Mac behaves normally there (especially after waking), that points to login items, VPN helpers, or sync tools — not the Wi-Fi hardware itself.

If you want a focused reference: VPN breaks internet on Mac — what to check and Mac login items causing issues — diagnosis.

I hear you — constant restarts are a symptom, not a lifestyle. The good news is you’ve already produced a strong diagnostic story:

• Issue is often triggered by sleep/wake
• Wi-Fi toggle helps sometimes → network stack is involved
• VPN toggle helps more consistently → VPN/DNS path likely involved
• Restart resets everything reliably → points to a stuck service/config rather than random web issues

Since we’re staying in “safe checks only,” here are the next observations that usually identify the root cause without guessing:

Safe check F — Login items (read-only review)
Open System Settings → General → Login Items and note what’s allowed in the background (VPN helpers, Drive, “menu bar” tools). Don’t remove anything yet — just list them. Conflicts here are common in “Mac works only after reboot” cases.

Safe check G — Storage headroom
Check System Settings → General → Storage. Very low free space can make network and app behavior worse over time (more caching failures, slower wake). You don’t need to clean anything now — we just want to know if storage pressure is part of the picture.

Safe check H — Console clue (optional)
If you’re comfortable, open Console right after the failure and search for “Wi-Fi”, “DNS”, “VPN”, or the VPN app name. We’re not interpreting every line — just looking for repeated errors that appear at the moment it breaks.

If you’d like, tell me: which VPN app is it (exact name), and whether this started after a macOS update (Sonoma/Sequoia updates sometimes change network behavior).

That combination explains a lot: AnyConnect + low-ish free space + sleep/wake trigger. I’m not saying AnyConnect is “wrong” — it’s widely used — but VPN/network extensions can be sensitive to OS updates and sleep/resume. And with only ~12 GB free, the Mac has less breathing room, which can amplify “works after restart” behavior because caches and temporary files get squeezed.

Safe summary (no full solution, just what your evidence points to):
1) This is very likely a network path / VPN + DNS resume issue after sleep, rather than a single browser problem.
2) The fact that Wi-Fi toggle sometimes helps suggests the network stack is “recoverable,” but not always — consistent with an extension/service staying stuck.
3) Low storage is a risk factor that can make the Mac feel progressively worse between restarts.

Best next step as a diagnostic (still safe): try Safe Mode once, then reproduce the problem by sleeping/waking. If it doesn’t happen in Safe Mode, that strengthens the “background helper / VPN extension / login item” theory. If it still happens, we’d focus more on Wi-Fi/DNS configuration and system-level network services.

If you want supporting reading that matches what we’re testing: When to use Safe Mode on Mac — diagnostic use and Mac DNS settings explained — how they affect browsing.