ZIP-based project migration
Live nowProjects can be moved into the editor through standard file upload flows and ZIP-based migration.
Canonical docsMigration
Move Existing LaTeX Projects Without Guesswork
Public migration support today is built around ZIP import/export and GitHub-backed workflows. This page keeps those live paths separate from roadmap-only ideas like direct account-to-account Overleaf import.
Live today
- ZIP upload from Overleaf or local projects
- ZIP export for backup and portability
- GitHub repository import
- GitHub push/pull sync
Roadmap
- Direct Overleaf account import
- Public Zotero or Mendeley integrations
Trust & Status
Migration claims grounded in the live product
Use this page and the linked product docs when comparing migration promises. Live ZIP or GitHub workflows are documented separately from roadmap-only items.
GitHub import, export, and sync
Live nowUsers can connect GitHub, import repositories, export projects, and run push/pull sync.
Canonical docsDirect Overleaf account import
RoadmapA direct account-to-account Overleaf import flow is not documented as publicly available yet.
Canonical docsPath 01
Move from Overleaf with ZIP Export
Export the project from Overleaf, upload the ZIP into LaTeX Cloud Studio, then recompile and verify your `main.tex`, images, and bibliography files.
Path 02
Import from GitHub
If the project already lives in a repository, import it directly through the GitHub workflow and keep using push or pull sync afterward.
Path 03
Export a Safe Backup First
Before major cleanup or sync work, export a ZIP backup so you always have a portable checkpoint outside the editor.