Version 2 is always safer, so use that - but from what I can gather, the most problematic profile policy is LUT. It seems to give problems in a lot of scenarios. So set it to Gamma (EOTF).   And then I thought I'd post some hard screenshots to back up my claims that I don't see any problems here. A blue sky is always first to highlight problems, so here they are. The blue is slightly muted to avoid clipping from ARGB to sRGB. This is one Adobe RGB file and one sRGB file, opened into Photoshop, InDesign and Illustrator: ... View more

    I think my question is legitimate: Switching color profiles in the Dell Display Manager under Windows 10 between CAL1 and CAL2 (sRGB and aRGB) was not resulting in image files in PS appearing different color-wise. Under Windows 11, it does so. Restarting Photoshop does not resolve the problem. By @raminolta   What is Dell display manager and what does it do, exactly? You need to find out what it does. Apparently, it doesn't do it correctly.   Two things need to happen if you want to switch the monitor between native wide gamut and an sRGB emulation: One, change the monitor's behavior. It doesn't matter how it is changed, just that it happens. Two, a new monitor profile describing that new behavior needs to be loaded into the operating system.   If those two happen, Photoshop will use the new profile on next startup, and display correctly. It has to. As long as Photoshop is given a valid and correct profile on startup, it will display correctly.   I'm running Windows 11 on two systems with wide gamut Eizos, and I switch between native gamut and sRGB emulation without any problems. ... View more

I can't quite make out what you're actually doing here, but I do get the feeling you're overcomplicating this and maybe changing settings that aren't relevant and you don't need to worry about. When people have problems with monitor calibration and profiling, it's usually because they do too much.   Take a breath. This is really simple.   The software measures the monitor in its current state and writes a profile describing that behavior. Done, there's nothing more you need to do. That profile is automatically set up in Windows as the default profile for that monitor.   When Photoshop starts up, it gets that default monitor profile from Windows. Photoshop then uses this profile in a standard profile conversion, from the document profile, and into the monitor profile. This happens on the fly, as you work.  These corrected numbers are sent to screen, thus representing the file correctly.   Now, if the monitor's behavior changes, regardless of how that change happens, you need a new profile as the old one is no longer valid. So you can either change profile in the OS yourself, or the calibration software can do it for you. Either way, Photoshop needs to restart so it can pick up the new profile.   Note that the monitor profile does not need to match any standard color space! Set the software to "native", not an Adobe RGB emulation. That just restricts the monitor's capabilities.   Just make sure these three components are present and correct, and the file has to display correctly. a document profile embedded in the file (sRGB, Adobe RGB, ProPhoto). a monitor profile that is a correct description of the monitor's actual and current behavior. color managed software that correctly converts from one into the other, and outputs those corrected numbers to screen. ... View more

@Chubbo  The color space setting in the camera has no relevance for raw files. A raw file doesn't have a color space, until it's encoded into one in the raw processor.   The camera setting only applies to in-camera processed files (jpeg or heic). ... View more

The action should close the original without saving. You don't want to overwite your master files, and this won't give any prompts. ... View more

AI is still dependent on humans... By @fbeaume Actually, there is increasing evidence that AI is dependent on AI. Few people realize this, but by the latest estimates, roughly 50 % of all content on the internet is now AI-generated...   I don't understand why more people aren't talking about this. ... View more

@tyleratwood    Thanks for reporting back! Yes, resetting preferences does seem to fix this in most cases. We've seen a lot of feedback to that effect.   I would generally recommend a total reset by moving the whole Photoshop Settings folder to the desktop. A "standard" reset will only address a subset of the full configuration. Apparently that was sufficient here. But moving the entire folder returns the application to absolutely clean, out-of-the-box factory state, as if it was the very first time it was installed.   For the few persistent cases, there is still the CC cleaner tool. This will also remove any leftover Windows registry settings. ... View more

Something has been corrupted in your preferences.   To completely reset preferences, go into your user accound and find the Adobe Photoshop 2026 Settings folder. Move the entire folder to your desktop. This returns the application to clean, out-of-the-box factory state. (Users > Your name > AppData > Roaming > Adobe > Photoshop 2026).   Save out any custom actions and brushes first. They will be wiped.   Preferences are rewritten on every application exit and so are prone to corruption by irregular shutdowns. Errors accumulate. ... View more

I've heard of this happening before, and uninstalling/reinstalling the printer driver always seems to fix it. Don't ask me why... 😉 ... View more

No problems here (also Eizo / Colornavigator 7). EDIT - I have PS / Ai / Id / LrC installed and they all display correctly and identically.   When these things happen, it's either a problem with the monitor profile, or a GPU bug. The conversion into the monitor profile is executed in the GPU, so those are two sides to the same coin. A problem in one can cause the other to fail, and it's not always easy to draw the line between them.   While Eizo's monitor profiles are very reliable, there is one gotcha: It makes LUT/table based profiles by default. That is known to be problematic in some scenarios (for instance, they won't work at all in MacOS). It also makes version 4 profiles, likewise known to be a bit problematic.   So first off, set CN to make matrix-based version 2 profiles, then make a new profile. In CN, matrix is known as Gamma (EOTF):   The "reflect black level" checkbox should be off/unchecked. It's for applications that don't support Black Point Compensation.   To test the GPU - which one are you using, BTW? - uncheck it in Photoshop Preferences. This shifts the display color management (the conversion into the monitor profile) back to the CPU in the traditional way.   Do not change anything in Color Settings. That is not where the problem is.   ... View more

You need to specify how you batch and what this batch executes per file, step by step.   As long as each file closes before the next one opens, memory/scratch disk is reused and recycled. The net result is that memory/disk consumption should never exceed what is required for the one single biggest file. On my own systems I have never observed any memory/disk buildup, and I run batches all the time.   What we have seen occasionally, is that the GPU uses excessive memory which is not recycled, but just builds up. I need to emphasize again that this is not normal and I have never seen it myself. But we do have a number of posts from users indicating that this is something that can happen.   Photoshop's use of a scratch disk is a very special case. All other processes and applications will go to the system pagefile on disk when physical memory runs out. That appears to be what is happening here. A system with an integrated GPU (Apple silicon or Windows laptops) will perhaps be particularly vulnerable to this because the GPU uses shared system memory, the GPU doesn't have its own onboard VRAM.   In short, this needs to be broken down, and where that memory goes needs to be investigated. I'm not sure what tools are available in MacOS for this. ... View more

OK. Two things.   First off, if this started suddenly, outside of any update cycle (PS or GPU or Windows), I would immediately suspect corrupt preferences. The preferences contain a lot more than your own user settings, it's the entire application configuration including lots of hidden and system-dependent parameters. Preferences are rewritten on every application exit, and so are prone to corruption by any kind of irregular shutdown. Corrupt preferences often look like application bugs and are frequently mistaken for that. Make sure to save out actions, brushes etc. before doing a reset.   Second, a more general problem is dual graphics. That's a known potential conflict. Photoshop uses the GPU in the data processing pipeline, it's not a simple one-way downstream flow. It goes both ways. Unfortunately, there is no way for Photoshop to control which GPU is called. That is entirely at the mercy of how the manufacturer has configured the operating system and the two GPU drivers. You can't send data to one GPU and get a result back from the other. In many cases it's necessary to completely disable the integrated GPU in Windows. Scroll down for instructions on how to disable the integrated GPU:  https://helpx.adobe.com/in/photoshop/kb/troubleshoot-gpu-graphics-card.html    ... View more

Photoshop is installed and running on your own machine. It's not an online tool, except for some optional functions that you don't need to use.   In other words, if Photoshop freezes it's a problem with your own machine. Please post the full Help > System Info from Photoshop. ... View more

You need to provide much more specific information about what you did and what you plan to do - and how.   But just for starters, are you logged in to the same account as the one you used when you uploaded this to CC storage in 2010?     ... View more

OK. Like you I have a handful of internal drives in the box, some NVMes, some high capacity spinning HDs (10 - 20 TB). Bridge opens to whatever directory it was last closed in, no problems in any of them.   However - I'm getting to a point eventually, so bear with me - we also have a company server, which I'm copying my finished master files on to (for the rest of the organization). And indeed, the only times I have have issues similar to what you're describing, with freezing and crashing, is when Bridge tried to open directly to that server location. So if I do use Bridge to access the server, I'm always very careful to go back to local folders before I close Bridge. That's just a basic precaution now. I don't really consider this a "Bridge problem" - server configurations are shrouded in so many layers of potential problems that I always approach it with caution.   The point is - folder access is likely playing a part here. So maybe there is a basic issue with that particular drive, maybe on OS level, SATA driver, something like that. If a particular drive is problematic while others are not, I'd replace that drive ASAP. ... View more

Right, so it was the profile. Now we're getting somewhere 🙂   That puts the spotlight on BenQ, once again. They really don't have a good track record at this point. I assume you're using their software with the Calibrite sensor?   So the logical next step now would be to find some other profiling software that actually makes healthy profiles. I'm not quite up to speed on third party vendors right now, but in the meantime there are two specific things you can look for in the BenQ software. First, if it's making LUT/table-based profiles, or matrix-based profiles. The latter is what you want. LUT profiles are known to not work well in MacOS. Second, if it's the version 2 icc specification or the version 4 icc specification. Version 2 is what you want here, it's always safer.   So start it up and run the full calibration and profiling, and look specifically for these options (if they exist here). Choose v2 matrix if given the choice.     ... View more

Just to make sure - did you relaunch Photoshop before trying the new display profile? Also, you did change the profile in MacOS, not in the monitor's own settings? Both are necessary, Photoshop gets the profile from the operating system when it starts up, and that profile is used for the remainder of the session.   To be honest, I've never really trusted BenQ, they have a long history of buggy profiling software and bad profiles. However, if sRGB exhibits the same problem, then we should be able to rule that out. ... View more

Well, what we can say with certainty here is that the normal color management chain isn't working correctly. With the settings shown in your screenshot, Photoshop and Save For Web will display absolutely identically (and they do on my end).   That can only be two things: Either it's a defective monitor profile, or it's a bug in MacOS's GPU driver component. Or even both - the GPU is handling the monitor profile conversion, so a defect in one can affect the other. But if this changes with mouse hover, that would point to MacOS.   What monitor calibration/profiling do you do? Where does the monitor profile come from? You can try to change it to sRGB IEC61966-2.1 and see if there is still a difference. Relaunch Photoshop when done.   It should be said that SFW is legacy code that hasn't been updated in a long time, and won't be any more, so if this is a new Mac, it could be a basic incompatibility that starts to show up now. Export As is intended to replace it, but unlike SFW, Export does have a color management bug on its own: the preview is incorrect, but the file itself comes out as it should.         ... View more

What it looks like to me in that screenshot, is that the application frame ignores the Windows taskbar.   So go into Windows Settings and Hide the taskbar (in case you worry, it pops back up when you bring the mouse cursor to the bottom of the screen). Does this bring the missing parts back?   With the taskbar hidden, resize the PS window. Click this button to "un-maximize" (or whatever it's called) the PS window - then you can resize it freely: Unhide the taskbar and re-maximize the Photoshop window. Better?   BTW - if the blue line doesn't appear, it's because you're not dragging far enough. Grab the panel by the header, and drag until the cursor - not the edge of the panel - hits the designated docking area. ... View more

Probably just unfortunate wording. "Not functionally limited"; not "unlimited number". But yes, they could have used clearer language.   There is usually no free lunch 😉     ... View more

True, the color picker only gives you 8 bit initial values. That's about the smallest difference your eyes can separate, so 16 bit values here wouldn't be of any practical use.    But from that point, everything operates in 16 bit mode - soft brushes, adjustments, gradients, masks, etc. And that's where 16 bit depth matters. Every pixel value can be shifted in 32 768 increments instead of 256.   This is where someone regularly comes forward to point out that Photoshop 16 bit is really 15 bits + 1, so it's not 65 536, but 32 768, as if that somehow breaks your files. This was done deliberately, to avoid / ensure a fixed middle value (can't recall which).   The only exception is selections. Selections are legacy code and always 8 bits. It's a common misconception that masks are also 8 bit, but that's not correct. Masks are full document bit depth. ... View more

For autorecovery to initiate, the file has to be saved to disk at least once. Files that you just open, work on and close again without saving, won't be recovered.   After a crash, recovered files should open automatically on next launch. There is no point in looking for the folder - if the files don't open automatically, there's nothing there. I haven't seen a crash in years, so I can't test - this is just what I know about how it works.   I suppose it's possible that the application crashes at the exact instance the recovery file is saved, and in that case it's probably gone. ... View more

By default Photoshop saves back to the original folder the file came from.   You can change it here. With this box unchecked, it saves to the previous location:   Saving to original folder will not overwrite as long as it's a different format. A raw file can never be overwritten under any circumstances. ... View more

It could also be that your files contain old and now incorrect print metadata. This might cause the printer driver to crash.   To delete all print metadata from the file, hold the spacebar as you click Print in Photoshop's File menu. ... View more

Photoshop is using the correct GPU. Thanks for the info! By @ggruberphotog   There is no way you can know that.    All Photoshop can do is say "send to GPU and return result", but it cannot know which one. That's a black box in the operating system.   Photoshop's use of the GPU is much more complex than the simple consumer applications and games a dual-graphics laptop is primarily designed for. It's not a one-way downstream flow. The GPU is used in the actual processing pipeline. You cannot send data to one GPU and get it back from the other. ... View more

Only one graphics card.  By @ggruberphotog   No, you have two listed in the system info: the RTX 5060, and an AMD integrated GPU. I suspect that's your problem.    GPU memory consumption can be very high. Hibernation dumps the memory content to disk, both physical RAM and virtual (system pagefile). The thing is, your integrated GPU and the RTX may return conflicting data.   Dual GPUs is a well known potential conflict. There is no way for Photoshop or ACR to control which GPU is called, or which application calls go where. That is entirely at the mercy of how the laptop manufacturer has configured the operating system and the two GPU drivers.   Disable the integrated GPU as described here: https://helpx.adobe.com/camera-raw/kb/acr-gpu-faq.html  ... View more

@ExUSA  It's pretty simple, actually. When you open a raw file, you get that many pixels wide by that many pixels high. That's the resolution. ... View more

Yes, as I said, it's almost never a perfect 3:2.  Sticking to your 3000 pixels long side, you may get 3000x2002, 3000x1999, etc.  I've had a large number of Nikons and Sonys over the years, and I don't think I've ever seen a perfect 3000x2000.   Your display is irrelevant here. This is about the camera sensor pixels. ... View more

Excellent link, but to condense it down: A blend mode is not a "thing", it's a relationship. The outcome depends not on either of the two layers, but on the relationship between them. ... View more

This is just the sensor's actual aspect ratio (it's almost never a clean 3:2).   3000 x 2001 becomes 300 x 200 simply because of rounding. You can't divide a pixel.  ... View more