Include Metadata in Save for Web JPEGS

I notice in Photoshop CS 4 that there is a new "Include Metadata" menu option in the SaveForWeb and Devices.
I have a Javascript which creates multiple files based on various sizes and i would like to know how i can get the Metadata from the original PSD file to be included in the JPEGS.
This is important as i have a database which reads the metadata fields to know where to place the images.
this is my ExportForWeb step
function SaveForWeb(saveFile) { 
var sfwOptions = new ExportOptionsSaveForWeb(); 
   sfwOptions.format = SaveDocumentType.JPEG; 
   sfwOptions.includeProfile = true;  //remove ICC profile from image
   sfwOptions.interlaced = 0; 
   sfwOptions.optimized = true; 
   sfwOptions.quality = 80;  //image quality has been set to high
app.activeDocument.exportDocument(saveFile, ExportType.SAVEFORWEB, sfwOptions);
many thanks

This is what I use...
function Cs4SFW(FileName,Quality,MetaData,Profile,Progressive) {
  function cTID(s) { return app.charIDToTypeID(s); };
  function sTID(s) { return app.stringIDToTypeID(s); };
  Metadata:-
'MDAl'  All metadata 'MDNn'  No metadata
'MDCp'  Copywright  'MDCC' Copyright and contact
'MDAx'  All except camera info
Profile:-
'CHsR' sRGB Profile    'CHDc'  Use document profile
//Set defaults
if(MetaData == undefined) MetaData = 'MDNn';
if(Quality == undefined) Quality = 80;
if(Profile == undefined) Profile = 'CHsR';
if(Progressive == undefined) Progressive = 1;
    var desc7 = new ActionDescriptor();
        var desc8 = new ActionDescriptor();
        desc8.putEnumerated( cTID('Op  '), cTID('SWOp'), cTID('OpSa') );
        desc8.putEnumerated( cTID('Fmt '), cTID('IRFm'), cTID('JPEG') );
        desc8.putBoolean( cTID('Intr'), false );
        desc8.putInteger( cTID('Qlty'), Quality );
        desc8.putInteger( cTID('QChS'), 0 );
        desc8.putInteger( cTID('QCUI'), 0 );
        desc8.putBoolean( cTID('QChT'), false );
        desc8.putBoolean( cTID('QChV'), false );
        desc8.putBoolean( cTID('Optm'), true );
        desc8.putInteger( cTID('Pass'), Progressive ); // 1 = Optimized 3 = Progressive
        desc8.putDouble( cTID('blur'), 0.000000 );
        desc8.putBoolean( cTID('EICC'), false ); //Embed Color Profile, Bool
        desc8.putBoolean( cTID('Mtt '), false );
        desc8.putInteger( cTID('MttR'), 255 );
        desc8.putInteger( cTID('MttG'), 255 );
        desc8.putInteger( cTID('MttB'), 255 );
        desc8.putBoolean( cTID('SHTM'), false );
        desc8.putBoolean( cTID('SImg'), true );
        desc8.putEnumerated( cTID('SWch'), cTID('STch'), cTID(Profile) );
        desc8.putEnumerated( cTID('SWmd'), cTID('STmd'), cTID(MetaData) );
        desc8.putBoolean( cTID('SSSO'), false );
            var list2 = new ActionList();
        desc8.putList( cTID('SSLt'), list2 );
        desc8.putBoolean( cTID('DIDr'), false );
        desc8.putPath( cTID('In  '), new File( FileName) );
    desc7.putObject( cTID('Usng'), sTID('SaveForWeb'), desc8 );
    executeAction( cTID('Expr'), desc7, DialogModes.NO );

Similar Messages

  • 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.

  • Photoshop CS4 Save for Web JPEG Colors are Off

    Ok, I've scoured the web to see about finding a solution for this and tried every possible option and still I'm coming up empty handed. I have a website that I'm developing for a painter and have an image converted to sRGB, and the colors are where I want them to be. I use Save for Web, and every iteration suggested online for the, embed and don't embed, convert to sRGB and dont' covert, use document color profile, use windows, yada yada. Here's a recent example:
    when i preview the image with Firefox, here's the difference:
    The photoshop version is on the left and is the color that I want/need. The image on the right is firefox and saturated. If I save for web with embedded profile, safari is accurate, whereas firefox is saturated, so it's obviously discarding the icc and using some color space that I can't see in my file. I did notice that if I have my Custom, Proof and select Monitor RGB, then I can see what firefox will ultimately display and also what Safari will display if i have Embed ICC Profile unchecked in the save for web dialogue box.
    I know that CS2 and CS3 were easier and less squirrely with color managing web files, but I think CS4 has some juju under the hood. Am I the only one out there frustrated, or like other web developers just accept the inaccuracy and move on? Since this is fine art, I'm doing my best to dial the color in, but it's been all afternoon beating on this.
    Any ideas, I'm ready to install CS3 and see if my life will be easier, but I'm wondering if having Photoshop CS3 and CS4 will cause any issues.

    >> your logic
    That's my rant and I'm sticking to it.
    The OP wrote he doesn't want or need to discuss the pros and cons of embedding profiles in Web images, but for the sake of anyone else reading this:
    1) Embedded ICC Profiles increase file sizes (about 4K per image).
    a) I may have over 100 thumbnails and dozens of photos on one page,
    b) Plus, I may have an image sliced into many pieces.
    c) That additional 4k per image, per slice, will add up fast and may kill dial-up traffic.
    2) Very few computers use color-managed web browsers or calibrated monitors anyway, and
    3) Problems with matching/blending image's edges or background color with a filled box or page color.
    d) If I tag the image — on Mac colormanaged browsers — the color will mismatch the box/page color on managed browsers because the tagged image is being Converted to MonitorRGB, and the untagged page or box color is having MonitorRGB Applied.
    e) This matching or blending a pixel-based graphic to page color is a pretty big deal to do correctly in professional web publishing.
    f) If I publish untagged sRGB images/graphics, the box/page color will match the images and blend correctly in all browsers.
    I WILL QUALIFY my general recommendation about embedding profiles in pixel-based web images for the following reasons:
    1) You are posting fine-art images, creative portfolios, and are not worried about adding 4K additional data per image, per slice.
    2) You are not worried about having Mac visitors seeing graphic blends or photos mismatched to a background color.
    3) You understand only properly-profiled monitors and color-managed web browsers will benefit from your embedded profile — and it is likely 99% of web surfers don't have either — however, if you are targeting the one percent who do, then there is your number one best reason for tagging web photos with embedded profiles.

  • Batch runs "Save As" instead of "Save For Web"

    Hi,
    I recorded an action to use for batch automation which included:
    - resize image
    - Save For Web & Devices (to JPG medium setting)
    But when I try to run it, the Save As dialog box shows up after every image.  Also, the image optimization is different (turns out about twice the size).
    Wonder if anyone might provide some advice on this, thanks!

    You probably need a close no save step at the end of your action.
    In the save for web dialog, when you record the action, save to the folder you
    want the batch dialog to put the images. Then set the batch dialog as below.
    MTSTUNER

  • 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-

  • Psd turn into JPEG prewiews after save for web. Help!

    save for web>save>save optimised as>save>close. That gives me a jpeg (the previous was a psd), but in the form of a preview thumbnail, top right corner bent, loupe and "JPEG" on it. I did about 20 psd just fine,ending in the folder as jpg images, keeping their previous names  and the new  "jpeg" underneath. What happened?
    Not less odd, as I was shrinking the folder window, (bring in the bottom right corner, but this is probably not related), all the previous ones (the jpeg images) turned into preview icons, too. By moving the cover flow, they turned back into images, and by moving them again, they turned back into jpeg
    icons, this time, not with the loupe and the photos, but with 3 geometrical shapes on them. If I bring them back into Ps CS3 and save for web again, and then close, I get a "save changes to the jpeg document?" question,>save,  which gives me a regular save as window, and they stay images, and I could end the problem like that, but that might cancel the previous save for web. Help! goodnight now.

    I guess I have been sending all along (my almost 2 years of photoshop) inflated pictures of images (which however I take the care of reducing to 1000
    pixels from the original 4000 something that they originally are). What's odd for you guys, and normal for me, is that the computer went back to turning
    out  "normal" .jpg images, in small characters, like it has been doing all along, as if it went on a freaky spree yesterday, and I will probably go along with it, just because i don't know how to provoke deliberatly the JPEG with the loupes which appeared breafly yesterday, and that I am supposed to expect.
    I don't have any third party add on (do you mean plug in?) Only GF, sitting there, unused for a year.
    Of course now i am intrigued: Marion: what do you mean by :"this may be affected by normal Finder settings" ? Any settings that i can control to get those JPEG with loupes that I should expect all the time?
    Thanks everybody, i'll just leave the thread open for a bit in case somebody wants to shed some more light on my state of confusion.

  • PSE 7 - Save for Web - Now Defaults to GIF - Prefer JPEG - Can I change it?

    When using PSE 7.0 File > Save for Web, I generally want the files to be JPEGs. In previous versions, the file format on this menu would stay at JPEG once you set it there. Now, each time I open the menu it returns to GIF. Is there a way to have it default or hold as a JPEG in that field?
    Thank you!
    Beverly

    Is there a competing program that is as good as PSE that I could try? I am having a few annoying problems with this program and I think it is time to try something else. I was really excited to use the Photoshop family of photos, but these three problems are getting me down:
    1) I hate that the save for web function defaults to .gif. It is really annoying. The fact that they have a tool to fix it yet that doesn't even work makes me even more bummed out.
    2) When I try to go from the organizer to the editor, it literally takes about 20 seconds for the photo to load. That is a big waste of time.
    3) Sometimes, when I am in the quick edit mode, the zoom feature doesn't work. Other times, the cropping feature doesn't work. I click it back to the full edit, and those functions work. It is odd.
    It isn't like I am trying to split the atom here. I am relatively computer savvy, and all I want to do is edit photos. I have had many problems like this with the previous version as well as the latest one.

  • PSE6 Mac OS - Save For Web won't save JPEG high res setting in Preset

    Why is it that, contrary to documentation, Save For Web won't remember that I always select JPEG High for every photo file I save? Each time, it comes up as "Custom" Low quality, and can't even remember that I want JPEG format. My reliable old copy of PSE 2 that I've used happily for six years was capable of remembering what I wanted out of Save For Web. There are always surprises with new Adobe versions, I just wish there were some good ones once in a while...

    I tried on my mac machine with PSE 6 and saved one file as PNG-24 and some settings. I saved the file.
    next time when i opened any other image and tried using save for web, the previous settings were remembered.
    So, i m not sure if the issue you facing is common to all.

  • Save for web as PNG-24 with slices is saving in JPEG format!

    Hello all.
    I'm using Photoshop Extended CS6 13.0.1 x64 and when I save for web as PNG-24, all the slices from the project, the final result are JPEG format pictures. I tried the same but exporting as GIF and it keeps saving as JPEG. I tried Save As instead of Save for Web and it works, but this way I'm not saving by slice and not for web.
    Any idea why this happens?

    Found the solution. I had to select all the slices.

  • Is it possible to preset to JPEG High when using 'Save for Web...'?

    Hi,
    I am using photoshop elements 10. When I am ready to save an image under 'SAVE FOR WEB..' can I preset it to 'JPEG HIGH' cos right now it will pop up 'GIF'.
    When I am using PSE2, I am able to launch it as JPEG HIGH. Now, I have to click on the popdown menu to select 'JPEG High'.

    You need to right-click on the PSE desktop icon and choose "Run as Administrator".
    Then, open a file in PSE, use Save for Web and change all the settings to what you prefer. Hold down the Alt key and the "Done" button will change to a "Remember" button. Click it and then save your image. The settings will be saved and you do not have to run PSE as an administrator again.
    Ken

  • Export PDF as JPEG fails with Adobe Save for Web AI Error

    Hello,
    We have an Illustrator Javascript program to convert a PDF file to a JPEG.  It does some adjustments along the way, but I have boiled the script down so it just opens the PDF file, then uses the export method to export it to a JPEG file.  The problem is the JPEG conversion is failing.  When I run with user interaction layer set to DONTDISPLAYALERTS, as I normally do, it silently fails and continues; I do not get an exception, and the export method does not have another way to return an error.  When I do display alerts, I get a dialog box saying:
    Adobe Save for Web AI Error
    Could not complete this operation. An unknown error has occurred.
    It looks like this:
    What's weird is if I open the same PDF file in Illustrator and select File / Export it works fine.  I do get this error though if I select File / Save for Web & Devices.  I'm not sure why the export method would do a Save for Web though.
    The code looks basically like this:
    // Set filename, docName, destFolder
    file = new File(filename);
    sourceDoc = app.open(file);
    var fileSpec = new File( destFolder + "/" + docName +"_LARGE");
    var exportOptions = new ExportOptionsJPEG();
    var type = ExportType.JPEG;
    app.activeDocument.exportFile( fileSpec, type );
    For testing purposes, I have shortened the code so it is that, with the variable setting code above.
    Any help is very much appreciated.
    Thanks!
    ------Scott.

    I have not tested exporting without passing any options. You have however created a variable to an empty options object but not passed it.
    did you also try…
    app.activeDocument.exportFile( fileSpec, type, exportOptions );

  • Is save for web in JPEG format lossless when quality is 100%?

    I am trying to figure out if I can reduce optimised JPEG sizes further than what Photoshop can offer.
    My boss has recently questioned whether the file sizes can be reduced using lossless JPEG's further than the sace for web function in photoshop.
    From what I can make of it, lossy is the option on GIF files, and therefore I am assuming that the optimisation is lossless for a JPEG at 100 percent quality and lossy when the quality is reduced?
    I just want to clarify that I am saving images for the web at the smallest size I can without losing too much quality.
    All the images I save are 450px wide @ 75 dpi, but vary in length from 800px high to 1500px high, but have to be saved under 100kb.
    Can anyone clarify the lossless and lossy in JPEG format in save for web?
    Thanks
    Ray

    As c. says above, JPEG is a lossy compression - there is no lossless JPEG.
    PNG 24bit offers lossless compression, that is it performs compression analogous to a zip archive, whereas JPEG works by (in extremely lay terms) building a new image that resembles the original.
    GIF and PNG exports let you reduce the number of colours to get better compression - there are fewer pixel differences to compress at 8bit colour depth. Hence a 16 colour PNG will have a vastly smaller file size than a 24bit PNG, and depending on the image may be much smaller than a similar quality JPEG.
    Depending on how far off your 100KB ceiling you are, you may be able to improve your file exports by cleaning up the source image - reduce noise and if possible explore exporting as 8bit pngs with fewer colours - avoid using diffusion or noise in the export options. Find the balance between acceptable file size and image quality... photographs tend to be the hardest thing to compress because there's so much detail data, especially in darker (low light) areas.

  • Creating an action includes "Save for Web."

    Is it possible to create an action set that also will use the "Save for Web" ability.
    thanx,
    gholmes

    Yes. It's my recollection that save for web (SFW) will only allow you to batch files to the folder specified in the SFW step of the action. In other words, you can't process images to multiple destination folders using one SFW action (as you would by utilizing save and close as the destination in a "save as" action).
    J

  • Save for Web and XMP

    I asked the following in the Photoshop forum, but got no response. So, ...
    In Photoshop CS3, "Save for Web" now offers an "Include XMP" option. Just to get an idea of what's going on, I set print resolution to a distinctive value--312 ppi--then used "Save for Web" with "Include XMP" to save a JPEG. Then I reopened the file and tried to find some record of that 312 ppi value. Photoshop reports 72 ppi. In other words, it can't find my 312 setting and so it shows its default 72. Same thing in Bridge. In fact, the only way I can "find" my odd-ball 312 ppi is to view the file in an EXIF utility, which shows X and Y resolutions of 312.
    For now, I'm ignoring the fact that there isn't much point to saving print resolution for a web file, but still I'm wondering why "Include XMP" goes to the trouble of saving this value as metadata, if neither PS nor Bridge can find it later on?

    As far as I can tell, "Save for web" discards ALL print resolution data. This makes sense, because such info is meaningless for a web image. If you subsequently view the web-saved image in PS, it reports 72 ppi, because Photoshop shows this default value when it can't find print resolution data in a file header.
    And here's where it gets weird: The "Include XMP" option saves the print res as metadata, presumably for use later on if you want to review and/or change it. And sure enough, I can read the saved print resolution data in a 3rd-party EXIF utility. But Photoshop itself can't read it. Neither can Bridge. So, what's the point of saving this stuff, if it can't be found later on? Maybe I'm overlooking something, or maybe it's a bug. Who knows?

  • 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)

Maybe you are looking for