Free Space Used by Browser Kernels

After a device has used several browser versions, it may retain more than one local browser kernel. Kernel files and profile data are separate: removing an old kernel can free space, but it does not delete profiles, cookies, extensions, proxy settings, or cloud data.

Confirm what is using the space

Open Updates → Browser version and find Local browser storage. It shows the detected kernel versions for the current platform, the actual file size of each version, and their combined size.

This total covers only local browser kernels managed by the client. It is not the combined size of profile data, downloads, or system caches. If the system drive is still full, identify the source before assuming that kernels account for all of it.

Remove an old kernel safely

1. Stop profiles that use the target version, then wait for any launch, download, verification, or installation to finish.
2. Under Local browser storage, confirm the version and estimated space to recover.
3. Choose Remove only for an old version whose button is enabled.
4. Recheck the version and size in the confirmation dialog, then confirm.
5. Wait for the list to refresh after removal and confirm that the total and versions changed. Refresh manually only if the state does not update.

The client removes only the local old-kernel version named in the confirmation dialog. Profile data, extension selections, proxy settings, and cloud bindings remain in place. If a profile later needs the removed version, the client may need to download it again.

Why removal is unavailable or refused

To avoid removing browser files that are active or are the only usable copy, the button may be unavailable or the final recheck may refuse removal when:

• the version is the newest local kernel on this device;
• the version is being launched, used, verified, or installed;
• the client is selecting a kernel for a launch;
• there is no newer, fully verified replacement kernel on the device; or
• an unclosed browser process prevents the client from confirming safe usage state.

Close the related profiles normally, wait for current operations to finish, and refresh the list. If you still need to remove that version, install and verify a newer version from Browser version first.

If cleanup fails

Do not delete files manually from the client resource directory. Before cleanup, the client rechecks the version, current usage, and directory boundary. It refuses the operation when a check fails so that a running profile or unrelated local data is not affected.

Close any remaining browser processes, refresh the page, and retry once. If a version appears missing or damaged, follow the browser download, verification, and repair checklist. For a failure of the desktop client update itself, see fix a failed client update or download.