@Raster_Eyes  Ctrl+N (new file) is set to the "clipboard" preset by default, in other words the size of the file in the clipboard.   So all you need to do is ctrl+V to paste from the clipboard. ... View more

TIFF and PSD are pretty much interchangeable, you can use either one. Both formats support anything you can do to a file in Photoshop. But I still think PSB is the long term solution. 2 GB or 4 GB, you'll still hit the ceiling sooner or later. ... View more

Enhance applies to raw files in the Camera Raw processor (the plugin).   It does not apply to RGB files in the Camera Raw filter (from the Photoshop Filter menu). ... View more

Also, in Preferences / File Handling, make sure that the option Disable Compression of PSD and PSB Files is not enabled, so that compression is being applied. By @Conrad_C   Actually, this is a dilemma of sorts. You don't really need compression until the files get very big, like several GB - but that's the size range where compressed open/save times get absolutely unbearable, like several minutes. You could call that a rock and a hard place.   Personally, I disable compression and plan for disk space expansion as needed. Today you can get 20 TB server-class drives at fairly reasonable prices. ... View more

I've already changed "Maximize PSD and PSB compatibility" to "Never" in the PS settings, which does reduce file sizes significantly. I'm not concerned with losing compatibility with old versions of Photoshop. By @MissLiz   You also lose compatibility with Lightroom Classic. I would recommend keeping compatibility on.   I use a 60 MP Sony, and I'm trying to get into the habit of always saving as PSB right from the start.   The problem is that both Photoshop and Lightroom are lagging a bit behind here. There should be a PSB option in Lightroom preferences "external editing", and there should be an option in PS preferences to save to PSB as default.   There's no other way around it. PSD stops at 2GB, and you won't know when you're hitting that limit until you're actually saving the file.     ... View more

PNG is most certainly listed under Save A Copy:     You're missing a whole bunch of other options as well, so what is the image mode? ... View more

Also, maybe anecdotal since I don't keep track of how many times it happened and when, but it seems to me that it used to happen a lot more in the past than nowadays. By @Imaginerie   Unfortunately I don't have a solution for you, but I do have the same impression. I have seen something similar before, but most of the cases many years ago. Both Mac and Windows affected IIRC.   I always assumed it was GPU-related, possibly OpenGL/OpenCL which are now phased out, and in any case as Photoshop's advanced GPU integration improved, the cases dropped.   The only thing you can do is gather as much documentation as possible, and when you have enough, post a bug report.   Another general observation: when a problem happens on several unrelated machines, that actually narrows down the troubleshooting, because you can concentrate on the things they have in common (which is usually a lot more than you think), and ignore all the differences. ... View more

Are you saving to jpeg? Then you need to include steps in the action that makes the file conform to the jpeg specification prior to the save. Flatten all layers, reduce to 8 bit color depth, delete alpha channels.   An operating system change a while ago made it impossible to directly save out a copy if the file has properties not supported in the target file format.   Generally: Make sure the path is not recorded in the action.   If it's highlighted in blue in the save dialog when you record, the save path is a permanent part of the action. It's also possible to re-record that specific step without re-recording the entire action. Just double-click the step. ... View more

This is related to a larger issue, where several modules stop responding after Photoshop has been running for an undetermined period (5 minutes to several hours).   The affected modules are Save For Web, the Camera Raw filter, Liquify - and a couple more filters from the Filter menu, but these are the most commonly reported.   Quite a lot of users are affected, but apparently not all. Or maybe they're just not letting Photoshop run long enough, or don't use these particular modules much.   I've been trying to draw attention to this many times, but I don't seem to be getting any traction, so I've resigned myself to it. Relaunching Photoshop returns everything to normal for a while, so it's not actually stopping you from using these modules. Just an inconvenience. Note that they still work correctly in actions, so it's not the underlying functionality - t's just that the interface doesn't come up..   This bug only exists in Photoshop 25.11 and later. Previous versions did not exhibit this. I keep 25.9 installed for time-critical projects. ... View more

You're not actually saving to Lightroom. You're just saving to a location on disk, just like any normal save in Photoshop.   The reason it appears in the Lightroom catalog, is that a background script tracks the file from "edit in Photoshop" all the way to the final save from Photoshop - and then adds it to the Lightroom catalog, at that disk location.   In other words, you don't need to import the saved file to the Lr catalog - the script is doing it for you, automatically.   For the script to run, both applications need to be open and running. If you close Lightroom prior to saving from Photoshop, the script stops, and then you have to manually import.   All that said, your sort order in Lightroom can sometimes trick you. The file may be imported, but end up at the end of the filmstrip, so that you don't see it next to the original. ... View more

Yes - but let's not confuse the issue with facts 😉   The point is that the RGB numbers don't change. ... View more

Assign Profile does not change any numbers. That's the whole point.   And because no numbers are changed, but those numbers now refer to a wholly different coordinate system, the appearance of the image changes.   Convert to Profile recalculates all numbers into the new color space, the new coordinate system, so that appearance is preserved.   You can't move from one color space to another and "pretend" the numbers mean the same when they just don't.   Without color management and icc profiles, different color spaces would be impossible. There could only be one color space that we all needed to use all the time. ... View more

Yeah, funny how something that didn't exist until 2 years ago is now considered absolutely essential for basic usage.   It's also interesting how none of the dissatisfied customers mention "the competition" anymore 😉 There isn't any; no other high-grade image editor on the market does generative AI at all. ... View more

@Ged_Traynor  Ah, excellent catch. Yes, that's a problem right off. ... View more

OK, calm down. So if the file isn't corrupt, there is still an obvious problem here, because those timings are not normal.   And what I'm saying is that saving/opening directly from an external drive is a known potential problem. This isn't the first. We get posts like this all the time. It is always the prime suspect - and usually turns out to be the actual problem - in cases like this.   Nobody ever said it always causes problems. The point is that sometimes it does, and that can happen unpredictably. That's why it's not recommended.   All that said, if these problematic TIFFs all come from a scanner, that is another unknown factor to look into.   ... View more

Again, you need to go higher on the GPU.   The GTX 1050 is already many years obsolete and outdated, released back in 2016. It will be a guaranteed disappointment. The GPU is probably the single most critical hardware component for Photoshop now.   For Photoshop to work efficiently, you need a GPU from the RTX series. The earliest I would recommend is RTX 3050 or preferably 3060 - up to the newer RTX 4060 or brand new 5060.   I also notice it says "integrated graphics" in the specs. If you're using a discrete Nvidia GPU, make sure you do not use that intgrated GPU for anything. It will most likely conflict. Don't connect any displays to the motherboard connectors, those connectors go to the integrated GPU. Use only the connectors on the GPU itself. ... View more

Well, you are having a problem opening files, right? So you can't say it works without issue.   What I'm saying is - take this out of the equation first. Resave the file to your internal drive, see if it opens OK now. Copy it over to the external, copy it back, check if it opens normally. ... View more

@Patrick Baldwin  It works until one day it doesn't.   https://helpx.adobe.com/photoshop/kb/networks-removable-media-photoshop.html?x-product=Helpx%2F1.0.0&x-product-location=Search%3AForums%3Alink%2F3.6.6    "Technical Support strongly recommends working in Photoshop directly on the local hard disk. To prevent data loss, save files to your hard disk first. Then transfer them to the network or removable drive in the Finder or in Windows Explorer" (my emphasis). ... View more

This is most likely a corrupt file.   The main problem with external drives is all the extra layers of the interface, USB drivers, protocols, etc. That results in a vastly increased risk of file corruption - especially if you save directly to it. Never do that, save locally, then copy over.. Not only because of all these extra interface layers that complicate the save process, but because of worn or loose cables and connectors. It only takes a nanosecond broken connection, and your file is toast. Never touch the drive while transfer is in progress.   (the speed you mention is the nominal speed. You never get that in practice because of all the extra layers. An external drive will never be nearly as fast as an internal drive running directly over a PCIe bus) ... View more

As Conrad says. The Intel UHD 630 isn't up to current standards. It may work and it may not work, but either way it won't work well. You'll need a Nvidia RTX. The sweet spot is RTX 4060 (or the newer 5060), excellent performance for a modest price tag. The higher models will be faster for most AI-based tasks, but the rapidly increasing price is in most cases not worth it. ... View more

@Miss_Val22 And that conclusion is wrong. You can hardly blame Windows or Photoshop if it displays oversaturated on other devices. We don't know how those other devices are set up, what applications you're using and whether they support color management at all.   You keep saying you didn't have any problem before, but nothing about what your current settings are.   The most likely explanation is that you're not embedding the color profile. Without a color profile, all colors are undefined.  This can happen if you have "played with" color settings without knowing what you're doing. Reset everything to defaults!   This basically works correctly out of the box - but a special note if you use Export or Save For Web. Here, the "embed color profile" checkbox is unchecked by default. Once checked, it sticks.   Getting a Mac won't fix your problem. Photoshop works identically on both platforms. You can mess up color settings equally on both.   Start by posting a screenshot of Photoshop's Color Settings dialog. ... View more

Corrupt preferences can cause all kinds of strange and unpredictable behavior. The preferences file contains a lot more than your own user settings - it's the whole application configuration including lots of hidden parameters. It's complex. It's everything that has been modified since the virgin first launch.   Preferences are prone to corruption because they are rewritten on every application exit. An irregular shutdown, or interrupted shutdown sequence, can corrupt them.   Preferences are stored in your user account, not in the installed program files. An uninstall will not touch them, you have to manually delete it. ... View more

First of all, there is no reason to match all these profiles, and in fact you shouldn't.   Set ACR to open in the color space you prefer, like Adobe RGB. This profile will be embedded into the processed RGB file ACR sends to Photoshop, and override any other working space you may have set there. The main thing in Photoshop is to have policies set to "Preserve Embedded Profiles". This is the only important setting! Set your monitor to Native, not any emulation like Adobe RGB. The monitor has its own native color space, and that's fine. It's not supposed to match anything else. Any preset will only limit its capabilities. Run the calibration software. When it's done calibrating, it will measure the monitor's color space in that calibrated state, and write a monitor profile that describes how the monitor behaves, in detail. It's a standard icc profile. This profile is automatically set as system default for that monitor. You don't need to do anything. When Photoshop starts up, it gets this profile from the operating system. Photoshop - and, independently, ACR! - uses this monitor profile in a standard profile conversion, from the source color space into the monitor color space. Those corrected numbers are sent to screen. This way, the image is correctly represented on screen.   Get all these ducks in a row first, then come back if it still doesn't look right.   EDIT: looking closer at the screenshot, there is something strange going on in the highlights. It's clearly the monitor profile, but it's not clipping; it looks like the whole tone curve is different, in all channels. The takeaway from that is that it's not a defective profile, it looks like the wrong profile. Which again brings me back to what I wrote above. ... View more

@Michael26531295kdax  That wasn't what anyone said - it was just mentioned in passing as a possible cause (hacker-modified code). Which isn't entirely unreasonable, given the extremely high volume of pirated copies being offered on the internet, to unsuspecting buyers.   But the general consensus is that this is most likely the GPU driver. If not that, then possibly an overheating/malfunctioning hardware component.   The bottom line is in any case that a modern application cannot cause a BSOD. That's prevented by sandboxes and insulating layers. What the application can do, is trigger a BSOD by making specific calls that expose latent problems. ... View more

Agree with Axel. The only logical conclusion is that Lightroom is the real problem. ... View more

First of all, I would reset SFW preferences, not Photoshop preferences (you need to google that; I can't recall which keys to press as you launch. But either way you can rename/move the SFW settings folder in your user account, which does the same thing).   Secondly - the preferences are much more than your own user settings. It's the sum total of the application configuration, including lots of hidden parameters that are dependent on other settings. It's complex, and that's why corrupt preferences can cause weird and unpredictable behavior. ... View more

A preset will not work the same way on an RGB file and a raw file.   That has nothing to do with the applications, but is a result of how the data are encoded in the file. Any numerical adjustment is relative to the color space - the three primaries and the tone response curve.   A raw file is linear (gamma 1.0) with ProPhoto primaries - at least it is by the time the presets are applied (out of the camera it's grayscale).    Once opened into Photoshop, the tone curve is not linear, but can be gamma 2.2, 1.8, or the rather idiosyncratic sRGB curve. The primaries are not necessarily the same either, they can be sRGB, Adobe RGB or DCI-P3. All of this affects what a certain adjustment will do.   Just as a very simple illustration, setting the black point at 1 or 2 in a ProPhoto file will usually result in significant and noticeable black clipping. Doing the same in an Adobe RGB file will probably not be very visible at all.   And, since this seems to be an extremely common misunderstanding: you do not need to match color settings or profiles between Lightroom and Photoshop. The whole point of color management is that color spaces do not need to match. Preserving color from one to the other is what color management does. Any profile you set in Lightroom will be correctly treated and correctly interpreted in Photoshop. ... View more

@patricktheart  If you lose your preferences in minor dot updates, something's wrong, like not having full administrator privileges in your user account.   With a major whole-number version update, preferences do not carry over, they never have. There is an option to migrate preferences, but I don't recommend it because of the high risk of accumulated errors carrying over as well.   As for actions, brushes, anything that can be saved out - save out and keep it in a safe place. Then it can always be easily reloaded. ... View more

Let's get some realism into this. Have you scrolled down to check all the other resource hog processes running? This is just a random screenshot from a cold started machine, no applications running.  And no, I have no idea what all this is:   And if you take a closer look, these CC processes aren't actually doing anything. They're just sitting there.   A few hundred MB of memory is totally insignificant. Once you open some image files to do actual work, you'll be needing orders of magnitude more memory than you have installed in total, so Photoshop uses its scratch disk to handle all the data. However much you have installed, there's not enough RAM to handle that. That's not Photoshop, that's the reality of editing raster based pixel images.   If you have performance problems, this is not the reason.   ... View more

Do not attempt to install on a non-system drive! It's the wrong way to go about it.   You only save around 2-3GB, which is absolutely negligible in this context. It's a drop in the ocean. You can free up 10-50 times that by doing a thorough cleanup on your system drive!   In any case, a large part of the installation will still end up in your user account on the system drive.   Start by running disk cleanup in Windows. That can be surprisingly effective.    If you're using Bridge, purge the cache. Empty the recycle bin. Take a look around your user account. All of your applications dump things here that you probably don't need, a lot of it won't be removed again even if you uninstall the application.   Hibernation can be disabled, that alone can give you 10 GB or so.   There's an excellent free utility called WinDirStat that shows you exactly what fills up your drive and where it is.   And all this is just to get Photoshop installed. To actually get some work done, you need about 100-250 GB for the scratch disk. You can get away with less, say 50, if you work with small files, don't have more than one open at a time, and reduce history states to 2-3. ... View more