How to Configure Notion Desktop Sync Bandwidth Throttling

Notion syncs your data continuously between the desktop app and its cloud servers. On a metered connection or a shared network, this sync can consume significant bandwidth and slow down other activities. Notion does not expose a bandwidth throttle setting inside its main user interface. This article explains how to configure bandwidth throttling for the Notion desktop app by modifying a hidden configuration file. You will learn the exact file location, the setting to change, and what to do if the change does not take effect.

Why Notion Desktop Sync Can Consume Excessive Bandwidth

Notion uses a persistent WebSocket connection to synchronize page edits, database changes, file uploads, and block operations in real time. When you work in a workspace with many pages, large attachments, or frequent updates, the sync process can send and receive several megabytes of data per minute. The desktop app does not have a built-in slider or dropdown to limit this traffic. The underlying Electron framework that powers Notion does include a bandwidth throttling mechanism, but it is not exposed through the user interface. By editing the app configuration file, you can instruct Electron to cap the data transfer rate.

Before You Start: Prerequisites for Bandwidth Throttling

You need the following before modifying the configuration file:

• Windows 10 or Windows 11 with the Notion desktop app installed and logged in
• Administrator access on the computer (to edit files in the AppData folder)
• A text editor such as Notepad, Visual Studio Code, or any plain-text editor
• The exact file path: %AppData%\Notion\config.json

The bandwidthLimit setting is not documented in Notion’s official help articles. The configuration file is created automatically after the first launch of the desktop app. If the file does not exist, you can create it manually.

Steps to Add Bandwidth Throttling to the Notion Desktop App

1. Open the config.json file
   Press Windows + R to open the Run dialog. Type %AppData%\Notion and press Enter. In the folder that opens, locate the file named config.json. If you do not see it, ensure file name extensions are visible in File Explorer. Double-click the file to open it in your default text editor.
2. Add the bandwidthLimit setting
   If the file is empty or contains only curly braces, add the following JSON object. If the file already has existing settings, insert the bandwidthLimit key inside the top-level object. Paste this exact text:
   { "bandwidthLimit": 512000 }
   The value 512000 represents 512,000 bytes per second, or 512 KB/s. Replace this number with your desired limit in bytes per second. For 100 KB/s use 102400. For 1 MB/s use 1048576.
3. Save the file
   Press Ctrl + S to save your changes. Close the text editor. Do not rename the file or change its extension.
4. Restart the Notion desktop app
   Close Notion completely. Right-click the Notion icon in the system tray and select Quit if it is still running. Then launch Notion again from the Start menu or desktop shortcut. The bandwidth limit is now active.
5. Verify the throttle is working
   Open Task Manager by pressing Ctrl + Shift + Escape. Go to the Performance tab and select your network adapter. Perform a sync-heavy action in Notion, such as uploading a large file or editing a database with many rows. Watch the network usage graph. It should peak at approximately your set value and not exceed it.

Common Issues After Configuring Bandwidth Throttling

Notion syncs at full speed despite the setting

The most common cause is a typo in the config.json file. Open the file again and check that the key is spelled exactly bandwidthLimit with a lowercase b. The value must be a plain number, not a string. A comma must separate it from any other settings. If you added the setting but Notion still uses full bandwidth, delete the config.json file, restart Notion, and repeat the steps from scratch.

Notion desktop app crashes on launch after editing config.json

This usually means the JSON syntax is invalid. Open the file in a JSON validator tool or check for missing commas, extra brackets, or unmatched quotes. A valid config.json with bandwidthLimit looks like this:
{ "bandwidthLimit": 512000 }
If the file had other settings, the correct syntax is:
{ "existingSetting": "value", "bandwidthLimit": 512000 }
Fix any syntax errors, save, and relaunch Notion.

bandwidthLimit setting is ignored after Notion updates

Notion desktop updates may overwrite the config.json file with default values. After each major update, open the file and verify that the bandwidthLimit key is still present. If it is missing, add it again and restart the app.

Notion Desktop Sync Throttling Methods Compared

Item	Config File Method	Third-Party Bandwidth Limiter
Setup difficulty	Modify one JSON file	Install and configure separate software
Requires admin rights	No	Yes, for network filter drivers
Affects only Notion	Yes	Depends on configuration
Persists after app update	May be overwritten	Yes
Granularity	Single global limit	Per-connection or per-protocol limits

Bandwidth throttling through the config.json file is the simplest method because it requires no extra software and affects only the Notion process. Third-party tools like NetLimiter or Traffic Shaper give you more control over scheduling and per-connection rules, but they require installation and ongoing maintenance.

You can now limit the sync bandwidth of the Notion desktop app by editing the config.json file and setting the bandwidthLimit value in bytes per second. After saving the file and restarting Notion, your network traffic for sync operations will stay within the cap you defined. If you work on multiple computers, repeat the configuration on each machine. For a more permanent solution that survives app updates, consider using a third-party bandwidth limiter instead of the config file method.