Maximize Compatibility vs Storage Optimization

I'm working on a new project that will require me to store thousands of PS files. I have noticed that the maximum compatibility option affects the end files size significantly. For example the original autogenerated PS file starts at 32 MB, and jumps to 57 MB when saved to maximize compatibility and shrinks to 21 MB when the option is not selected. What exactly am I losing by not maximizing compatibility? If it is just the file preview image and the ability to use on very old builds of PS, it might be worth the savings on storage space. The PS files don’t contain any new features where backsaving will be an issue. I was able to open the non-max comp file in CS2 with all its layers. I've attached a link to the example file I'm referring to. Thanks for the help.
https://app.box.com/s/35ssi02qaiz48jxgaten
-Brennan

Nothing more than you mentioned comes to mind.
Only thing about the composite previews (that won't be generated/saved) is that non-Adobe software may rely upon them. That said, many 3rd party programs now can see into .psd files and deal with the contents. The FastPictureViewer codec pack is one such example - it can thumbnail even .psd files not saved with Max Compat.
For what it's worth, I switched to Maximize Compatibility: Never quite a while ago, and I have had no problems. I don't share my .psd files with others much.
-Noel

Similar Messages

PS CS2 lens correction causes "Maximize Compatibility" issue in LR

Question: why does PS CS2/3 convert the layer "Background" to "Layer 0"?
This is the problem (and solution):
I encountered the widely discussed "Maximize Compatiblity" issue with a bunch of PSD files (slide scans) that contained only one layer. Puzzled as I was that the layer thing apparently could not cause the problem, I reopened some of those files in PS CS3 and I noticed that each of them had had a lens correction. Just to make sure I was on the right track I applied a lens correction to a file that had been already imported into LR successfully and used the SaveAs command and unchecked the Maximize Compatibility option. The new file could not be imported into LR. So no more lens corrections? - I thought.
A closer look on the troublesome files made me learn the (only) layer had been renamed from "Background" to "Layer 0" after the lens correction was made. I used the "Flatten Image" command and this turned it back into "Background". After this, the file could be imported into LR without a problem.
I can now apply this trick to all troublesome files that have had lens corrections and thus avoid the huge increase in file size (130MB is a lot already).
Now I write this for those of you who have the same problem and are still puzzled (to help out) but I also would like to have some insight into why PS CS2/3 lens corrections mess with the layers.
Thanks.

>My conclusion would be that LR can only import PSD files that meet the following requirements:
>1. must contain only one layer
>2. that layer must be called "Background"
Your conclusion is only partially correct.
Lightroom will import multi-layered PSD files that have been saved with the preference for "Maximize PSD and PSB File Compatibility" set to On. This is clearly stated in the Release Notes and Help documents:
>Photoshop format (PSD)
>Photoshop format (PSD) is the standard Photoshop file format. To import and work with a multi-layered PSD file in Lightroom, the file must have been saved in Photoshop with the Maximize PSD and PSB File Compatibility preference turned on. Youll find the option in the Photoshop file handling preferences. Lightroom saves PSD files with a bit depth or 8 bits or 16 bits per channel.
As to the original point -
PS CS2 lens correction causes "Maximize Compatibility" issue in LR.
Photoshop renaming Background Layer to Layer 0 is a Photoshop issue, not Lightroom. When it occurs the files effectively becomes a multi-layered file, even if there is only one layer (i.e layer 0). Why using the Lens Correction filter causes the background layer to be renamed is currently unclear, but I have raised it in the "appropriate" place. In the meantime, I recommend that you set the Maximise Compatibility preference to
Always. Doing so will save non layered files as normal and multi-layered will have the
necessary* composite preview. You can continue to use the flatten command to fix the errant files.
*Enabling the Maximise Compatibility preference ensures that Photoshop creates a composite preview of multi-layered images. It is intended to enable applications that can't read layers to preview the images. Lightroom cannot read multi-layered files, therefore the composite preview MUST be present in such files.
>Has anyone noticed different behaviour with the Lr v2 beta? I'd hate to double the size of all my multilayer PSDs just so they can load into Lr(?)
Lr 2.0 will function as per Lr1.x; i.e. not using Maximize Compatibility when saving multi-layered files will mean that they are not compatible with Lr2.0.

Remove 'Maximize Compatibility' on pre-existing PSDs...

Preferably via a batch function, since I have 50 or 60 files... maybe more, that I've been saving with maximized compatibility. I don't need the feature and never did, but used it because I was being ignorant and 'better safe than sorry'-minded.
Anyone have any ideas?
I tried disabling 'Maximize Compatibility' and re-saving the files, but this didn't result in reduced file sizes as far as I can tell.

Set your file handling preference for Maximise Compatibility to "Never". Record an Action of "Save As" with any file - the name and location will be overriden when using the Batch setup in the screenshot that follows the Action screenshot. It definitely works with CS6 on OS X 10.6.8, at least.

Maximize Compatibility vs QuickLook in Mac OS X

I found out that QuickLook in Mac OS X doesn't work properly for PSD documents if the file is saved without Maximize Compatibility feature. If you press space bar, only white canvas appears and not the actual document. I don't want to use this feature because I don't need the compatibility and all the files are much smaller without it. However, as I work with a lot of PSD files I am used to use QuickLook a lot. Is there a way to have maximize compatibility disabled and at the same time be able to use previews with QuickLook? Thank you.

samuelg0rd0n wrote:
Is there a way to have maximize compatibility disabled and at the same time be able to use previews with QuickLook?
QL relies on a compatibility image in a layered PSD (a single non-Background layer is still a layered document), although if the PSD contains only the special Background layer then that will be used by QL. Maximize Compatibility results in a compatibility composite in the PSD, otherwise a solid white compatibility image is embedded and that's what you see in QL.

Using actions and batch processing to maximize compatibility on old psd files

My apologies if this has been answered -- in my search I saw that it was asked multiple times, but not answered.
My goal is to be able to import 5 years of PSD files into Lightroom that were originally saved with maximize compatibility turned off. These files are in shoot folders within year folders.
I have been trying to do this with an action and batch processing through Bridge (Tools>PS>Batch). After switching preferences to MC=always, I have tried an action with a Save command, but that doesn't switch the file to max compat on. Save As does, but it also fixes the destination of the save in the action to a specific folder. I want to be able to overwrite the existing PSD file, leaving it where it is.
Has anyone successfully tackled this issue? I know I can handle it folder by folder, with an action for each folder, but that just wouldn't be cool.
Thank you

L Show - Yes, I found a way and did just that.
Everything as you wrote, using the save-as option. Yes, it will put the folder name into the action BUT it will override it when you run your batch from bridge IF you check in the box "override action save-as command" (and destination: save and close).
Works like a charm (although slow - not utilizing the multiple cores :( )

Maximize compatibility problem

I've been using LR 2.5 and now 2.6 for a while now and am finally prompted to post. From time to time, I have problems importing files. If it's a PSD file, then typically I get the old chestnut about saving with maximize compatibility turned on. Which is something I always do, because the LR installation notes told me to do it. I also have problems importing the occasional JPEG, maybe no more than 1 in a 100. I can barely import TIFF files at all -
more than 50% of the time LR just gives me the familiar gray rectangle and the warning mark. Keep in mind that these TIFF files aren't fancy - they're just boring old 16-bit RBG or sometimes 16-bit grayscale straight from my scanner. I would estimate that I can't import about 80% of my PSD files (I have CS2) in spite of having "maximize compatibility" turned on. I've tried tried re-saving the PDF file. Doesn't work. I've tried adding a layer, then saving. No joy. I've tried SHIFT-CTRL-ALT-e to create a whole new rolled-up layer. No way. On larger files PS even confirms that it's saving a full resolution composite. Do you think it makes any difference to LR? No on your life.
I've put up with this for some time, and now I'd like to know if this is normal. I've almost given up trying to import PSD files, and that doesn't seem right at all. The problems seem to occur more on larger files (say, 100MB+) than on smaller, but that may be my imagination. I've most recently had the problem on a 16-bit greyscale PSD file on which I've made some extensive changes and re-saved (compat mode is ALWAYS on). LR keeps rejecting it. I've just now resorted to creating a 16-bit greyscale, single-layer file in PS (all of 1.5MB) and LR STILL won't import it! Bridge thinks it's fine. Bridge thinks they're all fine.
This is really getting me down. How on earth do photographers with large legacy collections of PS files (i.e. every last one of us) survive? Pity help people with TIFF files, I feel sorry for them. Perhaps it's just some fragility with my system? I'd love to know.
Thanks for any hints or tips. I must be missing something obvious.
Regards,
-darryl

Ed,
There may be a CS2 vs. CS4 difference which is just confusing things.
If you look back my original posting in this thread, you'll see that I had problems importing TIFF files as well. Those problems were fixed by removing my Lightroom preferences file. Since then, importing TIFFs has been fine.
I don't know what "com.apple.Photoshop.plist" is - I'm guessing it's where Photoshop stores preferences on a Mac? I am currently using a Windoze laptop, but am planning to get a Mac, so will soon be educated in the finer things of life!
Regading Photoshop "asking" or not: what I notice is that if I use Photoshop standalone, then it does indeed ask. If I start Photoshop from Lightroom, then it doesn't ask. Some magic must be happening behind the scenes because even from the very beginning, starting Photoshop from Lightroom on an existing image always worked fine (I would have had Maximize Compatibility set to Always in those days). My problems were always with importing pre-existing PSD files which were saved with Maximize Compatibilty set to Never.
I'm glad you managed to make some progress, though. The more I use Lightroom, the more I wonder how I ever survived without it.
Regards,
-darryl

"Maximize Compatibility in PS" message when trying to open PSD in Lightroom

Upon importing a PSD saved image into Lightroom, I get this message: "The files could not be read. Please re-open the files in Photoshop and save them with the 'maximize Compatibility' preference enabled." I then opened the file in PS, went into preferences, changed "Maximize PSD and PSB File Compatibility" to "Always", and re-saved the image. I get the same message upon trying to import the image again into Lightroom. Help! Regina

Hi Jeff,
I just did a 'save as' with the new preferences, and, because I could not re-save it back to the DVD where it came from, I saved it to my document folder and was not prompted to save over the existing file. I just tried again to re-import it into LR, and I was successful (on 2 occasions). I am not sure what I did differently the first time(s). I am positive that this situation is going to be a big pain in the heiney, though, on future imports. Can you fill me in on what I can do to prevent this from occurring?
Thanks!
Regina

Maximize Compatibility option to save for earlier versions?

1. Where is the Maximize Compatibility option in CS6 to save to earlier versions?
2. Does this option still exist in CC? If so, how is it enabled?
Thanks.

Ctrl or Cmd k to open your Preferences, go to File Handling, then right at the bottom of this section:

Bulk save as psd file not saved with Maximize Compatibility selected in preference

I want to do a "bulk save as" for psd files that were not saved with Maximize File Compatibility selected in Preferences. I'm trying to import those files into LR5 but I get an error message. Or is there a work around for resolving this issue? I have both PS CS6 and PS CC. Also Bridge for both. I've just subscribed to LR5.

LR does not support Layers, PSD files may have layers so you may have a problem using LR to do what you want to do.
Set your Photoshop Preferences to always save with Max Compatibility.
Record a save action one step menu File>save.
Then use Adobe Bridge menu Edit>Find to find all your PSD files.
Then select all and use menu Tools>Photoshop>Batch and if your lucky and don't catch an Adobe Bug Photoshop will start and the Batch dialog will open, You can the set the Save Action Set and the Save Action all the PSD selected in the Bridge should open and saved.
I cancelled the search short here the search for all psd files could take a very long time and did not run the batch.
You will have a better chance not catching an Adobe bug if Photoshop is not up and running when you use the here. Bridge may try to start a different version of Photoshop then the one running when you use menu tools>Photoshop>Batch. Bridge CC was updated to start CC 2014 there is no bridge CC 2014.
This site scale image poorly you can scale them if you view them in a new tab or window.

Still no compatibility between Storage Client Library v3 and emulator?

Hi,
According to this blog post:
I'm apparently unable to post a link, but here's the text from the blog. I'm sure you can find it via google if interested.)
<<<<
Storage Emulator Guidance
As mentioned above an updated Windows Azure Storage Emulator is expected to ship with full support of these new features in the next couple of months. Users attempting to develop against the current version of the Storage emulator will receive Bad Request
errors as the protocol version (2013-08-15) is unsupported. Until then, users wanting to use the new features would need to develop and test against a Windows Azure Storage Account to leverage the 2013-08-15 REST version.
>>>>
So it seems there was not compatibility between the storage emulator and Storage Client Library v3. I'm wondering if that is still the case. I get a 400 error when calling container.CreateIfNotExists() when pointing to local storage, but no problem pointing
to production storage. I'm using SCL v3.0.2.
Thanks...
-Ben

Hi,
Please see
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/c961d0df-e6ab-4563-958c-b3646ee2cd9d/the-value-for-one-of-the-http-headers-is-not-in-the-correct-format?forum=windowsazuredevelopment#16892f11-498d-4975-aa4b-adfa12b03fea
Here is a snippet of this thread.
Storage Emulator 2.2 is currently incompatible with Storage Client Library 3.0.0.0. This has been mentioned in Storage Team Blob as well:
http://blogs.msdn.com/b/windowsazurestorage/archive/2013/11/27/windows-azure-storage-release-introducing-cors-json-minute-metrics-and-more.aspx (Please
read "Storage Emulator Guidance" section towards the end of the post).
It may be fixed in the next version.
Hope this helps
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Is there a way to maximize my 160gb storage without buying a 3rd party program like "CleanMyMac"?

I only have 29gb remaining of my 160 total and it just doesn't seem that I should be using that much. over 60gb is identified as "Other" which I have no idea how to improve on that. Any ideas?

I don't know why Mike got on his rant about MacKeeper. While it is true that you should avoid it that doesn't ap[pear to be what you are talking about here.
I would however echo Mike about CleanMyMac and/or CleanMyMac2. They are both to be avoid also. They are worthless and only known to cause problems on a Mac.
Instead try http://www.thexlab.com/faqs/freeingspace.html

Photoshop Extended version compatability

I have Photoshop CS3 Extended on both PC (Windows XP) and Mac (OS X Leopard). I'm able to upgrade the PC to CS5 Extended but not the Mac.
My questions are:
1 - Will Photoshop CS5 extended work on Windows XP?
2 - Are CS3 and CS5 backwards compatible - if I work on a document in PC CS5 will the Mac CS5 version be able to open it? I know there will be some things that would not translate backwards, such as Puppet Warp and some of the newer masking and layers features, but I'd still like to be able to work on more basic functions of masking, cloning, etc. on both computers.
Thanks for any help,
Marcy

Noel Car boni wrote:
For the most part, a document saved from Photoshop CS5 will be no problem to open in CS3. There's a "Maximize Compatibility" setting in Edit - Preferences - File Handling section that you'll want to set to "Always".
-Noel
My take is that the compatibility setting should be set based on the kind of work one does. I have it set to "Never". When you check this setting ON you tell Photoshop to save along with all your layers another entity, which is a flattened version of the image. This, makes every PSD file you save larger by a non trival amount.
So this setting should have no effect regarding Photoshop to Photoshop version compatibility. All Photoshop versions understand layers and do not need a flattened version. It's intended to maximize the compatibility between Photoshop and any other program that does not know about layers but reads PSD files. If you have many of your PSD files going to, for example, Lightroom or Premiere then set it to "Always". If not, you can set it to "Ask" or "Never" and save yourself a lot of storage space.
Paulo

Backwards compatability Id CC to CS6?

Hello all
I've been asked to pose this question on behalf of my front-office coworkers who are struggling with editing documents created with Id CC in Id CS6. As of 2014 we are now a big merged company and our West Coast division is making marketing materials in the CC version of InDesign while us folks in the Midwest are still trying to wring the last bit of usefulness out of CS6. I don't see a high degree of sophistication in most of this material so I'd think we could work something out here until everyone gets on the same software boat.
Since I'm not a regular user of either version of Id can someone lay out what is needed to ensure a decent level of backwards compatibility with documents made with CC? Is it as simple as in Photoshop where you can select maximize compatibility' or 'save as' a previously acceptable format (like .pm4 in the old Pagemaker)?
Yeah, that last reference really shows my age eh?
Thanks for any advice

Hey thanks Bob (hello again, Happy New Year and all)
I fear that simple suggestion might warp some creative sensibilities with the CC users but it seems like a reasonable solution.
Let's see what happens. Oh, BTW I have caved and signed up for the 'PS/LR CC Special'. It's like my Netflx subscription - too busy to use it for now, but soooomday...

File compatibility between cs3 and cs5

Hi,
What are the compatilibity issues between Photoshop CS3 and CS5? Can they be used together without much (if any) issues?
Thanks.

They can happily coexist on the same system, as long as you've got the disk space. Photoshop has always been like that.
You'll only be able to run one at a time, at any given instant, though.
Regarding file compatibility, I don't how much it's required to open a file in Photoshop CS3, but the newer version does offer a "Maximize Compatibility" preference setting for saving .psd files. On occasion I've opened .psd files in Photoshop CS3 saved by CS5 (using the aforementioned setting) and I haven't seen any issues at all.
-Noel

"Maximum compatibility"

Is there a way to know if a psd file has been saved with maximum compatibility? I have a bunch of PSD files that I want to move to light room from iPhoto and my understanding is that they will not move to light room unless they were saved with maximum compatibility. Or do I have to move these files back to Photoshop and re-save them with maximum compatibility checked in the preferences?

Yes, it is necessary: Maximize Compatibility « Julieanne Kost's Blog
So go ahead and resave and keep that setting to "Always".

Maximize Compatibility vs Storage Optimization

Similar Messages

Maybe you are looking for