TeXposit can link a project to a folder on your local machine. Changes sync both ways: when you save in the browser, the file is written to disk, and when you edit a file locally (with any editor), that change is pushed back to TeXposit.

Browser Support

Local sync uses the File System Access API. Supported browsers:

Chrome & Edge: Native FileSystemObserver for instant change detection
Safari: Polling every 3 seconds (checks file modification timestamps)
Firefox: Not supported. TeXposit disables the local-sync buttons and tells you to use Chrome, Edge, or Safari instead.

Two Ways to Start

There's no single "enable local sync" switch. You link a folder from one of two places, depending on whether the project exists yet:

Starting from a folder: On the projects dashboard, click Open Local Project. Pick a folder, and TeXposit reads its files, creates a brand-new project from them, uploads everything, and opens the editor.
Linking an existing project: Open the project in the editor and click the Link folder status chip at the bottom of the screen. Pick a folder, and TeXposit uploads the project's current files into it, then starts watching for changes on both sides.

Status Chip States

Green "Local": folder linked and syncing. Hovering shows which folder it's synced with.
Amber warning: the browser lost permission to access the folder (e.g. after a restart). Click it for a banner with a Reconnect button.
Muted "Link folder": no folder linked yet. Click to pick one.

Use your favourite editor

Once the folder is linked, open it in VS Code, Vim, or any other editor. Compilation still happens in TeXposit: save locally, switch to the browser, and compile as usual.

What Gets Synced

TeXposit filters files by type:

Synced: .tex, .md, .bib, and images (.png, .jpg, .jpeg, .gif, .bmp, .tiff, .webp, .eps, .ps, .svg)
Skipped: LaTeX build output (.aux, .log, .bbl, .blg, .out, .toc, .lof, .lot, .fls, .fdb_latexmk, .bcf, .run.xml), compiled/binary files (.pdf, .dvi, .woff, .woff2, .ttf, .otf, .zip), and the .git, node_modules, output, and __pycache__ directories

Conflict Handling

Local sync doesn't merge conflicting edits. If you change a file locally at the same time it's being edited in the browser, whichever side writes to the server last wins, and the other change is overwritten with no warning. If you're editing the same file in both places, save on one side before switching to the other.

Typical Workflows

Write locally, compile in browser

Draft in your preferred local editor, let TeXposit handle compilation and reference management.

Collaborate in browser, export to disk

Co-edit in real time with your team, then sync to disk for local backup or Git integration.

Stopping Sync

There's no separate button to unlink a folder while keeping the project. Local sync ends when you delete the project, or if the browser loses folder access and you don't reconnect. Either way, your local folder and its files are never modified or deleted by TeXposit.