MacOS Sequoia 15.2
FontBase 02.21.0
The fonts are not included in groups anymore, approximatley all fonts now are individual fonts which may cause a hassle especially when fonts are more than 6 weights per family.
P.S.
I restarted the computer, fontbase, deleted the fontbase root file and also the ‘group fonts into families’ option more than once and the issue still persistent.
Thank you for the quick reply and the additional information @mhdhssamco
This is quite strange, the latest update did not bring any changes to the grouping logic as far as I’m aware
To understand if the cause is somewhere within the application or in the fonts themselves, would it be possible for you to do the following:
Activate 5-10 groups of Google fonts in FontBase to download them the the Root folder.
Deactivate the above fonts.
Go to FontBase Root folder, copy these fonts into a separate folder outside of the FontBase Root folder.
Add this newly created folder into FontBase as a watched or regular folder, as you would with any other font folder.
Make sure “Group fonts into families” is turned on and check if the fonts in the newly added folder are grouped in FontBase
?
Hello @ida, thank you for your post and welcome to the forum
This shouldn’t happen normally if the data inside the font files is coded correctly, we’ll try to get to the bottom of this.
Same question if I may - are the pre-loaded Google fonts grouped when you view them in FontBase?
Configuration for testing:
VirtualBox + Windows 10 Pro (fully updated) + FontBase
Tested versions of FontBase:
2.20.7
2.21.0
Font families (pcs.):
Adobe Arno Pro (32)
Adobe Minion Pro (64)
Adobe Myriad Pro (40)
IBM Plex (16)
Public Sans (18)
When adding the above font families to the program:
Version 2.20.7 creates 5 font families in the program.
Version 2.21.0 creates:
12 families for Adobe Arno Pro
26 families for Adobe Minion Pro
12 families for Adobe Myriad Pro
7 families for IBM Plex
8 families for Public Sans
Addition: if you update the program to the latest version, then fonts added in previous versions of the program - are grouped correctly, and fonts added in version 2.21.0 are grouped incorrectly.
I’m having the same issue on my home system. It was a fresh install in December 2024, with the latest 2.21.0 Fontbase. Fonts are listed as different groups even if they belong in the same family, the same way it’s in the original post. At work I have Fontbase 2.20.7 I believe (or if not, it’s older than 2.21.0) and all fonts appear correctly grouped. I have identical font collection on both systems. Google Fonts are correctly grouped on both PCs however, so t he issue only seems to exist with local files
I did backup and restore a few files in order to keep my collections of fonts within Fontbase across the older Windows install to the new one. No idea if that could be a problem here. Those files are everything inside: %appdata%\FontBase\IndexedDB
Windows 11 Pro 24H2 build 26100.2894
FontBase 2.21.0
Im having the same issue and it is driving me crazy! The whole reason I used FontBase in the first place was to have everything nicely organised. This needs to be resolved fast.
I’m facing the same problem on an iMac. Some families are grouped partially others not even, and besides the auto-activation for Adobe products is also not working properly.
Hello @mibu, thank you for your reply
Noted
As for the Abobe products issue, could you please post a reply in the following topic Auto Activation for CC 2025 - #3 by SamB with more information on what the actual issue and behaviour is?
Thank you again,
Everyone, the fix should be up in the next update, very sorry for the long waiting time on this
similar to commenters, i have two macbook pros to test. one old from 2017 and one new from 2024.
removing/adding watched folders did not correct the family grouping issue on my new macbook pro running macos 15.2.
2.20.7 works correctly on my older macbook pro running macos 12.7.6
so i downgraded fontbase from latest version (as of jan 31, 2025) to 2.20.7 on the new machine. watched folders were still not grouping families. so i removed and re-added the watched folders and families that group correctly on the old machine now group on the new machine.
when i migrated to the new machine i DID copy over some of the fontbase application support files (the databases i think) to save myself from having to re-add all the folders manually.