What the sources actually say
HTTP/3 is the version of HTTP that runs over QUIC, which in turn runs over UDP rather than TCP. This matters for Zapret because the official documentation describes desynchronization techniques applied to TCP and UDP flows separately — a browser that moves YouTube traffic from TCP-based HTTP/2 to UDP-based HTTP/3 changes which part of your Zapret configuration is even involved in the connection.
In the Flowseal YouTube thread, Discussion #251, participants reported troubleshooting YouTube by changing HTTP/3 behavior in the browser. The concretely reported path is Firefox: opening about:config and toggling the network.http.http3 preference, then restarting the browser and retesting. Some participants reported that this changed whether YouTube loaded with Zapret active.
One thing the discussion does not support: copying lists of YouTube-related hostnames from old forum posts into your configuration as a universal fix. Hostname-based advice ages quickly — Google changes serving infrastructure, and a list that matched one ISP’s filtering at one point in time may be irrelevant or counterproductive now. Treat any such list as historical context for what the filter was targeting, not as configuration to paste.
Step-by-step diagnostic flow
- With Zapret running, record the exact failure: does the YouTube page fail to load, or does the page load while video playback stalls? The protocol path matters more for one of these than the other.
- In Firefox, open about:config, search for network.http.http3, and toggle the preference. This is the specific community-reported step; in Chromium browsers the analogous control is the Experimental QUIC flag.
- Restart the browser completely — protocol preferences do not reliably apply to already-open connections — and retest YouTube under the same Zapret strategy.
- If disabling HTTP/3 helps, the UDP/QUIC path is implicated in your case. That is diagnostic information: it suggests your ISP filtering and your current strategy interact differently on UDP than on TCP.
- Revert the preference if it changes nothing. A toggle that does not help should not stay changed, because it narrows your protocol options for no benefit.
- Use the result to choose your next step — strategy adjustment or DNS diagnostics — rather than stacking multiple experimental toggles at once.
What is source-backed vs community-reported
- Source-backed (official documentation): Zapret’s desynchronization applies to TCP and UDP flows, so a browser protocol switch changes which configuration is active on a connection.
- Community-reported (Discussion #251): toggling network.http.http3 in Firefox about:config changed YouTube behavior for some participants.
- Not established: any universal HTTP/3 setting, and any hostname list from old posts as current working configuration.
When the reported workaround may not apply
The HTTP/3 toggle only speaks to the protocol path. If your YouTube failure comes from DNS poisoning, an ad-blocking extension, or a strategy that no longer matches your ISP, forcing HTTP/2 changes nothing. Disabling HTTP/3 also means forgoing a newer protocol across every site, which is a real trade-off, and browser updates can change the preference’s name or default. Finally, a hostname list copied from an old thread may simply be stale — verify any such advice against current behavior before trusting it.
It is also worth keeping the scope of the evidence in view. The reports describe Firefox on individual networks, at the time they were written. They do not show that HTTP/3 is generally incompatible with Zapret, and they do not show that disabling it is safe to leave permanent. The honest reading of the thread is narrower: for some users, on some ISPs, forcing the browser off the QUIC path changed the outcome, which made it a useful diagnostic step and, for a while, a workable stopgap.