Electron Desktop App Development · Lesson

Sandboxing Renderer Process

Enable and configure sandboxing for your renderer processes to limit their access to system resources, enhancing the security of your application.

Sandboxing Renderer Process is a free Electron Desktop App Development 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 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 Sandboxing?

Imagine your computer as a house. Some guests (apps) you trust completely, others you want to keep in a specific room with limited access.

Sandboxing is like putting your app's renderer process in a secure, isolated "room." It limits what that part of your app can do and access on your system.

This is crucial for security, especially when displaying untrusted web content or protecting against malicious scripts.

Why Sandboxing Matters

Electron apps combine web content (HTML, CSS, JS) with native desktop capabilities. Without proper isolation, a vulnerability in your web content could be exploited to access your user's file system or other system resources.

Sandboxing prevents this by isolating the renderer process, making it much harder for malicious code to "break out" and harm the user's system.

Chromium's Security Layer

Electron uses Chromium, the same engine that powers Google Chrome. A key security feature of Chromium is its renderer sandbox.

By default in browsers, web pages run in a sandboxed renderer process, meaning they can't directly interact with your operating system. Electron extends this robust security model to your desktop applications.

Activating the Sandbox

Enabling sandboxing in Electron is straightforward. You do it when creating a new BrowserWindow by setting the sandbox option to true in webPreferences.

This is a critical step for enhancing the security posture of your Electron application.

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

function createWindow () {
  const win = new BrowserWindow({
    width: 800,
    height: 600,
    webPreferences: {
      sandbox: true // Set to true to enable sandboxing
    }
  });
  win.loadFile('index.html'); // Loads your web content
}

app.whenReady().then(createWindow);

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

Renderer Process Limitations

When a renderer process is sandboxed, it faces significant restrictions:

It cannot directly access Node.js APIs (e.g., require, process, fs).
It cannot use native modules.
Its access to system resources (like files) is severely limited.

This isolation prevents web content from performing unauthorized actions on the user's computer.

Node.js Access Denied Demo

Let's see what happens when a sandboxed renderer tries to access Node.js directly. The code below creates a window with sandboxing enabled and attempts to use the fs module.

Run this example and check the developer console (usually F12 or Cmd+Option+I) for the error message.

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

function createWindow () {
  const win = new BrowserWindow({
    width: 600,
    height: 400,
    webPreferences: {
      sandbox: true, // Sandboxing enabled
      nodeIntegration: false, // Explicitly disabled (default with sandbox)
      contextIsolation: true // Explicitly enabled (default with sandbox)
    }
  });

  // Load HTML that tries to use Node.js 'fs' module
  win.loadURL(`data:text/html;charset=utf-8,
        <!DOCTYPE html>
        <html>
        <head>
            <title>Sandboxed Demo</title>
        </head>
        <body>
            <h1>Sandboxed Renderer Test</h1>
            <p id="message">Attempting to access Node.js...</p>
            <script>
                try {
                    const fs = require('fs'); // This will fail!
                    document.getElementById('message').innerText = 'Node.js fs module loaded!';
                } catch (error) {
                    document.getElementById('message').innerText = 'Error: ' + error.message;
                    console.error('Renderer error:', error);
                }
            </script>
        </body>
        </html>
      `);

  win.webContents.openDevTools(); // Open DevTools to see the error
}

app.whenReady().then(createWindow);

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

Secure Interaction: Preload

Since sandboxed renderers can't directly access Node.js, how do they perform system tasks?

You use preload scripts with context isolation. These scripts run before your web content, have Node.js access, and can securely expose a limited API to your sandboxed renderer via contextBridge.

This ensures that your main process controls exactly what functionality is exposed.

Sandbox & Context Isolation

It's important to note that when webPreferences.sandbox is true, both nodeIntegration will be false and contextIsolation will be true by default, regardless of what you explicitly set.

This combination provides the strongest security for your renderer processes.

Best Practices

Always enable sandboxing: It's a fundamental security measure.
Minimize exposed APIs: Only expose essential functionality via preload scripts.
Validate all inputs: Any data passed from a renderer to the main process should be validated.

These practices create a robust and secure Electron application.

Quick Check

Understanding sandboxing is key to building secure Electron applications.

Recap: Securing Your App

In this lesson, we explored sandboxing in Electron. We learned that it's a critical security feature that isolates your renderer processes, preventing them from directly accessing system resources or Node.js APIs.

By setting webPreferences.sandbox: true, you activate this powerful protection, ensuring a safer application. Remember to use preload scripts with context isolation for secure communication between your sandboxed renderer and the main process.

Frequently asked questions

Is the “Sandboxing Renderer Process” lesson free?

Yes — the full text of “Sandboxing Renderer Process” 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 “Sandboxing Renderer Process”?

Enable and configure sandboxing for your renderer processes to limit their access to system resources, enhancing the security of your application. 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 3 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Sandboxing Renderer Process” 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

← Back to Electron Desktop App Development