Wiki • Server Pro • Contributing • Mailing List • Authors • License
Figure 1: A screenshot of a project being edited in Overleaf Community Edition.
Overleaf is an open-source online real-time collaborative LaTeX editor. We run a hosted version at www.overleaf.com, but you can also run your own local version, and contribute to the development of Overleaf.
Caution
Overleaf Community Edition is intended for use in environments where all users are trusted. Community Edition is not appropriate for scenarios where isolation of users is required due to Sandbox Compiles not being available. When not using Sandboxed Compiles, users have full read and write access to the sharelatex container resources (filesystem, network, environment variables) when running LaTeX compiles.
For more information on Sandbox Compiles check out our documentation.
If you want help installing and maintaining Overleaf in your lab or workplace, we offer an officially supported version called Overleaf Server Pro. It also includes more features for security (SSO with LDAP or SAML), administration and collaboration (e.g. tracked changes). Find out more!
Sign up to the mailing list to get updates on Overleaf releases and development.
We have detailed installation instructions in the Overleaf Toolkit.
If you are upgrading from a previous version of Overleaf, please see the Release Notes section on the Wiki for all of the versions between your current version and the version you are upgrading to.
Build and run this fork directly from its source checkout:
docker compose up --build -dOpen http://localhost:8080/launchpad to create the first administrator. Optional
configuration is documented in .env.example. See the
source deployment guide for persistent data, invitation
secrets, TeX package installation, upgrades, and reverse proxies.
server-ce/Dockerfile contains both the base dependency
target and the community application target. The application builds its base
layers from source in the same invocation, without requiring a published
Overleaf application or base image. Docker caches the dependency layers between
source changes. make -C server-ce build-community builds the complete image;
make -C server-ce build-base is available separately for publishing the
shared dependency target.
We use the Phusion base-image
(which is extended by our base image) to provide us with a VM-like container
in which to run the Overleaf services. Baseimage uses the runit service
manager to manage services, and we add our init-scripts from the server-ce/runit
folder.
Please see the CONTRIBUTING file for information on contributing to the development of Overleaf.
The code in this repository is released under the GNU AFFERO GENERAL PUBLIC LICENSE, version 3. A copy can be found in the LICENSE file.
Copyright (c) Overleaf, 2014-2025.