One file can be selected in several compatible fields. Those fields share the same library item; selecting it again does not copy it.
Catalog and content uses
Media files can appear in product galleries, brand and vendor images, category and collection images, blog featured images, author avatars and image attribute options. A variant selects its media from its parent product's gallery. Custom data file fields accept the library and formats configured for that field.
Online Store uses
Site assets can be used in favicons, theme sections and settings, SEO social images and checkout branding. A Media file cannot be substituted for a required Site asset, or vice versa.
Reviewing deletion impact
Before deleting, Tringify checks where each file is used. A file is flagged as in use when it is selected in a field, such as a product gallery, a collection image or a favicon.
A file is also in use when its link appears in written content: product, collection, category, brand and vendor descriptions; page, policy and blog post content; translations of product descriptions and of page, policy and blog post content; and email templates. Theme sections, theme settings and checkout branding count too.
You must confirm before a file in use is deleted. The impact dialog can summarize a long list of uses.
Links Tringify cannot check
Links to a library file in the HTML of descriptions, pages, policies, blog posts and email templates are tracked. Links in emails already sent, on other websites, and in translated collection, category, brand or vendor descriptions are not. Update those links yourself before deleting the file.
Removing a file from one record leaves the library item and other uses intact. Deleting the library item affects its tracked uses as described in Deleting files.