This is a binary image that consists of either black or white pixels. To properly see that pixel structure on screen, you need to view at 100%.    100% has nothing to do with size. It means one image pixel is represented by exactly one physical screen pixel.   You're viewing at 11.4 and 12.5 % zoom. That means 7100 pixels in the image are downsampled to around 750 pixels on screen. That's a lot of data that needs to be interpolated, and in that process, crisp black/white edges inevitably get replaced with fuzzy gray pixels.   Different screen resampling algorithms will put very different results up on screen.   If you view these two at 100%, you will see that they are identical and it exports correctly. ... View more

Yes, that was my point. It's physical RAM plus the system pagefile, so it can exceed installed RAM.   The scratch disk is not included.   But normally, system paging slows down everything and should be avoided.    We have seen this excessive paging on Mac and Windows in equal measure. As I said, a lot of people have fixed it with a clean install and clean preferences. So I'm inclined to think it is a bona fide Photoshop issue, but one that only occurs with a somehow faulty installation. My money is on corrupt preferences. ... View more

Yes. You just need to look at a laptop to see there are severe physical limitations. No one can suspend the laws of physics, despite marketing that tries to convince you otherwise. Don't buy that. ... View more

When this happens, the problem is that the conversion into the monitor profile isn't functioning correctly.   That conversion is executed in the GPU, so it could be a GPU driver bug - but in most cases it's a defective monitor profile. Sometimes, a problem in one can cause the other to fail.   The mathematics of the conversion can and usually will differ between different applications, which is why it can fail in one application but still work in another.   How is your monitor calibrated and profiled? What calibrator are you using? If you're not using a calibrator, you'll be getting Dell profiles distributed through WIndows Update, and these manufacturer profiles are surprisingly often defective in different ways.   You can test the monitor profile by replacing it in the OS. Replace the current profile with whatever standard profile is closest to the native response of the monitor (sRGB, Adobe RGB or Image P3). It won't be entirely accurate, but it will tell you if your current profile is the problem (which it most likely is).    Remember to relaunch Photoshop when the profile is changed. The profile is loaded when Photoshop starts, and it will use that profile for the remainder of the session, until next launch. ... View more

It's listed as "Extras", so you're forgiven for missing it. It also hides guides and a few other things.   But if you look below the main entry, there's also listed the individual elements that go under this umbrella, including selection edges - which means you can make a custom shortcut just for that if you wish.   Generally - if there's a menu item for it, you can make a shortcut (and also for tools and panel menus). ... View more

The Camera Raw filter shows up in history.   The Camera Raw processor, if used on an embedded raw file opened as smart object, shows up indirectly as "edit contents".   The initial opening from ACR just shows in history as "open".   ... View more

Tell us exactly what you're doing, step by step. ... View more

Content aware fill creates content based on what is not selected. So this is entirely expected.   What you need to do here is make a mask on this layer. Then bring in whatever background you want, created by whatever means you want. Put that under the people layer.   (and then of course, finish up by adding the proper shadows. In this case you can keep the shadows on the base). ... View more

Ctrl + H ... View more

I am puzzled as to how your Mac reports 75GB of RAM usage on a system that you say has only 64GB of RAM. By @davescm   We've seen some cases of that, both on Mac and Windows, and this has puzzled me too. So I took a closer look at how Windows Task Manager reports memory usage. It turns out, somewhat to my surprise, that the scratch disk does not turn up here.   What it has to be, in addition to physical RAM, is the system pagefile. That's the only possible explanation.   That also explains why people report their whole system slowing down. A saturated pagefile will do that.   In any case, we've had several indications that the root of the problem is a corrupt install, or, more likely, corrupt preferences. In many cases, people have fixed it with a completely fresh install with completely fresh preferences. ... View more

Yeah, even more likely. ... View more

But the original image is in png format, and the save as jpg process pops up the window, which is a bit annoying.   By @dublove   There can be lots of explanations for that, like 16 bit depth - not allowed in jpeg.   Generally, you always need to consider what properties are allowed in what file formats. There really isn't much you can do in Photoshop before PSD or TIFF are the only possible file formats.   I still believe this is at the root of your whole problem. ... View more

When Photoshop crashes it's almost always a GPU problem. Please post the full Help > System Info. ... View more

We've seen quite a lot of these cases where the problem turned out to be either a corrupt install or corrupt preferences. A totally clean install with clean preferences fixed it.   Preferences are significant. It contains a lot more than your own user settings. It's the sum total of the application configuration, including lots of hidden parameters and dependencies. That's why corrupt preferences can cause unpredictable and inexplicable behavior. Preferences are prone to corruption because they are rewritten on every application exit.   One basic precaution I always advise is to not migrate preferences, despite the obvious temptation of seamless updates. Small errors accumulate and get bigger. ... View more

Actually, we have to make a distinction between "Save As" and "Save", and this is one of those things you need to consider when recording the action.   A Stephen says, "Save As" will always record the absolute path. It has to. There is no Save As without telling it where to save.   But a simple "Save" will not record anything beyond the save operation itself. It will overwite the file and save it back to wherever it happens to be. No path is recorded, no name is recorded. So both stay the same (I just tested this to be sure).   I suspect what happened to the OP is that he recorded a "Save" action on a jpeg, but with added layers or 16 bit depth. Then, of course, it can't be saved as jpeg - which forces the Save As function instead. If you complete that, you have an action with a specified save path.   Disregarding the bad practice of resaving jpegs for the moment, the way around this is to include steps in the action that makes the file comply with the jpeg specification. Then a simple Save will be available and working as expected. ... View more

Post the full Help > System Info from Photoshop. ... View more

Most likely conflicting dual GPUs.   Disable the Intel UHD 770 as per section 6 & 7 here: https://helpx.adobe.com/photoshop/kb/troubleshoot-gpu-graphics-card.html  ... View more

What is your eyedropper sample size set to? ... View more

@Bewitched_character5DEE  Lightroom Classic has exactly the same tools and controls as ACR. There is no reason to use ACR.   Note that even though Bridge itself is free, ACR won't run from Bridge unless there is a licensed qualifying application installed.  That would normally be Photoshop, since ACR is a Photoshop plugin. I have no idea if Lightroom or Lightroom Classic (which one is it?) counts as a qualifying application, but I wouldn't be surprised if that turns out to be where the problem is.   The Photography plan, with both Photoshop and Lightroom/Lightroom Classic, is less expensive than any single-app plan. So you might want to reconsider your plan. ... View more

Backup of all your photos. Which you always should have in any case. ... View more

@dublove  Keep in mind that an action does exactly what is recorded. Always go over the steps, and always test.   And yes, @ExUSA is right. Make sure the file name and save path is not highlighted in blue when you record the action. You cannot use Save As, you have to use a plain Save, and you cannot change anything.   All that said, I would never, ever, ever, have an action that overwites the original. That's just too dangerous...   I have a lot of actions that save to different formats, and they all end with "close, no save" so that the original is always sent right back to where it came from unchanged. Effectively, you're saving out a copy. There are different ways to set the destination without risk to the original. ... View more

Well, you just need to go through the hardware chain. It could be a drive about to fail, or possibly bad RAM.   I would in any case advise you to make backups ASAP if you haven't already. Don't open anything, just copy off your drive, then check the files from the backup. ... View more

Reposition doesn't do anything to the image, no perspective correction. It just moves the frame as-is. In most cases you will get misaligned parts. Perspective correction is usually needed.   I've never been a fan of these rolled-into-one combo functions. If you split it up into its constituent components, you have a lot more control over the process: Stack > Auto-Align > Auto-Blend.   One importan aspect you can control is which frame serves as the reference frame that all the others align to: that's the one you put at the bottom of the stack. If you level this, the final result should be too. ... View more

That looks like corrupt files - try a different card reader/cable first of all. File corruption is always caused by hardware failure. No exception.   What you see initially in Lightroom and on the camera screen is just the embedded jpeg preview. It is just a very small part of the file, and it can be fine even if the main data are corrupted. ... View more

"unexpected end of file" is a corrupt file. That's just one of the forms corruption can take.   But getting that on a simple .atn file is extremely unlikely. This is something that happens to image files. So are you sure it was the actions file that was the problem, and not the image file itself? ... View more

This is most likely a defective monitor profile.   You misunderstand what a monitor profile is and what a calibrator does. A monitor profile is a standard icc profile, just like any other icc profile. The calibrator does two things: first it makes some adjustments to the monitor - low precision - and then it writes a profile describing the monitor in that calibrated state - high precision.   Photoshop/ACR/Lightroom use this profile in a standard profile conversion, from the document color space into the monitor color space. This is done on the fly, as you work. This way the file is correctly represented on screen.   Even though it all ends up in the same monitor profile, the source color spaces are very different. So the actual conversion is different, and that's why it may fail in one and still work in the other. In ACR, it's a custom linear gamma color space with ProPhoto primaries; in Photoshop it's a gamma encoded standard color space.   In fact - if two color managed applications display differently, that's a red flag. That's evidence that the conversion is not executed correctly. That is usually because the profile is bad.   The actual conversion into the monitor profile is executed in the GPU, so a buggy driver could also cause the conversion to fail. These are two sides to the same coin: a problem in one can cause the other to fail.   What calibrator are you using?   Oh, and to be clear : the color spaces do not need to match! That's a common misunderstanding. The whole point of color management is that color spaces do not need to match. They only need to match if there is no color management or icc profiles. ... View more

Have you looked for it in Finder, at the disk location where you saved it? Where did you save it? ... View more

This is not a bug.   Do not rely on "recent files" in the Home screen. It is just a passive link to whatever location on disk the file was last saved to. If the file is moved or modified outside Photoshop, the link breaks and you just get a blank document. It does not keep track of the file.   Recent Files is a convenience feature, to let you quickly pick up where you left off before lunch - it is not intended for file management. Use a file browser and note where you save your files.     ... View more

Raw files couldn't ever be opened directly into Photoshop - they have to be processed into RGB files in a raw processor first.   That's why Photoshop has a plugin called Adobe Camera Raw. That's Adobe's raw processor (also built into Lightroom and Lightroom Classic).   There are several raw processors on the market, and the camera manufacturers all have their own. I don't know how many of those are free, that probably depends on how advanced functionality they have. The simplest ones will probably just output a TIFF or jpeg without  any adjustment options.   There are also several third-party raw processors. The most widely used outside Adobe is probably Capture One, but that's not free either. ... View more

@Trevor.Dennis AFAIK the CS5 and CS6 servers haven't (yet) been shut down; but Adobe will no longer reset activation counts if the two slots are used.   The plug has been pulled on the CS - CS4 servers. It's probably just a matter of time before CS 5 and 6 follow. That doesn't mean the application will stop working, only that it can't be reinstalled if anything breaks.     ... View more