That still doesn't sound right. Any color space will be correctly represented in Photoshop, as long as the color profile is correctly embedded. Rec 2020 or Rec 2100 should display exactly the same as sRGB or Adobe RG or anything else (excluding minor gamut clipping where the monitor gamut exceeds the document colorspace gamut).   I just opened a file in both Rec 2020 and Rec 2100 from ACR and the colors were all correct.   So unless your monitor profile is broken (which would explain it) - it's most likely HDR <> SDR settings. I don't have an HDR display so I can't test that. ... View more

File corruption is always caused by hardware failure. A very common cause is saving directly to external storage or over a network connection. Both are unsupported and officially warned against for this reason. Save locally, then copy over.   Until you save them out, actions are kept as part of your general preferences, which is a version-specific "Settings" folder in your user account, separate from the program files. Each version has its own folder, and when a new version is installed, a new blank Settings folder is created.   Automatic updates is a problem here, and I always recommend to turn that off. You'll be notified when an update is coming, so you can take your precautions. I'd also recommend to keep the old version installed until you're confident the new one runs properly.   Actions and brushes should always be saved out. Workspaces and shortcuts can't for some reason be saved out - but as long as the old version (or its Settings folder) is still on disk, they can be copied and pasted over.   ... View more

All of this becomes much easier to understand when you realize that Photoshop doesn't work with sizes. It only works with pixels.   The physical size of a document is determined by whatever "pixels per inch"-number (ppi) is assigned. The ppi number can be arbitrarily changed, thus changing the physical print size, but not actually changing the file itself. The pixels remain the same - unless the ppi value is used as a parameter for resampling the pixel data.   Always start with pixels. Then see what the ppi value ends up as at a given size, or what the size becomes at a given ppi value. One goes up, the other goes down.   Pixels per inch means exactly what it says. Read it literally: pixels per inch. It's just a simple formula that translates from pixels to physical size units whenever that's needed, such as for printing or calculating font sizes (a point is a physical size unit from the old days of lead typesetting).   On screen ppi is wholly irrelevant. ... View more

Creating a history step for layer visibility is an option in the History panel options. Open the panel's flyout menu (the hamburger icon).   If that doesn't work as expected, it's corrupt preferences and a reset should fix it. ... View more

I save it by re[eatedly hitting ctrl+s. By @katem43656392   Then you don't know where it's going, it depends on several other factors. The file is there, it has been saved, you just don't know where.   Always use "Save As", at least for the first save, so you can control exactly where you're saving. Set up a logical folder tree on disk.    The recent files listings in the home screen is just a convenience feature, to let you quickly pick up where you left off before lunch. It is not a live path to the actual file, just a passive pointer to a certain address on disk, which may or may not contain the expected content. It is not intended for archival file management. ... View more

I tested this before I posted it. By @Charles_I   You can test this too:   Save with metadata "none" and open in Photoshop. It will open as 72 ppi, because that's the default value Photoshop assigns when there is no ppi value in the file. Then open it in some Microsoft application. Here it will open as 96 ppi, that's the default value there, when there is no ppi value in the file. I need a higher resolution than 72   No, that's not what you need. What you need is a higher number of pixels. The ppi number is irrelevant on screen, which is why a file coming out of Save For Web/Export does not have a ppi number at all. It's been stripped from the file. ... View more

@scobot  The point here is that you can't divide a pixel. Any measurement will always be rounded to the nearest whole pixel.   Photoshop works only with pixels. Physical measurements are derived and secondary, not a native property of the original data. The measurements are determined by whatever (arbitrary) "pixels per inch"-number (ppi) is assigned to the document. ... View more

Try to disable the home screen in preferences. I have a feeling that's where the glitch is. ... View more

Using ACR on jpeg, settings are written to the file header, not a separate sidecar. "Reset" in ACR/LrC, or "Clear Settings" in Bridge. ... View more

Whenever something seems to change when merging layers, it's because you are not viewing at 100%. The merged result is correct. The preview is misleading and incorrect. 100% has nothing to do with size. It means one image pixel is represented by exactly one physical screen pixel. For performance reasons, all blending and adjustment previews are calculated on the on-screen version of the image. When you are zoomed out, that means a resampled and softened version of the image. Pixel levels are averaged out. You get a lot of intermediate values that aren't there in the full original data. When you merge, commit an adjustment etc, the numbers are re-calculated on the full original data, pixel for pixel. Viewing at 100% avoids all this. You see every pixel before and after, and so nothing changes. ... View more

I'd just bulk select the original files and "write metadata to files", then "read metadata from files" in the derivative folder.   There are several ways to copy metadata in LrC, but it seems to me the simplest is just to embed it in the files. ... View more

I normally use about 1% luminance gaussian, then 0.5-1 % chroma gaussian - but with gaussian blur about radius 0.15-0.3 after each. Obviously, actual values will vary with resolution and noise level of the original.   That usually matches sensor noise pretty well. Not perfect, it still has a slightly "papery" texture, but good enough for most practical purposes. I also tried Grain in the ACR filter, but that looks distinctly synthetic. This is zoomed to 200%:     I don't do this often enough that I feel I need a dedicated setting for this. I'm OK with knowing it can be done when I need it.   ... View more

I'm with Jane. I vote nay.   Not that I ever use generative ai toys...eh, tools, so it doesn't affect me 😉 ... View more

@SirWalterRaleigh  Nvidia's model number convention is that the last two digits refer to the performance level, while the first two digits refer to the generation/version.    So 4060 is a newer version of the 3060. Improved, but not a "power up" step.   4070, 4080 and 4090 are the more powerful models up from 4060. That's what I referred to as "higher model numbers".   Currently they are at the 50xx-generation series, but same convention for performance (and price): 5060, 5070, 5080, 5090.   I have two machines, one with a 3060 and one with a newer 4060. Can't say I notice any significant difference between them. ... View more

@Glenn 8675309  The OP already has their actions saved out to .atn, so there's no need to copy the (possibly corrupted!) actions from the old preferences. ... View more

Do you mean Lightroom and Camera Raw? They will use the same presets retrieved from the same folder.   Lightroom and Photoshop don't, and can't, use the same presets. A preset in one doesn't work in the other. ... View more

Actions, once loaded, are kept as part of your general preferences, which are stored in your user account. All your preferences are loaded from here when the application starts up, and, crucially, rewritten on every application exit.   So two things can happen here. One, folder permissions in the operating system may be incorrectly set or corrupted.   The other is irregular shutdowns or crashes. This can corrupt the Preferences files themselves, and that can be fixed by resetting preferences. The most complete and reliable method is to move the whole Adobe Photoshop 2026 Settings folder to your desktop, allowing a fresh one to be rebuilt.    You've already saved out your actions to .atn, so that's covered. Do the same for brushes and any other customizations you want to keep. Shortcuts and workspaces can usually be copied from the old Settings folder and pasted into the new. ... View more

Dual graphics? That's a well known potential conflict and you may need to disable the integrated GPU in the operating system.   (Attachments are currently broken. Insert images directly in the reply box toolbar). ... View more

Photoshop crashing is nearly always a GPU problem. Post the full Help > System Info, just paste the whole thing in a reply.   I haven't seen a Photoshop crash in many, many years, on either of my two working machines (and I do this for a living). It's rock solid.   To get rid of the Home screen, make sure you have an empty PS workspace when closing the application (with the option turned off). To get rid of all popups and annoying notifications, check "Quiet mode" in Preferences. Generally, a lot of things people often complain about are available as options in Preferences.   You can have multiple folders open in Bridge. Now, Bridge does have one problem, which is that thumbnail/preview generation can be slow when the folder hasn't been opened recently. ... View more

Stamp visible should work regardless. It takes all visible layers, pixel layers and adjustment layers, and produces a merged layer which it puts over whatever layer is currently selected. I just tested it with and without a Curves layer on top, and it works normally in all cases.   I'd start by resetting preferences. Corrupt preferences can do the weirdest things. ... View more

@irealm  You're missing the point. In trying to pinpoint an issue like this, it's crucial to know the environment the application is running in. No bug exists in a vacuum. A bug isn't a thing; it's an interaction. Some get it, others with a different system don't. ... View more

@Earth Oliver  No, if color management works as it should, sRGB will display correctly, not oversaturated, on a P3 wide gamut display.   This happens when color management breaks down and doesn't work - defective profile, missing profile, GPU bug.   Also, the working space doesn't matter. The embedded profile will and should override it - as long as you don't touch the default policy to preserve embedded profiles. Don't ever change this. ... View more

@Earth Oliver  This isn't a raw file, it's the Camera Raw filter used on RGB data in Photoshop.   Until you save the file from Photoshop, it will still carry the raw file extension, in this case .NEF. An RGB file format has not yet been determined. ... View more

OK, here's the thing about monitor profiles:   It needs to describe the actual and current behavior of the monitor.   That's it; that's its sole job. The profile is used by Photoshop to remap the numbers correctly for sending out to the monitor. The profile is a map, and like any map it needs to represent the actual terrain. If the map is wrong, you go wrong.   The monitor profile is loaded into the application at launch, and that profile is used for that session. If the monitor's behavior is changed, e.g. by changing a preset on the monitor, the profile is no longer valid. Then you need to change to the appropriate profile in the operating system and close down and relaunch the application so that it can pick up the new profile.     ... View more

Is the color profile embedded in the Photoshop file?   If it is, it doesn't matter what the document color profile is (for the purposes of this discussion) - any profile will be correctly represented, and if they are all correct, they are identical.   Please set the status bar to show "Document profile" and post a screenshot, like this:   I still suspect a bad/broken/incorrect monitor profile. That usually affects applications differently, that's a smoking gun.   What is your monitor profile, where does it come from, what made it? Look it up in Windows Settings > System > Display. ... View more

Well, dual GPUs can be a general problem with a range of symptoms. The advice is usually to disable the integrated GPU altogether. Since the GPU is doing actual image processing for Photoshop - including converting into the monitor profile - it's obvious that multiple GPUs is just a potential conflict.   You can disable the GPU in Photoshop, but ACR requires a functional GPU to run at all. So you can't really test it that way.   But you can test the monitor profile, by replacing it with a system profile like sRGB, Adobe RGB or Display P3 (depending on type of display). Relaunch all applications when done, the profile is loaded at application startup.   If the symptoms disappear, you know you have a bad profile. Are you using a calibrator to make the monitor profile? ... View more

Do you have any layers above the one you're opening in the ACR filter? This is apparently a layered file, but the ACR filter doesn't show the full layer composite, only the specific layer selected. Any adjustments above are ignored.   If that's not it, it's most likely a broken monitor profile or a GPU bug. These are two sides to the same coin, since the conversion into the monitor profile is executed in the GPU. A problem in one can cause the other to fail. ... View more

@hopeful_Laughter4659  I think you misunderstand. Photoshop is not "online", it is still installed on your machine and works from your own physical drives. There is an option to store files in the cloud, but you don't need to do that. ... View more