Step 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.
Outcome
The complete manuscript project is open as one trusted VS Code workspace.
Before you start
- An extracted project folder containing the main
.texfile and supporting files. - A working LaTeX Workshop installation.
Verification state
- Status
- Needs review
- Environment
- Windows is the detailed screenshot path; macOS and Linux use the same Open Folder workflow.
- Workflow
- VS Code Open Folder, Workspace Trust, Explorer, and LaTeX Workshop build.
- Last verified
- Pending a current-product walkthrough.
- Operating-system support
- Windows detailed; macOS and Linux supported through equivalent VS Code controls.
Open folder
Click Open Folder in the left sidebar.
Choose the folder that contains the manuscript and its supporting files.
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.
If you have successfully opened the folder, you can see the following screen.
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
- Trigger the build from LaTeX Workshop rather than from a manual terminal command.
- Open the PDF preview and confirm the document compiles without errors.
- 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.
Confirm that the Explorer shows the whole project, the main .tex file is inside that tree, and the first build completes without errors.
Common problems
- Opening a single file or a nested child folder can hide the actual project root.
- Workspace Trust should only be accepted for a folder you recognize and control.
Completion check
Explorer shows the project tree, the main .tex file is inside it, and the PDF build succeeds.