Book an inspectionInspection
Joomla
HTMLAstroVite
Joomla template output → local page routes

Keep your Joomla pages
while you replace the CMS.

Capture public template markup and available assets. Keep query-based page URLs separate and use the source project to plan a move away from Joomla extensions.

Free · no account · nothing changes on your live site

Paste the full public page URL, including its query string when that selects a particular article or view. Do not use an administrator URL.

What comes with you

Your Joomla front end

  • Public template output

    Rendered HTML and discoverable design files from your published pages.

  • Distinct query-based pages

    URLs with different query strings get separate files instead of being merged into one index page.

  • A route map for the move

    Original URLs mapped to local pages, plus detected forms, scripts and component endpoint dependencies.

Plan the rest of the move

Replacements to build

  • PHP templates and overrides

    The captured front end does not recover server-side template logic or override files.

  • Extension and component behavior

    Replace extension-backed forms, user flows and AJAX endpoints as needed; copied markup alone cannot implement them.

  • Content and redirect rules

    Move the content store separately and use the route map to prepare redirects from your existing URLs.

Built for the move

Your Joomla move,
one step at a time.

  1. Choose an article or landing page.

    Use its full public URL, including query parameters, to preserve the exact view you are moving.

  2. Compare the local routes.

    Run the project and inspect routes.json to see how captured URLs map to local files.

  3. Replace extension-dependent flows.

    Review the dependency report, migrate content separately and build redirect rules before replacing Joomla.

Questions,
answered.

Can't find what you need? You'll get an answer from an engineer within a day.

Talk to us
What happens to index.php query URLs?

The exporter treats query strings as part of page identity and maps captured pages to distinct local files. The original-to-output mapping is included in routes.json.

Are Joomla extensions exported as source?

No. Public output and available assets are captured. Extension PHP code, administrator settings and database tables need a separate migration.

Will I get the original PHP code, CMS database or a React rewrite?

You get the public front-end HTML, downloaded assets and a runnable project structure. PHP source, database content, user accounts and CMS workflows cannot be recovered from a public URL. Astro and Vite outputs retain editable HTML; they are not generated component rewrites.

Can the exported project work without the original hosting?

Downloaded assets and copied pages can be served locally. CSS imports, fonts and background images are followed and localized when available. Missing assets remain remote, while forms, embedded services and runtime scripts may still depend on the old host. The report identifies detected dependencies so you can rebuild them.

How much can I export free?

Choose one, three or five linked public pages. Each project is capped at 100 asset attempts, 5 MB per asset, 2 MB per page and 25 MB total fetched data. Query-based pages are kept distinct. Pages and assets beyond the caps are listed in the report. No account or card required; request limits apply.

Explore website to code export →