Save for web 72ppi (part 2)

Hi all, the old post was http://forums.adobe.com/thread/662903
The Include Metadata option in Save For Web... saves the info found in File > File Info with the image. No resolution data.
This has zero effect on the image. Image resolution only affects printing the image. For viewing on the web, all that matters is height x depth measured in pixels.
Save For Web strips all resolution data from the file. The file simply doesn't have a resolution out of SFW.
The 72 ppi or whatever appears when you reopen into Photoshop, because Photoshop needs some resolution figure and therefore assigns 72 purely as a default value.
I have to save some images for my DPS workflow with 72ppi and the same also 108ppi.
I save the first using Save for Web and i think that is correct.
The problem is the 108ppi output - how is the best workflow to this? Can i use Save for Web? I think no!
I understand that Save for Web do not save 72ppi or any other ppi size...

Think what you are quoting is what I have read also.  Not sure why they would specify 72 and 108 ppi.  That is just the pixels per inch of the display.  Perhaps they want a larger image on the website.  This could be acomplished by making the pixel size larger, without resampling.  At least that is the way I see it, but could be wrong.
Take an image and open image/image size and play with the ppi with resampling off to check this out.

Similar Messages

  • Save for web 72ppi

    running CS5 on a 64bit win 7 PC....
    When I use the 'save for web' option and enable the 'include all the metadata info'
    the saved image (jpeg) is not at 72ppi, which is clearly best for the web as that is apparently the idea resolution for our screens.
    instead it saves it at 300ppi
    (please no debate on  72ppi v's  XXX ppi , there are enough posts on that as it is).
    but if you disable the 'include metadata option' then the image saves as a 72ppi jpg as i require.
    Does anyone have an answer to this.
    there is no reason why an image cannot be saved at 72ppi and have metadata.
    one assumes that the whole 'save for web' feature is about optimizing the image for that very reason.
    this sounds like a bug to me ?

    Sorry to disagree with some of the above...
    there clearly are some useful facts listed.
    but you have to ask with ref to the above, why did adobe bother with the 'save to web' option
    if most of you seem to imply it really doesn't make any difference on your uploads.
    well it does, i have a few photosharing websites
    and some display the images very well others do not, they can look quite blurred.
    i've been putting this down to resolution. (i've tried using the photo sites options of not adjusting file size
    as clearly im aware their own scaling systems could alter the photo's appearance.
    so what have i found.
    well reducing the image to 72ppi and say 1000 pixels wide looks good online
    as apposed to uploading the original which not only is a larger files size it also has different parameters.
    you need a different approach to sharpening for online images than for print images.
    hence back to the original, adobe implented this feature for a reason, we can all goto edit, image size in PS,easy
    but adobe added this feature where you can choose 'bi-cubic sharpening etc etc.....
    and this is why i want my metadata kept in place and 72ppi or 96 as stated above. which is why i still believe it to be a bug.
    also this also acts as image license protector as i doubt 72ppi (1000 pixels wide) images would be much use in print for picture thiefs.
    (72ppi is just a starting base point as i understand this goes back to CRT monitors, other displays can go higher though i doubt 300ppi)

  • Mac user, PS CC 2014 latest version. When using "Save for Web" I bring my 900 x600px @72 ppi in to SFW and the output becomes 300ppi. The only way it stays at 72ppi is if I check "none" for metadata. I know to should not matter much, but I would prefer to

    Mac user, PS CC 2014 latest version. When using "Save for Web" I bring my 900 x600px @72 ppi in to SFW and the output becomes 300ppi. The only way it stays at 72ppi is if I check "none" for metadata. I know to should not matter much, but I would prefer to keep all my web jpgs @ 72ppi. Any solutions?

    It opens up as 900x600 @300ppi
    Here's a screenshot-

  • I am using adobe photoshop cs6. I am facing a problem. When i save any image as "save for web". After saving image it show cropped. An image show many parts of the image after saving the image. Please help me. Thanks in advance.

    I am using adobe photoshop cs6. I am facing a problem. When i save any image as "save for web". After saving image it show cropped. An image show many parts of the image after saving the image. Please help me. Thanks in advance.

    Just go back in photoshop and use the Slice Select tool, then just click and select the slice and hit delete - if you're not sure which one is the active slice just right click and find the one that has the Delete Slice option.
    It's possible you either added the slices by accident or if you received it from someone they just had the slices hidden. For the future, you can go to View > Show > Slices to display (or hide) slices.

  • Save for Web & Devices is changing resolution from 72ppi to 300ppi

    Hi,
    I'm writing an action to do the following.
    Image size - change resolution from 300ppi to 72ppi
    Automate - Fit Image - 600px x 600px
    Save for web and devices - JPEG medium.
    If I save at any stage (up to save for web & devices) the image is 72ppi
    However when I open it again after saving for web & devices and check image size it's 300ppi HOW?
    Am I missing something really stupid?
    Peter

    Hi Charles,
    Sometimes we have to go through meaningless steps...
    The spec for the job is to "automate" a process whereby we end up with a web suitable 600px JPEG of about 50k with © watermark.
    Of course they are expecting a 72ppi image, so its easier if thats what they get!!!
    The other requirement involves the fact that the web end of the business want to change the filename, so in order to keep a link, I write the filename to IPTC Title Field (using Peter Krogh's script)
    However I've now found that if I "save for web & devices" with copyright & contact info, I get IPTC title and 72ppi,
    So happy days....
    Many thanks, but now just more curious to know exactly whats happening!
    Peter

  • Blurry smart objects in Photoshop Save for Web jpegs

    I create graphs, etc in Illustrator, place them as Smart Objects in a master Photoshop file before outputing Save for Web jpegs to use as PowerPoint slide backgrounds. Everything created in Illustrator or Photoshop through that process (Quality 80 or 100 with any of the SfW options on or off) Save for Webs are blurry when imported (at 100%) into PowerPoint. The only way I have been able to get anything crisp in PowerPoint was saving a Photoshop pdf. However, that was only the text created in Photoshop. The Illustrator Smart Object part was still blurry. Anyone have any idea on the best process to combine Photoshop and Illustrator files into one file for import into PowerPoint as a clean, crisp background? At this point I am open to all suggestions.

    There are parts that are being added in Photoshop, hence going from Illustrator through Photoshop as a Smart Object and then onto PowerPoint. If I wasn't 5 months down the line and just nearing deadline, I would recreate everything in Illustrator. Assuming that I have to continue at this point down the Illustrator through Photoshop line of working, how do you designate pngs or jpegs to be 220ppi. Jpegs have a 1-12 quality (and 12 is still blurry).
    Note regarding PowerPoint, I embed the full-page image into the background so others that are using this can't move (by accident or on purpose) the background.

  • Activation of "Convert to sRGB" in "Save for Web"

    Hello,
    I am using a script scaling and exporting my image via "Save for Web and Devices". When I open the menu there's a checkbox called "Convert to sRGB" - I want to activate that checkbox via Script, as then I get the wanted colour results. I already had a look at the guide PDFs, but I didn't found that option, not as part of the export options array, nor generally elsewhere in the PS scripting guide.
    So here's my question: how can I activate that checkbox with script?
    Thank you
    Thomas

    I believe the 'ColorSpaceType' of the Export options is what you need.
    EDIT: Sorry, I may have misspoken, I was under the impression that was part of the Export Options, but it does not seem to be.

  • Script for using layer name in Save for Web command

    I am using the Save for Web  command (Illustrator CS2) to export layers to CSS so that each layer is  saved as a different jpg.  The only issue I have is that I want the  layer name to be part of the file name, but layer name is not an option  when I look at the "Edit Output settings" dialog for saving files.  Is  there anyway I can do this? I do not have experience writing or working with scripts.
    For example. My fiel name is flower.ai.  I will have 20  different layers (each containing a different color of the same image)  and want the exported file to be flower-scarlet.jpg,  flower-cranberry,jpg, etc. Right now I am looking at renaming all the  files manually, but as I am creating 40 images per product on my website, this will be very time consuming.
    Thanks in advance
    Christine

    Btw.. to make it work for JPGs, change the PNG options to the following:
    var options = new ExportOptionsJPEG();
            options.antiAliasing = false;
            options.optimization = false;
            options.artBoardClipping = true;
            options.qualitySetting = 100; // value of 0 to 100, 60 is medium, 100 is perfect
            options.blurAmount = 0;
            options.verticalScale = 100;
            options.horizontalScale = 100;

  • Image resize quality not saved in Save For Web Preset?

    L.S.,
    I have been working on an Action to create 12 separate PNG's for further use in my icon-software. What I do is basically this:
    Start out with a 256x256px image, save it for web four times in steps from 256, 48, 32 and 16px, (32-bit)
    apply some masks / layers, save it for web again four times from 256-16px,  (8-bit)
    set the mode to indexed colour / apply other masks and layers, and save it for web again from 256-16px. (4-bit)
    I let the sizing be done in the Save for Web step.
    The 256-sized pics give me no problem as they are not scaled down.
    The 32-bit pics give me no problem as they are scaled down, and antialias comes along, but they have 8-bit transparency: no problem.
    In the 8-bit and 4-bit versions from 48-16px, I definitely want no antialias in the sized down versions. So I set the resize quality to 'Nearest Neighbor'.
    However, Photoshop seems not to be able to remember different resize qualities in one Action.
    In every Save for Web-action that I do, when I set it to resize, it does so. But the resize quality is not taken from the setting. It seems to be taken from the last used or recorded setting.
    That is pretty annoying, because:
    - When I let the downscaled ones of the first 4, be downscaled 'bicubic sharper'
    - And I let the downscaled ones of the second 4, and third 4, be downscaled 'nearest neighbor'
    Next time I run the Action, all downscaling is done by 'nearest neigbor'. That ruins my downscaled 32-bit icons - they get jaggy.
    If I alter the steps in the action manually and set the first ones to 'bicubic sharper' again, suddenly all downscaled ones are done by 'bicubic sharper'.
    That ruins my downscaled 8-bit and 4-bit icons: they get antialias, to lime green, and that shows...
    I can save Presets in the Save For Web dialog, but as the groupbox already tells me: these presets only apply to the Image quality parameters, not to the sizing parameters. Those seem to be taken from the last run.
    I have one alternative to this: before every Save for Web step, I downsize the image myself, and undo the history step after saving. It's quite some work and I would just rather see that the sizing parameters saved in the Preset!

    That's never been saved as part of the S4W presets. Bloody annoying.

  • Swirly lines in Save for Web

    Hi,
    This is probably a basic thing, but when I use gradients in an image and then save for web and devices, I get swirly, kind of translucent lines if I save as jpeg or png.  If I save as gif, I get banding.  Is there a way to get rid of them?  I should be able to use gradients for a web image, right?
    Thanks!

    Hi shunithD,
    Do you mean copying and pasting each layer into photoshop, then rasterizing each element or layer?  I could try that.
    I'm wondering if my monitor is the reason the image looks bad to me.  I have af large lcd flat screen.  I'll check on my daughter's computer.  If it doesn't really show for other people, I'm ok with it as it is.  I just realized that the main parts that look swirly or blurry to me are the letters on the logo, and the checkered background.  Those don't have gradients, so maybe that isn't the cause.
    Thanks!

  • Halo in "save for web"

    Hi,
    When I use "save for web" in Illustrator CS2, I get a halo effect on the left and bottom of the image. If I use "select eyedropper color" this thin line on left and bottom becomes that color. If I use "none" it is white.
    I have tried clipping to artboard and have exhausted ideas.
    This happens when I save jpegs. If I view the image in a browser from clicking the browser button in the lower right corner of "save for web" this thin rule left and bottom does not appear. But When I drop the save image in a webpage, there it it.
    I do not have this problem in Photoshop. I think they are both driven by Image Ready?
    Thanks for any help, it is much appreciated.
    Kevin

    That's never been saved as part of the S4W presets. Bloody annoying.

  • Save Image size setting in Save for Web

    I'm using Save for Web (CS3) and scaling the file to different sizes with "scale image". I'm wanting to use the same scale settings for many images but when I save the pre-set the image size settings don't get saved. I'm wanting to use it as part of an action but the setting wont stick. Any suggestions? Alternative work flows?

    That's never been saved as part of the S4W presets. Bloody annoying.

  • A different take on the "Save For Web" color shift issue...

    Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
    But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
    Nothing new here.
    Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
    Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
    Anyone know of such a beast?   I would gladly pay for a plug-in that really works and fixes the problem.
    And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
    Anyone got a decent solution for this?

    Sorry, I think I'm being unclear.  This has nothing to do with individual monitor profiles.  In Proof Setup, "Monitor RGB" amounts to turning off ALL color management, and simply letting the monitor do what it will.  It is what the vast majority of web browsers do (even if the operating system provides color management, the browsers don't take advantage of it), so that is what you need to consider for images that will be viewed on a web browser.  If you convert your image to sRGB,  select Monitor RGB in Proof Set up, and turn on Proof Colors, you will see the image as it would appear on a web browser (after you save it as a jpg or use "Save For Web/Devices" to save it as a jpg).   Since almost everyone is running different uncalibrated monitors, there will be lots of variation in how it will look to them, so precise control of the color is unimportant.
    That said, I would expect the color on a calibrated monitor (such as the one I use when editing) to be reasonably close to the colors I am seeing while editing in PS.  To the extent a monitor deviates from "calibrated", those colors will vary, but a good monitor should show good colors.   Unfortunately, this is NOT the case, as my previous post shows.  The colors produced by the steps above are oversaturated and significantly shifted in hue.  There is, to my mind, anyway, no reason for this.  Adobe clearly knows what the mapping is between the colors as it displays them in PS and the un-controlled "Monitor RGB" -- that is, it is the color map they are using during normal editing display.  If they were to reverse-apply that map prior to saving it as a jpg, then the image would appear on a browser on that same (presumably calibrated) monitor very similar to what you set up when editing.  Anyone else viewing the image on a web browser with a calibrated monitor would also see good colors.  To the extent other viewers' monitors are out of calibration, their colors will suck, but there's nothing you can do about that.
    I guess in some sense I AM "asking for a Color-Mamangement-solution for a "non-Color-Management-situation", but specifically I'm asking for PS Color Management to do the best it can for non-Color-Managed situations that we all face every day.
    Does that make more sense?

  • Is it possible to run a Save for Web Batch?

    I am trying to run a batch on a bunch of ai files to save them as JPEG using Save For Web & Devices (so they can be saved with certain settings).
    I record a Save For Web action and then try to run a batch, but the batch just hangs at the Save For Web Dialog and waits for me to hit one of the Save/Cancel/Done buttons before continuing. Is there a way around this to get this so it can be a true batch process and not require me to interact with it?
    Thanks

    Ahh! That was it! Well, part of it.
    Now I got it saving, but I can't seem to override the target directory using the batch, but thats ok.
    Thanks!

  • Looking for a better solution to the "Save for web" color shift issue

    Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
    But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
    Nothing new here.
    Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
    Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
    Anyone know of such a beast?   I would gladly pay for a plug-in that really works and fixes the problem.
    And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
    Anyone got a decent solution for this?

    Chris
    I spent all day Googling and doing side by side comparisons of my old and new systems.
    My display is a Dell U2410. It has several presets, including sRGB and Adobe RGB. I've been using sRGB.
    On my OLD system, (Win XP, PsCS2, DwCS4) there seems to be no distinction between color managed and non color managed apps, even on this wide gamut display. I could capture (digital camera) in Adobe RGB, open and edit in PsCS2, save as .psd, convert to CMYK for print, or convert to sRGB for SFW. All images looked identical and they printed and displayed perfectly. I thought this was normal, and seemed logical. This also seems to be the source of my incorrect assumptions. I was trying to get my new machine to behave like my old one.
    So I get this new machine (Windows 7, PsCS5, DwCS5) and now (still in sRGB display mode) all color managed apps appear de-saturated. Non color managed apps are OK. If I switch the display to Adobe RGB, color managed apps are OK, but non color managed apps are way too saturated. From my investigation, I believe this is normal behavior on a wide gamut display. I've tried changing the Control Panel > Display > Screen Resolution > Advanced settings > Color Management options, but to no avail. Either I'm missing something, or Windows 7 is doing color management differently.
    It seems my only option now is to use Adobe RGB display setting for Ps, etc. and switch to sRGB for Dw and non color managed apps. Or, have 2 separate files for print and web. I've Googled 'til my eyes are numb and still not sure I'm getting this. Any enlightenment would be greatly appreciated.
    Finally, I don't see an edit function here, so I can't remove my previous incorrect reply. Moderator, please feel free to do so.
    Thanks

Maybe you are looking for