If an image, icon, or component is missing or looks out of date in a Figma handoff, first check the selected layer, export settings, and your access. If those are correct, determine whether the design changed or a linked library needs an update. Use a library swap only when the original library is missing or inaccessible and you have an appropriate replacement.
Start by locating the failure
Work out whether the problem affects one object or many instances, whether the asset lives in the current file or a published library, and whether you have view or edit access. These clues point to different fixes: export a single object directly, compare design history if the approved design may have changed, review library updates for a connected library, or swap libraries when the source is unavailable.
- One object is missing or cannot be exported: check selection, export settings, and file restrictions.
- The handoff differs from what you expected: compare the frame or component with its history and confirm the approved version with the design owner.
- Several instances appear stale: look for published library updates.
- The library source is missing or inaccessible: consider swapping to an accessible replacement library.
Fix an export option or asset that is missing
1. Select the intended layer and check the mode
In Dev Mode, select the relevant layer or object. The Export section appears when an object is selected. In Design Mode, look for Export in the right sidebar; its location depends on whether you can edit the file or only view it. Figma’s guide to inspecting and export guide describe these workflows.
Dev Mode can detect icons and display downloadable assets in Inspect. It also exposes GIF and MP4 nodes and the source image at full resolution. For broader details about the developer workspace, see Figma’s Guide to Dev Mode.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
2. Check the export configuration and access
Inspect the selected layer’s export settings, or add an export configuration if the object needs one. Figma’s Dev Mode guide lists PNG, JPG, SVG, and PDF as supported formats. If the Export control is absent, refresh the file. If it remains absent, check whether the owner restricted copying and sharing; those restrictions can prevent viewers from exploring or exporting assets. Ask the owner to confirm or adjust access if needed. See Figma’s handoff optimization guide and export guide.
An absent Export control does not by itself mean the asset was deleted. Dev Mode is documented as available on paid plans for Full or Dev seats; if you cannot use it, check your plan and seat as well as file permissions. The Design Mode sidebar is a separate route to export settings.
Check whether the design changed
If the asset is present but differs from the version you implemented, compare the relevant top-level frame or component with its history in Dev Mode. Choose Compare changes to see its history against the current version and when it was last edited. This helps distinguish an outdated implementation from a newer design change; it does not determine which design is approved. Confirm that with the design owner before replacing implementation assets. Follow Figma’s Compare changes in Dev Mode guide.
Update an asset from a connected library
When a library’s published component, style, or variable has changed, the file using it can receive an available library update. Review the proposed changes, then apply the update to the affected instance or assets. Publishing makes changes available; it does not automatically apply them to every file. Use Figma’s Review and accept library updates instructions.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →This is the right workflow when the source library is still available and has a published update. It is different from swapping libraries, which is intended for a missing, deprecated, unpublished, or inaccessible source.
Replace a missing or inaccessible library
If the original library was unpublished, deprecated, or moved to a team you cannot access, inspect the missing libraries and use Swap libraries with a replacement library you can access. Figma matches component and style assets by name. Items without a match remain unswapped, so review the result rather than assuming every dependency was replaced. See Figma’s Swap libraries guide.
A swap changes the connected source: swapped instances continue receiving updates from their new main components. Confirm that the replacement is the intended design-system source before proceeding, particularly when similarly named assets may not be equivalent.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Prevent handoff gaps next time
Figma recommends applying export settings to the frames, components, and assets developers need; using descriptive page names; and marking handoff content “Ready for development.” Use meaningful component names and descriptions too. Descriptions can record intended use, variants or states, and accessibility or contrast guidance. Figma’s handoff optimization guide explains these practices. Figma’s wording is direct: “Mark content as “Ready for development” to help with developer handoff.”
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
