This seeems like a feature request , hence marking it as untriaged , so that it would get addressed.

Thanks !

Yes, this definitely a feature request, and specified it above.

Chris, wdyt about the UX here?

Folders in the Sources panel could have a "Save" command in their context menu, similar to regular files (though that seems to be flaky in current builds). Choosing this command could open a local folder picker, letting the user choose where to store the folder. Once selected, the folder in Sources, along with all its subfiles and subfolders, will be downloaded to that folder.

There are a lot of incidental issues that would need to be addressed here:

1. What happens if a folder with the same name already exists in the target folder? Does it get removed (after a prompt)? Do you merge the downloaded folder with its contents (and if so, what if there are name collisions within the folder)? Or does it get automatically renamed, like other Chrome downloads?

2. What happens if a subfile or subfolder has a filename that the filesystem doesn't support? Does it get normalized? What if multiple files have the same name when normalized?

3. What is subfolder contains multiple files with the same name? This is technically possible with query strings, but would not work in most filesystems.

4. Would the downloaded folder show up in Chrome's download manager? Does that support folders?

An alternative, instead of downloading the folder directly, would be to compress the contents of the folder into an archive format (i.e. ZIP) then let the user specify where to store the resulting archive. This is how services like Google Drive and Gmail support downloading multiple files/folders. This also bypasses the issues above, since ZIP doesn't have the same naming limitations and could use Chrome's download manager. This would require DevTools to support an archive format, though, which I'm not sure it does.

Well, there are quite intuitive decisions which exist in many apps.

1. If a folder already exists it could be renamed automatically like source_folder1, source_folder2 and so on. Another option is to just DON'T ALLOW to save folders in the location where such folder already exists. I cannot remember situation with several nesting levels hierarchy, so this should't be rather acute problem.

2. Yes, in this case some normalization should be applied.
3. Auto-rename like in point 1.
4. I assume this would be redundant. As there will be excessive amount of data, and this stuff is almost dev-related, this is not necessary to show this in download manager.

ZIP-saving should be the PERFECT alternative, in fact. If it support 7Zip, it would be wonderful twice!

I can only second this. I'm working on a npm package for a website, the models are provided in the source by the dev but reading them using dev tool while I could use my IDE is cumbersome.

/cc lushnikov for feasibility. How difficult would it be to ZIP the contents of a folder (and its subfolder) and then trigger a download?

it's hard to estimate the effort, but it is doable if there's a strong demand.

Why doesn't the "save page as.." satisfy the need?

As far as I know "save page as" does not save the scripts.

The goal here is to save those scripts which are all organized in a nice manner thanks to source maps ; http://i.imgur.com/EpPSb2B.png

Any updates about that?

I was wondering as well if it's possible to do this at present.

If it is not, have you guys found any kind of extension or third party tool which allows saving folders from the Sources tab?

No, I know no 3rd-tool. If someone know smth, he is welcome to suggest.