Live Server and Browser

Relative Paths in Local Preview

Learn to trace links, scripts, styles and images from the current document and avoid local 404 errors in this beginner-friendly Visual Studio Code lesson.

Learning outcomes

  • Explain how to trace links, scripts, styles and images from the current document.
  • Complete the guided activity safely.
  • Check that you can avoid local 404 errors.

Before you begin

Use a non-sensitive practice folder, inspect unfamiliar code before trusting it, and never place passwords, tokens or private information in project files.

Open official guidance ↗

Step-by-step instructions

  1. Open the intended practice workspace in Visual Studio Code and confirm its folder name and Workspace Trust state.
  2. Repair a deliberate missing asset.
  3. Save the relevant files and review the Problems panel, terminal, Source Control view or browser preview as appropriate.
  4. Check filenames, relative paths, console messages, keyboard use, mobile layout and privacy before continuing.
  5. Confirm that you can avoid local 404 errors, then create a clear commit, backup or saved checkpoint.
Ian's practical tip: Work in one named project folder, preview after small changes, read the actual error message and keep a recoverable version before broad edits.

Practical activity

Repair a deliberate missing asset. The expected result is to avoid local 404 errors.

Completion checklist