FontBase 2026.7.0 – All fonts disappeared, but database and collections remain intact

Bugs
1

Hi,

I’m experiencing a strange issue with FontBase 2026.7.0 on Windows 10.

My entire font library has disappeared from the interface. The All, Active, and Inactive sections show 0 fonts, and all my existing folders appear empty.

However, my custom collections are still present, and one of them correctly displays a count of 1,998 fonts, although none are visible.

Some details:

  • FontBase version: 2026.7.0

  • OS: Windows 10

  • Font library: Approximately 128,000 physical font files

  • Font root directory is correctly configured, and the original files are still present.

  • The IndexedDB database files are present and being updated.

  • Previously activated fonts remain available in Windows applications, even when FontBase is closed.

  • Restarting FontBase and Windows hasn’t resolved the issue.

An interesting discovery:

I imported a single font from my existing library into a temporary folder.

FontBase immediately displayed it under All. More importantly, it also recognized the font’s original folder associations and its membership in my existing custom collection.

This suggests that the original font metadata and collection associations are still stored in the database, but FontBase is failing to load or enumerate the existing font records.

Update history:

  • September 29: Updated to 2026.6.0

  • October 6: Automatically updated to 2026.7.0

  • October 17: Discovered the issue

The main.log doesn’t show any errors associated with the current problem.

I’ve backed up the entire FontBase application-data directory and would prefer to avoid resetting the database or reimporting approximately 128,000 font files.

Is this a known issue with 2026.7.0? Is there a way to rebuild or refresh the font index without losing existing collection memberships and folder associations?

Any guidance would be greatly appreciated.

2

Hello Mateja, thank you for your post and welcome to the forum :folded_hands:

Given the information you’ve gathered it seems the application thinks the fonts have been moved to a different location. Would it be possible to re-add the font folders into FontBase and see if that would fix the issue?

Thank you again,

3

Hi Yuriy,
Thank you for the response.

Yes, I guess it is definitely an option to spend hours/days re-adding fonts folder by folder, adding the time for the FontBase to process all individual fonts, yeah… But I would really appreciate if you could help me with a solution which involves FontBase ‘figuring out’ that no one moved the fonts from its root folder. Is there an option to force FontBase to rescan the root folder?

Thank you!

Mateja
long time FontBase subscriber :slight_smile:

4

Hello Mateja, thank you for such a quick reply :folded_hands:

We absolutely do understand the gravity of the situation and are by no means trying to downplay it, just trying to understand what the cause may be and fix it as soon as possible.

Without adding anything, would it be possible for you to select a different folder titled “FontBase” in the Settings page as the root folder as the first step? Then, via the Settings page again, selecting your original root folder as the current root folder location?

This will effectively make the app think it was given a new root folder, it will update accordingly, and once the original folder is re-selected the same will happen again and everything should be synced and re-added properly.

Thank you again,