diff --git a/WORKING_GROUPS.md b/WORKING_GROUPS.md
index fcf405bc..5c4c58f0 100644
--- a/WORKING_GROUPS.md
+++ b/WORKING_GROUPS.md
@@ -240,6 +240,7 @@ The [Node.js Code of Conduct][] applies to this WG.
 * [Release](#release)
 * [Package Maintenance](#package-maintenance)
 * [Undici](#undici)
+* [Web](#web)
 
 ### [Streams](https://github.com/nodejs/readable-stream)
 
@@ -354,4 +355,42 @@ Responsibilities include:
 * Documenting the undici API, examples, and best practices.
 * Development of Node.js HTTP Client APIs such as a WHATWG Fetch implementation.
 
+### [Web](https://github.com/nodejs/web-team)
+
+The Web Working Group is responsible for the Node.js project's web presence: the
+development, operation, and security of nodejs.org and the infrastructure that
+serves it.
+
+Responsibilities include:
+
+* Technical direction and day-to-day development of the Node.js website and its
+  supporting projects, including `nodejs/nodejs.org`, `nodejs/learn`, and
+  `nodejs/doc-kit`.
+* Operating and maintaining the infrastructure serving the Node.js web presence,
+  including CI/CD pipelines, `nodejs/website-cloudflare-worker`,
+  `nodejs/release-cloudflare-worker`, and `nodejs/discord-status-worker`.
+* Managing access to, and administration of, the third-party services used to run
+  the Node.js web presence, as enumerated in the Working Group's
+  [PERMISSIONS.md](https://github.com/nodejs/web-team/blob/main/PERMISSIONS.md).
+* Responding to availability and security incidents affecting the Node.js web
+  presence, per the Working Group's
+  [incident response plan](https://github.com/nodejs/web-team/blob/main/INCIDENT_RESPONSE_PLAN.md).
+* Maintaining localization tooling and workflows for the Node.js website.
+* Project governance and process for the Working Group, including its own
+  governance, contribution, and permissions policies.
+* Managing the membership of `@nodejs/web` and its subteams, including
+  `@nodejs/nodejs-website`, `@nodejs/web-infra`, and `@nodejs/web-admins`.
+* Overseeing repositories within the Working Group's scope (
+  archiving, removing) and their maintainer teams.
+
+The following remain outside the charter:
+
+* Website changes expressing a position about a global event or group of people,
+  which continue to require TSC approval.
+* Website content governed by the
+  [content vs. code](https://github.com/nodejs/nodejs.org/blob/main/docs/content-vs-code.md)
+  guidance, including OpenJS Foundation requests.
+* Cloudflare, which is owned by the Build Working Group; the Web Working Group
+  holds scoped access only.
+
 [Technical Steering Committee (TSC)]: ./TSC-Charter.md