This is an overview of the changes to the Webflow APIs and related tools. To filter the list, select one or more tags.
v1.17.0: Asset management commands
v1.17.0: Asset management commands
v1.17.0 adds a new assets command group for managing your Webflow site assets directly from the command line, along with an improved site selection experience and a CMS display fix.
New webflow assets commands
You can now list, upload, update, and organize assets without leaving your terminal.
List assets for a site:
Upload a file as an asset:
Supported file types: png, jpg, jpeg, gif, svg, webp, avif (≤ 4 MB); pdf, doc, docx, xls, xlsx, ppt, pptx, txt, csv, odt, ods, odp, json, lottie (≤ 10 MB).
Update asset metadata:
Manage asset folders:
Improved site selection
The site selection prompt now uses a searchable list sorted by most recently updated, with site slugs shown alongside display names to help disambiguate sites with similar names.
CMS list alignment fix
Column headers in webflow cms list output now line up correctly with data rows.
Google Fonts and Adobe Fonts now ship with DevLink Export
DevLink Export now automatically loads Google Fonts and Adobe Fonts at runtime, matching how a published Webflow site renders them.
What changed
fonts.manifest.json— a new file in every export, listing the Google Fonts families and Adobe Fonts kit ID in use on your site.useInjectFontshook — a new hook that readsfonts.manifest.jsonon mount and injects the WebFont Loader and the Adobe kit scripts intodocument.head.DevLinkProvider.tsx— now callsuseInjectFonts, so mounting the provider is enough to load both font families.
Custom uploaded fonts continue to ship as @font-face rules in css/fonts.css and are unaffected.
Action required
If your site uses Adobe Fonts, you need to add your deployment domains to your Adobe Fonts web project allowlist before fonts will render outside *.webflow.io. Google Fonts requires no setup.
Run webflow devlink sync to pick up the changes. For full details, see Fonts in DevLink Export.