When YouTube Comments Appear in Firefox but Never in Chrome, Start With Restricted Mode

A comment section that loads on a phone and in Firefox but stays empty in Chrome is not a YouTube outage. An outage does not pick one browser on one computer. The split itself is the diagnosis: something that is stored per browser profile is different in Chrome, and there are only a handful of things on that list.

The first one to check takes about thirty seconds and is the single most common answer, because it is a YouTube feature that does exactly this by design. YouTube's own documentation states that Restricted Mode "works on the browser or device level, so you must turn it on for each browser you use," and that "when Restricted Mode is turned on, you can't view comments on the videos you watch." A browser-scoped switch whose documented behaviour is hiding comments matches a browser-scoped symptom of hidden comments. Check it before anything else.

Check Restricted Mode in the browser that fails

On a computer, YouTube documents the path as follows: at the top right, click your profile photo; at the bottom of that menu, click Restricted Mode; in the box that opens at the top right, click Activate Restricted Mode to switch it on or off.

Three details make this worth checking even when it seems improbable.

• It does not travel with the Google account. Turning it off on a phone does nothing to Chrome on a desktop, which is precisely why the symptom looks browser-specific.
• YouTube states that computers "in libraries, universities, and other public institutions may have Restricted Mode turned on by a network administrator." On a managed machine, the control can be locked.
• When Restricted Mode is responsible, comments are hidden across every video, not on one. If comments are missing on one video and present on the next, Restricted Mode is not the cause and the rest of this diagnosis applies.

That last point is the fastest way to split the problem in two, so make it the second thing checked: open two or three unrelated videos from different channels in the failing browser. All blank points at the browser. One blank and the others fine points at the video.

Rule out the video and the account before touching Chrome settings

Three documented conditions turn comments off in a way no browser setting can undo. Each one produces the same blank space Chrome is being blamed for, and each one is worth eliminating before any setting is changed.

The video is marked made for kids

YouTube publishes a list of "features not available on made for kids watch or playback pages," and Comments is on it, alongside cards and end screens, video watermarks, channel memberships, notifications, the Miniplayer, Super Chat, and Save to playlist. Channels marked made for kids also lose comments, posts, memberships, and notifications at the channel level. The audience setting is chosen by the creator, per video or per channel, and there is no viewer-side override.

This one is easy to confirm from the outside: if the same video also lacks the Miniplayer and cannot be saved to Watch Later, the audience setting is the reason, not the browser.

The creator switched comments off or paused them

YouTube gives creators three states for a video's comment section: On, Pause, and Off. With Off, commenting is prevented and viewers are shown a message that comments are disabled; existing comments are hidden on the watch page and in YouTube Studio, and they reappear if comments are switched back on. With Pause, existing comments stay visible but no new ones are accepted.

When comments are On, a separate moderation level applies — None, Basic, Strict, or Hold all — and under Hold all every comment waits for the creator's approval before it publishes. A brand-new upload with a strict setting can therefore show an empty comment section for reasons that have nothing to do with any viewer. Separately, comments caught by a creator's blocked-words list are held for review for up to 60 days.

The signed-in account is supervised

For supervised accounts, the content setting decides comment access. YouTube documents that on Explore more and Most of YouTube, a supervised viewer can read comments but not write them, and that on Explore, comments are turned off. Comments are off entirely on made-for-kids content regardless of setting. If Chrome is signed in to a supervised profile and Firefox is signed out or signed in to a different account, the browser difference is a red herring — the account difference is doing the work.

Use one Incognito window instead of four separate experiments

An Incognito window changes several things at once, which makes it a poor tool for pinpointing a cause but an excellent one for splitting the search space. Chrome documents that extensions cannot be added while browsing in Incognito, and that an extension only runs there if Allow in incognito has been switched on for it in its Details page. Chrome also documents that third-party cookies are blocked by default in Incognito, and that a site exception added inside an Incognito session lasts only for that session, while the equivalent exception added from the address bar in a normal window lasts 90 days.

What that adds up to is a single window in which most extensions are inert and the profile's stored youtube.com data is not in play. So:

• Comments appear in Incognito — the cause is an extension, or the stored site data for youtube.com, or both. Continue below.
• Comments stay blank in Incognito — extensions and stored site data are both ruled out. Move to the per-site permissions and the managed-browser check.

One caveat that matters and is often skipped: an Incognito window is normally signed out. If the comment section depends on the signed-in account — a supervised profile, for instance — the Incognito result reflects the sign-in change, not the extension change. Sign in inside the Incognito window before drawing a conclusion, or accept that the test covers two variables.

Narrow it down inside the Chrome profile

Extensions, one at a time

Chrome documents the path as: at the top right, select More, then Extensions, then Manage extensions. Each entry can be turned on or off there, and each has a Details page containing Allow in incognito.

Turning every extension off and confirming the comment section returns is the cheap first move. The slower and more useful move is to turn them back on one at a time, reloading the watch page after each, until the section disappears again. Content blockers, privacy blockers, and anything that rewrites or restyles YouTube pages are the obvious candidates, but the point of the one-at-a-time pass is that it does not depend on guessing which one.

The stored site data for youtube.com

Chrome documents a per-site delete: Settings → Privacy and security → Third-party cookies → See all site data and permissions, then search for the site, select the delete control beside it, and confirm with Delete. That removes the stored data for youtube.com without clearing every site in the profile, which is the reason to prefer it over a blanket wipe.

A blanket wipe is also documented, at More → Delete browsing data, with the checkboxes Browsing history, Cookies and other site data, and Cached images and files, and a time range that includes Last hour through All time. Chrome states plainly that "if you delete cookies, you may get signed out of sites that remember you," so expect to sign back in afterwards.

Related and less well known: Chrome has a separate on-device site data control at Settings → Privacy and security → Site settings → Additional content settings → On-device site data, with three options — Allow sites to save data on your device, Delete data sites have saved to your device when you close all windows, and Don't allow sites to save data on your device (not recommended). Chrome's own warning on the last of these is that "sites may not work as you expect." A profile set that way, or with a site-level block on youtube.com, is a per-profile difference that would not exist in Firefox.

Per-site permissions, including JavaScript

Chrome documents a per-site settings page reachable without leaving the video: select the View site information icon to the left of the web address, then Site settings, then change the permission; changes save automatically. The permissions Chrome lists as manageable this way include JavaScript, third-party cookies, images, on-device site data, insecure content, and pop-ups and redirects, among others.

Confirm that JavaScript is not blocked for youtube.com specifically. A site-scoped block is easy to set years ago and forget, and it lives in exactly one browser profile.

Whether Chrome is managed

Chrome documents two ways to check: look at the bottom of the More menu for Managed by your organization, or type chrome://management in the address bar. Managed extensions are listed on that page, and chrome://policy lists the applied policies. Chrome states that an administrator of a managed browser can "set up or restrict certain features, install extensions, monitor activity, and control how you use Chrome."

This matters on a work laptop where Chrome is enrolled and Firefox is not. It also joins up with the Restricted Mode point: YouTube documents that public and institutional machines may have Restricted Mode enabled by an administrator, and on such a machine the fix is a request to that administrator rather than a setting change.

Two suggestions that circulate, and what the documentation supports

Hardware acceleration. Chrome does document this setting and its path — More → Settings → System → turn off Use hardware acceleration when available, then restart Chrome — but it documents it as a step for Chrome crashing or failing to open, not as a cause of a missing comment section. Some Chrome builds show a differently worded label in the same place; the string quoted here is the one in Google's current crash-troubleshooting article. It is a legitimate thing to try after the tests above have failed, and it is not a first move.

Blocking third-party cookies. Chrome defines first-party cookies as those "created by the site you visit," where "the site is shown in the address bar," and third-party cookies as those "created by other sites." On a youtube.com watch page, youtube.com cookies are first-party by that definition, so a third-party cookie block is a weak explanation for a blank comment section there. It is a much better fit for a YouTube player embedded on some other domain. Change the setting if the failure happens on an embed; do not change it on the strength of the youtube.com symptom alone.

One more boundary worth stating: no public YouTube or Chrome document explains the internal mechanism by which a comment section fails to render in one browser. Anything claiming to describe that machinery is describing something unpublished. What is documented is the list of switches above, and that list is enough to isolate the cause without guessing at internals.

When This Doesn't Apply

This diagnosis assumes a per-browser split. It stops being the right frame under these conditions.

• Comments are missing in every browser and on the phone. Then the browser is not involved. Look at the video's audience setting, the creator's comment setting, and the signed-in account.
• Only one video is affected. A browser-scoped setting such as Restricted Mode hides comments on everything. One blank video among many normal ones is a video-side setting.
• The browser is out of date. YouTube's stated requirement is the newest version of Chrome, Firefox, or Safari, and it warns that without the most up-to-date version "you may have problems using YouTube's newer features." Internet Explorer is no longer supported at all. Update first, then re-test, or the comparison is not clean.
• The comparison browsers differ by account. Chrome signed in as one user and Firefox signed out is a two-variable test. Match the sign-in state before concluding anything about Chrome.
• The failure is on an embedded player on a third-party site. Embeds and watch pages are different contexts, and third-party cookie rules apply differently to them.
• The page fails to load at all, or errors out. That is a connection or page-loading problem, not a comment-section problem, and it needs a different set of checks.

Working order

1. Open two or three unrelated videos in the failing browser. All blank means browser-side; one blank means video-side.
2. Check Restricted Mode in that browser: profile photo → Restricted Mode → Activate Restricted Mode. Confirm the state rather than assuming it.
3. Open the same video in an Incognito window, signed in to the same account.
4. If Incognito works: disable all extensions at More → Extensions → Manage extensions, confirm the fix, then re-enable one at a time.
5. If extensions are cleared: delete the stored data for youtube.com via Settings → Privacy and security → Third-party cookies → See all site data and permissions.
6. If Incognito also fails: check per-site permissions from the View site information icon, with JavaScript first.
7. Check chrome://management. If the browser is managed, stop and raise it with the administrator.
8. Only then try turning off Use hardware acceleration when available under Settings → System and restarting Chrome.

Steps 1 and 2 resolve the majority of cases in under a minute, and they cost nothing if they do not. The rest of the sequence is ordered so that each step either fixes the problem or removes a candidate — which is the point of running them in order rather than changing five settings and losing track of which one mattered.