How to Back Up Vivaldi Browser Settings on Linux

You spent hours making Vivaldi yours: custom keyboard shortcuts, tweaked tab stacking, a theme that perfectly matches your vibe, and (somehow) 43 pinned tabs that you absolutely, definitely need. Then Linux does a Linux thing: a distro hop, a reinstall, a new laptop, or a “tiny update” that turns into a weekend project.

The good news: backing up Vivaldi settings on Linux is mostly about copying the right folder at the right time. The even better news: you can do it in a way that’s reliable, repeatable, and doesn’t require mystical incantationsjust a little respect for hidden directories and the sacred rule: close the browser first.

Quick Answer (For People Who Have Things to Do)

1. In Vivaldi, open vivaldi://about and find Profile Path (that’s the folder you care about).
2. Quit Vivaldi completely (no background process).
3. Back up the entire User Data directory (not just bookmarks).
4. To restore, install Vivaldi, run it once, quit, then replace the newly created folder with your backup.

What Counts as “Vivaldi Settings,” Exactly?

In Vivaldi (a Chromium-based browser), your “settings” aren’t just a single tidy file labeled settings.json with a bow on it. They’re spread across your profile data: preferences, UI tweaks, extensions, sessions, bookmarks, history, cookies, and morebasically your browser life story.

Chromium documentation describes the “user data directory” as containing profile data (history, bookmarks, cookies) and other local state, with profiles stored as subfolders (often named Default). Vivaldi follows that same general model. This is why copying the right directory is the most complete backup approach.

Typical items you’ll preserve with a full profile backup

• Settings and UI preferences (themes, tab behavior, keyboard shortcuts, panels)
• Bookmarks and Speed Dials
• Extensions and extension data
• Saved sessions and “continue where you left off” state
• History, cookies, site permissions, autofill
• Passwords (usually), with one big asterisk (we’ll cover it)

Step 1: Find Your Vivaldi Profile Folder (Don’t GuessConfirm)

Linux has options. Vivaldi has options. Package formats have options. Guessing is how you end up backing up the wrong folder and confidently restoring… absolutely nothing.

Use Vivaldi’s About Page to locate “Profile Path”

1. Open Vivaldi.
2. Type vivaldi://about in the address bar.
3. Look for Profile Path. That’s the live, authoritative location for your current profile.

Common “User Data” locations on Linux (by install type)

If you prefer starting with likely locations, here’s the usual map. (Still: verify with vivaldi://aboutit’s the browser’s own receipt.)

One more important note: Vivaldi explicitly warns you shouldn’t run two installs (for example, native + Flatpak) using the same data directory. It’s not a cute experiment; it’s how profiles get weird. Keep them separate unless you’re doing a one-time migration.

Step 2: Close Vivaldi Like You Mean It

Before you copy anything, quit Vivaldi. Not “close the window.” Quit the application. You want the profile files to be in a consistent state (especially databases for history/cookies and whatever session state is being written).

Optional sanity check (recommended)

After quitting, verify it’s not running in the background:

Backup Method 1: Copy the Entire User Data Folder (Best Overall)

This is the “keep everything exactly as-is” method. If you want Vivaldi to come back looking and behaving like nothing ever happened, this is the move.

Copy to an external drive (simple, readable)

Replace the path below with your actual User Data directory from vivaldi://about.
If you’re on the native version, it’s usually ~/.config/vivaldi.

The -a flag is your friend: it preserves permissions and timestamps and copies directories recursively. Think of it as “copy this like I actually care.”

If you use multiple Vivaldi profiles

Inside the User Data directory you’ll typically see profile folders like Default and possibly Profile 1, Profile 2, etc. If you copy the entire User Data directory, you automatically get them all.

What about cache?

Cache is not “settings.” It’s “temporary performance confetti.” If you copy the whole directory, you’ll likely include some cache-like data anyway. That’s usually fine. If you want a cleaner backup, use the tar/rsync methods below with exclusionsbut don’t over-optimize on your first backup. A backup that exists is better than a perfect backup you never make.

Backup Method 2: Create a Compressed Archive (tar.gz)

If you want a single file you can store, upload, or toss onto a USB drive, use tar. This also makes it easier to keep multiple dated backups without creating a folder explosion.

Native install example

What’s happening here:

• -c creates an archive
• -z compresses with gzip
• -v shows progress (optional, but satisfying)
• -f names the output file
• -C changes directory first, so the archive path stays clean

Snap example

Flatpak example

SELinux / extended attributes note (only if you need it)

Most people backing up a browser profile inside their home directory won’t care about SELinux labels. But if you’re in a setup where contexts matter, know that tar does not retain some extended attributes by default. On SELinux-heavy systems, you may want to use the appropriate options and/or restore contexts after extraction.

Backup Method 3: Use rsync for Fast, Incremental Backups

If you back up frequently, rsync is the grown-up method: it copies only what changed. It’s fast, efficient, and perfect for backing up to an external drive or another machine.

Local external drive example

Let’s pretend your external drive is mounted at /media/you/BackupDrive.

A quick translation:

• -a preserves permissions and copies recursively
• --delete removes files on the destination that no longer exist in the source (keeps the backup mirror accurate)

Cleaner rsync (optional excludes)

If you want to reduce bloat, you can exclude cache-ish directories. The exact folder names can vary, so keep excludes conservative. Here’s a safe-ish starting point:

Pro tip: do one full “no excludes” backup first. Once you confirm restore works, then you can get fancy.

Backup Method 4 (Bonus): Vivaldi Sync Is HelpfulBut Don’t Treat It as Your Only Backup

Vivaldi Sync can synchronize a lot: bookmarks/speed dials, passwords, autofill, history, extensions, notes (partially), open tabs, and some settings. It’s end-to-end encrypted with a separate encryption password that Vivaldi doesn’t receive.

Two practical takeaways:

• Sync is great for convenience and device-to-device continuity.
• A local profile backup is still your best disaster recovery planespecially for “everything exactly how I like it.”

Save the Sync backup encryption key (seriously)

If you use Sync, save the backup encryption key from the Sync settings. It’s designed specifically for the “I lost the device that had my data” scenario. Store it somewhere safe (external drive, password manager attachment, trusted cloud vaultyour call).

Extra Credit: Export Bookmarks, Passwords, and Notes (Portable Backups)

Even if you do full profile backups, exporting key data gives you a “second parachute.” It’s also handy if you’re migrating to a different browser or you only need the essentials.

Export bookmarks (HTML file)

1. Open Vivaldi Menu
2. Go to File → Export Bookmarks
3. Choose a location (it saves an HTML file you can import elsewhere)

Export passwords (CSV filetreat carefully)

1. Go to File → Export → Export Passwords
2. Verify your identity when prompted
3. Save the CSV somewhere secure

Important: a CSV password export is readable text. If someone gets the file, they get the passwords. If you export it, store it encrypted (for example, inside an encrypted vault) and delete any stray copies.

Export notes (optional)

If you use Vivaldi Notes heavily, exporting them gives you a clean, portable backup:

1. Go to File → Export → Export Notes
2. Pick a destination folder

How to Restore Vivaldi Settings on Linux (Without Tears)

Restoration is basically the reverse process, with one extra trick that saves a lot of headaches: let Vivaldi create its folder structure first.

Restore checklist

1. Install Vivaldi (same package type if possible: native-to-native, Snap-to-Snap, Flatpak-to-Flatpak).
2. Run Vivaldi once, then quit completely.
3. Locate the new User Data folder (again: vivaldi://about is your friend).
4. Rename the newly created folder as a safety fallback (optional, but smart).
5. Copy your backup folder into place.
6. Launch Vivaldi and verify your settings, extensions, and bookmarks.

Example restore (native install)

Common Gotchas (And How to Out-Smart Them)

“My passwords didn’t restore!”

This can happen, especially when moving between machines. On Linux, saved passwords may rely on your system’s keyring integration (GNOME Keyring, KWallet, etc.). If the new system doesn’t have the same keyring state, some saved passwords may not decrypt properly even if the files are present.

The workaround is simple: before migrating machines, do a password export (CSV) and store it securely, or rely on Vivaldi Sync (plus the saved encryption key) for password continuity. If you do export, treat that CSV like it’s a live grenade with your name on it.

“Extensions are there, but some extension settings are missing.”

Most extension data lives inside the profile, so a full profile restore usually brings everything back. But some extensions also depend on native messaging or external helper apps. Note: Snap/Flatpak builds can limit native messaging features, which can affect extensions that talk to external apps (like some password managers). If you relied on that, native Vivaldi may behave differently than the sandboxed version.

“I switched from Snap to native (or Flatpak to native) and things got weird.”

Different install types store data in different locations. You can migrate by copying the whole User Data folder from one location to the other, but don’t run both installs against the same profile at the same time. If you want “keep both installs in sync,” use Vivaldi Sync.

“My backup is huge.”

Browser profiles can grow. History, caches, session data, site storage, and extension caches all add up. This is where rsync shines (incremental updates), and where smart excludes can help after you confirm restoration works.

A Simple Backup Routine You Can Actually Stick With

If you want a low-effort habit: make one monthly archive backup plus a weekly rsync mirror to an external drive. You’ll have “time machine” style dated archives and also a fast mirror that’s easy to restore.

Example: monthly tar backup

Example: weekly rsync to external drive

Real-World Experiences and Lessons ( of “This Is What Usually Happens”)

Backing up a browser profile sounds boring until you live through your first “why are all my tabs gone?” moment. The most common real-life story goes like this: you’re upgrading your distro (or moving to a new laptop), you assume “sync has me covered,” and you discover sync is great for bookmarks but not always the full vibelike your exact UI layout, your panel setup, your favorite custom search engines, your extension preferences, and that carefully curated list of keyboard shortcuts you invented because your hands are faster than menus.

People also learnusually the hard waythat timing matters. If you copy the profile while Vivaldi is still running, you might grab half-updated databases. The restore “works,” but it’s flaky: extensions complain, sessions don’t reopen cleanly, or history looks like it time-traveled. The fix is almost always the same: quit Vivaldi completely and copy again. It’s not dramatic. It’s just file consistency doing file consistency things.

Another common experience: migrating between package types. Maybe you started with a native install, but your distro store nudged you toward Flatpak, or you tried Snap because it was convenient. The first time you go hunting for your data in ~/.config and it’s not there, it can feel like your browser settings fell into a black hole. In reality, they’re just living in a sandbox-specific path. Once you know that Snap and Flatpak keep their own “User Data” directories, the mystery disappears, and you can migrate cleanly by copying the correct folder (or by using Sync for the basics and a local backup for the rest).

Passwords deserve their own mini-war story. Many Linux users assume “profile folder equals passwords.” Sometimes that’s truesometimes you restore and everything is perfect. Other times you move to a different machine and saved passwords don’t show up properly because the decryption depends on the local keyring environment. This is where a belt-and-suspenders approach pays off: keep a profile backup for convenience, and also export passwords to CSV before a major migrationthen store that export in something encrypted. Nobody wants a plain-text password file sitting in Downloads like a neon sign that says “FREE ACCOUNT ACCESS.”

The best experience, though, is the calm one: you do a backup once, you test a restore once (even just to a temporary folder), and suddenly browser migrations stop being scary. When your profile is backed up, you can try a new distro, reinstall your OS, or replace a drive without treating your browser setup like a fragile house of cards. It turns Vivaldi customization from “high commitment” into “high reward.”

Conclusion

Backing up Vivaldi on Linux isn’t complicatedit’s just specific. Find the correct User Data directory (preferably via vivaldi://about), quit the browser, and copy the whole folder using either a simple cp -a, a tidy tar.gz archive, or a smart rsync mirror.

If you want maximum safety: combine methods. Keep a full profile backup for “everything,” export bookmarks/passwords as portable insurance, and use Vivaldi Sync for day-to-day continuityespecially if you also save your Sync backup encryption key.

Your future self will thank you. Possibly with fewer sarcastic comments. No promises.