How can I find out which pages in Webflow unused assets belong to after deleting them?

Once an asset is deleted in Webflow, you cannot directly trace which pages it was previously used on. Webflow does not provide version history or usage logs for deleted assets.

However, here are several ways to identify asset usage before deletion or recover from accidental deletion:

1. Check Asset Usage Before Deleting

• Before deleting an asset in the Assets panel, hover over it to see if Webflow shows a “used in” indicator.
• This tooltip lists which pages and classes the asset is linked to.
• If no usage is shown, Webflow considers it an “unused” asset, although this may miss usage in custom code, CMS fields, or symbol content.

2. Use Webflow’s Site Search or Manual Audit

• Use Command + F (or Ctrl + F) in the Webflow Designer to search for the file name.
• Open each page (especially dynamic templates) and check for missing images or assets.
• Inspect Symbols, Rich Text fields, and CMS Collections—assets may be indirectly linked here.

3. Check the CMS & Custom Code

• Go to CMS Collections and check if the asset was uploaded to a file or image field.
• Check custom code blocks in pages or Site Settings (e.g., page headers or footers) for embedded assets referenced by filename or URL.
• If an asset was used in custom JavaScript or embeds, Webflow won't detect this as usage.

4. Use Backups to Recover Deleted Assets

• Go to Project Settings > Backups, and open a version from before the asset was deleted.
• You can duplicate the backup to a new site, then open it and manually identify where assets were used.
• Once found, you can return to your current project and re-upload or re-link the asset as needed.

5. Use Browser Developer Tools

• If the site was previously published and content cached, inspect the live site and check for broken links or references to deleted assets.
• In the browser, right-click and choose Inspect, then review missing image URLs or console errors.

Summary

Webflow does not track deleted asset history. Always check the “used in” info, inspect CMS and custom code, and make use of backups to recover or trace deleted assets. Prevent data loss by auditing usage before deletion.