Dashboard > SmugMug > Home > Pros > File Preparation
Log In   View a printable version of the current page.
SmugMug
File Preparation
Added by Andy Williams , last edited by Anne Bean on Jun 05, 2008  (view change)
Labels: 
(None)

You have choices as to files and file preparation, for SmugMug.

Finished Work (Ready to Print!):

1. process your files in your photo editing program (e.g., Photoshop CS3, Bridge, PS Elements, The Gimp, Irfanview, Apple Aperture, Adobe Lightroom, or similar). Be SURE that you are processing in sRGB Color Space. If you work in PS in a different color space, that's okay - but when you save the file as a jpg, you must convert it to sRGB for upload to SmugMug. Here's why.

2. Do not resize, or otherwise crop your images on your computer. Keep the files in their native size and resolution. Today's cameras produce files with plenty of pixels, and are large enough to sustain cropping. Why not "pre-crop?" This will cause confusion in the shopping cart. Let the customers choose the crop in the cart - no worries if they get it wrong, you'll have your galleries on proof delay, so that you can see and adjust the crops yourself as needed.

3. Compression - Use Photoshop 10, or Lightroom 90. Both are Lab Quality and will yield excellent files for printing. If you happen to be uploading a large amount of files (say, from an event) and you want to batch compress them all for faster uploading, Photoshop 8 or Lightroom 80 will do just fine. You can find out how to make an action in photoshop, here.

Files you want to display and sell, but retouch, edit, adjust upon Sale:

1. Useful when you have lots of photos to upload and make ready for sale, but you intend to post-process them upon order. Like a big event, wedding, etc. OK first, I really recommend getting the display copies looking beautiful! There are lots of ways to do this fast. One, is batch actions in Photoshop. Or run them through Lightroom or Aperture with some really fast adjustments for exposure, color and white balance.

2. The second part of this process is, how large do you need to make the files? You have 800 shots and you want them to upload fast. Well, the answer is, "smash 'em!" You can leave the files in the native resolution (file dimensions) and just compress the heck out of them. They'll still look great on-screen, for web viewing and ordering. When you get a sale, you make your edits on the original raw or jpg, and you save it with much less compression (remember, Photoshop 10, lab quality), and then upload that one.

With either of the above two workflows, you'll need to pay attention to the minimum file sizes, in order to have your images available for sale. You can see our resolution requirements here. If the photos don't have large enough resolution, the print sizes are removed from the shopping cart to guarantee the best quality.

Read more about upressing and why DPI Doesn't Matter

Uploading

Now, to upload them! There are lots of choices, our standard uploaders, as well as many excellent 3rd-party applications written by Smuggers!. Many folks swear by Star Explorer, SendToSmugMug and also SmugBrowser Give them a try

Could someone clarify something for me?  I still want to crop my images on my computer to create the best composition, right?  Cropping as this wiki is stating is more for resizing...

I'm confused...

Ryan

Posted by Anonymous at Jun 24, 2008 14:22 | Reply To This

Hey Ryan,

Yes you do, but it's very very important to always keep crop GENEROUSLY, and compensate for any number of print sizes that will be ordered, and further cropped in the shopping cart.  For example, a portrait orientation image cropped to 4x6 should leave PLENTY of head and foot room, because if an 8x10 is ordered, you'll lose a significant amount from the top and bottom.  4x6->8x10 are usually the common extremes, so after you crop to 4x6 (which is native to most cameras) overlay an 8x10 crop box to see how it would print if an 8x10 were ordered, and don't forget bleed-trim http://www.smugmug.com/help/bleed-trim , and a nice frame obscuring a bit.

Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators