The impact of moving an asset depends on where you're moving it to and which type of link you're using.
Moving within the same brand
When you move an asset between folders or between libraries within the same brand, the following applies:
Public share links (/s/... links) stay valid. Users who already have a share link don't need to update it.
Static CDN links stay valid. Static CDN links point to a specific revision of an asset and don't expire — they remain valid even if the asset is moved, renamed, or deleted later.
Dynamic CDN links stay valid. Dynamic links are designed to remain stable across moves, renames, and updates, always delivering the latest revision.
Browser/frontend URLs will change, since these reflect the asset's current path in Frontify. If you share a browser URL before moving an asset, that link will no longer work after the move.
Assets referenced in guidelines
If an asset lives in a library that's connected to a guideline, moving it within the same guideline won't break guideline references — the underlying asset ID stays the same. If the library itself moves to a different brand, the connection to the guideline would need to be re-established.
If an asset is deleted rather than moved, any guideline blocks referencing it will break. Frontify will warn you about referenced blocks when you delete content, but it's worth checking before removing anything that might be in use.
A note on share links and user deletion
Public share links are tied to the user who created them. If that user is removed from the account, all their share links are automatically deactivated. For anything that needs to stay accessible long-term, use direct frontend URLs (copied from the browser) for internal Frontify users, or dynamic CDN links for external use.
Which link type should I use?
Use case | Recommended link type |
Embedding assets in external websites or tools | Dynamic CDN link |
Sharing with internal Frontify users | Direct frontend URL |
Long-term archiving or compliance | Static CDN link |
Quick sharing with external users | Public share link (with caveats — see above) |
Note on moving libraries between brands
Cross-brand library or asset moves are not supported in the platform — the workaround is to download and re-upload. The assets will have to have their metadata added again if you do this.