Perl script to add indentation (leading horizontal space) to LaTeX files; as of V3.0, the script can also modify line breaks. The script is customisable through its YAML interface.
TeX Perl Shell Other
Clone or download


Build Status Build status Documentation Status is a perl script to indent (add horizontal leading space to) code within environments, commands, after headings and within special code blocks.

It has the ability to align delimiters in environments and commands, and can modify line breaks., version 3.4.3, 2018-06-08


Chris Hughes (cmhughes)

build status

I use both travis-ci (Linux) and AppVeyor (Windows) as continuous integration services to test for a small selection of test cases for every commit (I use git to track changes in the many test cases listed in the test-cases directory); you can see which versions of perl are tested by travis-ci within .travis.yml.

Build Status Build status


For complete details, please see:

Windows executable

latexindent.exe is available at and is created using

  perl -u -o latexindent.exe

using the Par::Packer perl module. is located in the helper-scripts directory.


You'll need

in the same directory. Windows users might prefer to grab latexindent.exe


A nice way to test the script is to navigate to the test-cases directory, and then run the command (on Linux/Mac -- sorry, a Windows test-case version is not available):



This script may not work for your style of formatting; I highly recommend comparing the outputfile.tex to make sure that nothing has been changed (or removed) in a way that will damage your file.

I recommend using each of the following:

  • a visual check, at the very least, make sure that each file has the same number of lines
  • a check using latexdiff inputfile.tex outputfile.tex
  • git status myfile.tex

feature requests

I'm happy to review feature requests, but I make no promises as to if they will be implemented; if they can be implemented, I make no promises as to how long it will take to implement them, and in which order I do so -- some features are more difficult than others! Feel free to post on the issues page of this repository.

development model

I follow the development model given here: which means that always has (at least) two branches:


The master branch always contains the released version and develop contains the development version. When developing a new feature or bug fix, I typically use:

    git checkout develop
    git checkout -b feature/name-of-feature

and then I merge it into the develop branch using

    git checkout develop
    git merge feature/name-of-feature --no-ff

perl version

I develop on Ubuntu Linux, using perlbrew; I currently develop on perl version v5.26.0

related projects

You might like to checkout the following related projects on github.

arara: GitHub stars

atom-beautify: GitHub stars