Photoshop slice tool and Save for Web image quality. Will it affect prints?

I want to slice a large photo into multiple smaller (4x6) printable photos to arrange in a 12x12 inch scrapbook binder pocket (made of of 4x6 pockets). I need to order separate 4x6s online so tiling in the print options is not what I need.
The slow way I know to do this involves cropping and saving each section (maybe even recording this action to do batch processing). However, another way is to use the slice tool to quickly divide up the sections then "Save for Web...". I can adjust some parameters, but I'm afraid there are other automatic adjustments that I don't want. For example, all images are converted to 96 dpi instead of the original 300 dpi. The number of pixels remains the same so I don't think there will be problems printing the picture.
My question is: does the Save for Web function reduce image quality in any way when printing (it is obviously intended to be used to optimize images for websites)? Are there settings in "Save for Web" that would optimize for high quality prints? Is there a better way to tile an image?
I have not yet compared any prints.
W7
CS6

If you understand that something will do something you do not want like convert to 96 DPI as long as it does not resample you can always convert back to 300 DPI. If you want 6 4x6 to form a 12x12 you must start with an square 1:1 aspect ratio image. That you resample to 12"x 12" at 300 dpi if you want 6 4x6 300 dpi images.
If the original images vary in size and aspect ratio you need to crop them square or add two borders to make them square.   The rest is easy to do with an action.
The square crop or border can be automated with a little scripting.  If crop  a center crop would be the route to go. My crafting actions package contains  more the a dozen scripts to be used within action. One is a plug-in script that would make center cropping a snap two steps menu File>Automat>AspectsRatioSelection followed menu Image>Crop.  Add a menu Image>Size set side to 12" and resolution 300 DPI and you have your  starting 12"x12" 300 dpi image.
Flatten the image make your first 4"x6" selection copy past to add it as a layer. Select the background select the next 4x6 area copy and paste repeat that process till you have added the 6 4"X6" layers. Then delete the background, Select all, target all layers and use layer>Align layers to selection>Top edge then repeat align to left edge. the Image>Trim you have your 6 4x6 in a stack.   You can the use Adobe Photoshop Script Export Layer to file.   All automated in an action however the last step Export layers to files is interactive for its not a plug-in script. So if you batch it you keen to hang around to interact with the last step for each image.
You could also write you own export script that would not need human intervention to use instead of Adobe interactive script.
Crafting Actions Package UPDATED Aug 10, 2014 Added Conditional Action steps to Action Palette Tips.
Contains
Action Actions Palette Tips.txt
Action Creation Guidelines.txt
Action Dealing with Image Size.txt
Action Enhanced via Scripted Photoshop Functions.txt
CraftedActions.atn Sample Action set includes an example Watermarking action
Sample Actions.txt Photoshop CraftedActions set saved as a text file.
More then a dozen Scripts for use in actions
Example
Download

Similar Messages

  • Adobe Photoshop Elements 2 and 'Save for Web' problem

    Hi everyone,
    I have used Photoshop Elements 2 for some time with absolutely no problems. However when I try to use the save for the web option I get an 'export could not be completed due to a program error' message.
    Nothing relevant is mentioned on Adobe's support site. After having gone through the usual 9 troubleshooting procedure I suspect that there is a problem with the 'Save for Web EL' plugin located in the PE 2 plugins folder. Has anyone else experienced this? Is there a way I can somehow find a functional plugin?
    Thank you for reading this post.
    PowerBook G4 DVI 667   Mac OS 9.2.x  

    I don't use Photoshop elements myself, but from Photoshop CS it works fine. I use JPG compression and optimization. First of all - make sure the file format extensions are all available. Applications/adobe/photoshop elements/file formats AND ALSO Applications/adobe/photoshop elements/photoshop elements only/file formats (here I am assuming the paths are the same or similar to Photoshop). Also, check the extensions disabled folder (Control click on Photoshop and go to package contents). If it's none of these, I suggest you check the settings in Elements when trying to save and make sure you are not using an option that conflicts.
    Also, check the Adobe forum. http://www.adobeforums.com
    Check for software upgrades also.
    You do have enough hard drive space and RAM I assume. If you are using PS Elements and virtual memory is on, you may not have enough phsyical space to save the file (but not likely)
    P.S. I see (after i wrote) that you are running 9.2.2 - so the paths will not be the same as if it was on OS X - but they will be similar.

  • Photoshop crashes when I try and save for web and devices. Making the image size smaller does not help.

    I'm trying to make a lopping .gif from an animation that I made. It's 147 total frames. It's crashed about 6 times now every time I either try and Save for Web or even just save the document on my desktop so in case it crashes I can reopen PS and recover it. Making the image size smaller (original size is 1920 x 1080 with resolution 72) does not help, it still makes the *ding* error when I attempt to save. I made the image more than half of the original size and the Save for Web box actually came up that time, but when I tried clicking save it said there was an error and PS crashed without warning.

    Look at the crash report for your Photoshop crashes see what they show

  • When I try and Save for Web in Photoshop CC I receive an error message saying 'The operation cannot be completed. The requested operation cannot be perfomed on a file with a user-mapped selection open'.

    When I try and Save for Web in Photoshop CC I receive an error message saying 'The operation cannot be completed. The requested operation cannot be performed on a file with a user-mapped selection open'. This happens with any of my files not just one in particular...
    Can anyone help solve this please?

    ELEMENTS 12 AND ELEMENTS 13
    Upgraded to 13 Thinking might resolve the issue.
    Was working fine up until we had "Tech" come in the office and "up grade some stuff"
    then all of a sudden i started getting this message, something happened but i don't have a clue what.

  • Slice Selection in Save for Web dialog in 17.1

    Since upgrading to Illustrator 17.1 I can no longer select slices in the Save for Web dialog, nor can I select a slice on a different layer than the one it was created on. Anyone else seeing this issue?

    Hi everyone,
    Our apologies for the inconviences. The product team is currently investigating the bug and is looking into providing a fix in the near future.
    In the meantime, please try the suggestions provided by Nolanco or jwsiddons as workarounds.
    Nolanco:
    In the save for web window if the image is bigger than window, zoom-out to view all artboard (Fit on Screen or less percentage), in this way is possible select any slice, when the image if bigger than window the wrong behavior take place.
    jwsiddons:
    My work around has been to use the slice select tool inside the artboard and go with File > Save Selected Slices.
    Thanks,
    Amy

  • What steps do I take to edit raw files and save for web use, such as Instagram, Facebook, Websites, and emailing?

    What Steps do I take to edit raw files and save for web use, such as Instagram, Facebook, Websites, and emailing?

    When you open a raw file it will open in Adobe camera raw. That is where you can do most of the editing. Then it will be placed inside Photoshop where you can do more if needed.
    Now you can use the save for web dialog to export your image as a png or jpg to use on those sites.

  • How differs soft proofing in View - Proof Colors and Save for Web - Preview?

    Hi, I'm currently confused with one inconsistency. My working space is Adobe RGB and I use calibrated monitor. After I finish my work on image I go to View -> Proof Colors -> Internet Standard RGB. Image looks terribly with the overall violet/purple hue. Then I open Save for Web dialogue, I check Convert to RGB and from Preview options I select again Internet Standard RGB. Now the previewed image looks as expected. The same results I get if I manually convert image to sRGB before soft proofing and saving for web. So... what's the difference between preview in Proof Colours and in Save for Web? Thank you for your opinions.

    Hi 21, thank you for your input. All what you say makes perfect sense, it is exactly how it should work and how I expected it works. My problem was, that while testing this theory in practice, I have come to different results. I expected, that if I stick to the theory (meaning keeping in mind all rules you perfectly described) I should get the same result in both soft proof and save for web preview. But... it was not the case. Save for web preview offered expected results while soft proof was completely out of any assumptions and colours were totally over-saturated with violet/purple hue. Also, Edit -> Assign Profile -> sRGB gave another result then Soft Proof -> Custom -> assign sRGB (preserve numbers), but the same as save for web preview.  What troubled me was why this is so.
    Today I've made tests on hardware calibrated monitor and... everything works exactly as you describe and as I expected.
    Then I went back to another monitor which is software calibrated (both monitors are calibrated with X-Rite i1 Display Pro). And again... I received strange results described above. So I did the last thing I thought and disabled colour calibration on that monitor. And suddenly... both soft proof and save for web preview gave the same result.
    Probable conclusion: soft proof and save for web preview (together with Edit -> Assign Profile) are programmed to use different algorithm which is evident on standard gamut monitors with software calibration. Question can be closed.
    Gene and 21, thank you for your effort.

  • Save for Web Image Is Offset

    I have AI CS4 on Windows Vista and have created an artboard that is 220 px wide and 88 px high. I then added a rectangle of the same dimensions as a background to cover the entire artboard. When I export it to Save for Web and Devices, the resulting image show a white boarder on the left. If I shift my background 1 px to the left on the artboard so that it shows white space on the right and overlaps on the left, it looks fine on the Save for Web export. Is there some set up that I'm missing to get a WYSIWYG conversion?
    Thanks,
    Curt

    If you are trying to save as a jpeg, gif or png then you are rasterizing the vector graphic, which is likely the case of the 'white' space.
    To get around this, try creating bleed of 2 pixels all the way around the artboard and then use the crop tool to crop the image to 220x88.
    An alternative to this would be to open the file saved for the web in Photoshop or Fireworks and fill in the white/blank space.

  • Photoshop CS3 color management "Save for Web" problem

    This problem is getting the best of me.......
    After spending 3 full days researching this problem, I am no closer to finding an answer than when I started. I still cannot produce a usable image through the "Save for Web" feature of Photoshop CS3. I have read web page after web page of "Tips, Tricks and Recommendations" from dozens of experts, some from this forum, and still I have no solution... I am exhausted and frustrated to say the least. Here's the simple facts that I know at this point.
    I have a web design project that was started in PS CS1. All artwork was created in photoshop and exported to JPG format by using "Save for Web". Every image displays correctly in these browsers (Safari, Camino, FireFox and even Internet Explorer on a PC).
    I have recently upgraded to PS CS3 and now cannot get any newly JPG'd image to display correctly. My original settings in CS1 were of no concern to me at the time, because it always just worked, and so I do not know what they were. I have opened a few of my previous images in CS3 and found that sRGB-2.1 displays them more or less accurately. I am using sRGB 2.1 working space. Upon openning these previous image files, I get the "Missing Profile" message and of course I select "Leave as is. Do Not color manage". CS3 assumes sRGB-2.1 working space, opens the file, and all is well.
    The problem is when I go to "Save for Web", the saturation goes up, and the colors change. The opposite of what most people are reporting. Here's another important point... new artwork created in CS3 does exactly the same thing, so it's not because of the older CS1 files.
    I have tried every combination of "uncompensated color", "Convert to sRGB", "ICC Profile", etc. while saving. I have Converted to sRGB before saving, and my monitor is calibrated correctly.
    I have tried setting the "Save for Web" page on 2-up and the "original" on the left is already color shifted before I even hit the "Save" button. Of course, the "Optimized" image on the right looks perfect because I am cheating by selecting the "Use Document Color Profile" item. Why do they even have this feature if doesn't work, or misleads you?
    Does anyone have any ideas what could be happening here? Why is this all so screwed up?
    CS1 worked fine out of the box.
    Final note: I do have an image file I could send along that demonstrates how it is possible to display an image exactly the same in all 4 of the browsers I mentioned with no color differences. It is untagged RGB and somehow it just works.
    I am very frustrated with all of this and any suggestions will be appreciated
    Thanks,
    Pete

    >> First of all... I'm using an Adobe RGB image master... I open it and get the Profile Mismatch Screen... I choose Use Enbedded profile... all looks well. Next I go to Proof Setup > Monitor RGB... again all looks well, no change that I can tell.
    This has further confused the issue on several points, not the least of which version PS you are doing this with?
    >> AdobeRGB> Convert to Profile > Working Space sRGB-2.1... all still looks well... but now, when I go to Proof Setup > Monitor RGB... I see the insane oversaturated look that is driving me nuts.
    That is your strongest clue...it sounds like you have a bad system or bad monitor profile. To rule out the monitor profile: Set sRGB as your monitor profile in System Prefs> Displays> Color.
    >> Adobe RGB image master... I open it and get the Profile Mismatch Screen... I choose Use Enbedded profile... all looks well. Next I go to Proof Setup > Monitor RGB... again all looks well
    That doesn't make sense, stripping an embedded AdobeRGB profile should desaturate the color in Softproof MonitorRGB, especially the reds -- you have something wacky going on there.
    At this point I think you need to review the links and get a grip about how color management and profiles work...
    BTW, forget about setting ColorSync in PS COlor Settings, use Adobe ACE.
    MO,
    I think SFW is fixed under CS3 :) By default it Converts to sRGB and strips the profile.

  • Actions and Save for Web

    I have tried to research this on my own searching the forum and asking users far more advanced than I am to no avail. I thought it might be possible that someone here would know whether what I want is feasible.
    I use the "Optimize to file size" feature in the Save For Web Panel constantly. I am planning on doing a large amount of conversions in the near future (by which I mean resaving .jpegs at a certain dimension and resolution. As far as the dimension and resolution go, there is no difficulty creating an action to do that. But the icing on the cake for me is have them all processed through Save for Web at a certain file size (for the sake of argument, say 500K). Yes, I know that the resulting images will vary in quality (obviously) because the end result will very much depend on their file size to begin with but that is not an issue for me for my purposes.
    Save for Web has various presets and allows you to save presets; however, it does not allow you to save the Optimize to file size as a preset. When I try to record an action, and go to the Save for Web, use the Optimize etcetera, the action created lists the quality of the image I process to record the action. So, for example, if my image is less than 500K, the quality recorded in the action is 100. If my image exceeds 500K, the quality might be 86 and that is what the action records. For whatever reason, what is recorded is the quality rather than the 500K. I am not sure if this is being written clearly enough to explain. I want every image to end up being 500K regardless of what the final quality is (quality being the difference between the original image and the image as saved by Save for Web). But actions are saving the attribute of quality rather than file size.  Sigh. I think I am just repeating myself trying to make it clear but probably failing. In case a screen shot helps clarify, here it is. If this can't be done, I would love to know that so I can give up trying.

    I want every image to end up being 500K regardless of what the final quality is (quality being the difference between the original image and the image as saved by Save for Web).
    You may have to resort to Scripting for this task … it may need a fairly convoluted approach but I think it has come up before, so someone may be able to help you over at
    http://forums.adobe.com/community/photoshop/photoshop_scripting

  • CS6 Save for Web image size limit (Retina)

    I have been designing for a lot of mobile sites these days, in particular: iphone retina display (640w).  Most of the time these designs can be long in the tooth with the height of these documents - exceeding 8000 pixels at times.  I noticed that 8000 pixels is the threshold limit for the "save for web" export.  Anything greater than 8000 pixels will be downgraded in quality on retina devices by scaling the image.  The jpg will still be the correct height and width, but when viewed on an iphone, you can easily see the degradation.   Images and text are blurry.  This is no bueno when trying to show a client what their site will look like on an iphone.
    So my question is, is there a work around?  A preference to be changed?  Am I missing something to get the full quality of my design comp in order to preserve retina display quality?

    Justin, what about your screenshot that I'm posting here:
    You posted that as an example of SFW downsizing to 78% to make its output be no taller than 8192 px, resulting in a width of 500 px. The iPhone will scale a 500 px wide image to make it fit the screen's 640 px width.
    And my CS6 SFW set to progressive JPEG (or anything else) refuses to allow a dimension to be greater than 8192 px. Here's the message when I try to make it larger:
    Likewise, the scale percentage cannot be made greater than the value which produces a dimension of 8192 px.
    Anyway, I'm glad you found a solution.

  • Photoshop CS3 crashing on Save for Web & Devices

    I'm having a problem with Photoshop CS3 crashing every time I use the "Save for Web & Devices" option. It allows me to open the dialog box and configure my file, but as soon as I click Save, it crashes. Has anyone else had this issue and if so, how did you resolve it?

    Then manually remove the prefs by reading this:
    http://forums.adobe.com/thread/375776?tstart=0

  • Ps 3d and filters and save for web are not working the way they should

    At work we just put cs6 on a w7 machine running 64 bit which has more than that required mem and or ram to run cs6 - unfortunately I have to use a windows based machine at work (cheapskates). Anyways. I see the 3d menus and the filter menu in PS but they aren't funtional. The filter menu drop down is there but Liquify is the only one that shows up the rest are gray. The option to choose 3d is also there but they are not functional (grayed out) - I took a look at some online tutorials on using the 3d effect in PS CS6 and Ive gone through it a few times and it still won't work for me. Also, in illustrator when I save for web - when I adjust the pixel dimensions and move the mouse over and click on the image that I am saving for web nothing happens and I'm completely boggled about how to get the image size to change in the save for web pane. Typically I am used to being able to input the the number into the pixel dimenion field and click on the image and the image resizes (on a mac you can either click on the image or hit return and the image will resize in front of your eyes!). I am unable to get this to work the way I am used to, this happens for me in both ill5 and ill6 on this piece of crap windows machine. Maybe I just need to reinstall? Maybe adobe has changed the way this works? Maybe a sledge hammer into this windows machine would solve all my problems!? IDK. someone help... help me... pleeeeaaaaaaaaaaasssseeeee

    unfortunately I have to use a windows based machine at work (cheapskates).
    This gets a "stupid comment of the day" medal. Seriously. These days Macs are just as convoluted and effed up as Windows was a few years ago - nice as long as everything works, but god forbid you have a problem. So by all means, update your graphics driver and be glad that you actually have that choice rather than having to wait half a year for Apple to fix it...
    Mylenium

  • Artboard name and save for web or export

    Hi when saving for web or exporting an artboard is there any way to pre-populate the save file name dialog box with the artboard's given name. It would save having to re-name the file and make good use of that metadata.
    Thanks in advance

    There is a way, but you have to use file >> export >> jpg.
    Worked great for me here where I have my artboards named the flavor, and when asked for fielname used "a".

  • JPGs and SAVE for WEB Save Too Dark

    I have seen many discussions on this topic and they always end in going to different websites and following what I consider to be a very complex set of instructions to fix it. The instructions are extremely intimidating for me as there are many steps messing with things on my computer, my monitor, and in Photoshop that I'm not comfortable with. What I really would love to see is a set 'beginner' instructions.  This is a common problem, I would love to see a more common kind of fix for those of us that aren't so technical.  <3
    The Problem:
    I create an asset and try to save it.  No matter the format, (except PSD) it saves Very dark and wipes out all of the detail with black.
    Thanks in advance, smart folks! 

    Impossible to say without seeing it. But it's probably much simpler than you think.
    Make a screenshot showing the two side by side. Press "Print Screen" on your keyboard and paste into a new Photoshop document. Save as jpeg and post here:

Maybe you are looking for

  • Question about JS code hinting

    When dreamweaver codehints javascript the code options have a little icon to the left i have seen red squares, hollow green circles, and yellow squares balanced on on it's its corners. what do these symbols mean?

  • M-Audio midisport and GB

    I have a M-Audio midisport 1x1 and wish to connect my Deger (electronic Bagpipe) to it and then into GB. I do have the software that came with the Midisport installed and the Midisport is connected correctly to my I-Mac. However I get nothing thru it

  • Codebase problem

    Both my client and server are in the same system, however, in different folders. They do not share other than Remote Interfaces. I want to test dynamic creation of stubs. However, I reciece Exceptions like Class not found exception when serializing o

  • Error messaging when trying to update apps

    When I try to update apps on the iPhone, I get an error message that reads "cannot connect to iTunes Store." This happens consistently. Any suggestions? Thanks. . .

  • Textedit in mountain lion doesn't show icloud option or versions.

    I upgraded from Lion to Mountain Lion this weekend.  Under Lion, Textedit would never ask me to save documents and I could access previous versions of the file, as expected.  After upgrading to Mountain Lion, textedit lost the versioning and does not