0Pricing
Electron Desktop App Development · Lesson

Inter-Process Communication (IPC)

Learn to implement secure communication channels between the main and renderer processes using Electron's IPC modules like `ipcMain` and `ipcRenderer`.

Inter-Process Communication (IPC) is a free Electron Desktop App Development lesson on CoddyKit — lesson 2 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 Electron Desktop App Development learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

What is IPC in Electron?

In Electron, your application runs across two main types of processes: the Main Process and Renderer Processes.

  • The Main Process manages the app's lifecycle and interacts with the operating system.
  • Renderer Processes (web pages) display your UI and run your web code.

They can't directly access each other's resources or global variables. This is where Inter-Process Communication (IPC) comes in!

Why IPC is Essential

Imagine your Renderer Process needs to:

  • Read a file from the user's computer.
  • Open a native dialog box.
  • Perform a heavy task without freezing the UI.

These actions require access to Node.js modules or the OS, which are restricted to the Main Process for security and stability. IPC provides a safe way for these processes to talk to each other.

IPC Core Modules: ipcMain & ipcRenderer

Electron provides two special modules for IPC:

  • ipcMain: Used in the Main Process to listen for and send messages.
  • ipcRenderer: Used in Renderer Processes to send messages to the main process and listen for replies.

These modules are the backbone of communication between your Electron app's different parts.

Renderer to Main: One-Way Send

The most common communication is from a Renderer Process to the Main Process. You can send a message using ipcRenderer.send().

This is useful for triggering native actions or requesting data from the main process without needing an immediate reply in the renderer.

Code: Renderer to Main (Client)

Here's how your renderer.js would send a message when a button is clicked. You'd also need an index.html with a button (<button id="myButton">) that loads this script.

const { ipcRenderer } = require('electron');

document.addEventListener('DOMContentLoaded', () => {
  const btn = document.getElementById('myButton');
  if (btn) {
    btn.addEventListener('click', () => {
      ipcRenderer.send('channel-name', 'Hello from Renderer!');
      console.log('Renderer sent message.');
    });
  }
});

Code: Renderer to Main (Server)

This is the main.js code. It sets up the Electron window and uses ipcMain.on() to listen for messages on the specified 'channel-name'.

Note: nodeIntegration and contextIsolation are simplified here. For secure apps, use preload scripts.

const { app, BrowserWindow, ipcMain } = require('electron');
const path = require('path');

let mainWindow;

function createWindow() {
  mainWindow = new BrowserWindow({
    width: 800,
    height: 600,
    webPreferences: {
      nodeIntegration: true, // Simplified for demo
      contextIsolation: false // Simplified for demo
    }
  });

  mainWindow.loadFile('index.html');
  // Open the DevTools.
  // mainWindow.webContents.openDevTools()
}

app.whenReady().then(() => {
  createWindow();

  app.on('activate', () => {
    if (BrowserWindow.getAllWindows().length === 0) {
      createWindow();
    }
  });
});

app.on('window-all-closed', () => {
  if (process.platform !== 'darwin') {
    app.quit();
  }
});

// Handle messages from the renderer process
ipcMain.on('channel-name', (event, message) => {
  console.log('Main process received:', message);
  // Acknowledge or perform an action
});

Main to Renderer: One-Way Send

The Main Process can also send messages to a Renderer Process using mainWindow.webContents.send().

This is useful for pushing updates from the main process (e.g., progress updates, data changes) to the UI without the renderer having to request them.

Code: Main to Renderer (Server)

This main.js will send a message to the renderer once the window has finished loading. This time, the ipcMain isn't listening, but sending!

const { app, BrowserWindow } = require('electron');
const path = require('path');

let mainWindow;

function createWindow() {
  mainWindow = new BrowserWindow({
    width: 800,
    height: 600,
    webPreferences: {
      nodeIntegration: true,
      contextIsolation: false
    }
  });

  mainWindow.loadFile('index.html');

  // Send a message to the renderer after the window is ready
  mainWindow.webContents.on('did-finish-load', () => {
    mainWindow.webContents.send('main-channel', 'Update from Main!');
    console.log('Main sent message to renderer.');
  });

  mainWindow.on('closed', () => {
    mainWindow = null;
  });
}

app.whenReady().then(() => {
  createWindow();

  app.on('activate', () => {
    if (BrowserWindow.getAllWindows().length === 0) {
      createWindow();
    }
  });
});

app.on('window-all-closed', () => {
  if (process.platform !== 'darwin') {
    app.quit();
  }
});

Code: Main to Renderer (Client)

In your renderer.js, you'll use ipcRenderer.on() to listen for messages coming from the main process. We'll display it in a <div id="messageDisplay">.

const { ipcRenderer } = require('electron');

document.addEventListener('DOMContentLoaded', () => {
  const messageDiv = document.getElementById('messageDisplay');
  if (messageDiv) {
    ipcRenderer.on('main-channel', (event, message) => {
      messageDiv.innerText = `Received: ${message}`;
      console.log('Renderer received:', message);
    });
  }
});

Request/Reply with Invoke & Handle

For more complex interactions where the Renderer needs a response from the Main Process, Electron offers a request/reply pattern.

  • ipcRenderer.invoke(channel, ...args): Sends a message from renderer and waits for a response.
  • ipcMain.handle(channel, listener): In the main process, sets up a handler function that processes the request and returns a value (or a Promise that resolves to a value).

This allows for more structured and asynchronous communication.

Quick Check: IPC Methods

Which of the following statements about Electron's IPC modules are TRUE?

Recap: Inter-Process Communication

Great job! You've learned the fundamentals of Electron's Inter-Process Communication.

  • IPC is vital for Main and Renderer Processes to safely interact.
  • ipcMain and ipcRenderer are the core modules.
  • One-way communication uses ipcRenderer.send() (Renderer to Main) and webContents.send() (Main to Renderer).
  • For request/reply patterns, ipcRenderer.invoke() and ipcMain.handle() provide a robust solution.

You're now ready to build more interactive and powerful Electron applications!

Frequently asked questions

Is the “Inter-Process Communication (IPC)” lesson free?

Yes — the full text of “Inter-Process Communication (IPC)” is free to read here on the web, and the Electron Desktop App Development 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 Electron Desktop App Development course, upgrade to CoddyKit PRO.

What will I learn in “Inter-Process Communication (IPC)”?

Learn to implement secure communication channels between the main and renderer processes using Electron's IPC modules like `ipcMain` and `ipcRenderer`. You practise Electron Desktop App Development 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 Electron Desktop App Development?

No prior experience is required. Electron Desktop App Development on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Inter-Process Communication (IPC)” 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 Electron Desktop App Development lesson?

Yes. Every Electron Desktop App Development 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

  1. Main vs. Renderer Process
  2. Inter-Process Communication (IPC)
  3. Packaging Your Electron App
  4. Managing Multiple Windows
← Back to Electron Desktop App Development