Use the package function:
File > Package …
Package will create a COPY of your file, with copies of the links in a single folder.
There is no function that will automatically copy links to a single folder as you work, and update the link path, but you can use the Copy Links To Folder command from the Links panel menu to do it manually, and it probably can be scripted.
I think it should be possible to assign a shortcut to this command.
Probably. I was thinking more on the lines of a startup script that would execute the command any time a new link was placed when I suggested scripting, though.
Thanks to everyone for these answers. I guess the real answer is "no", Adobe software engineers see no reason to create a script which
will place linked files into a folder. To bad. A really serious and lazy oversight in my view. The package function is helpful if one has already
organised their assetts.
As great as these programs are, this is an oversight of some frustration. As I said in my comments above, it seems an easy enough routine to program
into the app. Why should a user have to worry about collecting details of resources/links for a document?
Even after all these years?
Best regards, thanks to everyone who contributed some thoughts.
Did you read or understand our answers?
Package file is not for people who have organized their assets before, this command will creat a folder and put all links together.
And if you want to copy files in a folder, open the link panel. Select one or more linked files. In the flyout menu > Utilities > Copy Link(s) To…
Do you understand the downside of what you are asking? Linked files can be used over and over in many different projects. If they were to be copied automatically not only would you propagate many space eating copies, but you run the very real risk of having one version get edited but other uses would never be updated to match.
Ok Guys.....yes, I read and understand what you are saying. I know that there is always
a duplication of files...how many of you put your original files in a package folder?I would
say none. So the duplicate file issue is mute, perhaps a bit foolish.
There is no "down side" to applying functionality to the work flow in logical ways.
Having an option to have linked images go to an automatic folder
for collection (optional, with settings) has no down side. Difficult to imagine
all this posturing over the exclusion of a feature that does not exist.
The main thing is, the answer to the original question is no. "But" is another subject....
Since packaging is intended for archiving or handing off FINISHED work, it is reasonable to make copies of links in the current state (you have to send links with a hand-off, and you'd want to protect an archive from accidental changes).
On the other hand, I have several clients for whom I regularly reuse assets. Do I need 300 copies of their logo? And what happens when they need to update it?