Where Does Pulse Browser Store Profiles?
Pulse Browser uses Firefox style profiles on desktop. The profile paths for Windows, macOS and Linux, plus about:profiles.
Last updated
Pulse is a Firefox fork, so it inherits the Firefox profile system. Each profile lives in its own folder with a random prefix like a1b2c3d4.default, and a profiles.ini file one level up records which one loads at startup. Bookmarks, logins, extensions and history all sit inside the profile.
The folder names below follow the Firefox fork convention (product name in place of Firefox). Treat them as the pattern to look for rather than a quoted spec, then confirm the live folder with about:profiles. That page prints the real path for the running build, which settles Flatpak versus native packaging differences on Linux.
Where Pulse Browser stores this, by platform
%APPDATA%\Pulse\Profiles\[random].[name]
Family convention for the fork, following Firefox with the product name swapped in. profiles.ini sits one level up. Confirm the live folder with about:profiles before copying, and quit the browser first since databases lock while running.
~/Library/Application Support/Pulse/Profiles/[random].[name]
Same interior as Windows, with profiles.ini beside the Profiles folder. Use about:support and its Profile Directory row if about:profiles feels buried. The Library folder is hidden in Finder by default.
~/.pulse/Profiles/[random].[name]
Native tarball layout with Profiles inside. Flatpak builds keep profiles sandboxed under their own app ID tree instead, so trust about:profiles over this path when the folder looks empty.
Frequently asked questions
How do I open my Pulse Browser profile folder?
Type about:profiles in the address bar. It lists every profile with its full disk path and an Open Folder button. This beats guessing folder names, since profile folders carry a random prefix that differs per install.
Can I move my Pulse profile to a new computer?
Copy the whole random named profile folder plus the profiles.ini file one level above it. If the folder name changed on the new machine, fix the Path lines in profiles.ini. Extensions tied to exact versions may ask for an update after the move.
Notice an outdated path? Let us know.