How to Block Snapchat on a Kid's Chromebook: A Step-by-Step Playbook

Parent question hour at school pickup keeps surfacing the same problem: you blocked Snapchat on the phone, and now the kid is on Snapchat through their Chromebook instead. The fix is not one toggle — ChromeOS handles parental controls through several layers, and Snapchat itself has at least three ways onto the device. This playbook walks through the four blocking layers that actually hold: Family Link site and app rules on a personal Chromebook, a router or DNS backstop, what to do when the Chromebook is school-managed and Family Link refuses to attach, and the phone-side layer that closes the obvious loophole. By the end you will know exactly which entries to add, which boxes to untick, and how to verify the block is working before the next group chat goes live. On Discord, block it across phone, PC, and router takes the same layered approach.

Why Blocking Snapchat on a Chromebook Is Trickier Than It Looks

ChromeOS does not ship with a "Block Snapchat" switch. Blocking happens at three different layers — the supervised Google Account through Family Link, the network through your router or DNS, and the device itself through Chrome and Play Store policies — and you almost always need at least two of those layers working together.

Two early questions decide what you can actually do:

• Is the Chromebook personal or school-managed? If your child signed in with a school-issued @yourdistrict.org account, the school's Google Workspace policies usually outrank anything Family Link tries to apply. Family Link may simply refuse to attach.
• Which Snapchat vectors are open? Snapchat reaches the Chromebook through web.snapchat.com in Chrome, the Snapchat Android app installed from Google Play, and a "stretched" PWA or shelf shortcut that launches outside a normal tab.

Two ChromeOS modes — incognito and guest — can quietly bypass any rule attached to the child's profile. If you do not also turn those off, the block leaks. Finally, Family Link supervision on a Chromebook requires ChromeOS 71 or later, so very old hand-me-down devices may not be able to host a supervised profile at all.

Map Every Way Your Kid Can Reach Snapchat on a Chromebook

Before you block anything, list the doors. A block that only covers one door does not work for long.

The vectors that matter:

• web.snapchat.com in Chrome. The official web client. Loads inside any signed-in Chrome tab if the URL is not blocked.
• The Snapchat Android app from Google Play. ChromeOS runs Android apps natively. If Play Store is open, your kid can install Snapchat in two taps.
• A PWA or "Add to shelf" shortcut. Chrome can install web.snapchat.com as a standalone app that launches outside a tab and sometimes dodges naive site-rule logic.
• Incognito and guest mode. Both can ignore profile-level rules unless explicitly disabled. Guest mode does not require a sign-in at all.
• A secondary, non-supervised Google account. If the kid signs in with a personal Gmail you do not control, Family Link rules attached to the supervised account no longer apply.

Spend five minutes auditing what is already on the device:

1. Open Chrome history and search for "snapchat" — past visits tell you which vectors are in use.
2. Open Settings → Apps → Manage your apps and scan for the Snapchat Android app and any Snapchat-branded PWA.
3. Right-click the shelf icons and remove anything labeled Snapchat or "Snap."
4. Check who is signed in: Settings → Accounts. If you see accounts you do not recognize, that is a vector.

Step 1: Block Snapchat With Family Link on a Personal Chromebook

This is the primary, free, Google-supported method when the Chromebook is yours.

Before you start. Confirm the child is signed in with a supervised Google Account (created through Family Link, not a regular Gmail), and the Chromebook is on ChromeOS 71 or later. Settings → About ChromeOS shows the version.

The walkthrough:

1. Open the Family Link app on your phone and pick your child's profile.
2. Tap Controls → Content restrictions → Google Chrome → Manage sites.
3. Under Blocked, add each of these entries one at a time:
   • snapchat.com
   • web.snapchat.com
   • accounts.snapchat.com
   • *.snapchat.com (if your Family Link version accepts the wildcard)
4. Back on the Chrome screen, switch the filter to either Try to block explicit sites (looser) or Only allow approved sites (strict allowlist). The strict mode is more effective for younger kids but means you will be approving the rest of the open web too.
5. Go back to Controls and open Google Play. Block the Snapchat Android app, set Apps & games to require Approval for all new installs, and revoke approval for Snapchat if it is already installed.
6. Disable guest browsing on the Chromebook itself. On the sign-in screen tap the bottom-right status area → Settings (gear) → Manage other people, then turn Enable Guest browsing off. This requires the device owner account.
7. Restrict incognito mode through the supervised account. Family Link applies Chrome policy that disables incognito on supervised profiles by default, but check Settings → Privacy and security on the child's profile to confirm.
8. Sign the child out and back in. Some Chrome and Play policies only take effect after a fresh login.

Two notes worth flagging now:

• A Chrome extension with proxy or VPN capability can bypass site rules. Family Link blocks extension installs on supervised accounts by default — confirm the child has not been promoted out of supervision.
• The block will hold while the kid is signed into the supervised profile. If they switch accounts, the rules do not follow them. The next two steps add backup layers for exactly that case.

Step 2: Add a Router or DNS Layer So the Block Sticks

Family Link is profile-level. A router or DNS rule is network-level — it does not care which Chrome profile is signed in. Parents on community forums keep landing on this layer for a reason: it is the cheapest insurance against the profile-switch bypass.

Your two options:

• Router-level block by device. Most home routers (Asus, TP-Link, Eero, Netgear Nighthawk, Google Nest WiFi) let you create a "Kids" device group, add the Chromebook by MAC address, and apply a domain blacklist. Add snapchat.com, web.snapchat.com, sc-cdn.net, and snap-dev.net — Snapchat uses the last two for content and CDN traffic, so blocking only snapchat.com is not enough.
• Family-safe DNS. Point either the Chromebook (Settings → Network → your WiFi → Name servers → Custom name servers) or the whole router at a service like CleanBrowsing Family or NextDNS. Both let you add Snapchat domains to a custom blocklist and toggle categories like "Social Media." NextDNS in particular lets you see which device tried to reach which domain — useful for spotting workaround attempts.

If your router supports scheduled rules, set Snapchat to blocked during school hours, homework windows, and bedtime even on devices that are normally allowed. A schedule is more sustainable than an all-day ban when the kid is older.

One honest limitation: a router rule only applies when the Chromebook is on your WiFi. A Chromebook tethered to a phone hotspot, on a neighbor's network, or on a coffee-shop WiFi will skip the rule entirely. That is why Step 4 matters.

Step 3: What to Do If It's a School-Managed Chromebook

Many parents discover the device is school-managed only when Family Link refuses to attach. Signs it is managed:

• A blue or gray "Managed by yourdistrict.org" banner on the sign-in screen.
• You cannot add a personal supervised account because adding accounts is disabled.
• The Chrome menu shows a small briefcase icon next to "Managed."

On a managed Chromebook, the school admin owns Chrome policies, the Play Store, extensions, and most settings. You usually cannot install parental control software, change DNS, or sideload anything.

What you can still do:

• Email the school's IT contact or principal. Ask them to block Snapchat across the managed fleet in the Google Admin console. Send them the exact list: snapchat.com, web.snapchat.com, accounts.snapchat.com, sc-cdn.net, snap-dev.net. Many districts will say yes — Snapchat is already on most acceptable-use blocklists.
• Cover your home network with the router/DNS rules from Step 2. Even if you cannot touch the Chromebook directly, every minute it is on your WiFi it inherits your network filtering.
• Set a "school device stays in shared spaces" rule. Kitchens and living rooms get used; bedrooms get tethered to a phone hotspot. The physical rule does the work the software cannot.
• Be realistic about the rest. If the school's MDM allows the Snapchat app or web.snapchat.com and refuses to change, you are out of options on the device itself. The phone layer in the next step is your remaining lever.

The dedicated Snapchat parental controls guide page covers the phone-side lever that holds when Chromebook MDM cannot be changed.

Step 4: Close the Loophole on Your Kid's Phone With NexSpy

Here is the part most articles skip. The day you lock down the Chromebook is usually the day your kid opens Snapchat on their phone instead. Until the phone is covered, the Chromebook block is theater. NexSpy was built for exactly this hand-off — per-app and per-URL blocking on the child's Android or iPhone with parent approval in the loop.

Block the Snapchat app on the phone, instantly or on a schedule

From the NexSpy Parent Dashboard you can apply a per-app block to Snapchat on the child's Android or iOS phone — either an instant block that takes effect right now, or a scheduled block that activates during school hours, homework windows, and bedtime. The schedule mirrors whatever you already set on the router, so the rules feel consistent to the kid: Snapchat is just off between 3 pm and 9 pm on school nights, on every device they own. A scheduled block holds up better than an all-day ban for older teens, because it is harder to argue with "you can have it after homework."

Close the browser route, not just the app

Kids who lose the Snapchat app on their phone immediately try web.snapchat.com in mobile Chrome or Safari. Add both snapchat.com and web.snapchat.com to NexSpy's custom URL blacklist so the browser route is closed too. Turn on the adult-content website category at the same time — that catches lookalike sites and adjacent search results that route around brand-name blocks. Keep NexSpy's Safe Search enforcement on across Chrome, Edge, Firefox, Opera, Samsung Internet, and Safari, so search engines themselves do not surface a workaround domain the moment you blacklist a known one.

Let your kid ask instead of hunting for a workaround

The cat-and-mouse pattern is exhausting for everyone. NexSpy's request-permission flow lets the child send you a request directly from their phone: "Can I have Snapchat for an hour to plan the group project with Maya?" You approve or deny from the dashboard. Approvals can be one-off or time-bound. Most parents find that once the request flow exists, the kid uses it — because it is faster than hunting for a new PWA, a new VPN extension, or a new alt domain. The block becomes a conversation rather than a wall.

On Android, you also get a browsing history review in the dashboard. Skim it once a week. If new Snapchat-adjacent domains show up — alternate sign-in pages, mirror sites, message-relay services — add them to the blacklist. That weekly five-minute habit is what keeps the whole stack honest as kids try new workarounds. Be honest about the limits too: browsing-history review is Android only, and some app blocks depend on the Android or iOS version and the permissions the child device has granted.

How to Check the Block Is Actually Working

Settings can save without applying. Verify each layer before you walk away.

1. Sign in as the child on the Chromebook and load web.snapchat.com. You should see the Family Link block page, not the Snapchat login.
2. Open the Play Store on the Chromebook and search Snapchat. Install should be blocked or require parent approval.
3. Open an incognito window and try Snapchat again. If incognito loads it, your supervised profile is not enforcing the rule — recheck Family Link Chrome policy. Then try guest mode from the sign-in screen; if guest is available at all, go back to Settings → Manage other people and disable it.
4. From a different device on your home WiFi, try web.snapchat.com. If it loads, the router or DNS rule from Step 2 is not in place yet.
5. On the child's phone, try to open the Snapchat app — it should be blocked. Then try web.snapchat.com in mobile Chrome and Safari — same result. If either route still works, recheck the per-app block and the URL blacklist in NexSpy.
6. Re-check weekly. Kids try alt domains (snap.com, snapchat-web.app-style mirrors), new PWAs, and VPN extensions. The browsing-history review on the NexSpy dashboard is the fastest way to spot new workaround domains before they become a habit.