Topic 1

Register Folder

In VS Code, you work at the folder level, not the file level. A workspace is not just a .tex file — it also includes figures, code, and other supporting files that VS Code manages together as one folder.

Open folder

Click Open Folder in the left sidebar.

VS Code empty window with the Open Folder button visible

Choose the folder that contains the manuscript and its supporting files.

Windows folder picker with the Seed document project folder selected

Now, we call such opened folder the workspace. In the above figure, Seed document folder is the workspace. If VS Code shows a trust prompt, allow the workspace only when it is your own folder and you want the editor features fully enabled.

VS Code trust prompt asking whether to trust the authors of the opened folder

If you have successfully opened the folder, you can see the following screen.

VS Code open project workspace after the folder is loaded

Common mistakes

Do not start from the Downloads folder, a temporary ZIP preview, or a deeply nested child folder unless that folder is truly the project root.

If LaTeX Workshop cannot find the main file, the problem is often the folder you opened rather than the extension itself.

Run the first build

  1. Trigger the build from LaTeX Workshop rather than from a manual terminal command.
  2. Open the PDF preview and confirm the document compiles without errors.
  3. If the template builds cleanly, your distribution, editor, and extension are all working together.

Open another folder

If you want to open another registered folder, type Ctrl + R (macOS: Cmd + R) to select another folder.

VS Code folder picker opened with Ctrl+R

Before proceeding

Confirm that the Explorer shows the whole project, the main .tex file is inside that tree, and the first build completes without errors.