Skip to main content

Extraction with AuraExtract

AuraExtract is the engine that clones a live website's design. Give it a URL and it crawls the site, decomposes its visual identity into structured data, and stores the result as an extracted brand ready for migration into the Aura runtime.

Start an AuraExtract run

How it works​

Start an extraction from your brand by entering the source site's URL. The job runs through a series of stages, and you watch progress in real time — the extraction pipeline streams updates over WebSocket, so the checklist moves as the engine works, without refreshing the page.

The AuraExtract dashboard — start an extraction and watch recent jobs

Each stage has a clear pass/fail state:

  • Typography — font families, weights, sizes, and line heights.
  • Colors — palettes, backgrounds, accents, and gradients.
  • Layout — grid structure, section ordering, and spacing rhythm.
  • Components — recurring UI patterns such as navbars, heroes, cards, and forms.
  • Assets — images, icons, logos, and other media the site uses.
  • Tokens — the normalized design-token set derived from everything above.

Retrying failed stages​

Websites are messy: a single broken stylesheet or a bot-blocked asset can fail one stage while the rest succeed. Rather than re-running the whole extraction, you can retry individual failed stages. The engine re-attempts only that piece of work and stitches the result back into the existing extraction.

Editable design tokens​

When the extraction completes, the site's design lives in your brand as a set of design tokens — and they are not read-only. Open them in the brand workspace and adjust values before or after migration:

  • Swap a color for your client's exact brand hex.
  • Tighten a heading scale or adjust line-height values.
  • Remove tokens the clone picked up but you do not want.

Because the rest of AURAFUSE consumes these tokens — Aura Engine's rebuild, AI content generation, media styling — a small token edit propagates cleanly through the whole product.

Tips​

  • Public, statically rendered sites extract best. Heavy client-side apps may miss content that only appears after interaction.
  • Retry before restarting: stage retries are much cheaper than full runs.
  • Review the extracted tokens before migrating; clean tokens make the Aura rebuild noticeably better.