Hi everyone!
I cannot find similar topic, but if there is one, let me know!
I’m building library where I have components (of course), custom icons, fonts etc. When I shared library, mentioned icons and font family (which I’ve made default) are not visible in other projects across workspace. Do you have any tips? I really don’t want to import icons and fonts all over again in every new project.
Hey Dominika 
,
welcome to the community and thanks for the great question!
From what I understand right now, components in a shared library can be reused across projects, but custom icon sets and font files still need to be uploaded and configured inside each individual project rather than being “auto‑available” at the workspace level. So even if the components come from your library, the icons and fonts they rely on won’t show up until those assets are added to that specific project.
That said, I’m not 100% sure if there’s any newer internal feature or workaround for making fonts/icons truly global across a workspace, so I’ll double‑check this with the WeWeb team and update you here once I have a more definitive answer.
Hey Dominika!
Right now, libraries can share components and typography tokens across projects, but icons and actual font files are still configured per project in the Assets panel, even when those components come from a shared library.
That means the expected behavior is to add your icon sets and fonts in each project where you use the library, then set your default font once; after that, all imported library components should work as intended without further configuration.
There is currently no workspace‑level global layer for fonts/icons, and libraries do not automatically import those asset files into consuming projects.
PS: As a more advanced workaround, you could technically bind icons to external URLs (similar to how you might reference remote images), but you would lose the built‑in no‑code icon picker and make maintenance harder, so the recommended and most reliable approach remains uploading icon sets and fonts on a per‑project basis.
Thank you Agustin very much! Do you know maybe about any plans to change that? Custom fonts are big part of the core of any library.
I don’t think we have plans to implement that, but I would encourage you to submit a feedback ticket explaining your situation and idea.