A finished static website should not have to be rebuilt just because it needs to live in WordPress. Shilpi HTML Studio imports complete HTML projects while preserving the files, paths, and structure that already make the design work.
Bring the whole project, not fragments
Many import workflows begin by copying sections into a page builder. That can be useful for a single landing page, but it often breaks down when a project contains multiple documents, shared stylesheets, scripts, images, fonts, and carefully organised folders.
Shilpi HTML Studio accepts the complete project as a ZIP. It preserves the original HTML, CSS, JavaScript, media, fonts, and directory layout instead of flattening everything into disconnected blocks.
One WordPress page for every HTML document
During import, each HTML document becomes a corresponding WordPress page. Relative asset paths continue to work, so a stylesheet or image does not need to be manually relinked simply because the project moved into WordPress.
- Multi-page static projects remain multi-page websites.
- Shared assets keep their existing folder relationships.
- HTML remains readable instead of being converted into opaque builder data.
- WordPress manages publishing and routes around the imported project.
Edit visually without surrendering the source
Imported pages open in Shilpi Builder for visual editing. Content, layout, classes, and page-specific code can be adjusted through the same canvas used for native Shilpi pages. The underlying project remains recognisable to a developer, which makes later maintenance and handoff substantially easier.
This is particularly useful when an AI agent produces a complete static website. The agent can create ordinary frontend files, the owner can import them, and the design can still be reviewed and refined inside WordPress.
Export a portable project again
WordPress does not have to become the final resting place for the source. Shilpi HTML Studio can export Builder changes back into a portable ZIP, keeping the project useful outside the current installation. That makes the workflow suitable for staging, client delivery, backups, and migration.
Compatibility for existing HTML packages
Version 1.0.0 moves the HTML Packages system out of the Shilpi theme and into a focused companion plugin. Existing packages created with Shilpi 1.10 through 1.12 continue to use the same post types, metadata, upload paths, and integration hooks.
Separating the feature from the theme lets the importer and export workflow evolve independently while keeping the core theme smaller.
Security and project trust
HTML Studio is available to administrators with unfiltered HTML access. A complete frontend project can contain executable JavaScript, so only trusted packages should be imported. This is the same trust decision involved in deploying any static project to a public server.
Requirements
- WordPress 6.4 or newer
- PHP 8.0 or newer
- The Shilpi theme must be active
- A trusted ZIP containing the static HTML project
Get Shilpi HTML Studio
Shilpi HTML Studio is free and released under the GPL. Install it from Shilpi → Plugins in your WordPress dashboard, or download Shilpi HTML Studio 1.0.0 as a ZIP.
After activation, open Shilpi → HTML Studio, upload the project ZIP, and let WordPress publish the existing design without a manual rewrite.

