Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

LaTeX Studio

Write LaTeX in VS Code. See a beautiful PDF the moment you save.

LaTeX Studio turns VS Code into a complete LaTeX authoring environment — no TeX install, no command line, no extra setup. Open a .tex file, press Ctrl+K V, and start writing. The real, compiled PDF appears next to your editor and refreshes automatically every time you save.


Why LaTeX Studio

  • Zero setup. The first time you build, LaTeX Studio downloads a self-contained Tectonic engine for your OS. You never have to install TeX Live or MiKTeX, and you never have to manage packages — Tectonic fetches what your document needs on demand.
  • What you see is what you ship. The preview shows the actual compiled PDF rendered by PDF.js — not an HTML approximation. Floats, page breaks, microtypography, math, bibliography, and hyperlinks all look exactly like the final document.
  • Publication-quality output. Built on the XeTeX engine for full Unicode, system fonts, and OpenType math. Fonts are embedded as vector subsets and PDFs come out clean and print-ready.
  • Feels like Markdown preview. Same keybindings (Ctrl+K V), same side-by-side workflow, same auto-refresh-on-save. If you can use Markdown preview, you already know how to use this.
  • Stays out of your way. Errors and warnings land in the Problems panel with file + line numbers. The build log is one click away in the Output panel. Build artifacts live in a single .latex-build/ folder you can .gitignore.

Quick start

  1. Install LaTeX Studio from the VS Code Marketplace.
  2. Open any .tex file.
  3. Press Ctrl+K V (macOS: Cmd+K V) to open the preview to the side.
  4. Press Ctrl+Alt+B to build — or just save. That's it.

First-run heads-up: the first time you build, you'll see a one-time prompt to download the LaTeX engine (~30 MB). Click Download and grab a coffee — it's a one-shot setup. Builds after that are fast and offline. If you'd rather use a TeX distribution you already have installed, see Bring your own engine below.

What gets installed, and when

LaTeX Studio is deliberately small. The actual LaTeX toolchain is downloaded on demand so the extension stays lightweight.

WhenWhat happensSizeNotes
Install the extensionNothing extra is downloaded~35 KBPure JS, ships from the Marketplace
First build(one-time prompt)Downloads the Tectonic engine for your OS~30 MBStored inside the extension folder
First time a document uses a LaTeX packageTectonic fetches it from CTAN and caches it locallyvariesPer-user cache, reused across projects
Subsequent buildsFully offline0No network access

Behind a corporate proxy or air-gapped? Either configure a system proxy so the first-run downloads can reach github.com and ctan.org, or set latexStudio.engine to xelatex / lualatex / pdflatex to use an existing TeX install instead — nothing extra will be downloaded in that case.

What you get

A real, live PDF preview

A side-by-side webview shows the actual compiled PDF. Scroll, zoom, fit-to-width, search inside the PDF, and toggle a dark/inverted mode for night writing. The preview re-renders only the pages that changed, so your scroll position is preserved between builds.

Build on save (or on demand)

Auto-rebuild fires every time you save (toggle off if you prefer). All output — the PDF, log, and intermediates — goes into .latex-build/ next to your root .tex.

Real errors, in the right place

The build log is parsed into VS Code's Problems panel with file and line numbers, so failures click straight back to the offending line. The full log is always available via LaTeX: Show Build Log.

Multi-file projects

Working in a folder with a main.tex and a bunch of chapter files? Drop a magic comment at the top of any sub-file and LaTeX Studio will always compile the right root:

% !TEX root = ../main.tex

This is the same convention used by TeXShop and LaTeX Workshop, so existing projects just work.

Bibliographies that just work

Tectonic detects biber/bibtex automatically and runs the right number of passes — no latexmk config to babysit.

Authoring aids

Snippets for the things you type all day: doc-article, sec, ssec, fig, tab, eq, align, itemize, enumerate, env, texroot. Completion suggestions for \ref, \cite, and \includegraphics file paths.

SyncTeX (coming soon)

  • Forward searchCtrl+Alt+J jumps the preview to your cursor position.
  • Inverse searchCtrl+Click anywhere in the PDF jumps the editor to that source line.

Commands

Open the Command Palette (Ctrl+Shift+P) and type "LaTeX":

CommandKeybinding
LaTeX: Build PDFCtrl+Alt+B
LaTeX: Open Preview to the SideCtrl+K V
LaTeX: Jump to PDF (SyncTeX Forward Search)Ctrl+Alt+J
LaTeX: Clean Build Artifacts
LaTeX: Show Build Log
LaTeX: Download/Update Tectonic Engine
LaTeX Studio: Reset Everything (Before Uninstall)

Settings

All settings live under latexStudio.* in your VS Code settings.

SettingDefaultWhat it does
latexStudio.enginetectonicEngine to compile with: tectonic, xelatex, lualatex, or pdflatex.
latexStudio.tectonicPath(empty)Path to a Tectonic executable to use instead of the bundled one.
latexStudio.build.onSavetrueRebuild the PDF every time you save a .tex file.
latexStudio.build.outputDirectory.latex-buildWhere compiled PDFs and intermediates go (relative to the root .tex).
latexStudio.preview.invertColorsfalseDark mode for the PDF preview.
latexStudio.preview.renderScale1.5Preview render scale, 0.53.0. Higher is sharper but uses more memory.
latexStudio.preview.openOnBuildtrueOpen the preview to the side after your first successful build.

Bring your own engine

Prefer the TeX distribution you already have? Set latexStudio.engine to xelatex, lualatex, or pdflatex. LaTeX Studio will drive it via latexmk if available. You can also point latexStudio.tectonicPath at a Tectonic binary you maintain yourself.

Privacy & network use

  • On first build, LaTeX Studio downloads the official Tectonic binary from its GitHub releases page.
  • Tectonic itself downloads any LaTeX packages your document references from CTAN, into a local cache on your machine.
  • No telemetry. No accounts. Your documents never leave your computer.

Uninstalling

Run LaTeX Studio: Reset Everything (Before Uninstall) before removing the extension. That command cleans up the downloaded engine and cached state.

Project & design

This repository contains the extension source under app/. For the architecture and technical design, see Design.md.

License

See LICENSE (if present in this repository) or the marketplace listing for license terms.


Crafted by Bipul Raman. Made with ♥ for LaTeX.

About

LaTeX Studio turns VS Code into a complete LaTeX authoring environment. No TeX install. No command line. No setup. Open a .tex file and start writing — the real, compiled PDF appears next to your editor and refreshes the instant you save.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

LaTeX Studio

Write LaTeX in VS Code. See a beautiful PDF the moment you save.

LaTeX Studio turns VS Code into a complete LaTeX authoring environment — no TeX install, no command line, no extra setup. Open a .tex file, press Ctrl+K V, and start writing. The real, compiled PDF appears next to your editor and refreshes automatically every time you save.


Why LaTeX Studio

  • Zero setup. The first time you build, LaTeX Studio downloads a self-contained Tectonic engine for your OS. You never have to install TeX Live or MiKTeX, and you never have to manage packages — Tectonic fetches what your document needs on demand.
  • What you see is what you ship. The preview shows the actual compiled PDF rendered by PDF.js — not an HTML approximation. Floats, page breaks, microtypography, math, bibliography, and hyperlinks all look exactly like the final document.
  • Publication-quality output. Built on the XeTeX engine for full Unicode, system fonts, and OpenType math. Fonts are embedded as vector subsets and PDFs come out clean and print-ready.
  • Feels like Markdown preview. Same keybindings (Ctrl+K V), same side-by-side workflow, same auto-refresh-on-save. If you can use Markdown preview, you already know how to use this.
  • Stays out of your way. Errors and warnings land in the Problems panel with file + line numbers. The build log is one click away in the Output panel. Build artifacts live in a single .latex-build/ folder you can .gitignore.

Quick start

  1. Install LaTeX Studio from the VS Code Marketplace.
  2. Open any .tex file.
  3. Press Ctrl+K V (macOS: Cmd+K V) to open the preview to the side.
  4. Press Ctrl+Alt+B to build — or just save. That's it.

First-run heads-up: the first time you build, you'll see a one-time prompt to download the LaTeX engine (~30 MB). Click Download and grab a coffee — it's a one-shot setup. Builds after that are fast and offline. If you'd rather use a TeX distribution you already have installed, see Bring your own engine below.

What gets installed, and when

LaTeX Studio is deliberately small. The actual LaTeX toolchain is downloaded on demand so the extension stays lightweight.

WhenWhat happensSizeNotes
Install the extensionNothing extra is downloaded~35 KBPure JS, ships from the Marketplace
First build(one-time prompt)Downloads the Tectonic engine for your OS~30 MBStored inside the extension folder
First time a document uses a LaTeX packageTectonic fetches it from CTAN and caches it locallyvariesPer-user cache, reused across projects
Subsequent buildsFully offline0No network access

Behind a corporate proxy or air-gapped? Either configure a system proxy so the first-run downloads can reach github.com and ctan.org, or set latexStudio.engine to xelatex / lualatex / pdflatex to use an existing TeX install instead — nothing extra will be downloaded in that case.

What you get

A real, live PDF preview

A side-by-side webview shows the actual compiled PDF. Scroll, zoom, fit-to-width, search inside the PDF, and toggle a dark/inverted mode for night writing. The preview re-renders only the pages that changed, so your scroll position is preserved between builds.

Build on save (or on demand)

Auto-rebuild fires every time you save (toggle off if you prefer). All output — the PDF, log, and intermediates — goes into .latex-build/ next to your root .tex.

Real errors, in the right place

The build log is parsed into VS Code's Problems panel with file and line numbers, so failures click straight back to the offending line. The full log is always available via LaTeX: Show Build Log.

Multi-file projects

Working in a folder with a main.tex and a bunch of chapter files? Drop a magic comment at the top of any sub-file and LaTeX Studio will always compile the right root:

% !TEX root = ../main.tex

This is the same convention used by TeXShop and LaTeX Workshop, so existing projects just work.

Bibliographies that just work

Tectonic detects biber/bibtex automatically and runs the right number of passes — no latexmk config to babysit.

Authoring aids

Snippets for the things you type all day: doc-article, sec, ssec, fig, tab, eq, align, itemize, enumerate, env, texroot. Completion suggestions for \ref, \cite, and \includegraphics file paths.

SyncTeX (coming soon)

  • Forward searchCtrl+Alt+J jumps the preview to your cursor position.
  • Inverse searchCtrl+Click anywhere in the PDF jumps the editor to that source line.

Commands

Open the Command Palette (Ctrl+Shift+P) and type "LaTeX":

CommandKeybinding
LaTeX: Build PDFCtrl+Alt+B
LaTeX: Open Preview to the SideCtrl+K V
LaTeX: Jump to PDF (SyncTeX Forward Search)Ctrl+Alt+J
LaTeX: Clean Build Artifacts
LaTeX: Show Build Log
LaTeX: Download/Update Tectonic Engine
LaTeX Studio: Reset Everything (Before Uninstall)

Settings

All settings live under latexStudio.* in your VS Code settings.

SettingDefaultWhat it does
latexStudio.enginetectonicEngine to compile with: tectonic, xelatex, lualatex, or pdflatex.
latexStudio.tectonicPath(empty)Path to a Tectonic executable to use instead of the bundled one.
latexStudio.build.onSavetrueRebuild the PDF every time you save a .tex file.
latexStudio.build.outputDirectory.latex-buildWhere compiled PDFs and intermediates go (relative to the root .tex).
latexStudio.preview.invertColorsfalseDark mode for the PDF preview.
latexStudio.preview.renderScale1.5Preview render scale, 0.53.0. Higher is sharper but uses more memory.
latexStudio.preview.openOnBuildtrueOpen the preview to the side after your first successful build.

Bring your own engine

Prefer the TeX distribution you already have? Set latexStudio.engine to xelatex, lualatex, or pdflatex. LaTeX Studio will drive it via latexmk if available. You can also point latexStudio.tectonicPath at a Tectonic binary you maintain yourself.

Privacy & network use

  • On first build, LaTeX Studio downloads the official Tectonic binary from its GitHub releases page.
  • Tectonic itself downloads any LaTeX packages your document references from CTAN, into a local cache on your machine.
  • No telemetry. No accounts. Your documents never leave your computer.

Uninstalling

Run LaTeX Studio: Reset Everything (Before Uninstall) before removing the extension. That command cleans up the downloaded engine and cached state.

Project & design

This repository contains the extension source under app/. For the architecture and technical design, see Design.md.

License

See LICENSE (if present in this repository) or the marketplace listing for license terms.


Crafted by Bipul Raman. Made with ♥ for LaTeX.

About

LaTeX Studio turns VS Code into a complete LaTeX authoring environment. No TeX install. No command line. No setup. Open a .tex file and start writing — the real, compiled PDF appears next to your editor and refreshes the instant you save.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

LaTeX Studio

Write LaTeX in VS Code. See a beautiful PDF the moment you save.

LaTeX Studio turns VS Code into a complete LaTeX authoring environment — no TeX install, no command line, no extra setup. Open a .tex file, press Ctrl+K V, and start writing. The real, compiled PDF appears next to your editor and refreshes automatically every time you save.


Why LaTeX Studio

  • Zero setup. The first time you build, LaTeX Studio downloads a self-contained Tectonic engine for your OS. You never have to install TeX Live or MiKTeX, and you never have to manage packages — Tectonic fetches what your document needs on demand.
  • What you see is what you ship. The preview shows the actual compiled PDF rendered by PDF.js — not an HTML approximation. Floats, page breaks, microtypography, math, bibliography, and hyperlinks all look exactly like the final document.
  • Publication-quality output. Built on the XeTeX engine for full Unicode, system fonts, and OpenType math. Fonts are embedded as vector subsets and PDFs come out clean and print-ready.
  • Feels like Markdown preview. Same keybindings (Ctrl+K V), same side-by-side workflow, same auto-refresh-on-save. If you can use Markdown preview, you already know how to use this.
  • Stays out of your way. Errors and warnings land in the Problems panel with file + line numbers. The build log is one click away in the Output panel. Build artifacts live in a single .latex-build/ folder you can .gitignore.

Quick start

  1. Install LaTeX Studio from the VS Code Marketplace.
  2. Open any .tex file.
  3. Press Ctrl+K V (macOS: Cmd+K V) to open the preview to the side.
  4. Press Ctrl+Alt+B to build — or just save. That's it.

First-run heads-up: the first time you build, you'll see a one-time prompt to download the LaTeX engine (~30 MB). Click Download and grab a coffee — it's a one-shot setup. Builds after that are fast and offline. If you'd rather use a TeX distribution you already have installed, see Bring your own engine below.

What gets installed, and when

LaTeX Studio is deliberately small. The actual LaTeX toolchain is downloaded on demand so the extension stays lightweight.

WhenWhat happensSizeNotes
Install the extensionNothing extra is downloaded~35 KBPure JS, ships from the Marketplace
First build(one-time prompt)Downloads the Tectonic engine for your OS~30 MBStored inside the extension folder
First time a document uses a LaTeX packageTectonic fetches it from CTAN and caches it locallyvariesPer-user cache, reused across projects
Subsequent buildsFully offline0No network access

Behind a corporate proxy or air-gapped? Either configure a system proxy so the first-run downloads can reach github.com and ctan.org, or set latexStudio.engine to xelatex / lualatex / pdflatex to use an existing TeX install instead — nothing extra will be downloaded in that case.

What you get

A real, live PDF preview

A side-by-side webview shows the actual compiled PDF. Scroll, zoom, fit-to-width, search inside the PDF, and toggle a dark/inverted mode for night writing. The preview re-renders only the pages that changed, so your scroll position is preserved between builds.

Build on save (or on demand)

Auto-rebuild fires every time you save (toggle off if you prefer). All output — the PDF, log, and intermediates — goes into .latex-build/ next to your root .tex.

Real errors, in the right place

The build log is parsed into VS Code's Problems panel with file and line numbers, so failures click straight back to the offending line. The full log is always available via LaTeX: Show Build Log.

Multi-file projects

Working in a folder with a main.tex and a bunch of chapter files? Drop a magic comment at the top of any sub-file and LaTeX Studio will always compile the right root:

% !TEX root = ../main.tex

This is the same convention used by TeXShop and LaTeX Workshop, so existing projects just work.

Bibliographies that just work

Tectonic detects biber/bibtex automatically and runs the right number of passes — no latexmk config to babysit.

Authoring aids

Snippets for the things you type all day: doc-article, sec, ssec, fig, tab, eq, align, itemize, enumerate, env, texroot. Completion suggestions for \ref, \cite, and \includegraphics file paths.

SyncTeX (coming soon)

  • Forward searchCtrl+Alt+J jumps the preview to your cursor position.
  • Inverse searchCtrl+Click anywhere in the PDF jumps the editor to that source line.

Commands

Open the Command Palette (Ctrl+Shift+P) and type "LaTeX":

CommandKeybinding
LaTeX: Build PDFCtrl+Alt+B
LaTeX: Open Preview to the SideCtrl+K V
LaTeX: Jump to PDF (SyncTeX Forward Search)Ctrl+Alt+J
LaTeX: Clean Build Artifacts
LaTeX: Show Build Log
LaTeX: Download/Update Tectonic Engine
LaTeX Studio: Reset Everything (Before Uninstall)

Settings

All settings live under latexStudio.* in your VS Code settings.

SettingDefaultWhat it does
latexStudio.enginetectonicEngine to compile with: tectonic, xelatex, lualatex, or pdflatex.
latexStudio.tectonicPath(empty)Path to a Tectonic executable to use instead of the bundled one.
latexStudio.build.onSavetrueRebuild the PDF every time you save a .tex file.
latexStudio.build.outputDirectory.latex-buildWhere compiled PDFs and intermediates go (relative to the root .tex).
latexStudio.preview.invertColorsfalseDark mode for the PDF preview.
latexStudio.preview.renderScale1.5Preview render scale, 0.53.0. Higher is sharper but uses more memory.
latexStudio.preview.openOnBuildtrueOpen the preview to the side after your first successful build.

Bring your own engine

Prefer the TeX distribution you already have? Set latexStudio.engine to xelatex, lualatex, or pdflatex. LaTeX Studio will drive it via latexmk if available. You can also point latexStudio.tectonicPath at a Tectonic binary you maintain yourself.

Privacy & network use

  • On first build, LaTeX Studio downloads the official Tectonic binary from its GitHub releases page.
  • Tectonic itself downloads any LaTeX packages your document references from CTAN, into a local cache on your machine.
  • No telemetry. No accounts. Your documents never leave your computer.

Uninstalling

Run LaTeX Studio: Reset Everything (Before Uninstall) before removing the extension. That command cleans up the downloaded engine and cached state.

Project & design

This repository contains the extension source under app/. For the architecture and technical design, see Design.md.

License

See LICENSE (if present in this repository) or the marketplace listing for license terms.


Crafted by Bipul Raman. Made with ♥ for LaTeX.

About

LaTeX Studio turns VS Code into a complete LaTeX authoring environment. No TeX install. No command line. No setup. Open a .tex file and start writing — the real, compiled PDF appears next to your editor and refreshes the instant you save.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

LaTeX Studio

Write LaTeX in VS Code. See a beautiful PDF the moment you save.

LaTeX Studio turns VS Code into a complete LaTeX authoring environment — no TeX install, no command line, no extra setup. Open a .tex file, press Ctrl+K V, and start writing. The real, compiled PDF appears next to your editor and refreshes automatically every time you save.


Why LaTeX Studio

  • Zero setup. The first time you build, LaTeX Studio downloads a self-contained Tectonic engine for your OS. You never have to install TeX Live or MiKTeX, and you never have to manage packages — Tectonic fetches what your document needs on demand.
  • What you see is what you ship. The preview shows the actual compiled PDF rendered by PDF.js — not an HTML approximation. Floats, page breaks, microtypography, math, bibliography, and hyperlinks all look exactly like the final document.
  • Publication-quality output. Built on the XeTeX engine for full Unicode, system fonts, and OpenType math. Fonts are embedded as vector subsets and PDFs come out clean and print-ready.
  • Feels like Markdown preview. Same keybindings (Ctrl+K V), same side-by-side workflow, same auto-refresh-on-save. If you can use Markdown preview, you already know how to use this.
  • Stays out of your way. Errors and warnings land in the Problems panel with file + line numbers. The build log is one click away in the Output panel. Build artifacts live in a single .latex-build/ folder you can .gitignore.

Quick start

  1. Install LaTeX Studio from the VS Code Marketplace.
  2. Open any .tex file.
  3. Press Ctrl+K V (macOS: Cmd+K V) to open the preview to the side.
  4. Press Ctrl+Alt+B to build — or just save. That's it.

First-run heads-up: the first time you build, you'll see a one-time prompt to download the LaTeX engine (~30 MB). Click Download and grab a coffee — it's a one-shot setup. Builds after that are fast and offline. If you'd rather use a TeX distribution you already have installed, see Bring your own engine below.

What gets installed, and when

LaTeX Studio is deliberately small. The actual LaTeX toolchain is downloaded on demand so the extension stays lightweight.

WhenWhat happensSizeNotes
Install the extensionNothing extra is downloaded~35 KBPure JS, ships from the Marketplace
First build(one-time prompt)Downloads the Tectonic engine for your OS~30 MBStored inside the extension folder
First time a document uses a LaTeX packageTectonic fetches it from CTAN and caches it locallyvariesPer-user cache, reused across projects
Subsequent buildsFully offline0No network access

Behind a corporate proxy or air-gapped? Either configure a system proxy so the first-run downloads can reach github.com and ctan.org, or set latexStudio.engine to xelatex / lualatex / pdflatex to use an existing TeX install instead — nothing extra will be downloaded in that case.

What you get

A real, live PDF preview

A side-by-side webview shows the actual compiled PDF. Scroll, zoom, fit-to-width, search inside the PDF, and toggle a dark/inverted mode for night writing. The preview re-renders only the pages that changed, so your scroll position is preserved between builds.

Build on save (or on demand)

Auto-rebuild fires every time you save (toggle off if you prefer). All output — the PDF, log, and intermediates — goes into .latex-build/ next to your root .tex.

Real errors, in the right place

The build log is parsed into VS Code's Problems panel with file and line numbers, so failures click straight back to the offending line. The full log is always available via LaTeX: Show Build Log.

Multi-file projects

Working in a folder with a main.tex and a bunch of chapter files? Drop a magic comment at the top of any sub-file and LaTeX Studio will always compile the right root:

% !TEX root = ../main.tex

This is the same convention used by TeXShop and LaTeX Workshop, so existing projects just work.

Bibliographies that just work

Tectonic detects biber/bibtex automatically and runs the right number of passes — no latexmk config to babysit.

Authoring aids

Snippets for the things you type all day: doc-article, sec, ssec, fig, tab, eq, align, itemize, enumerate, env, texroot. Completion suggestions for \ref, \cite, and \includegraphics file paths.

SyncTeX (coming soon)

  • Forward searchCtrl+Alt+J jumps the preview to your cursor position.
  • Inverse searchCtrl+Click anywhere in the PDF jumps the editor to that source line.

Commands

Open the Command Palette (Ctrl+Shift+P) and type "LaTeX":

CommandKeybinding
LaTeX: Build PDFCtrl+Alt+B
LaTeX: Open Preview to the SideCtrl+K V
LaTeX: Jump to PDF (SyncTeX Forward Search)Ctrl+Alt+J
LaTeX: Clean Build Artifacts
LaTeX: Show Build Log
LaTeX: Download/Update Tectonic Engine
LaTeX Studio: Reset Everything (Before Uninstall)

Settings

All settings live under latexStudio.* in your VS Code settings.

SettingDefaultWhat it does
latexStudio.enginetectonicEngine to compile with: tectonic, xelatex, lualatex, or pdflatex.
latexStudio.tectonicPath(empty)Path to a Tectonic executable to use instead of the bundled one.
latexStudio.build.onSavetrueRebuild the PDF every time you save a .tex file.
latexStudio.build.outputDirectory.latex-buildWhere compiled PDFs and intermediates go (relative to the root .tex).
latexStudio.preview.invertColorsfalseDark mode for the PDF preview.
latexStudio.preview.renderScale1.5Preview render scale, 0.53.0. Higher is sharper but uses more memory.
latexStudio.preview.openOnBuildtrueOpen the preview to the side after your first successful build.

Bring your own engine

Prefer the TeX distribution you already have? Set latexStudio.engine to xelatex, lualatex, or pdflatex. LaTeX Studio will drive it via latexmk if available. You can also point latexStudio.tectonicPath at a Tectonic binary you maintain yourself.

Privacy & network use

  • On first build, LaTeX Studio downloads the official Tectonic binary from its GitHub releases page.
  • Tectonic itself downloads any LaTeX packages your document references from CTAN, into a local cache on your machine.
  • No telemetry. No accounts. Your documents never leave your computer.

Uninstalling

Run LaTeX Studio: Reset Everything (Before Uninstall) before removing the extension. That command cleans up the downloaded engine and cached state.

Project & design

This repository contains the extension source under app/. For the architecture and technical design, see Design.md.

License

See LICENSE (if present in this repository) or the marketplace listing for license terms.


Crafted by Bipul Raman. Made with ♥ for LaTeX.

About

LaTeX Studio turns VS Code into a complete LaTeX authoring environment. No TeX install. No command line. No setup. Open a .tex file and start writing — the real, compiled PDF appears next to your editor and refreshes the instant you save.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

LaTeX Studio

Write LaTeX in VS Code. See a beautiful PDF the moment you save.

LaTeX Studio turns VS Code into a complete LaTeX authoring environment — no TeX install, no command line, no extra setup. Open a .tex file, press Ctrl+K V, and start writing. The real, compiled PDF appears next to your editor and refreshes automatically every time you save.


Why LaTeX Studio

  • Zero setup. The first time you build, LaTeX Studio downloads a self-contained Tectonic engine for your OS. You never have to install TeX Live or MiKTeX, and you never have to manage packages — Tectonic fetches what your document needs on demand.
  • What you see is what you ship. The preview shows the actual compiled PDF rendered by PDF.js — not an HTML approximation. Floats, page breaks, microtypography, math, bibliography, and hyperlinks all look exactly like the final document.
  • Publication-quality output. Built on the XeTeX engine for full Unicode, system fonts, and OpenType math. Fonts are embedded as vector subsets and PDFs come out clean and print-ready.
  • Feels like Markdown preview. Same keybindings (Ctrl+K V), same side-by-side workflow, same auto-refresh-on-save. If you can use Markdown preview, you already know how to use this.
  • Stays out of your way. Errors and warnings land in the Problems panel with file + line numbers. The build log is one click away in the Output panel. Build artifacts live in a single .latex-build/ folder you can .gitignore.

Quick start

  1. Install LaTeX Studio from the VS Code Marketplace.
  2. Open any .tex file.
  3. Press Ctrl+K V (macOS: Cmd+K V) to open the preview to the side.
  4. Press Ctrl+Alt+B to build — or just save. That's it.

First-run heads-up: the first time you build, you'll see a one-time prompt to download the LaTeX engine (~30 MB). Click Download and grab a coffee — it's a one-shot setup. Builds after that are fast and offline. If you'd rather use a TeX distribution you already have installed, see Bring your own engine below.

What gets installed, and when

LaTeX Studio is deliberately small. The actual LaTeX toolchain is downloaded on demand so the extension stays lightweight.

WhenWhat happensSizeNotes
Install the extensionNothing extra is downloaded~35 KBPure JS, ships from the Marketplace
First build(one-time prompt)Downloads the Tectonic engine for your OS~30 MBStored inside the extension folder
First time a document uses a LaTeX packageTectonic fetches it from CTAN and caches it locallyvariesPer-user cache, reused across projects
Subsequent buildsFully offline0No network access

Behind a corporate proxy or air-gapped? Either configure a system proxy so the first-run downloads can reach github.com and ctan.org, or set latexStudio.engine to xelatex / lualatex / pdflatex to use an existing TeX install instead — nothing extra will be downloaded in that case.

What you get

A real, live PDF preview

A side-by-side webview shows the actual compiled PDF. Scroll, zoom, fit-to-width, search inside the PDF, and toggle a dark/inverted mode for night writing. The preview re-renders only the pages that changed, so your scroll position is preserved between builds.

Build on save (or on demand)

Auto-rebuild fires every time you save (toggle off if you prefer). All output — the PDF, log, and intermediates — goes into .latex-build/ next to your root .tex.

Real errors, in the right place

The build log is parsed into VS Code's Problems panel with file and line numbers, so failures click straight back to the offending line. The full log is always available via LaTeX: Show Build Log.

Multi-file projects

Working in a folder with a main.tex and a bunch of chapter files? Drop a magic comment at the top of any sub-file and LaTeX Studio will always compile the right root:

% !TEX root = ../main.tex

This is the same convention used by TeXShop and LaTeX Workshop, so existing projects just work.

Bibliographies that just work

Tectonic detects biber/bibtex automatically and runs the right number of passes — no latexmk config to babysit.

Authoring aids

Snippets for the things you type all day: doc-article, sec, ssec, fig, tab, eq, align, itemize, enumerate, env, texroot. Completion suggestions for \ref, \cite, and \includegraphics file paths.

SyncTeX (coming soon)

  • Forward searchCtrl+Alt+J jumps the preview to your cursor position.
  • Inverse searchCtrl+Click anywhere in the PDF jumps the editor to that source line.

Commands

Open the Command Palette (Ctrl+Shift+P) and type "LaTeX":

CommandKeybinding
LaTeX: Build PDFCtrl+Alt+B
LaTeX: Open Preview to the SideCtrl+K V
LaTeX: Jump to PDF (SyncTeX Forward Search)Ctrl+Alt+J
LaTeX: Clean Build Artifacts
LaTeX: Show Build Log
LaTeX: Download/Update Tectonic Engine
LaTeX Studio: Reset Everything (Before Uninstall)

Settings

All settings live under latexStudio.* in your VS Code settings.

SettingDefaultWhat it does
latexStudio.enginetectonicEngine to compile with: tectonic, xelatex, lualatex, or pdflatex.
latexStudio.tectonicPath(empty)Path to a Tectonic executable to use instead of the bundled one.
latexStudio.build.onSavetrueRebuild the PDF every time you save a .tex file.
latexStudio.build.outputDirectory.latex-buildWhere compiled PDFs and intermediates go (relative to the root .tex).
latexStudio.preview.invertColorsfalseDark mode for the PDF preview.
latexStudio.preview.renderScale1.5Preview render scale, 0.53.0. Higher is sharper but uses more memory.
latexStudio.preview.openOnBuildtrueOpen the preview to the side after your first successful build.

Bring your own engine

Prefer the TeX distribution you already have? Set latexStudio.engine to xelatex, lualatex, or pdflatex. LaTeX Studio will drive it via latexmk if available. You can also point latexStudio.tectonicPath at a Tectonic binary you maintain yourself.

Privacy & network use

  • On first build, LaTeX Studio downloads the official Tectonic binary from its GitHub releases page.
  • Tectonic itself downloads any LaTeX packages your document references from CTAN, into a local cache on your machine.
  • No telemetry. No accounts. Your documents never leave your computer.

Uninstalling

Run LaTeX Studio: Reset Everything (Before Uninstall) before removing the extension. That command cleans up the downloaded engine and cached state.

Project & design

This repository contains the extension source under app/. For the architecture and technical design, see Design.md.

License

See LICENSE (if present in this repository) or the marketplace listing for license terms.


Crafted by Bipul Raman. Made with ♥ for LaTeX.

About

LaTeX Studio turns VS Code into a complete LaTeX authoring environment. No TeX install. No command line. No setup. Open a .tex file and start writing — the real, compiled PDF appears next to your editor and refreshes the instant you save.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

LaTeX Studio

Write LaTeX in VS Code. See a beautiful PDF the moment you save.

LaTeX Studio turns VS Code into a complete LaTeX authoring environment — no TeX install, no command line, no extra setup. Open a .tex file, press Ctrl+K V, and start writing. The real, compiled PDF appears next to your editor and refreshes automatically every time you save.


Why LaTeX Studio

  • Zero setup. The first time you build, LaTeX Studio downloads a self-contained Tectonic engine for your OS. You never have to install TeX Live or MiKTeX, and you never have to manage packages — Tectonic fetches what your document needs on demand.
  • What you see is what you ship. The preview shows the actual compiled PDF rendered by PDF.js — not an HTML approximation. Floats, page breaks, microtypography, math, bibliography, and hyperlinks all look exactly like the final document.
  • Publication-quality output. Built on the XeTeX engine for full Unicode, system fonts, and OpenType math. Fonts are embedded as vector subsets and PDFs come out clean and print-ready.
  • Feels like Markdown preview. Same keybindings (Ctrl+K V), same side-by-side workflow, same auto-refresh-on-save. If you can use Markdown preview, you already know how to use this.
  • Stays out of your way. Errors and warnings land in the Problems panel with file + line numbers. The build log is one click away in the Output panel. Build artifacts live in a single .latex-build/ folder you can .gitignore.

Quick start

  1. Install LaTeX Studio from the VS Code Marketplace.
  2. Open any .tex file.
  3. Press Ctrl+K V (macOS: Cmd+K V) to open the preview to the side.
  4. Press Ctrl+Alt+B to build — or just save. That's it.

First-run heads-up: the first time you build, you'll see a one-time prompt to download the LaTeX engine (~30 MB). Click Download and grab a coffee — it's a one-shot setup. Builds after that are fast and offline. If you'd rather use a TeX distribution you already have installed, see Bring your own engine below.

What gets installed, and when

LaTeX Studio is deliberately small. The actual LaTeX toolchain is downloaded on demand so the extension stays lightweight.

WhenWhat happensSizeNotes
Install the extensionNothing extra is downloaded~35 KBPure JS, ships from the Marketplace
First build(one-time prompt)Downloads the Tectonic engine for your OS~30 MBStored inside the extension folder
First time a document uses a LaTeX packageTectonic fetches it from CTAN and caches it locallyvariesPer-user cache, reused across projects
Subsequent buildsFully offline0No network access

Behind a corporate proxy or air-gapped? Either configure a system proxy so the first-run downloads can reach github.com and ctan.org, or set latexStudio.engine to xelatex / lualatex / pdflatex to use an existing TeX install instead — nothing extra will be downloaded in that case.

What you get

A real, live PDF preview

A side-by-side webview shows the actual compiled PDF. Scroll, zoom, fit-to-width, search inside the PDF, and toggle a dark/inverted mode for night writing. The preview re-renders only the pages that changed, so your scroll position is preserved between builds.

Build on save (or on demand)

Auto-rebuild fires every time you save (toggle off if you prefer). All output — the PDF, log, and intermediates — goes into .latex-build/ next to your root .tex.

Real errors, in the right place

The build log is parsed into VS Code's Problems panel with file and line numbers, so failures click straight back to the offending line. The full log is always available via LaTeX: Show Build Log.

Multi-file projects

Working in a folder with a main.tex and a bunch of chapter files? Drop a magic comment at the top of any sub-file and LaTeX Studio will always compile the right root:

% !TEX root = ../main.tex

This is the same convention used by TeXShop and LaTeX Workshop, so existing projects just work.

Bibliographies that just work

Tectonic detects biber/bibtex automatically and runs the right number of passes — no latexmk config to babysit.

Authoring aids

Snippets for the things you type all day: doc-article, sec, ssec, fig, tab, eq, align, itemize, enumerate, env, texroot. Completion suggestions for \ref, \cite, and \includegraphics file paths.

SyncTeX (coming soon)

  • Forward searchCtrl+Alt+J jumps the preview to your cursor position.
  • Inverse searchCtrl+Click anywhere in the PDF jumps the editor to that source line.

Commands

Open the Command Palette (Ctrl+Shift+P) and type "LaTeX":

CommandKeybinding
LaTeX: Build PDFCtrl+Alt+B
LaTeX: Open Preview to the SideCtrl+K V
LaTeX: Jump to PDF (SyncTeX Forward Search)Ctrl+Alt+J
LaTeX: Clean Build Artifacts
LaTeX: Show Build Log
LaTeX: Download/Update Tectonic Engine
LaTeX Studio: Reset Everything (Before Uninstall)

Settings

All settings live under latexStudio.* in your VS Code settings.

SettingDefaultWhat it does
latexStudio.enginetectonicEngine to compile with: tectonic, xelatex, lualatex, or pdflatex.
latexStudio.tectonicPath(empty)Path to a Tectonic executable to use instead of the bundled one.
latexStudio.build.onSavetrueRebuild the PDF every time you save a .tex file.
latexStudio.build.outputDirectory.latex-buildWhere compiled PDFs and intermediates go (relative to the root .tex).
latexStudio.preview.invertColorsfalseDark mode for the PDF preview.
latexStudio.preview.renderScale1.5Preview render scale, 0.53.0. Higher is sharper but uses more memory.
latexStudio.preview.openOnBuildtrueOpen the preview to the side after your first successful build.

Bring your own engine

Prefer the TeX distribution you already have? Set latexStudio.engine to xelatex, lualatex, or pdflatex. LaTeX Studio will drive it via latexmk if available. You can also point latexStudio.tectonicPath at a Tectonic binary you maintain yourself.

Privacy & network use

  • On first build, LaTeX Studio downloads the official Tectonic binary from its GitHub releases page.
  • Tectonic itself downloads any LaTeX packages your document references from CTAN, into a local cache on your machine.
  • No telemetry. No accounts. Your documents never leave your computer.

Uninstalling

Run LaTeX Studio: Reset Everything (Before Uninstall) before removing the extension. That command cleans up the downloaded engine and cached state.

Project & design

This repository contains the extension source under app/. For the architecture and technical design, see Design.md.

License

See LICENSE (if present in this repository) or the marketplace listing for license terms.


Crafted by Bipul Raman. Made with ♥ for LaTeX.

About

LaTeX Studio turns VS Code into a complete LaTeX authoring environment. No TeX install. No command line. No setup. Open a .tex file and start writing — the real, compiled PDF appears next to your editor and refreshes the instant you save.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

LaTeX Studio

Write LaTeX in VS Code. See a beautiful PDF the moment you save.

LaTeX Studio turns VS Code into a complete LaTeX authoring environment — no TeX install, no command line, no extra setup. Open a .tex file, press Ctrl+K V, and start writing. The real, compiled PDF appears next to your editor and refreshes automatically every time you save.


Why LaTeX Studio

  • Zero setup. The first time you build, LaTeX Studio downloads a self-contained Tectonic engine for your OS. You never have to install TeX Live or MiKTeX, and you never have to manage packages — Tectonic fetches what your document needs on demand.
  • What you see is what you ship. The preview shows the actual compiled PDF rendered by PDF.js — not an HTML approximation. Floats, page breaks, microtypography, math, bibliography, and hyperlinks all look exactly like the final document.
  • Publication-quality output. Built on the XeTeX engine for full Unicode, system fonts, and OpenType math. Fonts are embedded as vector subsets and PDFs come out clean and print-ready.
  • Feels like Markdown preview. Same keybindings (Ctrl+K V), same side-by-side workflow, same auto-refresh-on-save. If you can use Markdown preview, you already know how to use this.
  • Stays out of your way. Errors and warnings land in the Problems panel with file + line numbers. The build log is one click away in the Output panel. Build artifacts live in a single .latex-build/ folder you can .gitignore.

Quick start

  1. Install LaTeX Studio from the VS Code Marketplace.
  2. Open any .tex file.
  3. Press Ctrl+K V (macOS: Cmd+K V) to open the preview to the side.
  4. Press Ctrl+Alt+B to build — or just save. That's it.

First-run heads-up: the first time you build, you'll see a one-time prompt to download the LaTeX engine (~30 MB). Click Download and grab a coffee — it's a one-shot setup. Builds after that are fast and offline. If you'd rather use a TeX distribution you already have installed, see Bring your own engine below.

What gets installed, and when

LaTeX Studio is deliberately small. The actual LaTeX toolchain is downloaded on demand so the extension stays lightweight.

WhenWhat happensSizeNotes
Install the extensionNothing extra is downloaded~35 KBPure JS, ships from the Marketplace
First build(one-time prompt)Downloads the Tectonic engine for your OS~30 MBStored inside the extension folder
First time a document uses a LaTeX packageTectonic fetches it from CTAN and caches it locallyvariesPer-user cache, reused across projects
Subsequent buildsFully offline0No network access

Behind a corporate proxy or air-gapped? Either configure a system proxy so the first-run downloads can reach github.com and ctan.org, or set latexStudio.engine to xelatex / lualatex / pdflatex to use an existing TeX install instead — nothing extra will be downloaded in that case.

What you get

A real, live PDF preview

A side-by-side webview shows the actual compiled PDF. Scroll, zoom, fit-to-width, search inside the PDF, and toggle a dark/inverted mode for night writing. The preview re-renders only the pages that changed, so your scroll position is preserved between builds.

Build on save (or on demand)

Auto-rebuild fires every time you save (toggle off if you prefer). All output — the PDF, log, and intermediates — goes into .latex-build/ next to your root .tex.

Real errors, in the right place

The build log is parsed into VS Code's Problems panel with file and line numbers, so failures click straight back to the offending line. The full log is always available via LaTeX: Show Build Log.

Multi-file projects

Working in a folder with a main.tex and a bunch of chapter files? Drop a magic comment at the top of any sub-file and LaTeX Studio will always compile the right root:

% !TEX root = ../main.tex

This is the same convention used by TeXShop and LaTeX Workshop, so existing projects just work.

Bibliographies that just work

Tectonic detects biber/bibtex automatically and runs the right number of passes — no latexmk config to babysit.

Authoring aids

Snippets for the things you type all day: doc-article, sec, ssec, fig, tab, eq, align, itemize, enumerate, env, texroot. Completion suggestions for \ref, \cite, and \includegraphics file paths.

SyncTeX (coming soon)

  • Forward searchCtrl+Alt+J jumps the preview to your cursor position.
  • Inverse searchCtrl+Click anywhere in the PDF jumps the editor to that source line.

Commands

Open the Command Palette (Ctrl+Shift+P) and type "LaTeX":

CommandKeybinding
LaTeX: Build PDFCtrl+Alt+B
LaTeX: Open Preview to the SideCtrl+K V
LaTeX: Jump to PDF (SyncTeX Forward Search)Ctrl+Alt+J
LaTeX: Clean Build Artifacts
LaTeX: Show Build Log
LaTeX: Download/Update Tectonic Engine
LaTeX Studio: Reset Everything (Before Uninstall)

Settings

All settings live under latexStudio.* in your VS Code settings.

SettingDefaultWhat it does
latexStudio.enginetectonicEngine to compile with: tectonic, xelatex, lualatex, or pdflatex.
latexStudio.tectonicPath(empty)Path to a Tectonic executable to use instead of the bundled one.
latexStudio.build.onSavetrueRebuild the PDF every time you save a .tex file.
latexStudio.build.outputDirectory.latex-buildWhere compiled PDFs and intermediates go (relative to the root .tex).
latexStudio.preview.invertColorsfalseDark mode for the PDF preview.
latexStudio.preview.renderScale1.5Preview render scale, 0.53.0. Higher is sharper but uses more memory.
latexStudio.preview.openOnBuildtrueOpen the preview to the side after your first successful build.

Bring your own engine

Prefer the TeX distribution you already have? Set latexStudio.engine to xelatex, lualatex, or pdflatex. LaTeX Studio will drive it via latexmk if available. You can also point latexStudio.tectonicPath at a Tectonic binary you maintain yourself.

Privacy & network use

  • On first build, LaTeX Studio downloads the official Tectonic binary from its GitHub releases page.
  • Tectonic itself downloads any LaTeX packages your document references from CTAN, into a local cache on your machine.
  • No telemetry. No accounts. Your documents never leave your computer.

Uninstalling

Run LaTeX Studio: Reset Everything (Before Uninstall) before removing the extension. That command cleans up the downloaded engine and cached state.

Project & design

This repository contains the extension source under app/. For the architecture and technical design, see Design.md.

License

See LICENSE (if present in this repository) or the marketplace listing for license terms.


Crafted by Bipul Raman. Made with ♥ for LaTeX.

About

LaTeX Studio turns VS Code into a complete LaTeX authoring environment. No TeX install. No command line. No setup. Open a .tex file and start writing — the real, compiled PDF appears next to your editor and refreshes the instant you save.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

Latest commit

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

LaTeX Studio

Write LaTeX in VS Code. See a beautiful PDF the moment you save.

LaTeX Studio turns VS Code into a complete LaTeX authoring environment — no TeX install, no command line, no extra setup. Open a .tex file, press Ctrl+K V, and start writing. The real, compiled PDF appears next to your editor and refreshes automatically every time you save.


Why LaTeX Studio

  • Zero setup. The first time you build, LaTeX Studio downloads a self-contained Tectonic engine for your OS. You never have to install TeX Live or MiKTeX, and you never have to manage packages — Tectonic fetches what your document needs on demand.
  • What you see is what you ship. The preview shows the actual compiled PDF rendered by PDF.js — not an HTML approximation. Floats, page breaks, microtypography, math, bibliography, and hyperlinks all look exactly like the final document.
  • Publication-quality output. Built on the XeTeX engine for full Unicode, system fonts, and OpenType math. Fonts are embedded as vector subsets and PDFs come out clean and print-ready.
  • Feels like Markdown preview. Same keybindings (Ctrl+K V), same side-by-side workflow, same auto-refresh-on-save. If you can use Markdown preview, you already know how to use this.
  • Stays out of your way. Errors and warnings land in the Problems panel with file + line numbers. The build log is one click away in the Output panel. Build artifacts live in a single .latex-build/ folder you can .gitignore.

Quick start

  1. Install LaTeX Studio from the VS Code Marketplace.
  2. Open any .tex file.
  3. Press Ctrl+K V (macOS: Cmd+K V) to open the preview to the side.
  4. Press Ctrl+Alt+B to build — or just save. That's it.

First-run heads-up: the first time you build, you'll see a one-time prompt to download the LaTeX engine (~30 MB). Click Download and grab a coffee — it's a one-shot setup. Builds after that are fast and offline. If you'd rather use a TeX distribution you already have installed, see Bring your own engine below.

What gets installed, and when

LaTeX Studio is deliberately small. The actual LaTeX toolchain is downloaded on demand so the extension stays lightweight.

WhenWhat happensSizeNotes
Install the extensionNothing extra is downloaded~35 KBPure JS, ships from the Marketplace
First build(one-time prompt)Downloads the Tectonic engine for your OS~30 MBStored inside the extension folder
First time a document uses a LaTeX packageTectonic fetches it from CTAN and caches it locallyvariesPer-user cache, reused across projects
Subsequent buildsFully offline0No network access

Behind a corporate proxy or air-gapped? Either configure a system proxy so the first-run downloads can reach github.com and ctan.org, or set latexStudio.engine to xelatex / lualatex / pdflatex to use an existing TeX install instead — nothing extra will be downloaded in that case.

What you get

A real, live PDF preview

A side-by-side webview shows the actual compiled PDF. Scroll, zoom, fit-to-width, search inside the PDF, and toggle a dark/inverted mode for night writing. The preview re-renders only the pages that changed, so your scroll position is preserved between builds.

Build on save (or on demand)

Auto-rebuild fires every time you save (toggle off if you prefer). All output — the PDF, log, and intermediates — goes into .latex-build/ next to your root .tex.

Real errors, in the right place

The build log is parsed into VS Code's Problems panel with file and line numbers, so failures click straight back to the offending line. The full log is always available via LaTeX: Show Build Log.

Multi-file projects

Working in a folder with a main.tex and a bunch of chapter files? Drop a magic comment at the top of any sub-file and LaTeX Studio will always compile the right root:

% !TEX root = ../main.tex

This is the same convention used by TeXShop and LaTeX Workshop, so existing projects just work.

Bibliographies that just work

Tectonic detects biber/bibtex automatically and runs the right number of passes — no latexmk config to babysit.

Authoring aids

Snippets for the things you type all day: doc-article, sec, ssec, fig, tab, eq, align, itemize, enumerate, env, texroot. Completion suggestions for \ref, \cite, and \includegraphics file paths.

SyncTeX (coming soon)

  • Forward searchCtrl+Alt+J jumps the preview to your cursor position.
  • Inverse searchCtrl+Click anywhere in the PDF jumps the editor to that source line.

Commands

Open the Command Palette (Ctrl+Shift+P) and type "LaTeX":

CommandKeybinding
LaTeX: Build PDFCtrl+Alt+B
LaTeX: Open Preview to the SideCtrl+K V
LaTeX: Jump to PDF (SyncTeX Forward Search)Ctrl+Alt+J
LaTeX: Clean Build Artifacts
LaTeX: Show Build Log
LaTeX: Download/Update Tectonic Engine
LaTeX Studio: Reset Everything (Before Uninstall)

Settings

All settings live under latexStudio.* in your VS Code settings.

SettingDefaultWhat it does
latexStudio.enginetectonicEngine to compile with: tectonic, xelatex, lualatex, or pdflatex.
latexStudio.tectonicPath(empty)Path to a Tectonic executable to use instead of the bundled one.
latexStudio.build.onSavetrueRebuild the PDF every time you save a .tex file.
latexStudio.build.outputDirectory.latex-buildWhere compiled PDFs and intermediates go (relative to the root .tex).
latexStudio.preview.invertColorsfalseDark mode for the PDF preview.
latexStudio.preview.renderScale1.5Preview render scale, 0.53.0. Higher is sharper but uses more memory.
latexStudio.preview.openOnBuildtrueOpen the preview to the side after your first successful build.

Bring your own engine

Prefer the TeX distribution you already have? Set latexStudio.engine to xelatex, lualatex, or pdflatex. LaTeX Studio will drive it via latexmk if available. You can also point latexStudio.tectonicPath at a Tectonic binary you maintain yourself.

Privacy & network use

  • On first build, LaTeX Studio downloads the official Tectonic binary from its GitHub releases page.
  • Tectonic itself downloads any LaTeX packages your document references from CTAN, into a local cache on your machine.
  • No telemetry. No accounts. Your documents never leave your computer.

Uninstalling

Run LaTeX Studio: Reset Everything (Before Uninstall) before removing the extension. That command cleans up the downloaded engine and cached state.

Project & design

This repository contains the extension source under app/. For the architecture and technical design, see Design.md.

License

See LICENSE (if present in this repository) or the marketplace listing for license terms.


Crafted by Bipul Raman. Made with ♥ for LaTeX.

About

LaTeX Studio turns VS Code into a complete LaTeX authoring environment. No TeX install. No command line. No setup. Open a .tex file and start writing — the real, compiled PDF appears next to your editor and refreshes the instant you save.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages