WebSockets & Realtime Systems Programming · Lesson

Broadcasting Messages to Clients

Learn how to send messages from the server to all connected clients or specific ones.

Broadcasting Messages to Clients is a free WebSockets & Realtime Systems Programming lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the WebSockets & Realtime Systems Programming learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

What is Broadcasting?

Realtime applications often need to send updates to many users at once. Imagine a live sports score or a chat room.

Broadcasting is when your server sends a single message that is delivered to all currently connected clients.

Why Broadcast Messages?

Broadcasting is a fundamental pattern for many interactive applications:

Live Updates: Stock prices, news alerts, sensor data.
Chat Rooms: New messages visible to all participants.
Notifications: System-wide alerts to all active users.
Multiplayer Games: Player movements, game state changes for all players.

Server's Client List

To broadcast, your WebSocket server needs to know who's connected. The ws library (our Node.js WebSocket server library) automatically keeps track of all active connections.

When a client connects, its WebSocket object is added to an internal list. When it disconnects, it's removed.

Accessing Connected Clients

The ws library exposes the wss.clients property. This is a JavaScript Set containing all currently connected WebSocket client objects.

We can iterate over this Set to send messages to each individual client.

Implementing Full Broadcast

Here's how to modify your server to broadcast any message it receives to all connected clients:

const WebSocket = require('ws');
const wss = new WebSocket.Server({ port: 8080 });

wss.on('connection', ws => {
  console.log('Client connected');

  ws.on('message', message => {
    // Convert Buffer to string for display/processing
    const msg = message.toString();
    console.log(`Received: ${msg}`);
    
    // Broadcast the received message to all connected clients
    wss.clients.forEach(client => {
      if (client !== ws && client.readyState === WebSocket.OPEN) {
        client.send(`Broadcast: ${msg}`);
      }
    });
    
    // Also send back to the sender as confirmation
    if (ws.readyState === WebSocket.OPEN) {
      ws.send(`You sent: ${msg}`);
    }
  });

  ws.on('close', () => {
    console.log('Client disconnected');
  });

  ws.send('Welcome to the broadcast server!');
});

console.log('WebSocket server started on port 8080');

Broadcast Code Walkthrough

Let's break down the broadcast logic:

wss.clients.forEach(client => { ... }): This loop goes through every client in the connected set.
if (client !== ws && client.readyState === WebSocket.OPEN): We check if the client is not the sender (to avoid echoing back to them twice) and if their connection is still open.
client.send(`Broadcast: ${msg}`);: This is the magic! It sends the message to that specific client.

Testing the Broadcast

To test this, start your Node.js server. Then, open multiple browser tabs or client applications, all connecting to ws://localhost:8080.

When you send a message from one client, you should see it appear on all other connected clients!

Targeted Messaging

Broadcasting is powerful, but what if you need to send a message to just one or a few specific clients, not everyone?

This is called targeted messaging. Examples include private chat messages, direct user notifications, or status updates for specific admin users.

Identifying Specific Clients

The ws library doesn't inherently give clients unique IDs you can use for targeting. You'll need to implement this yourself:

When a client connects, assign it a unique ID (e.g., a UUID).
Store this ID along with the ws object in a Map or object on your server.
When a client sends a message that requires a targeted response, it can include its ID.

Simple Targeted Example

For a basic example, let's make a server that *only* sends a message back to the client that sent it (a direct echo). This demonstrates sending to a single ws object.

const WebSocket = require('ws');
const wss = new WebSocket.Server({ port: 8081 }); // Use a different port

wss.on('connection', ws => {
  console.log('Client connected for targeted example');

  ws.on('message', message => {
    const msg = message.toString();
    console.log(`Received: ${msg}`);
    
    // Send the message back ONLY to the client that sent it
    if (ws.readyState === WebSocket.OPEN) {
      ws.send(`You said: ${msg}`);
    }
  });

  ws.on('close', () => {
    console.log('Client disconnected from targeted example');
  });

  ws.send('Welcome! I will only talk directly to you.');
});

console.log('Targeted WebSocket server started on port 8081');

Broadcasting Check

You're building a live chat application. When a user sends a message, you want *all* other users in the same chat room to see that message.

Recap & Next Steps

Fantastic work! You've mastered how to send messages from your Node.js WebSocket server:

Broadcasting: Sending a message to all connected clients by looping through wss.clients.
Targeted Messaging: Sending to a specific client using its individual ws object.

These techniques are crucial for building dynamic and interactive realtime applications. Next, we'll dive into how clients connect and interact with these server-side messages!

Frequently asked questions

Is the “Broadcasting Messages to Clients” lesson free?

Yes — the full text of “Broadcasting Messages to Clients” is free to read here on the web, and the WebSockets & Realtime Systems Programming course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the WebSockets & Realtime Systems Programming course, upgrade to CoddyKit PRO.

What will I learn in “Broadcasting Messages to Clients”?

Learn how to send messages from the server to all connected clients or specific ones. You practise WebSockets & Realtime Systems Programming with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start WebSockets & Realtime Systems Programming?

No prior experience is required. WebSockets & Realtime Systems Programming on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Broadcasting Messages to Clients” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this WebSockets & Realtime Systems Programming lesson?

Yes. Every WebSockets & Realtime Systems Programming lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to WebSockets & Realtime Systems Programming