Save for Web / Save Optimized As - outdated UI

[Frank_B]

Is there a reason why Save for Web > Save Optimized As doesn't let us copy and paste directory path?

It feels like this PS pop up window belongs to Windows 3.1.
Forcing us to click through folders in search of the destination folder on that little pop-up window makes this saving system clunky and inefficient.

I already have my destination folder opened in Windows Explorer. The directory path with its' subfolders is long. Why can't I copy this directory path and paste it to Photoshop "Save Optimized As" to save myself time and frustration? Imagine if you have to do this multiple times on daily basis...

In short,
Please make "Save Optimized As" pop-up window to look like "Save As" pop-up window.

Thanks.

[Jeff Arola]

I won't say never, but it's more than likely Adobe won't update the "Save Optimized As" dialogs on the Windows side since

Save For Web is labeled Legacy.

In the mean time if you have a location you use over and over you can Pin it to the Quick Access in the standard Windows Explorer

window, then it will carry over to the Save Optimized As dialog.

[Stephen_A_Marsh]

I usually use a Mac, but where can you paste a path to save? Save, Save As, Save a Copy? Export As?

[Frank_B]

@Stephen_A_MarshYou can copy/paste directory path in: Save As, Export As, Quick Export As PNG, Save A Copy, Open, etc... Basically everywhere except that outdated Save for Web.

@Jeff ArolaLegacy, huh? Well, I'm not surprised since it feels ancient but then how are we supposed to batch export sliced image (tiles)?
It's a basic feature considering Instagram 3x grids...

[Jeff Arola]

Save for Web is ancient in computer terms, being first introduced in Photoshop 5.5 circa 1999.

[Stephen_A_Marsh]

@Stephen_A_MarshYou can copy/paste directory path in: Save As, Export As, Quick Export As PNG, Save A Copy, Open, etc... Basically everywhere except that outdated Save for Web.

By @Frank_B

Thanks for the clarification, I mostly use a Mac where things are different.

[Stephen_A_Marsh]

but then how are we supposed to batch export sliced image (tiles)?
It's a basic feature considering Instagram 3x grids...

By @Frank_B

Slicing for recombining in HTML table cells is considered "old school" and has fallen from favour with modern CSS methods to show/hide a single large image in sections.

This could be one reason why slice output is not yet offered in Export As.

Export As is meant to replace the limitations of Save for Web (Legacy), however, Export As is still a work-in-progress and has many things missing from it, which means that many still use Save for Web (Legacy).

Save for Web (Legacy) has an input size limitation of 8192px on the longest edge, if the input image is larger then it is scaled down from 100% or 1:1 pixel size when output (whether slicing or not).

Even Export As has a limit of 15,000px on the longest edge of the input image.

There are legacy JSX scripts that can bypass Save for Web (Legacy) and save slices or create layers from slices without the 8192px limit. AFAIK the new UXP scripting has not yet had equivalent scripts created:

https://community.adobe.com/t5/photoshop-ecosystem-discussions/divide-my-image-to-layers/m-p/1246752...

https://community.adobe.com/t5/photoshop-ecosystem-discussions/script-for-splitting-multiple-psds-to...

https://community.adobe.com/t5/photoshop-ecosystem-discussions/can-slices-be-saved-at-300-ppi-in-pho...

[Frank_B]

Thanks for all the info! I've checked the links. It seems that the better solution for preparing images for instagram 3x grid might be free android apps which are designed solely to do the slicing.
Or do that Pin in the Quick Access thing Jeff mentioned...