/t5/photoshop-ecosystem-bugs/export-at-3x-scaling-is-broken-in-26-2/idi-p/15113977Jan 26, 2025
Jan 26, 2025
Copy link to clipboard
Copied
I had to roll back to 25.7 because export scaling at 3x looks horrendous in all later version. Here are my export settings and what it looks like in 26.2 comparted to 25.7.
/t5/photoshop-ecosystem-bugs/export-at-3x-scaling-is-broken-in-26-2/idc-p/15114134#M118100Jan 26, 2025
Jan 26, 2025
Copy link to clipboard
Copied
I cannot reproduce the problem between 25.12.1 and 26.2.0 at least.
Upscaling by 300% does not seem a good idea anyway; it might be advisable to create the file at the maximum necessary size right away (or use Artboards to create the different sizes).
Could you please post screenshots taken at View > 100% with the pertinent Panels (Toolbar, Layers, Options Bar, …) visible?
/t5/photoshop-ecosystem-bugs/export-at-3x-scaling-is-broken-in-26-2/idc-p/15114163#M118101Jan 27, 2025
Jan 27, 2025
Copy link to clipboard
Copied
I've been using the upscaling feature for 5 years. It hasn't been a problem until after version 25.7. Why have scaling if it isn't a good idea? It shouldn't matter if you're dealing with vector layers.
/t5/photoshop-ecosystem-bugs/export-at-3x-scaling-is-broken-in-26-2/idc-p/15114190#M118102Jan 27, 2025
Jan 27, 2025
Copy link to clipboard
Copied
Ah, I can reproduce in Photoshop 2023.
»Why have scaling if it isn't a good idea?«
Sometimes even a weak solution is better than nothing.
»It shouldn't matter if you're dealing with vector layers.«
But then why work with a pixel-oriented image editing application?
But drollery aside you are right that the change (upscaling the vector/type content versus upscaling pixel content) in »Export As« is unexpected and does yield inferior results.
With the settings you show, you are upsampling the original 3x. Yes, that will look horrible, not because of Photoshop/Export, but because it's upsampled.
This isn't how it's intended to be used. You're supposed to start with a bigger original, which is then downsampled to the target size, plus double or triple as the case may be.
The point is that the final file is not upsampled from a small original, but downsampled from a much bigger original.
/t5/photoshop-ecosystem-bugs/export-at-3x-scaling-is-broken-in-26-2/idc-p/15114257#M118107Jan 27, 2025
Jan 27, 2025
Copy link to clipboard
Copied
@c.pfaffenbichler That's an interesting theory. Hopefuly developers can provide some insite or correct the issue. It's only been an issue for a bit over a year 😕
Actually I'd be more concerned with how live text looks when downsampled from a bigger original in Export. If that looks fuzzy, I agree there's a case.
I still maintain that using 2x and 3x as upsampling from a small original is not a good idea.
/t5/photoshop-ecosystem-bugs/export-at-3x-scaling-is-broken-in-26-2/idc-p/15114335#M118109Jan 27, 2025
Jan 27, 2025
Copy link to clipboard
Copied
@D Fosse But it's a vector layer. And the background is a smart object that is 5x what it needs to be to not be pixelated. Upscaling has worked great on all versions I've ever used prior to 25.7. Why should it matter now, especially if the layer in question is vector? What the point of a vector if you can't upscale? 😉
/t5/photoshop-ecosystem-bugs/export-at-3x-scaling-is-broken-in-26-2/idc-p/15114345#M118111Jan 27, 2025
Jan 27, 2025
Copy link to clipboard
Copied
Yeah, I certainly agree that I have an unconventional way of doing things. I'm just don't understand why it stopped working as expected after a certain version. Very strange.
/t5/photoshop-ecosystem-bugs/export-at-3x-scaling-is-broken-in-26-2/idc-p/15118303#M118115Jan 28, 2025
Jan 28, 2025
Copy link to clipboard
Copied
So, no response from Adobe on a bug that has been in their software since 25.7? I'm honestly tempted to cancel my subscription and go with a different package. It's not worth $720/year.
/t5/photoshop-ecosystem-bugs/export-at-3x-scaling-is-broken-in-26-2/idc-p/15204057#M119919Mar 11, 2025
Mar 11, 2025
Copy link to clipboard
Copied
I have a problem with scaling of layers with FX when doing export or image resize.
If I go to "Export As" on an image and export the image resized (50% for example), layers with FX on them will export wrong. For some reason the export image includes scaling on those layers with FX on them. I belive the correct behaviour should be that it just exports the final raster image and doesnt touch anything else. Unless I am missing something? If i rasterize the layer with FX, it will scale correctly. However this is highly counterintuitive that I have to make a rasterized layer before exporting, makes no sense when export should be the final raster image regardless. I have tried "scaling options" on "image resize" but it does absolutely nothing.
The legacy "Save for web" scales the image correctly. See photos for reference.
/t5/photoshop-ecosystem-bugs/export-at-3x-scaling-is-broken-in-26-2/idc-p/15204167#M119920Mar 11, 2025
Mar 11, 2025
Copy link to clipboard
Copied
I would say this is a bug with export as. I've never cared for that feature and still prefer to use save for web. Save for web was suppose to be removed, once Adobe got export as refined — doesn't look like that has hapened or will happe. Any time soon. It sounds like you need a workaround. I've been using Bridge's file export a lot, for multiple files. That way I often don't need to even open PS.