Trouble with images when exporting to Word

Aug 01, 2023

We always export our courses to a Word document once the course is completed, and use that Word document in a variety of ways. 

I am running the latest version of Articulate 360, and when exporting to a Word doc, many of the images each slide look like static. See the attached screenshot. It's mostly just images on the page that look like static, although some other images - like graphics I created in Storyline - don't look good either. I also thought at first that it was only the content library images that were affected, but that is not the case. This is affecting 60 - 70% of my slides.

I have attempted to publish to Word and also Export to Word for Translation. Both have images that are affected by this, but not the same images, which just makes this more odd to me. My coworker who also uses 360 is not having this problem. 

Has this happened to anyone else? Maybe it's something in the way I am placing images into my course?

4 Replies
John Morgan

Hi Kristin,

Thanks for reaching out! I understand that you are seeing images that look like static after publishing them to Word. After testing a file on my end, I wasn't able to reproduce the same behavior you are experiencing. I'd love to know more about your setup so we can figure this out together.

I look forward to your response!

Kristin Hatcher

Hi John, 

Thank you for the response. I was hoping it was something easy, but it sounds like it's not! I am not working from a shared drive. This does happen to all of the Word documents I produce from other courses, but it does not happen to my coworker, so it's something specific to me. 

I will open a support case. Thank you!

Kristin Hatcher

My computer was waiting on some operating system updates today, so I installed those before opening a ticket. Would you believe it? It solved the issue. Perhaps the version of the OS I was on had some kind of interaction with Storyline - not a bug on either end, but a "bad interaction."

In any event, the problem appears to be fixed, but I will open a ticket if this happens in the future.