A premium membership costs $4.99 per month (student discounts are available!) and enables
- unlimited length document editing,
- one-click publishing,
- integrations with Dropbox and Google Drive,
- offline mode,
- and support over email.
A number of useful, common LaTeX packages can be included with the \usepackage macro.
- ae
- amsfonts
- amsmath
- babelib
- colortbl
- fancyhdr
- fix2col
- geometry
- graphics
- graphicx
- hyperref
- mflogo
- natbib
- pdtex-def
- pslatex
- pspicture
- url
We plan on eventually supporting all custom packages hosted at CTAN, but please let us know if that's a critical need for you.
Images can be included in LaTeX Base documents by using the
\includegraphics macro from the graphicx
package. However, instead of providing a file path, you must use a direct
image url. imgur, Google Drive, and Dropbox are all good candidates for
uploading an image to be included in a LaTeX Base doc. Once uploaded to a
third-party file hosting service, make sure the image is publicly viewable
and that you've copied a direct link (ie using "Copy Image Location" in
Chrome) to paste as an argument to \includegraphics within
LaTeX Base.
Unlike other online LaTeX editors, we perform typesetting right in the browser! That means that if you're not connected to the Internet, you can still make changes to, preview, and download your files when using Chrome 46+ or Opera 33+. Just navigate to https://latexbase.com when offline to load the app. The "https" bit is important. Also make sure not to hard refresh! Offline mode is powered by service workers which are discussed in this article.
- Offline mode is currently only available for Chrome 46+, Opera 33+, and Firefox 59+.
- The compiler will fail if you try to use a new package while offline. That means you can only use packages offline that you've previously used while online.
We're working to make document previews instantaneous, but today you should expect a few second delay before your changes are reflected in the live preview. The preview updates most quickly in Firefox, likely because of asm.js optimizations.
Feel free to get in touch!