{"id":14528,"date":"2026-09-24T10:32:07","date_gmt":"2026-09-24T10:32:07","guid":{"rendered":"https:\/\/playgama.com\/blog\/?p=14528"},"modified":"2026-09-24T10:32:07","modified_gmt":"2026-09-24T10:32:07","slug":"what-networking-protocols-are-supported-in-godot-4-web-expor","status":"publish","type":"post","link":"https:\/\/playgama.com\/blog\/business-faqs\/what-networking-protocols-are-supported-in-godot-4-web-expor\/","title":{"rendered":"What networking protocols are supported in Godot 4 web exports?"},"content":{"rendered":"

Godot 4 web exports are limited to what browsers allow: HTTP\/HTTPS requests and WebSocket connections work normally. Raw TCP and UDP sockets do not work in the browser, so Godot’s low-level networking classes that depend on them are unavailable; multiplayer must go through WebSocket or WebRTC’s data channel instead.<\/strong><\/p>\n

At a glance<\/h2>\n\n\n\n\n\n\n\n
Fact<\/th>\nValue<\/th>\nSource<\/th>\n<\/tr>\n<\/thead>\n
Browser sandbox blocks raw sockets<\/td>\nTCP\/UDP unavailable<\/td>\ndocs.godotengine.org<\/a><\/td>\n<\/tr>\n
Working transport in web exports<\/td>\nHTTP and WebSocket<\/td>\ndeveloper.mozilla.org<\/a><\/td>\n<\/tr>\n
Godot 4 web threading model<\/td>\ndifferent from native<\/td>\ndocs.godotengine.org<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Godot 4 web exports can only use the networking a browser actually allows: HTTP\/HTTPS for regular requests (HTTPRequest node works fine) and WebSocket for persistent two-way connections. Godot’s StreamPeerTCP<\/code>, PacketPeerUDP<\/code> and the high-level multiplayer API built on raw ENet\/UDP do not work in a web export, because browsers do not expose raw TCP or UDP sockets to page scripts. For real-time multiplayer in a web build you need a server that speaks WebSocket, or you route through WebRTC’s data channel, which itself needs a signaling step over HTTP or WebSocket to set up.<\/p>\n

If your game also needs to talk to a non-networking browser API – ads, storage, platform login – that goes through JavaScriptBridge<\/code>, Godot 4’s singleton for calling browser JavaScript from GDScript, replacing the old JavaScript<\/code> singleton from Godot 3. This is the same pattern Unity WebGL uses with its .jslib plugin: the engine can’t reach the browser’s native APIs directly, so it calls out to JS. A practical shortcut here is Playgama Bridge<\/a>, which ships a Godot 3 and 4 plugin and wraps ads, storage and platform calls behind one API instead of writing JavaScriptBridge calls by hand for each platform.<\/p>\n

What should I check before shipping multiplayer on a Godot 4 web build?<\/h2>\n