FNJ / Images & fonts
Fix images, fonts and assets after an HTML export
Find failed asset requests, correct relative paths, inspect external dependencies and preserve typography on the new host.
Start with the outcome
An asset inventory with working paths and a clear record of external dependencies. Locally captured files can be served from your new host; an embedded video or remote script may still rely on its original provider.
Choose your original builder below. The task is shared, but the dependencies, URL structure and missing features to check depend on the platform. Each guide includes a reviewed platform note, a full procedure and a prompt you can adapt for your agent.
Choose your website builder
Framer / Images & fonts
Fix images, fonts and assets after an HTML export
Framer output can contain captured image variants and local fonts alongside remaining dependencies. Check which file a responsive srcset actually requests and whether the required font weight loads. Compare the HTML mode's asset references separately from the original Next.js project's runtime modules; they are not identical bundles.
Read the guide →Webflow / Images & fonts
Fix images, fonts and assets after an HTML export
Webflow galleries may reference responsive image variants and external interaction scripts. Inspect srcset and CSS background URLs as well as image tags. Keep a record of which scripts remain remote and test their behavior from the new host before assuming the project no longer depends on Webflow services.
Read the guide →Gamma / Images & fonts
Fix images, fonts and assets after an HTML export
Gamma video and document embeds can stay external even when nearby images are captured locally. Inventory each player and document URL alongside ordinary assets. Replacing an embed with a file requires its own authorized source and controls; uploading the surrounding HTML does not make a hosted player independent.
Read the guide →systeme.io / Images & fonts
Fix images, fonts and assets after an HTML export
Funnel assets can include tracking scripts, embedded checkout and remote course media. Separate design assets from scripts handling business actions before removing dependencies. Keep credentials and contact data out of the export repository, and verify payment destinations using the service's appropriate test process.
Read the guide →Carrd / Images & fonts
Fix images, fonts and assets after an HTML export
Carrd can combine local-looking images with external embeds and CSS backgrounds. Test the whole landing page after lazy-loaded assets appear. Preserve background positioning and compare font wrapping when moving files, and document embedded booking or form services rather than treating them as ordinary downloadable assets.
Read the guide →Duda / Images & fonts
Fix images, fonts and assets after an HTML export
Duda widgets can fetch media and behavior from external endpoints. Check those requests from the deployed preview and record blocked or missing assets. Do not assume a font mismatch is caused by CSS until you verify that the actual font response and required weight are available.
Read the guide →Elementor / Images & fonts
Fix images, fonts and assets after an HTML export
Elementor page styles can reference WordPress upload folders, plugin CSS and externally served fonts. Inspect CSS background URLs and font requests on nested article routes. Keep only needed public dependencies, and maintain a separate WordPress backup; copying uploads alone does not preserve plugin configuration.
Read the guide →Squarespace / Images & fonts
Fix images, fonts and assets after an HTML export
Squarespace image blocks can request remote image variants while galleries depend on controls or scripts. Test responsive images and lightboxes from the new host. Inventory scheduling and store embeds as services, and retain their intended URLs until a working replacement is verified.
Read the guide →Strikingly / Images & fonts
Fix images, fonts and assets after an HTML export
Strikingly widget media and store assets may continue loading from hosted services. Inspect request failures and responsive image sizing separately. Keep widget dependencies documented, and do not mix member or order records with publicly downloadable asset files during handoff to a repository.
Read the guide →Tilda / Images & fonts
Fix images, fonts and assets after an HTML export
Tilda layouts can combine CSS-positioned media, web fonts and scripts controlling motion. Verify font responses before correcting alignment, then inspect images and backgrounds at the same viewport as the source. Removing a remote script requires a behavior review, not just a replacement file name.
Read the guide →Weebly / Images & fonts
Fix images, fonts and assets after an HTML export
Check Weebly assets from both the root page and legacy .html routes. Relative references can behave differently after a host normalizes a path. Preserve images and fonts with the exported pages, and catalog Square scripts as commerce dependencies rather than assuming they are local design assets.
Read the guide →Wix / Images & fonts
Fix images, fonts and assets after an HTML export
Wix media can load through platform endpoints and responsive transformations. Inspect the actual captured files and requested variants before renaming URLs. A remote script may also create the content referencing an image; absent markup and a failed asset request require different repair plans.
Read the guide →What a completed task should demonstrate
- Representative root and nested routes have no required asset failures.
- Font weights, image crops and responsive sources are reviewed.
- Remaining remote services are documented and intentional.