The case for freezing a PHP site
Legacy PHP applications — a hand-built CMS, an old CodeIgniter or Laravel marketing site, a Joomla or Drupal install nobody wants to upgrade — carry real maintenance cost and security risk. Once a site is mostly read-only, a static snapshot keeps it online with none of that:
- No PHP version to upgrade and no database to back up or patch.
- Hosting on a CDN or object storage for a fraction of the cost.
- No login pages or query endpoints for attackers to probe.
How the conversion handles dynamic pages
The crawler requests each page exactly as a visitor would, so templates, includes and database lookups are all resolved into final HTML. It follows internal links (including pagination links you configure), downloads referenced CSS, JavaScript, images, fonts and videos, and rewrites URLs so the result works from any domain — or from a subfolder if you enable relative links.
Anything that must respond to user input at runtime needs a substitute: map forms to a live endpoint, and replace search, logins or shopping carts with hosted services or client-side code.
How to do it with Static Converter
- 1Add the siteEnter the live URL and choose a full crawl.
- 2ConfigureEnable relative links, minification and WebP; map forms; add SEO fallbacks for pages missing titles or descriptions.
- 3ConvertWatch the live log; re-run later with "skip existing pages" for fast incremental updates.
- 4Deploy and retireHost the ZIP anywhere, switch DNS, then decommission the old server.