When opening my colleague's Storyline file, I get a message box (attached) telling me that the fonts listed are not installed on my PC. They are. I can see them in my fonts list and they are also in my Fonts folder. Once in Storyline, I can even select the font claimed to be missing from the Fonts menu. The problem is that it does not render it consistently or correctly. Is this a common problem and is there an easy solution?
Oswald Light isn't a font that is automatically installed when you install Storyline 360, but you can still use it on other non-Content Library slides in your course.
Simply select the text box, and manually type 'Oswald Light' in the font area. Now the text should adopt the Oswald Light font.
My team of instructional designers and I recently upgraded to Storyline 3. We have the newest version and update; however, we are still receiving error messages about missing fonts. From the previous comments, it seems that Articulate staff members are calling this issue a bug. Is it safe to ignore these error messages and continue building? Or do we need to install the fonts to avoid additional issues?
We had an issue previously where this message was being received when the fonts were installed. This was addressed in Update 2 and you can see the details of this release and all release notes here.
Yes, please be sure the fonts are installed on your system. Let me know if that alleviates the error you are seeing.
What about a fix for Articulate 360? I'm getting the missing font message although the font is installed on my computer. When I view in Articulate Review, the font is indeed missing. All font in the entire output now displays in Times New Roman vs. Segoe UI.
FYI: This was also a problem when I changed from Storyline 2 to Storyline 3 now. The "use modern fonts" button was non excisting in the first download, I had to "search update" and install the update to even see the button :) But now my text are fine!
Whew! Sorry for the extra steps, Malin. It sounds like you may have had an older install of Storyline 3? You can always find the latest version linked here.
I updated all of my Articulate apps earlier today so I am assuming I am on the latest and greatest? My process involved importing a PPT slide deck that uses a specific font we had created for marketing purposes. It's important that the right font be used. A replacement is unacceptable.
I have found that the font works everywhere else AND if I select a block of text I can select the original company font from the list and it then displays correctly. However - by that time the damage is done, as all of my slides use the wrong replacement font everywhere...so I basically need to manually edit everything again.
Seems like the import ppt feature needs to be examined for font identification issues. ???
I still have the same problem, Story Line can't read the lines I need. By the way Microsoft Word and such programs can read the fonts, which mean that is installed on PC.
I'd like to get a couple more details from you. First, are you on the latest update of Storyline 360? To check, click the Help tab, then click About Storyline. You should see 3.22.17236.0 in the bottom-right corner.
Next, go to your Windows Control Panel > Appearance and Personalization > Fonts. Do you see those fonts listed in your fonts list?
Hi there, Cynthia. We had an issue with the "missing fonts" message appearing despite the font being installed in an earlier version of Storyline 360. We released an update that had resolved the issue at that point.
The original issue was only appearing in specific files. Was this file originally on another machine? Could you please test opening a new Storyline 360 project and attempt to use the Imago book font? If that works, please try importing the slides from the original project into a new project.
Let me know how you make out, and we'll determine if we have a new bug to squash. Thanks!
I see this was an issue in the past. I am getting the same Storyline error now stating that a font is missing. I know the font is there. Perhaps we need to re-open this ticket and solve this problem again??
Hi there, Lee! I've opened a priority support case so our team can explore the error you're receiving. I'll follow the case as well so I can update the community discussion on what we discover. Thanks!
That's definitely odd and I haven't run into the same issue using Storyline's latest update and the Velocity template. I'm curious if you could share the version you're using so that I can give that a test?
Also, can you check where the Font files are installed on your computer? They should be in the Font folder within your local Windows install. I'd also like to know if you're seeing an issue with any of the other fonts that are installed when Storyline is installed.
I've done everything on this thread and this is still an issue. I feel like this issue has continued from every iteration of Storyline and this is Still slowing me down. I've updated to Storyline 360, and the issue persists. I use all these fonts daily with no issue, except in Storyline.
You can see in my image that these fonts are clearly in my windows font folder, and yet here is the error message again.
Is there any solution for this issue?
I feel like Articulate says this is fixed in this update and yet here we are again...I find it very frustrating that this issue has been occurring for over two years and yet there is still no resolution.
Hi there, Lee. I'm sorry this issue is still plaguing you! You shared that this message appears when the file was originally created on another person's machine and then transferred to your machine. Cleo suggested uninstalling the font on your end and reinstalling with the same file the original user had if possible.
Does that make any difference when opening the file on your machine?
It seems like Articulate continues to suggest the same fix to a problem that really needs to be solved. It is getting to the point where I need to remove and reinstall the font every time I open a Storyline file from a different person.
I really wish we could simply solve this problem that is over 3 years old rather than offer a workaround that does not address the problem!
I've reinstalled these fonts at least 12 times, and this is now ridiculous.
I can understand how problematic and labor-intensive it is to reinstall the fonts, again and again, to deal with this issue. I know you've shared details with Cleo in your case, and I believe this issue to be different than the original one discussed here due to the limited number of customers experiencing it.
I've asked Cleo to share your case with our team of Senior Support Engineers so that we can dig in further to your font and the way in which files are shared to shed some light on this!
I found a workaround for this issue. When you see there is a missing font, it really helps to replace that font with a Web Font like Open Sans. Our odd fonts often don't display well in HTML 5. Once you open a file and you get the infamous Missing Font error message from Storyline here is a solution. Use the replace font tool in Storyline 360 to replace your font with a Webfont.
This isn't always an option. Often corporate branding guidelines specify the use of certain fonts. Also Open Sans was one of the fonts reported as missing in the initial comments.
THIS is STILL very much an issue even with the update to Articulate that came out on 12/17/19. Font (Arial) is installed on the PC with Windows 10 and the message pops up stating it's missing. Articulate just does not have a clue what's wrong, let's be real about that, one can see it from the same response over and over. There is no real resolution.
112 Replies
Hi Cecelia,
That font is on the Serenity template, so we're looking into why you can't select it. We'll let you know as soon as we can about it!
Hi Cecelia,
Oswald Light isn't a font that is automatically installed when you install Storyline 360, but you can still use it on other non-Content Library slides in your course.
Simply select the text box, and manually type 'Oswald Light' in the font area. Now the text should adopt the Oswald Light font.
Check out this video to see this in action!
Hello there
My team of instructional designers and I recently upgraded to Storyline 3. We have the newest version and update; however, we are still receiving error messages about missing fonts. From the previous comments, it seems that Articulate staff members are calling this issue a bug. Is it safe to ignore these error messages and continue building? Or do we need to install the fonts to avoid additional issues?
Hello Emily and welcome to E-Learning Heroes :)
We had an issue previously where this message was being received when the fonts were installed. This was addressed in Update 2 and you can see the details of this release and all release notes here.
Yes, please be sure the fonts are installed on your system. Let me know if that alleviates the error you are seeing.
What about a fix for Articulate 360? I'm getting the missing font message although the font is installed on my computer. When I view in Articulate Review, the font is indeed missing. All font in the entire output now displays in Times New Roman vs. Segoe UI.
Hello Cindy,
Storyline 360 also had a fix for the issue reported here back in Update 8. We are currently on Update 18.
What version of Storyline are you currently using?
This article shares some common reasons you may be seeing the wrong fonts in your output.
FYI: This was also a problem when I changed from Storyline 2 to Storyline 3 now. The "use modern fonts" button was non excisting in the first download, I had to "search update" and install the update to even see the button :) But now my text are fine!
Whew! Sorry for the extra steps, Malin. It sounds like you may have had an older install of Storyline 3? You can always find the latest version linked here.
Let us know if you need anything else!
This just happened to me as well. 10/30/2018.
I updated all of my Articulate apps earlier today so I am assuming I am on the latest and greatest? My process involved importing a PPT slide deck that uses a specific font we had created for marketing purposes. It's important that the right font be used. A replacement is unacceptable.
I have found that the font works everywhere else AND if I select a block of text I can select the original company font from the list and it then displays correctly. However - by that time the damage is done, as all of my slides use the wrong replacement font everywhere...so I basically need to manually edit everything again.
Seems like the import ppt feature needs to be examined for font identification issues. ???
Hi Geoff,
It sounds like the specific font you need is already installed on your system, is that right?
If you were to open a new Storyline file and insert a text box, is the specific font available in the dropdown list?
What font is used in the PowerPoint, and what replacement font is used in Storyline?
Hello
I still have the same problem, Story Line can't read the lines I need. By the way Microsoft Word and such programs can read the fonts, which mean that is installed on PC.
Hello, Marianne!
I'd like to get a couple more details from you. First, are you on the latest update of Storyline 360? To check, click the Help tab, then click About Storyline. You should see 3.22.17236.0 in the bottom-right corner.
Next, go to your Windows Control Panel > Appearance and Personalization > Fonts. Do you see those fonts listed in your fonts list?
360 SL Version 3.25.18009.0
And the font is available (similar to your image) on Windows control panel > Font.
Any fix to this yet? I submitted a ticket. SL states the "Imago book font" is missing.
Hi there, Cynthia. We had an issue with the "missing fonts" message appearing despite the font being installed in an earlier version of Storyline 360. We released an update that had resolved the issue at that point.
The original issue was only appearing in specific files. Was this file originally on another machine? Could you please test opening a new Storyline 360 project and attempt to use the Imago book font? If that works, please try importing the slides from the original project into a new project.
Let me know how you make out, and we'll determine if we have a new bug to squash. Thanks!
I see this was an issue in the past. I am getting the same Storyline error now stating that a font is missing. I know the font is there. Perhaps we need to re-open this ticket and solve this problem again??
Hi Curt, long time no see. :)
Lee
Hi there, Lee! I've opened a priority support case so our team can explore the error you're receiving. I'll follow the case as well so I can update the community discussion on what we discover. Thanks!
Hi Thaine,
That's definitely odd and I haven't run into the same issue using Storyline's latest update and the Velocity template. I'm curious if you could share the version you're using so that I can give that a test?
Also, can you check where the Font files are installed on your computer? They should be in the Font folder within your local Windows install. I'd also like to know if you're seeing an issue with any of the other fonts that are installed when Storyline is installed.
I've done everything on this thread and this is still an issue. I feel like this issue has continued from every iteration of Storyline and this is Still slowing me down. I've updated to Storyline 360, and the issue persists. I use all these fonts daily with no issue, except in Storyline.
You can see in my image that these fonts are clearly in my windows font folder, and yet here is the error message again.
Is there any solution for this issue?
I feel like Articulate says this is fixed in this update and yet here we are again...I find it very frustrating that this issue has been occurring for over two years and yet there is still no resolution.
What can I do to solve this? For real...
Nothing has changed. This is still very much an issue and I really need help to find a solution.
I would think this would be a priority to solve, but....
Hi there, Lee. I'm sorry this issue is still plaguing you! You shared that this message appears when the file was originally created on another person's machine and then transferred to your machine. Cleo suggested uninstalling the font on your end and reinstalling with the same file the original user had if possible.
Does that make any difference when opening the file on your machine?
It seems like Articulate continues to suggest the same fix to a problem that really needs to be solved. It is getting to the point where I need to remove and reinstall the font every time I open a Storyline file from a different person.
I really wish we could simply solve this problem that is over 3 years old rather than offer a workaround that does not address the problem!
I've reinstalled these fonts at least 12 times, and this is now ridiculous.
Lee
Hi Lee,
I can understand how problematic and labor-intensive it is to reinstall the fonts, again and again, to deal with this issue. I know you've shared details with Cleo in your case, and I believe this issue to be different than the original one discussed here due to the limited number of customers experiencing it.
I've asked Cleo to share your case with our team of Senior Support Engineers so that we can dig in further to your font and the way in which files are shared to shed some light on this!
I found a workaround for this issue. When you see there is a missing font, it really helps to replace that font with a Web Font like Open Sans. Our odd fonts often don't display well in HTML 5. Once you open a file and you get the infamous Missing Font error message from Storyline here is a solution. Use the replace font tool in Storyline 360 to replace your font with a Webfont.
Here is an article on the process: https://community.articulate.com/series/74/articles/articulate-storyline-360-user-guide-how-to-replace-fonts
This isn't always an option. Often corporate branding guidelines specify the use of certain fonts. Also Open Sans was one of the fonts reported as missing in the initial comments.
THIS is STILL very much an issue even with the update to Articulate that came out on 12/17/19. Font (Arial) is installed on the PC with Windows 10 and the message pops up stating it's missing. Articulate just does not have a clue what's wrong, let's be real about that, one can see it from the same response over and over. There is no real resolution.