How to Run HTML Code

Use a browser to run HTML code and instantly preview how your page looks. The fastest workflow is to save your HTML file and open it directly in Chrome, Safari, Edge, or Firefox.

What you’ll build or solve

You’ll learn how to run HTML code by saving an .html file and opening it in a browser. You’ll also know the fastest ways to preview updates while you edit.

When this approach works best

This approach is the right choice when you want to test layouts, forms, buttons, media, or full web pages locally.

Common real-world scenarios include:

  • Testing landing pages
  • Previewing course lesson pages
  • Checking responsive layouts
  • Debugging forms and buttons
  • Reviewing marketing page changes

This is a bad idea when the page depends on backend routes, APIs, or a build tool that requires a local server.

Prerequisites

You only need:

  • A text editor
  • A browser like Chrome, Safari, Edge, or Firefox
  • A saved .html file

No server is required for basic HTML previews.

Step-by-step instructions

Step 1: Save the file as .html and open it in a browser

Create a file that ends in .html, then open it in your browser.

<!DOCTYPE html>
<html>
  <body>
    <h1>Hello USA</h1>
  </body>
</html>

Save it as:

index.html

Then open the file by double-clicking it or dragging it into your browser window.

What to look for:

  • The browser tab should display your HTML page
  • The file must end in .html
  • Save the file before refreshing
  • Use browser refresh after each edit
  • Keep the file path easy to find, such as a project folder on your desktop

Examples you can copy

Basic test page

<!DOCTYPE html>
<html>
  <body>
    <h1>France pricing page</h1>
  </body>
</html>

Form preview

<!DOCTYPE html>
<html>
  <body>
    <input type="email" placeholder="Enter your email">
  </body>
</html>

Responsive layout test

<!DOCTYPE html>
<html>
  <body>
    <div style="width:100%; max-width:600px;">
      UK landing page content
    </div>
  </body>
</html>

Common mistakes and how to fix them

Mistake 1: Saving as .txt instead of .html

What the reader might do:

index.txt

Why it breaks: the browser treats it as plain text instead of rendering the HTML structure.

Corrected approach:

index.html

Mistake 2: Editing the file without refreshing

What the reader might do:

<h1>Updated title</h1>

Why it breaks: the browser still shows the old version until the page reloads.

Corrected approach:

After saving the file, refresh the browser tab.

Mistake 3: Opening the wrong file

What the reader might do:

project-old/index.html

Why it breaks: the browser loads a different HTML file than the one being edited.

Corrected approach:

Open the exact file you are currently editing and keep the folder structure simple.

Troubleshooting

If the browser shows raw code, confirm the file ends in .html.

If your changes do not appear, save the file and refresh the tab.

If the wrong page opens, verify the file path and folder location.

If CSS or images are missing, confirm the relative file paths are correct.

Quick recap

  • Save the file with the .html extension
  • Open it directly in a browser
  • Refresh after every edit
  • Confirm you opened the correct file
  • Check file paths if linked assets do not load