jim_muirhead's profile

9 Messages

 • 

220 Points

Mon, Oct 6, 2014 3:17 PM

Photoshop CC: Extract Assets Feature Is a Disaster (2014.2 update)

The new Extract Assets feature in Photoshop CC 2014 is a disaster. Take a look at Sketch for the proper way to do this that designers will actually want to use.

Problems & Suggestions:
1) Come up with a solution that doesn't mess with my layer or layer group names - let me name the asset in the Extract Assets window and then remember it.

2) Allow me to add padding around an asset when I export - with the flexibility to provide different padding on each side of the asset.

3) Provide a 100% export option - I work at Retina resolution and so the base asset is actually my @2x asset, so I want to be able to select an 100% option and give it the @2x suffix.

4) Remember where I last extract assets to and don't force me to rename a destination folder each and every time.

5) Let me decide what the default resolution options should be, so I don't have to keep opening a dialog to set the ones I want.

Responses

4 Messages

 • 

90 Points

7 y ago

I have been using PSD for a while and recently moved computers. The new computers has a slightly different network setup linking to a different proxy.

The one thing that broke immediately was "extract Assets" Why would the proxy connection make the Extract assets fail?

15.1K Messages

 • 

195.8K Points

Sounds like your proxy broke the localhost (127.0.0.1) connection as well for some reason - so apps and servers can't communicate on your system.

81 Messages

 • 

896 Points

Extract uses a local connection to the Generator server to get the image assets. It is likely that your proxy connection has tried to route all localhost requests to be via the proxy. Check this response from a user who has a similar issue with proxy in the forum https://forums.adobe.com/message/6930791#6930791  

4 Messages

 • 

90 Points

Thank you for the comments. Divya the link helped me resolve the issue.

Under network settings > Advanced > Proxy
I simply checked "Exclude simple hostname" (for Mac user)

This resolved the proxy issue on my machine.

5 Messages

 • 

292 Points

6 y ago

Good to see Divya letting us know what's going on here. Any news of the update to this feature?

I have been pulling my hair out for some time now with this one. I agree with all of the issues in this thread but the most painful (rendering the entire feature useless for me) is the fact that the exports crop the asset to the pixel and not 100% of the canvas.

4 Messages

 • 

90 Points

I was able to get round this by creating a mask over the entire canvas. This should constrain it to just the canvas and not the group or pixels.

81 Messages

 • 

896 Points

The newest update defaults to limiting the asset export to the canvas dimensions if it is larger than the canvas dimensions. Is that not working for you Simon? 

Addtionally we are working on better ways to get images out of PS. If you would like to give us feedback on our approach, please do email me! manian@adobe.com 

5 Messages

 • 

292 Points

Chris that's a neat little work around, don't know why I didn't think of trying that... thanks!

Divya, excuse me if I have misunderstood but my issue isn't with assets that are larger than the canvas dimensions and I feel that I shouldn't have to apply masks or tease the canvas in any way to achieve that end result.

Simply, If I have a a single layer that only covers, let's say, 25% of the canvas area but am wanting to export the asset at 100% of the canvas size (including 75% transparent padding), I would like to have the option to export exactly as it appears on the canvas, in the same way that saving the PNG manually would do without creating extra work for me.

A simple option in the export settings that allow you to choose from: 'Export 100% of canvas' or 'Constrain to pixels, group etc.' would be the most obvious solution in my opinion, without requiring masks or 'empty' layers etc.

81 Messages

 • 

896 Points

Ah i see. This is something I have heard once earlier too. Can you email me manian@adobe.com possibly with a sample PSD where you have this issue? I want to understand your workflow so we can see what we can provide. 

4 Messages

 • 

90 Points

6 y ago

Is there any way to extract the assets to a folder and control the naming of the folder. When I extract all the assets Photoshop places them in a folder with the same name as the folder. I have not been able to work out how to say put the assets in a folder called "images" without renaming the PSD.

81 Messages

 • 

896 Points

You should be able to change the folder name to whatever you want when you choose the folder location to save the file into (as shown below). Does that not work for you?

 

5 Messages

 • 

292 Points

6 y ago

Ok, sorry for lengthy message but after some trial I have found a few more issues:

After being suggested that applying a layer mask will help with the extract, I thought I'd hit jackpot and would now use the extract tool across all of my PSDs.

Divya, I will send you my PSDs in an email as requested. You'll see better what I mean.

LAYER MASK FIX WORKED FOR SOME THINGS

The layer mask solution from Chris worked fine for an animation I was exporting assets for (for X-Code) where the canvas needed to be a constant size, just with lots of different asset states, and exported in 1x, 2x and 3x. Every asset kept the full canvas ratio and so the animation stitched nicely. That was cool.

1. EXTRACT SMART OBJECTS at 100% CANVAS SIZE

A problem arose when smart-object-placed-assets are only a small fraction of the canvas size (i.e an icon asset on an iPhone screen) and need to be 'sliced' out upon extraction. Therefore, layer masks do not work here.

I'd like to be able to extract assets (slice style) but with the extract tool maintaining 100% of the smart object canvas size (including any padding or empty space within the smart object) rather than constraining to the pixels as I have previously said in this thread. See image for example.



When I'm designing for iOS, I currently store all of my assets (1x, 2x, 3x) in a separate Asset PSD and export manually (see image). I also drop the @2x into my App Design PSD to work from. Even here, it would be great to just have ONE of each asset that I can use the extract tool to successfully export multiple sizes of. I created this work flow originally to get around the 'Generate Asset' feature's hidden layer issue where it would remove exported assets if the layer was hidden in the PSD. I stopped using that tool for all it's flaws a while ago - but it's good for some things. Anyway...



Either way, whether I want to extract assets from smart objects in bulk from the Asset or App Design PSD, neither works for me due to this canvas size issue and I still have to do it manually. This extract tool could save me (and I'm sure a few others) so much time if Adobe can just tighten a few things up.

The icons I create all have padding - or empty space - around the icon because the dev guys moan at me if they can't just place the asset straight in and create their button to be the same size as the asset file. They moan enough about Xcode as it is!!

2. BASE SIZE

Working from @2x as a base really isn't supported with your naming conventions. I can export at 1.5x with the suffix @3x which is useful and I can export at 0.5x with no suffix which is also useful. However, I can't export at 1x with an @2x suffix.

Likewise, if I name my layer with a 2x suffix to get around this, I can't then use the suffix tool for the 0.5 and 1.5 versions because it will become 'assetname@2x@3x.png' which again is useless.

I'd like the option to have 1x scale with an @2x (or otherwise nameable) suffix.

It may also be useful to consider that people designing at @3x would need a 0.66 and 0.33 option to extract that asset with a re-nameable suffix.

S

81 Messages

 • 

896 Points

OMG. Simon! Thank you so much for the detailed feedback. This is great! Also did you email as an attachment, if so it is likely flagged somewhere as spam and I never received it :( Can you just send me a 'hi' email and we can take it from there? manian @adobe.com 

2 Messages

 • 

80 Points

6 y ago

For those wanting to know how to customise the folder names and sizes what I found was that after using the Extract Assets UI to set up an initial export of the default and one other size, PS creates a layer (on top) called Default with some size information in it.

The format of that seems to be:


Default [size] [folder/], [size] [folder/], ...


For example I have a 4" iPhone screenshot that I need to export for the 4", 4.7" and 5.5" (I don't have the hardware so this is my only option).

I changed the information in that layer name to:


default 100%, 1334x750 667h/@2x, 2208x1242 736h/


This produces 3 copies of the asset, all correctly sized, and in folders that make it easy to grab and upload to Apple.

Tell me if I'm teaching you guys to suck eggs. I'm new to PS, so this is a major convenience for me, though it could be improved by PS cropping to the canvas boundary.

5 Messages

 • 

292 Points

Peter

Not teaching us to suck eggs at all and I wouldn't worry about that, a lot of people will read this thread - however, layer naming conventions for export have been around a while and is ultimately time consuming, especially on large-scale projects with an insane amount of layers, smart-objects and asset states. It shouldn't be necessary, and this new tool is very close to nailing it.

It's not so much the output folder either with regards to the naming - I think that has been updated already since this thread began - but more the 'base' resolution and correct suffix naming of each asset which is still an issue. It doesn't accommodate people choosing to work at resolutions other than 'default' or 1x.

In short, yes, you can use layer naming with the generate asset feature but it will soon start to grate on you when you have such long, non-identifiable names for each layer and you're trying to move about the project quickly.

1 Message

 • 

60 Points

6 y ago

Don't know if you guys still read this. But I'm trying to convert a complete sprite map to SVGs. There a few hundred icons. And I need to normalize the height, but keep the aspect ratio.
I've tried to set the height with layer naming. Like:
* x 500px
? x 500px
But this doesn't seem to work.
Is it something you have o will add?

81 Messages

 • 

896 Points

Hi Jon, have you tried the following from the generate assets functional spec https://github.com/adobe-photoshop/generator-assets/wiki/Generate-Web-Assets-Functional-Spec (be aware of no space between x and the units)

100x? foo.png (wild card)
?x60in foo.png (wild card at beginning)
That should work on your PSD. If not, can you send me a sample PSD to my email id? Let me know!

44 Messages

 • 

1K Points

6 y ago

I'm glad I found this little topic. I agree with all issues that have been made so far. I just wanted to get some clarification for the assets extract for document cropped vs pixel based cropped issue.

In my latest test, if I have a smart object, it still crops the image the size of the smart object, not the document size. Am I not correct on this?

Also, I know it was mentioned once, but I just want to add my vote on this issue about the quality difference between save for web vs Extract assets. Looks like if you use 60% in Extract assets, it's more like 30 in save for web, and with better results for the later at the same weight of file.
And while your at it, the export jpeg as a setting of 1-12, and save for web as 1-100 settings, shouldn't it be all the same? Consistency guys;-)

15.1K Messages

 • 

195.8K Points

If you create a smart object from layers, then yes the newly created smart object will be restricted to the area of those layers that actually contains something - it will not be the size of the entire parent document. We started with it using the parent document size, and got a lot of complaints about wasted space and large document sizes.

If you place an existing document, then you get the full size of that document, of course.

44 Messages

 • 

1K Points

OK, I might not have explained myself correctly. If I place a smart object, of smart linked object in a document, if I don't put a mask on it, the extracted asset will be the size of that smart object, even if the document is smaller than the SO.

Think of a workflow where you would crop all the images for a web carousel to the same size. You take one photoshop document, place the images as linked smart objects and you have a fast way of doing all your assets. Right now, I have to put a vector mask (or pixel mask, it doesn't matter) of the size of the document to acheive this. And I can't just put the whole thing in a group and mask that group either, it will not work that way. So I need to make a mask for EVERY layer.

I understand that sometimes, I'll want a smaller than my document asset to be extracted, so using the mask in those case is a great option too. But I didn't expect the asset to exceed the document crop size though.

I also agree that if I make a layer, put a vector mask on it, then make it a smart object, that object is cropped to the layer mask. That's fine by me.

I have a bunch of other comments on Smart objects if you're interested, but I don't think this thread is the right place to put them.

15.1K Messages

 • 

195.8K Points

Yeah, Smart Object requests should go in another topic.
I just couldn't figure out which part of your comment referred to Smart Objects in general, and which referred to using extract assets on them.

44 Messages

 • 

1K Points

I'll try again then.

If you have a document of 400X400 pixel, and you place a linked Smart object in it that has a dimension of 500X400 pixel and you don't scale it to fit because you want to crop it to the 400X400 pixel of your document.

Now if you don't do anything special, the jpeg or png that extract asset will do will be of 500X400 pixel, not 400X400 pixel like the document size. That's what is unexpected in my opinion.

The workaround is to make a layer mask on on that linked smart object at the same dimension then the document (400X400 in my example).

The thing is, you have to do this for every layer in your document. You cannot put them all in one group and put a mask on that group and tell it to be the mask for all layers within it.

Hope this is clearer this time:-)

15.1K Messages

 • 

195.8K Points

Yep, that makes it easier to parse. Unfortunately the solution is not trivial - since the SO can be placed anywhere in the parent document, you have to interact the bounds of the child document (after transforms) and the parent document, then crop and possibly expand the child document to get something that would match the position and size of the parent. I'm also not sure how often a parent size match is needed versus a tight bounds on the child document (trimming away transparent areas) for the exported image size. It sounds like a couple of different options are needed.

44 Messages

 • 

1K Points

I thought it would be simpler than that, you'd just have to do as if the layer would crop to the document size. It works when you put a mask on the layer, so why would it be more complicated to just get the document size and apply it as a mask?
I just dabble in Applescript, so I'm no programer and I might not get how it can get so complicated:-)

15.1K Messages

 • 

195.8K Points

Oh, it's doable. The trick is identifying all the cases where it isn't, and making sure we do something reasonable in those cases or give appropriate errors. That and explaining the difference in policies in simplest terms for the UI.

81 Messages

 • 

896 Points

Hi Jeff! Thanks for your feedback. We actually have updated it so assets outside of the bounds of the canvas will be clipped like so:

Original Smart Object: https://cloudup.com/cN2-oyF5ZXm 

Rendered Image: https://cloudup.com/cGpjmuBKsgI 

Have you updated your Photoshop yet? 

Are you talking about JPG quality when you are talking about quality? JPEG in Extract Assets and in Save for Web go up to 100%? Are you comparing vs 'Save as'? 

44 Messages

 • 

1K Points

huh, I was sure I had retested this, that's great, thanks Divya!

As for the quality of the jpeg, I made two points.

One is the fact that the quality at equal settings between save for web and extract asset don't seem to do the same output quality. If you set the save for web at 30%, you get the same file size and quality as about 60% in extract assets.
I have an exemple of this but can't post it online so I'll try to email it to you directly.

And the second point was that when you save as a Jpeg, you get a 1-12 slider vs a 1-100% in save for web and extract assets.

So knowing that you can set the same percentage in one place and get the same results wether you use save for web or save as would be nice.

Thanks for listening!

44 Messages

 • 

1K Points

Divya, I thought I could find your email on your profile, but I can't so shoot me an email if you can and I'll send you the two examples of what I mean for the quality issues in save for web vs extract assets.

81 Messages

 • 

896 Points

Yeah Extract Assets seeks to gain parity with what Save for Web offered, we will look at consistency with Save as once we are able to get users who use Save for Web on-boarded onto new export options. To be clear, this inconsistency between Save as and Save for Web has been in existence for at least 10 years :) 

44 Messages

 • 

1K Points

I know it's been there since the beginning, I just didn't have to use it until recently;-) I've worked for print for a long time and just starting to have work for web.

167 Messages

 • 

3.2K Points

6 y ago

I'd like to be able to have extract assets export slices for each layers. this is the only page that comes up for extract assets slices. I see above that you are aiming for feature parity with save for web. Is this coming or am I missing something in the extract assets dialog?

81 Messages

 • 

896 Points

Hi Bryn! Woah, thats a lot of slices! What do you use it for? We haven't found many folks using slices actually so we are not prioritizing working on that at the moment. If it is easier to speak on the phone about this, please do email me: manian@adobe.com Thanks!

4 Messages

 • 

110 Points

6 y ago

I thought I'd throw my hat in the ring here. I've been really wanting to be able to use this feature as it would save a lot of resizing when it comes to exporting retina-ready graphics. However I'm running into wall of inconsistency, weird color and quality behavior with smart objects.

My current workflow consists of this:
- Create images usually consisting of various smart objects
- Create slices
- Save for web

When saving 2x retina graphics I'll do a temporary image resize at 200% to and use the same defined slices and do a save for web.

What I've noticed is that Extract Assets and Save for Web yield very different results. I don't know if it's because I'm using a smart object and photo (although, I don't think that should matter) or if it's something else.

I first noticed the difference when I looked at the 2x version of an Extracted Asset JPG 100% quality it was very blurry almost as if the JPG had been upsampled without using the smart object (which is a very high resolution photo). Compared to the Save for Web version (also at 100% quality) it was very low quality.I tried another photo, created a new document thinking it was my PSD, but I kept getting the same poor results on the Extracted Assets JPG 100%.

In the non 2x version of the Extracted Assets I noticed a color shift, more contrast, and more brightness applied when the original had less contrast and wasn't as bright. So I don't know what is going on. I've included the comparison and a screen shot of the layers.

Please let me know if I need to do something different.

81 Messages

 • 

896 Points

Extract Assets can do 2x,3x etc with highest fidelity if you have converted an existing layer into an embedded smart object. We are unable to do so when you paste into your PSD something as a smart object or when you use a linked smart object. We are working to fix it, as we speak but there is a lot of work we need to do to get there. 

W.r.t JPG, if you are using an embedded color profile, Extract Assets will discard it. Very soon we should be able to provide an option to convert to sRGB, would that be sufficient in your case? 

44 Messages

 • 

1K Points

I thought the whole point of using the smart objects was that you could use it for such things! So you're saying I can't get a correct 2X when I used a linked smart object? This is bad. I have seen many tutorials all over the web telling people exactly to use that method.

Let say you need a 2X image, if you have a 300X300 image, and as you say, convert it to smart object, that image will just be 300X300 up sampled to 600X600, so why use a smart object in the first place?? It makes no sense. The natural workflow is to place a image as smart object from somewhere else that has enough resolution for both 300X300 and 600X600 images and extract it. Was that not the whole point?? I don't see why the linked Smart Object wouldn't work either, it's basically the same thing. Please tell me I didn't understand your previous answer correctly.

44 Messages

 • 

1K Points

Ok, I've done a few test and it doesn't work as you say it does and works as expected. It works fine on linked smart object and all. Fiew I was scared for a moment!

4 Messages

 • 

110 Points

Thanks Divya for your quick response and the light shed on this topic. I concur with Jeff that this is the whole purpose of using Smart Objects is to be able to scale to 2x or whatever without losing fidelity.

Jeff, are you saying that you're not seeing the problems that I've encountered? Could this be an issue where it's just me and not everyone?

It is a little odd that you must Place the smart object into your document -> Rasterize your Smart Object -> Make rasterized layer Smart Object in order for Extract Assets to work. Will Placed Smart Objects (embedded and linked) soon work. I think this is the behavior that people expect, and I think a lot of people may not even realize that they've been exporting poor 2x assets.

But, in my tests using your instructions, I was able to get the same quality as I do in Save for Web (it wasn't blurry this time). However, I still am noticing the Extract Assets version brighter than the Save for Web (see original comparison).

Is anyone else seeing this brightness shift? I've replicated it on two different images. All sharing the same color profile (sRGB).

44 Messages

 • 

1K Points

Hey Chris, I'm not seeing differences in my images in terms of colors. My document is in sRGB, and most of my images are for prints so they are in Adobe RGB, which is "converted" on the fly when I place them in my sRGB PSD. If you have a Adobe RGB file and extract the assets, then you'll have a shift in color because photoshop strips the profile of the resulting jpg as mentioned by Divya. Other than that, I'd check my color setting and see what's your setup there, maybe you have something that is set to ignore profile or something like that?

But you said you're all using sRGB so I don't know what's happening.

4 Messages

 • 

110 Points

Thanks Jeff, after finding out that you weren't experiencing the same color brightness shift, I tried another test in a new document. This time I didn't see the shift. I don't know what could've happened before.

Other things that I've found worth noting, but aren't really a big deal to me:
- Smaller file size on the Extracted Assets version vs. Save for Web version is 37KB and 91KB respectively on the 1x version.

Hopefully there aren't any other surprises in using this new tool. I'll have to keep a close eye on the exports. Thanks for the help.

44 Messages

 • 

1K Points

Chris, on the size comment, if you select the same setting, for exemple, 60% in save for web and 60% in extract assets, you won't get the same level of quality and compression, that's why you see a size difference. That is one of the things I mentioned to Divya and the team, and I'm not the only one who has seen this difference. I think it is important to have the same algorithm for both since people are probably coming from the save for web way of doing things, they will be accustomed to those percentage/quality and expect the same. Divya assured us that they are working hard to resolve this for the next major release. Lets hope they do:-)

4 Messages

 • 

110 Points

6 y ago

I looked into the brightness shift a little more, and found out what was causing it, and I'm posting it here, because it could be a potential bug that Adobe would like to look at.

I found that the brightness shift was coming from an above turned off layer that contained a curves adjustment layer (also turned off). While the turned off curves layer didn't affect the image when turned off (as expected), it somehow retained the curves effects when using Extracted Assets. I've detailed this in the screenshot below.

I've cropped the Extract Assets dialog box a little so it may be hard to understand the relationship of everything in the screenshot. The portion in the middle of the screen grab is the Extract Assets dialog box with the actual image on the left. I've increased the curves layer adjustment to show the problem better.

1 Message

 • 

60 Points

6 y ago

I'm Chou Le@eluohc (Twitter)

Dear Dev Team, I must say that this feature make me love and decide to stay with Photoshop forever. It's really helpful
For the problem other users even myself have to face it, I found a solution for them and happy with the results:

- Export @1x @3x when your design is based on @2x
---> Extract as 0.5 and add suffix @1x, 1.5 with suffix 3x - Problem solved!

- Suffix bug: 2x@3x , 2x@1x if we rename the default size as @2x
---> Rename them on Mac and replace @2x with blank. I think it will take much time to do it.

The feature is amazing, keep it up :D

4 Messages

 • 

90 Points

6 y ago

I just got the 2015 CC Update for Photoshop and I'm devastated that this feature appears to have been crippled.

It appears as though the functionality that allowed you to simultaneously save multiple res images of the same layer has been removed and now I would need to extract the same image several time at different scales.

It also no longer remembers what layers I have previously exported when I reopen the Export Assets dialog. I have to reselect all the layers I want to export.

Both of these are HUGE steps back in terms of efficiency.

Please tell me I'm wrong and there is some setting I'm not seeing, and I can still extract images at multiple resolutions simultaneously.

81 Messages

 • 

896 Points

Hi Ray, yes you are right that we have changed this feature to make export from Photoshop easy and then regroup on what remembered export would look like. We are investigating using Design Space to provide this feature in a much more contextual manner. 

It is funny that folks remember that Extract Assets is a disaster and then complain when we act upon users calling it so. :) Just another fact of life I guess! 

4 Messages

 • 

90 Points

I was never among those who could have possibly thought it was a disaster. It was awesome and an amazing time-saver.

But I can't imagine anyone who did have complaints would have wanted the best functionality of the feature removed.

This change does make things 'easy'.

Is there anyway to rollback the update?

3 Messages

 • 

92 Points

Ray, I'm in exactly the same boat as you. If you want to upgrade (!) to the previous version, open Creative Cloud, and within "Find additional apps", click on the "Install" beside Photoshop. You'll see a version listing and it will allow you to pick CC 2014 instead.

This is extremely frustrating. The export window also consistently appears off-screen if you work with more than one monitor.

81 Messages

 • 

896 Points

Can you send me a screenshot of how it appears 'off-screen'? 

3 Messages

 • 

92 Points

Hi Divya, here is a link to how it shows up: https://i.imgur.com/hIV39kt.png

This is on OS X 10.10.3. Photoshop is on the other (second) monitor, I use it with the application frame, and it's sized to the full screen. No part of the modal is visible on this other screen. I can consistently reproduce this behavior as soon as my second monitor is plugged in.

81 Messages

 • 

896 Points

yikes that looks bad. We will look into fixing this asap. 

4 Messages

 • 

90 Points

Thanks for the info Louis! Worked like a charm.

Divya, I really hope you guys reconsider putting that functionality back into the Extract Assets feature in future updates.

44 Messages

 • 

1K Points

Ray, I'm not the expert on this Generator or Extract assets feature BUT, from what I can tell, the only thing that is not there anymore is the interface. If you're used to work with Generator and exporting your assets that way, just continue to do so and it will still work!
This is pretty awesome because it works with the new stuff too, meaning it will clip to your Artboard, will keep adjustment layer who are outside of any Artboard and affect the ouptut with the adjustment.

The generator syntax works on Artboard, layer groups and individual layers as well, so go nuts;-)

I'll put my comments on the new Export As feature in another post.

4 Messages

 • 

90 Points

Hey Jeff,

Not familiar with PS's Generator functionality other than it automatically updating exported images, which I didn't use.

The major issue I have is previously you were able to export an asset at different resolutions simultaneously. So basically save once, get two (or more) images with control over adding a prefix to the filename (ex. _2x for high res images)

As a Front End Web Developer that was an amazing function and I used it a lot.

The updated version removed that functionality, so now it doesn't offer much of a benefit over slicing the image and using the usual Save for Web dialog.

44 Messages

 • 

1K Points

Ray, check this out, it will resolve your issue. https://helpx.adobe.com/photoshop/usi...

44 Messages

 • 

1K Points

6 y ago

I don't know if I should put this in a new subject for Export As CC 2015, but since others have commented on this one, I'll follow suit.

I have a couple of comment on the new feature, which I think is a step in the right direction.

1. Artboard a wayyyy cool, thanks for that. The fact that when you export an asset from an Artboard and it crops to the size of that Artboard is great!

2. The fact that you can use an adjustment layer put it outside an Artboard and be able to have that adjustment reflect on ALL Artboard bellow it is awesome!

3. Generator still works! So you can rename Artboard, layer groups and layers and they will generate the assets as before, that great. The only thing missing is that you no longer have a GUI to do this.

If you're not a fan of Generator and the fact that it needs to rename your layers to do its thing, than the new Export As feature is cool.

There are some stuff that could be improved.
First, you can't select a bunch of layers, then go to Export As and change them ALL to jpeg 60% in one swoop, nope, you have to click on each layer or artboard or whatever you had selected in the layers panel, and do all settings for each of those. This is a real show stopper for most production. Yeah you can change the Export setting and set it to jpeg, 60% and thats good, but if you want to scale all those same assets to 200%, oh oh, you can't set that in the Export asset settings that work with the Quick Export as ...

You can't export to multiple format or scale in one go either with the Export As. It would be nice to multi select the layers on the left of the dialog, set the settings once on the right, clic on a + Assets or something like that, set another settings, and so one. I don't know how you could show that info in a clear manner, I'm not a UI designer, but I'm pretty sure you have some awesome designer who gets it and would find a great way to tackle this problem.

So, great work so far, with these little enhancement, it would be awesome.

PS, when selecting multiple item, the preview should just show "Multiple item selected". If you need to fine tune an image, you can always select just that one and modify it.

I'm curious what others think of those suggestions.

81 Messages

 • 

896 Points

6 y ago

First, you can't select a bunch of layers, then go to Export As and change them ALL to jpeg 60% in one swoop, nope, you have to click on each layer or artboard or whatever you had selected in the layers panel, and do all settings for each of those. This is a real show stopper for most production. Yeah you can change the Export setting and set it to jpeg, 60% and thats good, but if you want to scale all those same assets to 200%
Yes, we have this done and ready to go for the next release! We just couldn't get to it in time for this one. 

oh oh, you can't set that in the Export asset settings that work with the Quick Export as ... 

We experimented with this but found it was really confusing for the users what that means.

You can't export to multiple format or scale in one go either with the Export As. It would be nice to multi select the layers on the left of the dialog, set the settings once on the right, clic on a + Assets or something like that, set another settings, and so one. I don't know how you could show that info in a clear manner, I'm not a UI designer, but I'm pretty sure you have some awesome designer who gets it and would find a great way to tackle this problem


We had many designs to try and tackle this issue but none that resonated with users as 'yes give me this now'. We are back to the drawing board on this one and will look at it mostly as part of Design Space so it is very contextual and probably on the canvas itself too. 

44 Messages

 • 

1K Points

Thanks for the update Divya, glad to know the first one will be addressed. As for the other comments, I guess I'll wait in line:-)

4 Messages

 • 

114 Points

@Divya: Hi, We love Extract Assets in Photoshop CC2014 but why you remove this feature in Photoshop CC2015. We need export UI design, mobile design icon to 2x,3x. It automate, but now we have do it manual that's waste our time. Can you please bring back this feature. Thank you.

81 Messages

 • 

896 Points

6 y ago

Hi Ray if you are a front end developer this might be of use to you:
https://github.com/adobe-photoshop/generator-assets/wiki/Generate-Web-Assets-Functional-Spec

or you can synch your PSDs to Creative Cloud and use Extract