On this page

What Overleaf does

Overleaf combines a browser-based LaTeX editor, compilation and collaboration. Its distinct role is managing a manuscript as connected source files that produce a rendered document. A source ZIP, PDF, project history and Git repository retain different things. Optional Writefull and AI features sit within that environment but have separate allowances and processing conditions. This profile is based on official documentation; no account, project upload, Overleaf compilation or AI feature test was performed.

Choose the handoff you actually need

Building, reviewing and retaining a project are separate decisions.

Overleaf workflows by task
Your taskStart withCheck before continuing
Make the correct document compileThe main file and template requirementsIdentify the compiler, TeX Live and bibliography system; inspect the log. [2] [3] [4]
Request inspectable feedbackNamed collaborators and review permissionsCheck the owner’s feature access and preserve review context before Git or copying. [10] [9] [11]
Retain a submission packageSource, PDF and the recipient’s instructionsDownload each required object; a source ZIP is not the rendered PDF or all project history. [6] [7] [8]

Where it fits, and where it falls short

Useful strengths

  • Main-document, compiler and TeX Live settings make the project’s build choices explicit.
  • Bibliography data and citation commands can be retained with the manuscript source.
  • Project roles, comments, history and tracked changes support different collaboration decisions.

Limits to consider

  • A PDF can be produced while errors remain; inspect the compile log.
  • Source downloads, project copies and Git synchronization do not preserve every review or history record in the same way.
  • Compile budgets, collaborator limits and AI entitlements depend on plan and institutional access.

A suggested Overleaf workflow

View the workflow diagram
Overleaf: an illustrated workflow for checking sources and reviewing your work
An editorial illustration of the workflow.
  1. 1

    Identify the required template, main file, compiler and bibliography system.

  2. 2

    Compile and inspect the log, references, figures and rendered document.

  3. 3

    Review collaborators’ changes under the intended permissions.

  4. 4

    Retain source and PDF separately, with build settings and any submission-specific files.

Identify the entry point and the project’s build settings

A LaTeX project can contain a main .tex file, chapter files, bibliography data, images and template-specific classes or styles. The Main document setting identifies the default file supplied to the compiler. Overleaf recommends putting it in the project root and requires a documentclass declaration. A chapter included by the main file is not automatically the document you should compile independently.

There is an important interface detail: an opened alternative file containing documentclass can be compiled even without changing the stored main-file setting. Same-named files in the root and a subfolder can also cause the root file to be compiled. Check the actual target before diagnosing a missing chapter or apparently ignored edit.

Compiler and TeX Live choices are project-specific. The default is pdfLaTeX, with LaTeX, XeLaTeX and LuaLaTeX also available. Follow the template’s language, font and package requirements and record the chosen settings for a handoff. Choosing a different engine is a build decision, not a language edit.

Supporting documentation: [2] [3]

Read the log even when a PDF appears

Recompile turns the project’s source and associated files into a PDF. Auto compile can repeat this as you edit. The default error-handling mode attempts to produce a PDF even when errors occur, so the presence of a preview does not establish a clean build. Inspect the log and the affected source location.

Overleaf recommends Stop on first error when diagnosing errors or timeouts. Its Fast draft option skips image processing and displays empty boxes instead; that draft should not be mistaken for a final figure check. Temporary helper files may be retained between compilations, and a recompile from scratch can remove stale cached helpers.

For a final pass, our suggested checks are the correct title and included sections, resolved references, figure placement and the log’s unresolved issues. These are inspection prompts rather than a performed compilation test or a guarantee of publisher compliance.

Supporting documentation: [1]

Keep bibliography data, citation commands and backend compatible

The documented bibliography workflow needs a .bib data file, configuration for the selected bibliography system, citation commands using its keys and a command that prints the bibliography. A supplied template may already choose BibTeX, natbib or biblatex. Do not mix a tutorial’s commands into that template without checking compatibility.

For biblatex, Overleaf’s tutorial documents Biber as the default and recommended backend; a bibtex backend is an alternative with different capabilities. The bibliography backend, LaTeX compiler and citation style are related settings but different objects. Keeping the .bib file is necessary for many source handoffs, while the recipient may also request generated bibliography output.

You can create or upload .bib data without a premium reference-manager integration. Integrated imports and advanced reference search have their own access conditions. Formatting an entry does not establish that the publication exists or supports the sentence. Use the separate source-verification worksheet for that evidence decision.

Supporting documentation: [4] [5]

Choose the audience and the review role deliberately

Projects start private. Email invitations name collaborators who authenticate their accounts and accept access. Current link sharing instead selects Anyone with the link and a permission level; Viewer is the default. People joining through a link do not appear individually in Manage access, so that list is not a complete description of link-based access.

Changing back to Only invited people removes link-derived permissions while preserving email-invited access. Links do not expire by default. A publicly posted link permits project viewing and downloading, so sharing a preview is not automatically a way to conceal manuscript source.

Tracked changes is a premium feature made available within a project when the owning account has it. Editors can switch between editing and reviewing modes; review-only users cannot change their mode. Use review permissions for suggested edits and resolve changes against technical meaning and evidence. A tracked revision shows a change, not its correctness.

Supporting documentation: [10] [9]

Preserve the original review record before making a copy

Free history shows edits from the last 24 hours plus labeled versions. Full history depends on the project owner’s premium subscription. Labels identify milestones, and an older version can be downloaded through History instead of taking only the current source ZIP.

A project copy starts with a different owner, no transferred collaborators and link sharing disabled. History, tracked-change records, comments and chat are empty; tracked edits are applied in the copied content rather than remaining available for review. Copying is therefore not a complete preservation method for a supervision or coauthoring record.

Copies also use the latest TeX Live by default, which can affect an older template. Record and check the version before using a copied project as a submission source. Restoring a historical project state is a different action: the documentation says it restores comments and tracked changes to the selected point as well.

Supporting documentation: [7] [8] [9]

Retain source ZIP, rendered PDF and requested build output separately

The standard project ZIP contains source files only. The final typeset PDF is downloaded separately after compilation. Give the recipient the object they requested: a PDF for reading does not provide editable LaTeX source, while a source package without its build requirements may be difficult to reconstruct.

Some submission processes request the generated .bbl bibliography file. Overleaf documents downloading output.bbl through Logs and output files, then Other logs and output files. It also documents a submission-files ZIP route that includes .bbl. A normal source download should not be described as automatically including every auxiliary file.

Keep a small build note with the main document, compiler, TeX Live, bibliography system and necessary files. Verify the recipient’s instructions rather than assuming that a source ZIP is a full archive of comments, history or collaboration permissions.

Supporting documentation: [6] [3] [7]

A proposed practice: read the file graph before handing off the project

This original five-file practice is a constructed manuscript project, not a published study or a test of Overleaf. Before opening the explanation, inspect README.md and follow the file graph: main.tex includes sections/handoff.tex and names references.bib. The bibliography has two real Overleaf documentation records, not invented evidence of learning gains. MANIFEST.sha256 records the other four files; it does not hash itself.

Try first: name the entry point, included fragment and bibliography input, then explain which files are absent from a PDF-only handoff. The main file uses the plain bibliography style and the references.bib database through standard BibTeX; this example is not a biblatex/Biber template. Record the actual engine and environment rather than changing bibliography systems to match an unrelated tutorial.

Use a disposable copy to predict the failure caused by renaming sections/handoff.tex, then restore the fragment before rebuilding. Keep your original source tree intact. Distinguish input references.bib from generated bibliography output and list which online review or permission records this local bundle cannot demonstrate. The exercise concerns file dependencies and retention, not editing accuracy, statistical results or measured learning.

The supplied reference PDF was compiled locally with Tectonic 0.17.0, a XeTeX-based engine. Two fresh extractions of this ZIP produced the same extracted PDF text, and a separate missing-fragment check failed as expected. The reference has one page with resolved bibliography entries. These are checks of our source bundle, not an Overleaf session, a test of its installed TeX Live or proof that your own project will compile.

Compare your handoff decisions with the practice rationale

main.tex is the entry point. Its input command depends on sections/handoff.tex, and its bibliography command names references.bib with the plain bibliography style. README.md describes the workflow; MANIFEST.sha256 checks the other four retained files. Restore sections/handoff.tex if that included fragment is missing. Keep the source tree and build note, and retain PDF or requested generated bibliography output separately. The local bundle supplies no online comments, complete project history or collaborator permissions. Successful compilation does not verify a scholarly claim or establish Overleaf compatibility.

Supporting documentation: [2] [6] [8] [7]

Treat Git synchronization as a source workflow with review risks

Overleaf’s Git integration translates its internal history into Git rather than providing a complete Git implementation. Commits may be generated when fetching or pulling the current state, and source edits from multiple collaborators do not map one-to-one to separate Git author records. Native branching, tags and Git LFS are not supported in the documented integration.

GitHub synchronization is a premium manual push-and-pull workflow. It can create a new Overleaf project from an existing repository, or a new repository from a project; it cannot simply link an already-existing project to an already-existing repository. Direct synchronization uses github.com, with account and repository permissions applying separately.

The documentation warns that incoming Git changes can lose or displace comments and tracked changes. Renaming files through Git can also remove associated review metadata. Avoid mixing active review work with uncoordinated sync operations. Agree where changes are made and preserve the review decisions before pulling or moving files.

Supporting documentation: [11] [12]

Check compile budgets and the account that owns the project

The current limits table lists 10 seconds for Free compilation and 240 seconds for premium plans. Both share limits such as 2,000 files per project, 7 MB of editable material and a 50 MB individual upload. These are different limits: a long-running document can time out even when its files fit the upload allowance.

Institutional Commons access requires an eligible affiliation confirmed through the institution’s email or SSO route. An existing account can join; a separate account is not required. Losing an institutional subscription does not itself remove projects, but premium features change. Joining Commons also does not automatically cancel an individual paid subscription.

Check the owning account and the required features, not only a university email or a collaborator’s subscription. For a large thesis, additional compile time may help, while a malformed command or unsuitable image pipeline still needs diagnosis. No plan guarantees that every template compiles successfully.

Supporting documentation: [13] [14] [7]

Separate the AI allowance from compilation and language review

Current documentation gives Free and Commons a Basic daily AI allowance without the AI assistant. Student has Basic with assistant, Standard has Standard with assistant, and Pro and Commons AI have Max subject to fair use. Error Assist, assistant exchanges and language or generator actions share an allowance that resets every 24 hours. No universal numerical quota is established here.

Writefull language tools are integrated into host menus and shared settings; the old separate toolbar has been removed. The current troubleshooting text also says Summarize and Explain were removed despite a retained introductory list mentioning them. For detailed academic-language review decisions, use the separate Writefull profile rather than assuming every older tutorial still matches the interface.

Some AI features send selected text, context, code or project information to external services. The first acceptance of external-processing AI terms covers all AI features rather than prompting for every later action. Overleaf states that data is not used to train AI models; this provider statement is not a guarantee of no processing, no storage or immediate deletion. Institutions can disable AI, and Commons access should not be confused with Commons AI.

Supporting documentation: [16] [15] [14]

Pricing, free access and plan checks

Overleaf has a Free plan and individual, group and institutional subscriptions. Current plan-limit documentation lists a 10-second compile timeout for Free and 240 seconds for premium plans; complex projects can still need troubleshooting. Full history, tracked changes and integrations have premium conditions. AI uses a separate daily allowance: Free and Commons have Basic access without AI assistant, while other current tiers differ. Check the actual institution and owning account before buying; no paid price or numeric AI-use allowance is quoted here.

Confirm billing period, renewal terms, limits and regional availability on the provider’s current plan page before paying.

Questions about Overleaf

Is Overleaf the same product as Writefull?

No. Overleaf is a LaTeX project editor, compiler and collaboration environment. It integrates Writefull language functions and other AI tools. A build-setting, bibliography or source-package decision is different from reviewing a sentence edit.

Does a successful PDF preview mean the project has no errors?

No. Default compilation attempts to produce a PDF despite errors. Inspect the log and relevant source; the documentation recommends Stop on first error for diagnosis.

Does Download as source include the final PDF?

No. The documented source ZIP contains source files only; download the PDF separately. A required generated .bbl may also need the documented auxiliary-output or submission-files download route.

Does copying a project preserve tracked changes and history?

No. The copy starts without original history, comments or tracked-change records, and tracked edits are applied in the copy. Collaborators do not transfer and sharing links are disabled. Record important review decisions before copying.

Does GitHub synchronization run automatically?

No. It uses explicit push and pull actions. Incoming changes can affect comments and tracked changes, and Overleaf history is not a one-to-one record of GitHub commits.

Does Free or institutional Commons access include AI assistant?

The current AI table says Free and Commons have Basic AI allowance without assistant. Other plans differ, and institutions can disable AI. Compile time, premium project features and AI allowance are separate entitlements.

Was the project-handoff exercise compiled in Overleaf?

No Overleaf session was run. The original source bundle was compiled locally with Tectonic 0.17.0; two fresh ZIP extractions reproduced the reference PDF text, and a missing included file failed as expected. These local artifact checks are not an Overleaf compatibility, AI or learning-outcome test.

Sources and research notes

This guide synthesizes official product information with our editorial assessment of academic use. Suggested exercises are examples you can repeat; they are not results of tests we performed. We do not infer accuracy from a provider’s marketing claims.

  1. Recompiling — Overleaf official documentation
  2. Main document — Overleaf official documentation
  3. Compiler version — Overleaf official documentation
  4. Bibliography — Overleaf official documentation
  5. Biber — Overleaf official documentation
  6. Download — Overleaf official documentation
  7. History — Overleaf official documentation
  8. Copy — Overleaf official documentation
  9. Track changes — Overleaf official documentation
  10. Sharing — Overleaf official documentation
  11. Git — Overleaf official documentation
  12. Github — Overleaf official documentation
  13. Limits — Overleaf official documentation
  14. Commons — Overleaf official documentation
  15. Processors — Overleaf official documentation
  16. Ai — Overleaf official documentation

Found a changed feature or a factual error? Send the exact page and an official source to info@ai-essay.com. Read our editorial policy for how we handle corrections.