A focused alternative for browser-based LaTeX projects
Turquoise Jackal is an independent online LaTeX workspace for people who want to write, compile, organise, and review LaTeX projects in a browser. It is not connected with, endorsed by, or an integration for Overleaf.
Move standard source, then verify the build
Overleaf can export a project's source as a ZIP. Turquoise Jackal can import a validated standard LaTeX ZIP, preserve supported nested files, let you select the correct root TeX document, and compile it with the hosted pdfLaTeX environment.
The workflow includes templates, file and folder organisation, revisions, PDF preview, project export, sharing roles, line comments, replies, and optional review-first Jackal assistance. It does not attempt to copy every feature or compilation setting of another service.
A clear path from source to result
- 01
Export your source ZIP
Download the complete source project from your current editor, including TeX, bibliography, images, and permitted style files.
- 02
Import and choose the root
Upload the ZIP to Turquoise Jackal and select the TeX file that builds the complete document.
- 03
Compile and compare
Check packages, references, figures, fonts, and the resulting PDF before continuing work.
Know what the tool does not promise
There is no official Overleaf integration or account transfer. Comments, history, collaborators, settings, generated files, and service-specific features do not move with a source ZIP. Compiler engines, package versions, fonts, and build options can differ, so compare the imported PDF carefully. Overleaf is a trademark of its respective owner.
Frequently asked questions
Is Turquoise Jackal connected to Overleaf?
No. Turquoise Jackal is an independent product and has no official Overleaf integration or endorsement.
Can I import an Overleaf project?
You can download standard source as a ZIP from Overleaf and import that ZIP. Service-specific history, comments, collaborators, and settings are not included.
Will the imported PDF look identical?
Not always. TeX engines, package versions, fonts, build settings, and generated files may differ. Compile and compare the result before relying on it.
Put the workflow into practice.
Start with the real tool, keep the limitations in view, and review the result.