I use a lot of images, sometimes from stock image sites, sometimes from Articulate inventory. The issue here is that I often need small images, (eg: 200x200) but I have to insert a 3000x2000 pixel image to resize it inside the slide. My doubt is: will the image be saved in the original 3000 pixel size or SL will save it in the new resized 200 pixel size? I know SL compresses images, but this is different, it is resizing. Should I resize the image before inserting it in the slide?
I'd recommend resizing outside of SL. The net result will be smaller overall story project files, faster project loading times and faster publishing times
I would do any resizing outside of Storyline as well. That way you've got your image at the right size prior to import, and if it's saved as such outside of Storyline, that's all that Storyline will be referring to.
As a best practice, if you don't have an external image editing software, once you resize or crop your image to its desired size, right-click and save as image (JPG if no transparency needed, or PNG if it is needed) to your working folder.
Them import the image you just saved back into Storyline and align it to your original. Delete the original. Note: using replace image here requires additional steps to undo all your original image edits, etc.
Even with the built-in Storyline optimization settings, this can greatly reduce file size and improve learner download times, especially if they are seeing the HTML5 version.
Thank you.
I was just hopeful that SL would have some feature like Powerpoint's.
Discard cropped parts and keep the last size.
This workflow is tedious, especially considering the ability to import a
photo from SL online image bank. It would be great to just import it,
resize it, position it and voilà.
A slick time-saving tip. However, I agree with the following comment from Marcos, Storyline itself should have an option to do this for us automatically. If Microsoft can figure this out, Articulate should be able to manage it as well.
6 Replies
I'd recommend resizing outside of SL. The net result will be smaller overall story project files, faster project loading times and faster publishing times
Are you sure that SL will not save the resized image instead of the
original?
This is a lot work.
I want to be sure.
Hi Marcos,
I would do any resizing outside of Storyline as well. That way you've got your image at the right size prior to import, and if it's saved as such outside of Storyline, that's all that Storyline will be referring to.
Also, take a look at our best practices for working with media here.
As a best practice, if you don't have an external image editing software, once you resize or crop your image to its desired size, right-click and save as image (JPG if no transparency needed, or PNG if it is needed) to your working folder.
Them import the image you just saved back into Storyline and align it to your original. Delete the original. Note: using replace image here requires additional steps to undo all your original image edits, etc.
Even with the built-in Storyline optimization settings, this can greatly reduce file size and improve learner download times, especially if they are seeing the HTML5 version.
Hope that helps.
Thank you.
I was just hopeful that SL would have some feature like Powerpoint's.
Discard cropped parts and keep the last size.
This workflow is tedious, especially considering the ability to import a
photo from SL online image bank. It would be great to just import it,
resize it, position it and voilà.
Thanks Scott,
A slick time-saving tip. However, I agree with the following comment from Marcos, Storyline itself should have an option to do this for us automatically. If Microsoft can figure this out, Articulate should be able to manage it as well.