<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[ThemeVault Blog]]></title><description><![CDATA[Free and premium website templates: HTML, WordPress, Elementor, Next.js and Astro. Guides from building 190+ of them]]></description><link>https://themevault.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6afbed37ba611ce8e5b07f23/9ec90769-a521-465c-b1d9-90be370e543d.png</url><title>ThemeVault Blog</title><link>https://themevault.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 14:54:12 GMT</lastBuildDate><atom:link href="https://themevault.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How to Install an Elementor Template Kit (2026 Guide)]]></title><description><![CDATA[How to install an Elementor template kit: Elementor website templates, Envato kits with Template Kit Import, and fixes when it doesn't look like the demo.]]></description><link>https://themevault.hashnode.dev/how-to-install-an-elementor-template-kit-2026-guide</link><guid isPermaLink="true">https://themevault.hashnode.dev/how-to-install-an-elementor-template-kit-2026-guide</guid><category><![CDATA[WordPress]]></category><category><![CDATA[Elementor]]></category><category><![CDATA[webdev]]></category><category><![CDATA[Tutorial]]></category><dc:creator><![CDATA[ThemeVault]]></dc:creator><pubDate>Wed, 18 Nov 2026 06:08:03 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6afbed37ba611ce8e5b07f23/da89fccd-f765-47fd-afef-db7140277d5d.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>You bought or downloaded an Elementor template kit, you have a zip file on your desktop, and now you’re staring at the WordPress dashboard wondering where it goes. That’s a very normal place to be. The confusing part isn’t that installing a kit is hard. It’s that “Elementor template kit” means two different things, they install in two different places, and most guides only describe one of them.</p>
<p>To write this properly we didn’t work from memory. On 2 November 2026 we set up clean WordPress sites (WordPress 7.1, the free Hello Elementor theme, free Elementor 4.2.4), built a small three-page café kit called Corner Crumb, exported it in both formats, and installed it again on empty sites the way a buyer would. Every menu name, button and message below is copied from those screens. Elementor renames things often, so if your screen looks slightly different, the steps will still be in the same order.</p>
<h2>First, work out which kind of kit you have</h2>
<p>Envato’s own export plugin explains the difference better than most articles do, so here it is in their words. An <strong>Envato Template Kit</strong> is the format sold on ThemeForest and Envato Elements: “Customers can pick and choose individual templates to import. Supports 3rd party plugins.” An <strong>Elementor Kit</strong> (Elementor now calls these “Website Templates”) is a full-site package: “Customers cannot choose individual templates, only a ‘Full Site’ import overwriting their current site.”</p>
<p>You can usually tell which one you have in ten seconds. Open the zip (don’t install it yet, just look inside):</p>
<ul>
<li>If you see a <strong>templates</strong> folder full of .json files, a <strong>screenshots</strong> folder and a manifest.json, it’s an <strong>Envato-style kit</strong>. Use the Template Kit Import plugin (Route B below).</li>
<li>If you see <strong>site-settings.json</strong>, a <strong>content</strong> folder and a <strong>wp-content</strong> folder, it’s an <strong>Elementor website template</strong>. Use Elementor’s own importer (Route A).</li>
<li>If the zip has a style.css and functions.php inside a folder, it isn’t a kit at all. It’s a WordPress theme, and it installs under Appearance → Themes (Route C).</li>
</ul>
<p>Many marketplace downloads are a zip <em>inside</em> a zip, with the licence and help files next to the real kit. If the folders above aren’t there, look for a second zip and use that one.</p>
<h2>Before you start: three checks</h2>
<p><strong>Use a fresh or test site if you can.</strong> A full-site kit import replaces your front page, adds pages and menus, and changes your global colours and fonts. Elementor doesn’t delete your existing pages, but it does change how the whole site looks. If you’re importing into a site that already has content, take a backup first.</p>
<p><strong>Install the theme the kit was made for.</strong> Almost every kit is built and tested with Hello Elementor, the free, almost-empty theme from the Elementor team. Envato’s importer says so outright: “This Template Kit has only been tested with the ‘Hello Elementor’ WordPress theme.” Install it under Appearance → Themes → Add New Theme before you import anything. Other themes often add their own title bars, sidebars and fonts on top of the kit.</p>
<p><strong>Check whether the kit needs Elementor Pro.</strong> This is the one that catches people out. Headers, footers, popups and blog archive templates are Pro features, so a kit that includes them only works fully with Pro. Good kit pages say “Elementor Pro required” or “works with free Elementor” clearly. If it doesn’t say, assume the header and footer won’t import on the free version (we explain what you see when that happens below).</p>
<h2>Route A: install an Elementor website template (.zip)</h2>
<p>This is Elementor’s built-in importer. It needs only the free Elementor plugin.</p>
<h3>1. Open the importer</h3>
<p>In wp-admin go to <strong>Elementor → Tools</strong> and click the <strong>Website Templates</strong> tab. You’ll see two boxes: “Export this website” and “Apply a Website Template”. Under Apply a Website Template click <strong>Import</strong>.</p>
<img src="https://www.themevault.net/images/uploads/blog-install-elementor-template-kit/elementor-tools-website-templates.jpg" alt="Elementor Tools screen, Website Templates tab, with the Export this website and Apply a Website Template boxes" style="display:block;margin:0 auto" />

<p><em>Elementor → Tools → Website Templates. Kits are applied from here, not from the Templates menu.</em></p>
<p>Don’t confuse this with <strong>Templates → Import Templates</strong> in the same menu. That button takes a single template file (one .json), not a whole kit, and a full kit zip uploaded there won’t give you the pages and settings.</p>
<h3>2. Upload the zip</h3>
<p>The next screen says “Import a website template” with a box to click or drag a file into. Drop your kit’s .zip on it. Ours was 8.5 KB because it had no photos; a real kit with images is usually several megabytes, so give it a moment.</p>
<h3>3. Choose what to apply</h3>
<p>After the upload Elementor shows “Select which parts you want to apply”, with everything ticked:</p>
<ul>
<li><strong>Content</strong>: the kit’s pages, posts and menus.</li>
<li><strong>Templates</strong>: saved templates, headers, footers, archives, popups. On free Elementor this row is greyed out with an <strong>Upgrade</strong> button, because those are Pro features.</li>
<li><strong>Settings &amp; configurations</strong>: global colours, global fonts, theme style, layout settings.</li>
<li><strong>Plugins</strong>: “All plugins are required for this website templates to work.”</li>
</ul>
<img src="https://www.themevault.net/images/uploads/blog-install-elementor-template-kit/elementor-select-parts.jpg" alt="Elementor import screen titled Select which parts you want to apply, with Content, Templates (Upgrade), Settings and configurations, and Plugins" style="display:block;margin:0 auto" />

<p><em>On free Elementor the Templates row is locked. Your kit’s pages and styles still come in.</em></p>
<p>Click <strong>Edit</strong> on the Plugins row before you go on. A kit records every plugin that was active on the site it was exported from, and the importer will activate them all. Our first test kit listed three plugins, and all three were switched on during the import, including one the kit didn’t actually need. If you see something you don’t want, untick it here.</p>
<h3>4. Import and apply</h3>
<p>Click <strong>Import and apply</strong>. You’ll see “Setting up your website template… Don’t close this window until the process is finished” while it activates plugins and creates pages. Leave the tab alone until it finishes. When it’s done you get “Your website template is now live on your site!” and a list of what was imported.</p>
<img src="https://www.themevault.net/images/uploads/blog-install-elementor-template-kit/elementor-import-done.jpg" alt="Elementor confirmation: Your website template is now live on your site, with the list of imported pages, settings and plugins" style="display:block;margin:0 auto" />

<p><em>The finish screen lists everything the kit changed.</em></p>
<h3>5. Tidy up</h3>
<p>Visit the site. On ours, the kit’s Home page had become the front page and the brand colours were applied everywhere. One thing didn’t change: the site title still said “Fresh site”, because the kit doesn’t touch it. Set yours under <strong>Settings → General</strong>, then work through the kit’s pages replacing its text and photos with your own.</p>
<p>A note on Elementor’s own library: clicking the Website Templates tab heading opens a gallery of ready-made kits you can apply directly. When we counted on 2 November it listed 58, and only 6 were marked Free. The other 52 showed an Upgrade button (9 on the Essential plan, 43 on Advanced and higher). So if you’re browsing there on the free plugin, use the <strong>Plan → Free</strong> filter first to save yourself some disappointment.</p>
<h2>Route B: install an Envato kit with Template Kit Import</h2>
<p>Kits from ThemeForest and Envato Elements work differently. Instead of rebuilding your whole site, they import each page design as a template, and you place those templates onto pages yourself. It takes a few more clicks, but you choose exactly what goes where.</p>
<h3>1. Install the right plugin</h3>
<p>Go to <strong>Plugins → Add Plugin</strong> and search for <strong>Template Kit Import</strong>. Be careful here: in our search the first result was a different plugin (an add-ons pack). The one you want is <strong>“Template Kit – Import” by Envato</strong>, which had 400,000+ active installations. Install it and click Activate.</p>
<img src="https://www.themevault.net/images/uploads/blog-install-elementor-template-kit/template-kit-import-search.jpg" alt="WordPress plugin search for Template Kit Import, showing Template Kit – Import by Envato with 400,000+ active installations as the second result" style="display:block;margin:0 auto" />

<p><em>The Envato importer was the second result, not the first.</em></p>
<p>One technical note: the plugin’s <a href="http://WordPress.org">WordPress.org</a> listing currently asks for PHP 8.3. If your host is on an older PHP version, change it in your hosting panel first (most hosts have a one-click PHP version switch).</p>
<h3>2. Upload the kit</h3>
<p>The plugin adds its screen under <strong>Tools → Template Kit</strong>. Click <strong>Upload Template Kit (Zip File)</strong> and choose the kit zip. Use the inner kit zip, not the whole download, if your purchase came as a zip inside a zip.</p>
<p>After the upload you’ll see the kit’s name and a card for every template in it, each with an <strong>Import Template</strong> button.</p>
<img src="https://www.themevault.net/images/uploads/blog-install-elementor-template-kit/template-kit-cards.jpg" alt="Template Kit Import screen for the Corner Crumb Cafe kit, showing cards for Global Kit Styles, Visit us, Menu and Home, each with an Import Template button" style="display:block;margin:0 auto" />

<p><em>Every page design in the kit gets its own card. Global Kit Styles is the one to import first.</em></p>
<h3>3. Install the requirements</h3>
<p>Above the cards you may see a yellow banner: “Attention! There are 2 requirements that need installing for this Template Kit to work correctly.” Click <strong>Install Requirements</strong>. For our kit, the two “requirements” weren’t plugins at all. They were two Elementor settings (Elementor’s default colour schemes and default typography schemes), which the importer switches off so the kit’s own colours and fonts can take over. Leave both ticked and click <strong>Install Above Selected Requirements</strong>. Kit authors also record which plugins their kit depends on when they export it, so if the kit was built with an extra plugin (a forms plugin, say), check the kit’s description and install it before importing the pages that use it.</p>
<img src="https://www.themevault.net/images/uploads/blog-install-elementor-template-kit/template-kit-requirements.jpg" alt="Missing Requirements dialog listing Elementor default color schemes and typography schemes, with a note that the kit was tested with Hello Elementor" style="display:block;margin:0 auto" />

<p><em>The requirements screen also reminds you which theme the kit was tested with.</em></p>
<h3>4. Import Global Kit Styles first</h3>
<p>This is the step most people skip, and it’s why their kit “looks wrong”. Find the card called <strong>Global Kit Styles</strong> (“the global theme styles configured through the Elementor Theme Styles area”) and click <strong>Import Template</strong> on it before anything else. On our test site this switched the site’s Elementor styles over to the kit’s own set (it appeared as “Kit Styles: Corner Crumb Cafe”), with its colour palette and fonts.</p>
<p>We tried it the wrong way round first, deliberately. Without Global Kit Styles, the Home template came in with Elementor’s default bright blue headings and the default font, nothing like the kit preview:</p>
<img src="https://www.themevault.net/images/uploads/blog-install-elementor-template-kit/kit-without-global-styles.jpg" alt="The kit's home page inserted without Global Kit Styles: the main heading shows in Elementor's default light blue instead of the kit's brown" style="display:block;margin:0 auto" />

<p><em>Without Global Kit Styles: default blue heading, default font, plus the theme’s page title on top.</em></p>
<h3>5. Import the page templates you want</h3>
<p>Now click <strong>Import Template</strong> on each page design you want. Each card then changes to “View Template” and “Import Again”. Here’s the bit the plugin doesn’t spell out: importing doesn’t create a page. It saves the design into <strong>Elementor → Templates</strong> (your saved templates). Your site’s pages are still empty until you place the templates on them.</p>
<h3>6. Put a template on a page</h3>
<ol>
<li>Go to <strong>Pages → Add Page</strong>, give it a title (for example Home), and open it with <strong>Edit with Elementor</strong>.</li>
<li>In the empty page area click the folder icon, <strong>Add Template</strong>.</li>
<li>The library opens with three tabs: Blocks, Pages and Templates. Click <strong>Templates</strong>. That’s where your imported kit designs are.</li>
<li>Hover the one you want and click <strong>Insert</strong>.</li>
</ol>
<h3>7. Set the page layout to full width</h3>
<p>If you publish now, you’ll probably see the page title (“Home”) printed above the design, and the content boxed in by the theme. Fix it in the editor: click the <strong>Page Settings</strong> icon in the top bar, then under <strong>Page Layout</strong> choose <strong>Elementor Full Width</strong> (the other options are Default, Elementor Canvas and Theme). Full Width keeps your theme’s header and footer; Canvas removes them too, which suits landing pages. There’s also a <strong>Hide Title</strong> switch in the same panel.</p>
<img src="https://www.themevault.net/images/uploads/blog-install-elementor-template-kit/page-settings-layout.jpg" alt="Elementor Page Settings panel with the Page Layout menu showing Default, Elementor Canvas, Elementor Full Width and Theme" style="display:block;margin:0 auto" />

<p><em>Page Settings → Page Layout → Elementor Full Width removes the extra title and the boxed layout.</em></p>
<p>Click <strong>Publish</strong>. With Global Kit Styles imported and the layout set, our page finally matched the kit: brown serif headings, the cream hero and no stray title.</p>
<img src="https://www.themevault.net/images/uploads/blog-install-elementor-template-kit/kit-with-global-styles.jpg" alt="The same kit page after importing Global Kit Styles and setting Elementor Full Width: brown serif heading on a cream band, no page title" style="display:block;margin:0 auto" />

<p><em>The same template after steps 4 and 7.</em></p>
<p>Repeat steps 6 and 7 for each page, then set your front page under <strong>Settings → Reading</strong> (“A static page”, then pick your Home page) and build your menu under <strong>Appearance → Menus</strong>. An Envato kit doesn’t do those for you.</p>
<h2>If something looks wrong after importing</h2>
<p><strong>The colours and fonts are Elementor’s defaults (light blue headings, plain font).</strong> Global Kit Styles wasn’t imported, or another kit’s styles are still active. Go back to Tools → Template Kit, open the kit and import Global Kit Styles. For Route A kits, re-run the import with Settings &amp; configurations ticked.</p>
<p><strong>There’s a page title or a narrow column above the design.</strong> Set Page Layout to Elementor Full Width (or switch Hide Title on) in that page’s Page Settings.</p>
<p><strong>The header and footer from the preview are missing.</strong> On free Elementor that’s expected: theme headers and footers are a Pro feature, so the Templates row was locked during import. Your theme’s own header shows instead. Either add Elementor Pro, or use a theme whose header and footer are part of the theme itself.</p>
<p><strong>The upload fails or nothing happens.</strong> Check you’re uploading the inner kit zip, not the whole marketplace download. Large kits can also hit your host’s upload limit; the maximum size is shown under Media → Add Media File, and your host can raise it.</p>
<p><strong>Some sections are blank or show a notice about a missing widget.</strong> The kit uses a widget from a plugin you haven’t installed (or from Elementor Pro). Look at the kit’s requirements again and install what it lists.</p>
<p><strong>The photos are grey placeholders.</strong> Many kits ship without the stock photos the preview uses, for licensing reasons. Envato’s exporter even has a step where the author records where each image came from. Replace them with your own photos; that’s better for your business anyway.</p>
<h2>Route C: an Elementor theme, when you don’t want to assemble it</h2>
<p>Kits are flexible, but you’ve probably noticed how many steps sit between “I have a zip” and “my site looks like the preview”: the right theme, the requirements, Global Kit Styles first, then every page by hand, then layout, front page and menu. And on the free plugin you still won’t get the header and footer you saw in the demo.</p>
<p>That’s why our own Elementor products are built as <strong>themes</strong> rather than kits. Take <a href="https://www.themevault.net/bistrofeast-restaurant-and-cafe-elementor-wordpress-theme?utm_source=hashnode&amp;utm_medium=referral&amp;utm_campaign=how-to-install-elementor-template-kit">Bistrofeast, our restaurant and café Elementor theme</a>. You install it like any WordPress theme (Appearance → Themes → Add New Theme → Upload Theme), then click once to install its companion plugin, which comes inside the theme. After that, <strong>Appearance → Import demo content → Import the demo</strong> takes about a minute and builds the menu items, chefs, gallery, reviews, blog posts and the pages (Home, About, Book a table, Contact, Thank you), sets up the header menu and makes Home the front page.</p>
<img src="https://www.themevault.net/images/uploads/blog-install-elementor-template-kit/bistrofeast-demo-import.jpg" alt="The Bistrofeast Elementor theme's Import demo content screen in wp-admin with the Import the demo button" style="display:block;margin:0 auto" />

<p><em>One button instead of a page-by-page assembly.</em></p>
<p>It runs on <strong>free Elementor</strong>: the header and footer belong to the theme and are edited in the Customizer, so nothing is locked behind Pro. Each section of the design is its own Elementor widget (search “Bistrofeast” in the widget panel) with its text, layout switches and colours in the left panel. Running the import again updates the demo records rather than duplicating them, and it never deletes anything you already have.</p>
<p>A theme isn’t always the better choice. If you want to mix and match designs, or you already own Elementor Pro and love building headers in Theme Builder, a kit gives you more freedom. But if you want a finished site you can edit, on the free plugin, with the least setup, a theme is the shorter road. You can browse all our <a href="https://www.themevault.net/elementor-themes?utm_source=hashnode&amp;utm_medium=referral&amp;utm_campaign=how-to-install-elementor-template-kit">Elementor themes</a>, and if you’re still deciding between platforms, our comparison of <a href="https://www.themevault.net/nextjs-vs-wordpress?utm_source=hashnode&amp;utm_medium=referral&amp;utm_campaign=how-to-install-elementor-template-kit">Next.js vs WordPress for a small business website</a> covers that choice.</p>
<h2>FAQ</h2>
<h3>Do I need Elementor Pro to install a template kit?</h3>
<p>No. The importers work on free Elementor. But if the kit includes headers, footers, popups or archive templates, those parts need Pro, and on the free version they’re skipped (Elementor’s importer shows that row locked with an Upgrade button). The pages and global styles still import.</p>
<h3>Where do I upload an Elementor kit zip?</h3>
<p>For an Elementor website template, go to Elementor → Tools → Website Templates → Apply a Website Template → Import. For an Envato kit from ThemeForest or Envato Elements, install the “Template Kit – Import” plugin and use Tools → Template Kit → Upload Template Kit (Zip File). Templates → Import Templates is only for single template files.</p>
<h3>Why does my imported kit not look like the demo?</h3>
<p>Usually one of three things: Global Kit Styles wasn’t imported (so Elementor’s default colours and fonts show), the page layout isn’t set to Elementor Full Width (so the theme adds a title and boxes the content), or the demo’s header and footer need Elementor Pro. Also check you’re using the Hello Elementor theme.</p>
<h3>Will importing a kit delete my existing pages?</h3>
<p>In our tests neither importer deleted existing pages. An Elementor website template does replace your front page and your global colours and fonts, though, which changes how every page looks. Take a backup before importing into a site that already has content.</p>
<h3>Which theme should I use with an Elementor kit?</h3>
<p>Hello Elementor, unless the kit says otherwise. Envato’s importer states that kits have only been tested with it, and it adds almost nothing of its own, so the kit’s design shows as intended.</p>
<h3>What’s the difference between a template kit and an Elementor theme?</h3>
<p>A kit is a set of page designs and styles that you import into Elementor and place on pages yourself, on top of a theme such as Hello. An Elementor theme is the whole website package: it includes its own header and footer, and usually a one-click demo import that creates the pages, menu and content in one go.</p>
<hr />
<p><em>Originally published on</em> <a href="https://www.themevault.net/how-to-install-elementor-template-kit?utm_source=hashnode&amp;utm_medium=referral&amp;utm_campaign=how-to-install-elementor-template-kit"><em>ThemeVault</em></a><em>.</em></p>
]]></content:encoded></item><item><title><![CDATA[HTML Template to WordPress: Convert It Yourself or Use a WordPress Version?]]></title><description><![CDATA[You found an HTML template you love, and now you want it on WordPress, so you (or a client) can change the text, add a dish to the menu or publish a post…]]></description><link>https://themevault.hashnode.dev/html-template-to-wordpress-convert-it-yourself-or-use-a-wordpress-version</link><guid isPermaLink="true">https://themevault.hashnode.dev/html-template-to-wordpress-convert-it-yourself-or-use-a-wordpress-version</guid><category><![CDATA[WordPress]]></category><category><![CDATA[HTML]]></category><category><![CDATA[webdev]]></category><category><![CDATA[Beginner Developers]]></category><dc:creator><![CDATA[ThemeVault]]></dc:creator><pubDate>Tue, 17 Nov 2026 06:27:19 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6afbed37ba611ce8e5b07f23/b5cdd0e0-bcdb-4d80-b949-395b2a791068.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>You found an HTML template you love, and now you want it on WordPress, so you (or a client) can change the text, add a dish to the menu or publish a post without opening a code editor. Good news first: it can be done, and the first part is easier than it looks. The less good news is that “it shows up in WordPress” and “you can run your business from WordPress” are two very different finish lines, and most tutorials stop at the first one.</p>
<p>To write this honestly, we did the conversion ourselves. On 3 November 2026 we took our free Bistrofeast restaurant template (eleven HTML pages, Bootstrap 5, the usual css, js, fonts and images folders) and turned it into a WordPress theme on a clean WordPress 7.1 site, the way a developer would. Below is every step, the mistakes we made on the way, how long it took, and the point where we stopped and asked whether it was worth it.</p>
<h2>The short answer</h2>
<p>If you’re a developer, or you want to learn how WordPress themes work, converting an HTML template is a very good exercise and you can have the home page running in an afternoon. If you need a working business site (editable pages, a menu you can update, a booking or contact form that actually sends), converting it yourself is a long project, and starting from a theme that was built for WordPress is usually the cheaper, faster route. There’s also a middle way: rebuild the design in a page builder. We cover all three.</p>
<h2>What “converting HTML to WordPress” actually means</h2>
<p>An HTML template is a set of finished pages. Every word, price and photo is typed straight into the .html files. WordPress works the other way round: content lives in a database, and the theme is a set of PHP templates that pull that content in and wrap it in your design. So a conversion has two halves:</p>
<ol>
<li><strong>Making WordPress show the design.</strong> Splitting the HTML into a header, footer and page templates, loading the CSS and JavaScript properly, fixing paths and links, turning the nav into a WordPress menu.</li>
<li><strong>Making the content editable.</strong> Replacing the hard-coded text, menus, team cards, galleries and forms with things you can manage from wp-admin.</li>
</ol>
<p>The first half is mostly mechanical. The second half is where the hours go. Keep that split in mind, because it explains almost everything below.</p>
<h2>Step 1: the version everyone tries first</h2>
<p>The quickest experiment is to copy the template folder into <strong>wp-content/themes</strong>, add a <strong>style.css</strong> with a theme name at the top (WordPress won’t list a theme without it), rename index.html to index.php and activate it under Appearance → Themes. WordPress accepts it straight away. Then you open the site:</p>
<img src="https://www.themevault.net/images/uploads/blog-html-to-wordpress/html-to-wordpress-naive.jpg" alt="The Bistrofeast template's home page in WordPress after a plain copy and rename: unstyled black text, giant icons and no images" style="display:block;margin:0 auto" />

<p><em>Copy, rename, activate: the HTML is there, but nothing else is. 0 of 33 images loaded.</em></p>
<p>That’s what we got: <strong>0 of 33 images and 22 failed requests</strong>. Every stylesheet, script and photo returned “not found”. The reason is simple once you see it. The template says <code>href="css/style.css"</code>, and the browser looks for that next to the page’s address. In the HTML version that was the template folder. In WordPress the page lives at your site’s root, so it asks for <a href="http://yoursite.com/css/style.css"><strong>yoursite.com/css/style.css</strong></a>, which doesn’t exist. The files are really in wp-content/themes/your-theme/css/.</p>
<h2>Step 2: make WordPress show the design properly</h2>
<p>This is the classic theme conversion. On our template it came down to six jobs.</p>
<h3>Split the page into header, footer and template</h3>
<p>Everything from <code>&lt;!DOCTYPE html&gt;</code> down to the end of the site header goes into <strong>header.php</strong>. The footer and closing tags go into <strong>footer.php</strong>. The home page’s sections go into <strong>front-page.php</strong>, wrapped in <code>get_header()</code> and <code>get_footer()</code>. You also need an <strong>index.php</strong> as the fallback for every other page; ours prints the page title and the editor content between the same header and footer.</p>
<h3>Load the CSS and JavaScript the WordPress way</h3>
<p>Delete the template’s <code>&lt;link&gt;</code> and <code>&lt;script&gt;</code> tags and load the same files from <strong>functions.php</strong>:</p>
<pre><code class="language-php">add_action( 'wp_enqueue_scripts', function () {
  wp_enqueue_style( 'bootstrap',
    get_theme_file_uri( 'css/bootstrap.min.css' ) );
  wp_enqueue_style( 'bistrofeast',
    get_theme_file_uri( 'css/style.css' ),
    array( 'bootstrap' ) );
  wp_enqueue_script( 'bistrofeast',
    get_theme_file_uri( 'js/main.js' ),
    array(), null,
    array( 'strategy' =&gt; 'defer' ) );
} );
</code></pre>
<p>Then add <code>&lt;?php wp_head(); ?&gt;</code> just before <code>&lt;/head&gt;</code> and <code>&lt;?php wp_footer(); ?&gt;</code> just before <code>&lt;/body&gt;</code>. Those two lines are where WordPress prints your styles and scripts, plus everything plugins add (SEO tags, analytics, the admin bar). Skip them and many plugins quietly stop working, because they have nowhere to print their code. While you’re in header.php, swap the hard-coded <code>&lt;html lang="en"&gt;</code> and <code>&lt;body class="..."&gt;</code> for <code>language_attributes()</code> and <code>body_class()</code>, and let WordPress print the page title by adding <code>add_theme_support( 'title-tag' )</code>.</p>
<h3>Fix every image path, including the hidden ones</h3>
<p>Each <code>images/...</code> path needs the theme folder in front of it: <code>&lt;?php echo esc_url( get_theme_file_uri( 'images/hero.jpg' ) ); ?&gt;</code>. Our home page alone had 41 of them. Most are in plain <code>src</code> attributes, but watch for the ones that aren’t. Bistrofeast, like many modern templates, lazy-loads background photos with an attribute (<code>data-tv-bg="images/gallery-1.jpg"</code>) that its JavaScript reads later. Miss those and the page looks fine at the top, then shows grey boxes further down.</p>
<h3>Turn page links into WordPress links</h3>
<p>Links such as <code>about.html</code> and <code>reservation.html</code> point at files that no longer exist. Replace them with <code>home_url( '/about/' )</code> and so on, and create those pages in wp-admin.</p>
<h3>Make the navigation a real WordPress menu</h3>
<p>Register a menu location (<code>register_nav_menus()</code>), build the menu under Appearance → Menus, and print it with <code>wp_nav_menu()</code>. This was the fiddliest part of our test. WordPress prints its own class names (<code>menu-item</code>, <code>sub-menu</code>), but the template’s CSS and JavaScript expect its own (<code>tv-nav__item</code>, <code>tv-nav__link</code>, a caret button for drop-downs). We had to write a small custom menu walker, about 25 lines of PHP, to print the template’s exact markup so the mobile menu and drop-down kept working.</p>
<h3>Remove the duplicate meta tags</h3>
<p>The template has its own <code>&lt;title&gt;</code>, description and social sharing tags. WordPress and your SEO plugin print those now, so delete the template’s copies. A small warning from experience: we first rewrote the image paths and <em>then</em> removed the old tags, and a broken leftover of the sharing image tag ended up as stray text at the very top of the page. Clean the head first, then fix paths.</p>
<p>After those six jobs, the home page in WordPress matched the HTML demo exactly, with no failed requests.</p>
<img src="https://www.themevault.net/images/uploads/blog-html-to-wordpress/html-to-wordpress-converted.jpg" alt="The converted Bistrofeast home page running in WordPress: dark hero with the headline Seasonal food, cooked without the fuss, the menu and a Book a table button" style="display:block;margin:0 auto" />

<p><em>The same template after step 2: identical to the HTML demo, now served by WordPress.</em></p>
<p>How long did that take? About 30 minutes for us, and that’s the flattering number: we know this template inside out and scripted the edits. For someone doing it by hand for the first time, an afternoon to a day for the home page is more realistic.</p>
<h2>Step 3: the part that takes the real time</h2>
<p>This is where we stopped celebrating. With the home page looking perfect, we tested what an owner would actually do with the site.</p>
<p><strong>We clicked “About”.</strong> We got a blank page with the word “About” and the footer. The template’s About design (its story section, numbers, team) didn’t come across, because we had only converted the home page. Each of the other ten HTML pages needs its own PHP template. Worse, the site name and the menu had disappeared: the template’s header has white text designed to sit over the dark home page photo, so on a plain white inner page it was white on white.</p>
<img src="https://www.themevault.net/images/uploads/blog-html-to-wordpress/html-to-wordpress-about-page.jpg" alt="The About page of the converted theme: only the word About on a white page, and the site name and menu invisible in the header" style="display:block;margin:0 auto" />

<p><em>One page converted, ten to go. Note the empty header: white text on a white page.</em></p>
<p><strong>We tried to change the headline.</strong> We created a Home page in WordPress, typed a new headline into the block editor, set it as the front page and published. The site still said “Seasonal food, cooked without the fuss.” Of course it did: that text lives in front-page.php. Every headline, price, chef and review on the converted site is still typed into a PHP file. To change it you edit code, which is exactly what you were trying to get away from.</p>
<p><strong>We tested the booking form.</strong> It showed “Thank you, your message has been sent.” Nothing was sent anywhere. Like most HTML templates, Bistrofeast’s forms only simulate a send. The template’s own JavaScript says so in a comment, asking you to connect it to a form service or your own code. On a converted WordPress site that’s easy to miss, and for a restaurant it means every booking request quietly disappears. If you convert, test every form with a real submission and connect it to something (a form plugin such as Contact Form 7, WPForms or Fluent Forms, or your own handler).</p>
<p>To finish the job properly you’d still need to:</p>
<ul>
<li>build a template for each remaining page (or a page header and blocks that work on any page);</li>
<li>make the text and photos editable, typically with block patterns, custom blocks, the Customizer or a field plugin such as ACF;</li>
<li>turn repeating things (dishes, chefs, gallery photos, reviews) into records you can add in wp-admin, so the menu updates when you add a dish;</li>
<li>make the blog pages pull real WordPress posts instead of the template’s sample cards;</li>
<li>wire up the forms and test that bookings actually arrive;</li>
<li>check mobile, run the theme check and keep it updated as WordPress changes.</li>
</ul>
<p>Done properly, that’s days of developer work for a template this size, not hours. It’s worth doing if you’re learning, if the template is small (a one-page site with no forms), or if you’re a developer building a theme you’ll reuse. It’s rarely worth doing to save money on one business site.</p>
<h2>The middle way: rebuild it in a page builder</h2>
<p>A popular alternative is to install a page builder such as Elementor on a lightweight theme and rebuild the design section by section, copying the template’s colours, fonts and photos. You skip the PHP entirely, and the result is editable by dragging and typing. The trade-offs: it’s a rebuild by eye rather than a conversion, so expect small differences from the original; complex effects in the template’s JavaScript won’t come along; and a bigger site with headers, footers and blog templates may need the builder’s paid version. If you go this way, our guide to <a href="https://www.themevault.net/how-to-install-elementor-template-kit?utm_source=hashnode&amp;utm_medium=referral&amp;utm_campaign=html-to-wordpress">installing an Elementor template kit</a> explains the free-versus-Pro details we found when testing.</p>
<h2>Or start from the WordPress version</h2>
<p>The third route is not to convert at all, and to start from a theme that was built for WordPress in the first place. For Bistrofeast that’s exactly why we made <a href="https://www.themevault.net/bistrofeast-restaurant-and-cafe-wordpress-theme?utm_source=hashnode&amp;utm_medium=referral&amp;utm_campaign=html-to-wordpress">a WordPress edition of the same design</a>. Everything step 3 says is missing is already done:</p>
<ul>
<li>Every page (Home, About, Book a table, Contact, Thank you) is built from Bistrofeast blocks, one block per section, and you edit the text, photos and buttons in the editor’s side panel.</li>
<li>Menu items, chefs, gallery photos, reviews and bookings are records in wp-admin, so adding a dish adds it to the menu page.</li>
<li>The booking form works and saves each request under Bookings in wp-admin.</li>
<li>A one-click demo import (Appearance → Import demo content) builds the pages, menu and sample content in about a minute.</li>
<li>No page builder needed: it runs on WordPress 6.5 or newer and PHP 8.0 or newer.</li>
</ul>
<img src="https://www.themevault.net/images/uploads/blog-html-to-wordpress/bistrofeast-wordpress-block-editor.jpg" alt="Editing the About page of the Bistrofeast WordPress theme: the intro and numbers section selected, with its eyebrow, title, lead text and button fields in the right-hand panel" style="display:block;margin:0 auto" />

<p><em>The WordPress edition: each section is a block, and its text sits in the side panel instead of a PHP file.</em></p>
<p>The HTML version stays free, and it’s still the right choice if you’re hand-coding, learning, or hosting a static site. The WordPress theme costs $19 (₹999 in India), less than most developers charge for a single hour, against the days step 3 would take. You can browse every design that has a WordPress version on our <a href="https://www.themevault.net/wordpress-themes?utm_source=hashnode&amp;utm_medium=referral&amp;utm_campaign=html-to-wordpress">WordPress themes</a> page. If you’re not sure WordPress is right for you at all, our comparison of <a href="https://www.themevault.net/nextjs-vs-wordpress?utm_source=hashnode&amp;utm_medium=referral&amp;utm_campaign=html-to-wordpress">Next.js vs WordPress for a small business</a> may help.</p>
<h2>A quick way to decide</h2>
<ul>
<li><strong>You want to learn WordPress theme development:</strong> convert it. Start with the home page, then one inner page, then the menu. You’ll learn the template hierarchy, enqueueing and menus properly.</li>
<li><strong>It’s a one-page site with no forms, and you’re comfortable with code:</strong> convert it. The second half of the work is small.</li>
<li><strong>A non-technical person will edit the site:</strong> don’t convert by hand. Use a WordPress version of the design, or rebuild it in a page builder.</li>
<li><strong>The site takes bookings, orders or enquiries:</strong> whichever route you pick, test every form with a real submission before launch.</li>
<li><strong>You’re paying someone:</strong> ask them to quote for both halves of the work, not just “getting it into WordPress”.</li>
</ul>
<h2>FAQ</h2>
<h3>Can I convert an HTML template to WordPress for free?</h3>
<p>Yes. WordPress is free and a theme is just files, so the only cost is your time. Making the design appear is a few hours of work for most templates; making every page and its content editable takes much longer.</p>
<h3>Do I need to know PHP to convert HTML to WordPress?</h3>
<p>A little. You need to be comfortable splitting files into header.php and footer.php, adding a few WordPress functions (wp_head, wp_footer, get_theme_file_uri, wp_nav_menu) and editing functions.php. Making content editable needs more WordPress knowledge, such as blocks, custom post types or a field plugin.</p>
<h3>Why are my CSS and images not loading after converting?</h3>
<p>Because the paths are relative. In WordPress the page is served from your site’s root, so <code>css/style.css</code> points at the wrong place. Load CSS and JavaScript with wp_enqueue_style and wp_enqueue_script, and put get_theme_file_uri() in front of every image path, including ones in data attributes used by JavaScript.</p>
<h3>Will my HTML template’s forms work in WordPress?</h3>
<p>Usually not on their own. Most HTML templates only simulate sending, or post to a service you have to set up. Connect each form to a form plugin or your own handler, then send a real test message and check it arrives.</p>
<h3>Is there a plugin that converts HTML to WordPress automatically?</h3>
<p>Some tools and services import static pages, but the result is usually pages of fixed HTML or builder blocks rather than a clean theme with editable menus, posts and forms. Treat any automatic conversion as a starting point and test the editing, forms and mobile layout yourself.</p>
<h3>How long does it take to convert an HTML template to WordPress?</h3>
<p>In our test, about 30 minutes for the home page of an 11-page template, done by someone who knows it well. A first-timer should allow an afternoon to a day for the home page, and several days to make the whole site editable with working forms.</p>
<hr />
<p><em>Originally published on</em> <a href="https://www.themevault.net/html-to-wordpress?utm_source=hashnode&amp;utm_medium=referral&amp;utm_campaign=html-to-wordpress"><em>ThemeVault</em></a><em>.</em></p>
]]></content:encoded></item></channel></rss>