Making VSCode Flatpak Use Fonts from ~/.fonts

VSCode Flatpak cannot access ~/.fonts by default due to sandbox restrictions. To resolve this, you must either install fonts into the system-wide directory /usr/share/fonts or use the flatpak override command to grant the application permission to read your user font directory. This ensures VSCode recognizes custom typefaces without compromising security.

Understanding the Sandboxing Mechanism

Flatpak applications run in a restricted environment to enhance security and stability. Unlike traditional .deb or .rpm packages, Flatpaks do not have automatic access to user-specific directories like ~/.local or ~/.fonts. When you install VSCode via Flathub, it operates within its own isolated filesystem tree. Consequently, any fonts placed in your home directory are invisible to the editor unless explicitly exposed. This isolation is intentional. It prevents malicious applications from reading sensitive data in your home folder. However, for utilities like text editors that require access to system resources like fonts, developers provide mechanisms to bridge this gap safely. The two primary methods involve either moving fonts to a shared location or granting specific permissions to the existing location.

Method 1: Using flatpak override

The most flexible approach allows you to keep your fonts in ~/.fonts while giving VSCode permission to read them. You can achieve this using the flatpak override command-line tool. This method does not require root privileges and persists across updates. First, ensure you know the exact app ID of your installed VSCode Flatpak. You can find this by running:

flatpak list | grep vscode

Typically, the ID is com.visualstudio.code. Once confirmed, execute the override command to allow the application to access your home directory's fonts folder:

flatpak override com.visualstudio.code --filesystem=~/.fonts

If you have moved your fonts to ~/.local/share/fonts, which is the modern standard, replace the path accordingly:

flatpak override com.visualstudio.code --filesystem=~/.local/share/fonts

After running this command, restart VSCode completely. The editor should now detect and list the new fonts in its settings. If you wish to revoke access later, simply run:

flatpak override --unset-files com.visualstudio.code

For more information on managing community-supported Flatpaks, see our guide on How Safe Are Community Supported Flatpaks on Flathub?.

Method 2: Installing Fonts System-Wide

A cleaner, albeit more invasive, solution is to install fonts into the system-wide font directory. This makes the fonts available to all users and all applications, including non-Flatpak versions of VSCode. This method requires root access. Create the necessary directory if it does not exist:

sudo mkdir -p /usr/share/fonts/custom

Copy your font files (usually .ttf or .otf) into this directory:

sudo cp ~/path/to/font.ttf /usr/share/fonts/custom/

Once the files are copied, update the font cache so the system recognizes them. Run:

sudo fc-cache -fv

The -f flag forces a rebuild, and -v provides verbose output to confirm success. After this completes, restart VSCode. The fonts will appear immediately. This method is preferred if you share your machine with other users who also need access to these specific typefaces.

Verifying Font Availability

To confirm that VSCode sees the fonts, open the Command Palette (Ctrl+Shift+P) and select Preferences: Open Settings (JSON). Look at the editor.fontFamily setting. If you added a custom font named "Fira Code", your configuration might look like this:

{
    "editor.fontFamily": "'Fira Code', Consolas, 'Courier New', monospace"
}

If the font does not appear in the dropdown menu within the graphical settings, it is likely still not visible to the process. Check the terminal output when launching VSCode from the command line for any font-related errors. You can also verify system-wide visibility by opening another application, such as GIMP or LibreOffice, and checking if the font appears there. If it works in other apps but not VSCode, the issue is likely related to the Flatpak sandbox rather than the font installation itself. For troubleshooting terminal font issues specifically in WSL environments, refer to our article on Unable to Change Terminal Fonts in VSCode (Windows-WSL Ubuntu).

Common Pitfalls

One common mistake is placing fonts in ~/.fonts but forgetting to run fc-cache after copying them. While Flatpak overrides bypass some caching issues, ensuring the system fontconfig database is up-to-date is best practice. Another pitfall is typos in the App ID. Always double-check the ID returned by flatpak list before applying overrides. Additionally, be aware that some older versions of VSCode had bugs where they failed to reload the font list dynamically. If changes do not take effect, a full logout and login to your desktop session may be required to clear the font cache entirely.

Frequently Asked Questions

Does overriding the filesystem reduce security?

Granting filesystem access slightly expands the attack surface but is generally safe for trusted applications like VSCode. It only exposes the specified directory, not your entire home folder. You can always remove the override if you no longer need the fonts.

Why do my fonts disappear after a VSCode update?

Flatpak updates usually preserve your override settings and local data. However, if you installed fonts system-wide, they remain unaffected. If you used an override, ensure the App ID has not changed during the update process.

Can I use symbolic links instead of copying fonts?

Yes, symbolic links work within the overridden directory. Create a symlink in ~/.fonts pointing to your actual font storage location. The Flatpak will follow the link and render the font correctly.

How do I check which fonts are available to Flatpak apps?

You can inspect the virtual file system inside the Flatpak container using flatpak run --command=bash com.visualstudio.code and then listing the contents of ~/.fonts or /usr/share/fonts within that shell.

Is ~/.local/share/fonts better than ~/.fonts?

~/.local/share/fonts is the XDG-compliant standard and is preferred by modern Linux distributions. It keeps personal data separate from legacy configurations. Both paths work with the Flatpak override method.