If you add an image to a web site that is 7MB (for example) and 2000 px wide but set the width to 200 px, then it looks small but you are still downloading a 7 MB pig of an image.
So you would never do that.
But if Storyline just gets its file size from the final display/rendering, then I want to know if I am wasting my time in optimizing before inserting.
So if I receive a hi-rez image (i.e 7 MB), will that cause the final file size of my project to be larger than if I resized my 7MB pig first.
Storyline is pretty smart about image instance management and will export the image at the largest size used. So, for example:
On slide 1, you use an 5MB source image and size it to 320x200. The result could be a 25K image on publish. The 5MB source image remains in the source.
You copy and paste the same image from slide 1 to slide 5 and rescale it up to 1024x768. The result could be a 50K image on publish. In this case, the same image is used for the slide on slide 1 and slide 5. So only a single 50K image is exported. If you were to re-import the image or drag it in from an external folder, a new instance of the image would be created in Storyline and two images would be exported.
Another trick is super-scaling a very large image. You can scale an image to a the native size off stage if you always want to retain that resolution for some reason. For example, if you wanted to zoom in on an image and have the result be crisp. This way, when you copy and paste then rescale the super-scaled image, it'll retain all of the pixels in the copy.
Publishing will take longer if you make Storyline resample/resize your image. That may not be a concern since it also takes time to resize an image in Photoshop. My guess is Photoshop probably does a better job of resampling than Storyline does...
Good point, Brett. Agree about better 1:1 pixel representation for some image types. If I were making an illustration and objects were already small or I was worried about line widths, I'd probably export a 1:1 size for pixel perfect placement.
I am having an issue with a photo that keeps shrinking when clicked on. I have tried so many things. Other photos seem to do the samething when placed in the same position- so I thought it might be the slide acting weird. Then finally found a photo that behaves as the other two photos on either side of it. Not sure why this is happening, I even tried a variety of cropping, that Riot program mentioned above....nada.... highly frustrating. Any thoughts?
I have attached the file with the slide in question. I appreciate it!
ugh...the funny thing is it changed itself as I had it set. I love storyline, but sometimes there are some weird glitches. I was typing the other day and the letter "t" wouldn't work properly. I wonder if it is the template I am using?
Anyhow thank you so much for your help with this. I can now be sure to check this on each module I am building.
I am posting my question here because subject is accurate enough.
I have use the same background image on several slide(same format, same name). Will SL2 use the same instance of the image hence not make the published output file bigger or will it create a file everytime I've used that image?
It depends on how the image is added. If you import then copy and paste the image from slide to slide, it'll only export a single instance of the image. If you import the same image more than once, a new instance container is created for the image and it'll export as many instances as you imported.
15 Replies
Hmm, a 7Mb image? That's pretty damn big and not something I would add to a course.
I optimise/compress all of my bigger images, in most cases sizing them according to the course window.
RIOT is great for this. I get excellent results 8 out of 10 times.
Thanks Simon,
I agree.
To clarify the point of my question...
If you add an image to a web site that is 7MB (for example) and 2000 px wide but set the width to 200 px, then it looks small but you are still downloading a 7 MB pig of an image.
So you would never do that.
But if Storyline just gets its file size from the final display/rendering, then I want to know if I am wasting my time in optimizing before inserting.
So if I receive a hi-rez image (i.e 7 MB), will that cause the final file size of my project to be larger than if I resized my 7MB pig first.
I hope what I am asking makes sense.
Indeed, 7MB in itself adds nothing to the course
Cheers,
Bruce
Hey Bruce,
Storyline is pretty smart about image instance management and will export the image at the largest size used. So, for example:
On slide 1, you use an 5MB source image and size it to 320x200. The result could be a 25K image on publish. The 5MB source image remains in the source.
You copy and paste the same image from slide 1 to slide 5 and rescale it up to 1024x768. The result could be a 50K image on publish. In this case, the same image is used for the slide on slide 1 and slide 5. So only a single 50K image is exported. If you were to re-import the image or drag it in from an external folder, a new instance of the image would be created in Storyline and two images would be exported.
Another trick is super-scaling a very large image. You can scale an image to a the native size off stage if you always want to retain that resolution for some reason. For example, if you wanted to zoom in on an image and have the result be crisp. This way, when you copy and paste then rescale the super-scaled image, it'll retain all of the pixels in the copy.
Publishing will take longer if you make Storyline resample/resize your image. That may not be a concern since it also takes time to resize an image in Photoshop. My guess is Photoshop probably does a better job of resampling than Storyline does...
Good point, Brett. Agree about better 1:1 pixel representation for some image types. If I were making an illustration and objects were already small or I was worried about line widths, I'd probably export a 1:1 size for pixel perfect placement.
I am having an issue with a photo that keeps shrinking when clicked on. I have tried so many things. Other photos seem to do the samething when placed in the same position- so I thought it might be the slide acting weird. Then finally found a photo that behaves as the other two photos on either side of it. Not sure why this is happening, I even tried a variety of cropping, that Riot program mentioned above....nada.... highly frustrating. Any thoughts?
I have attached the file with the slide in question. I appreciate it!
Hi Kristine
actually there was a problem with hover state of that image i have made changes in your file please check out the attached file
prashant
Thank you so much. What was it about the state?
Hello Kristine,
The Hover state of the image was a smaller size than the Normal state.
ugh...the funny thing is it changed itself as I had it set. I love storyline, but sometimes there are some weird glitches. I was typing the other day and the letter "t" wouldn't work properly. I wonder if it is the template I am using?
Anyhow thank you so much for your help with this. I can now be sure to check this on each module I am building.
What a great resource this community is!
Glad you got assistance here Kristine!
If you do see any odd behavior continue, you could always try running a repair of the software as described here.
Hi there,
I am posting my question here because subject is accurate enough.
I have use the same background image on several slide(same format, same name). Will SL2 use the same instance of the image hence not make the published output file bigger or will it create a file everytime I've used that image?
Thanks!
Hi Richard -
It depends on how the image is added. If you import then copy and paste the image from slide to slide, it'll only export a single instance of the image. If you import the same image more than once, a new instance container is created for the image and it'll export as many instances as you imported.
Thanks Steve!
Those little details are gold!
Best Regards!
Delighted to hear you are all set, Richard! And thanks, as always, for your input, Steve! :)
This discussion is closed. You can start a new discussion or contact Articulate Support.