Skip to main content
Leonavr
Participant
June 18, 2015

P: Export As does not support Actions or scripting

  • June 18, 2015
  • 106 replies
  • 9848 views

There is no way to record an action so that I can automate Export As dialogue box. What I want to do is to record an action which will save one image in three formats via the Export As dialogue box and the action should remember the settings i input for each dimension. Previously Save for Web did this, but now you are calling it legacy so i expect Export As to be accessible same way via actions as Save for Web was. Thank you.

106 replies

Legend
May 8, 2017
I'm not following you. What's missing from CC that you have in CS 5.1?
Inspiring
May 8, 2017
I have to open my old CS5.1 to convert a bunch of PSDs to PNGs because CC can't do it? That is seriously the most bizarre regression I've ever seen in a $600/year piece of software. 
Legend
April 15, 2017
This is the best place to add me toos, and comments. This is a top issue and I've been after the Export As team to try and get this in.
Earth Oliver
Legend
April 14, 2017
This feature is still desperately needed.
Participant
March 17, 2017

Agree wholeheartedly with both Max and Tom above. Furthermore, by not facilitating 'Export As' in actions, there's an implicit devaluing of the importance and power of automation and batching in a key new(er) feature of Photoshop. Power users want power features. And feature parity.

I pay a monthly subscription for a 'professional' product, and I'm used to relying on processes and features which aid repetitive, iterative creation and output. I've always thought that's what marks PS out from the competition.

If batch functionality is siloed to an older, slower and less efficient process (Save for web, versus Export As) that sends a message that professional needs are less important than new but unrefined features... and that valuable customer feedback is not being taken onboard.

We've had several major (version) and many minor (point) updates since 'Export As' was introduced and there's no sign action functionality has even been considered. And as Max indicates, the suffixing of Save for Web with (Legacy) suggests that's not the prefered route, and could even be mothballed in a future release.

Jeffrey Tranberry what can we do to make the system work for us... and for Adobe to hear the experience of real-world customers? Is there a mechanism in place to actively petition for product improvements which the users on this thread could use to better make the case for this feature? I'm sure most of us would happily state our case in more detail if we thought it would add weight to the demand to implement action support for 'Export As'. Thanks.

Participant
March 17, 2017

Totally agree with Max Johnson - PlayStudios and Tom Hole.

The 'Export As' feature is great as far as it goes, but there is a real need for using actions to batch process. Adobe are basically giving us a choice of saving a single image at different sizes and resolutions (essential for responsive web design) in 'Export As'; or saving multiple images at a single size using 'Save for web'...

Neither of which address the need that we have to save multiple images in different sizes and resolutions.

And we've been asking for a year or more...

Inspiring
March 17, 2017

Max Johnson - PlayStudios is spot on. The issue here is that "Export As" was pitched as the replacement for "Save for Web". 

The use case for "Save for Web" is pretty clear - you are generating a one-off file that then goes somewhere else (i.e. online etc).

"Export As" on the face of it is a much more powerful alternative and that is why people who routinely used "Save for Web" in actions/batch workflows were super excited to see it come in. (It is 2017 -- we should be able to export a standard/retina/svg/'whatever else we want' image in one go - right?)

The frustration in this thread is that (a) you guys didn't even consider this use case in putting together the replacement for Save for Web (b) there has been no acknowledgement that this is an issue for people or that something is in the pipeline to fix it ... 

Known Participant
March 16, 2017
I think a lot of the confusion and anger around this comes from the fact that 'Export As' was advertised as the replacement to "Save for Web" which was named to "Save for Web (Legacy)".

In doing so, Adobe implied that "Save for Web" would not be supported moving forward and we end users are trying to figure out how and when to make the switch over. It would be nice to have a single solution, but "Export As" is lacking some core functionality that was relied upon for workflows and asset pipelines.

I appreciate that changes take time and look forward to the next release in the hopes that this and other feature requests will be addressed.
Legend
March 16, 2017
I agree. I'm not saying it shouldn't. Just clarifying that it was never implanted by the team that created Export As.
Earth Oliver
Legend
March 16, 2017
It really should be implemented though, Jeff. I'm trying to design an end to end workflow for a client at Microsoft next week and being able to add Export As to an action would work perfectly for what i'm trying to accomplish.

Fortunately, Image Processor Pro is still functioning, but it hasn't been updated in ages and i'm left wondering if the day is soon arriving when this tool to will be no longer supported.