In Publisher, any benefits/problems to linking to Photo file directly?

[Gobo]

Hello folks!

Just wondering if there were any benefits/problems to linking directly to a Photo file in Publisher instead of the exported image file. The obvious benefit is that it removes the step of writing out the image file. Any other benefits/problems that I should consider?

Thanks!

[Catshill]

I use linked rather than embedded images when the file I am linking to might be updated/revised. I then update the APh or ADe file knowing that APu will use the latest content.

[Brian_J]

In addition to what Catshill mentioned, here are a few other things to consider when deciding whether to embed or link files.

If the combined size of the files in your document is large, linking will reduce the file size, which can make some operations run faster.

If a linked file is moved or renamed, you’ll need to relocate the file in the Asset Manager — i.e., linked files need to be managed in relation to the file they’re in. If you upload or share a file that contains linked files, the linked files must accompany the parent file.

if you’re not concerned about file size or maintaining asset files externally, embedding files keeps things simple…. no need to worry about keeping track of linked files.

[Old Bruce]

19 hours ago, Gobo said:

Just wondering if there were any benefits/problems to linking directly to a Photo file in Publisher instead of the exported image file. The obvious benefit is that it removes the step of writing out the image file. Any other benefits/problems that I should consider?

For the most part the Affinity Photo file is going to be larger in bytes than any Exported File format. I try to use Exported TIFFs simply because those files are much smaller than the Photo files. If I need to Gather the images or Package the Publisher file then I have a much small collection.

[Gobo]

Thanks for the info, folks!