If you have ever fought a word processor over numbered headings, a table that jumps to the wrong page, or references that renumber themselves at the last minute, you will understand why many researchers write in LaTeX. LaTeX is a document preparation system in which you write plain text marked up with commands, and a compiler turns it into a beautifully typeset PDF. It is especially strong for papers with mathematics, tables, figures, and long reference lists.
This beginner guide takes you from installation to a finished draft. You will set up your first document, learn the commands you actually need, add figures and references, and fix the errors every beginner meets. No prior experience is assumed, and nothing here requires you to learn programming: LaTeX is a markup language, and a small set of commands covers most of what a research paper needs.
In a word processor, what you see is what you get: you format the document by hand, and the program tries to keep it looking right. In LaTeX, you describe the structure — this is a section heading, this is a figure, this is a citation — and the compiler handles the layout. That separation is the whole point: you focus on content and structure, while numbering, cross-references, and the table of contents update themselves whenever the document changes.
Researchers choose LaTeX for three practical reasons. First, mathematics is typeset cleanly, including complex equations that are painful to build by hand. Second, long documents stay consistent: sections, figures, tables, and references are numbered automatically, so inserting a new figure does not break every later number. Third, the source is plain text, which works well with version control and with collaboration, because changes can be tracked line by line. For a thesis, a methods-heavy paper, or any document with many equations, those advantages are hard to give up once you have felt them.
The easiest start is Overleaf, a free online editor that runs LaTeX in your browser. You need no installation, your work is saved online, and you can share a project with a supervisor or co-author who edits the same document. For a first paper, Overleaf removes the largest beginner obstacle, which is getting a working LaTeX installation on your own computer, and it lets you learn the language itself first.
A local installation suits you if you work offline, handle sensitive data, or want full control. On most systems this means installing a TeX distribution, such as TeX Live, together with an editor that understands LaTeX. The installation is large and takes time, so set it aside for a quiet afternoon rather than the day a draft is due. Whichever route you choose, the documents you write are the same, and you can move a project between Overleaf and a local setup by copying the source files.
Whichever route you choose, keep your TeX distribution updated, but not on the day a draft is due. Updates occasionally change how a package behaves, and a document that compiled yesterday should still compile today when a deadline is near. Update in a quiet week, recompile your current projects, and fix any differences while you have time.
Every LaTeX document has the same skeleton. It begins with a document class, which sets the overall layout, then a preamble where you load packages and set the title and author, then the document body between the begin and end document commands. A minimal article looks like this in words: document class article, a title and author, then the document body containing a section heading and a paragraph of text. Compiling that file produces a PDF with a title, a heading, and your paragraph, correctly formatted.
Build your paper by growing that skeleton, one piece at a time, and compile after each addition. Add the title and abstract first, then one section, then a second, compiling as you go. This habit matters because LaTeX errors are far easier to find when you know which addition caused them. If a compile fails, read the first error message, not the last: later errors are often consequences of the first, and fixing the first one frequently clears the rest.
Journal templates save time once you know the basics. Many journals publish a LaTeX template with their class file and author instructions; starting from the template means your headings, margins, and reference style already match the journal. Read the template's instructions before writing, because a template used blindly still produces a paper that ignores the journal's structure.
Structure in LaTeX is explicit. A section command creates a numbered heading, a subsection command creates a subheading, and the compiler numbers them and builds a table of contents from them automatically. Write your section headings as real headings, not as bold paragraphs, because only real headings appear in the contents list and can be cross-referenced from elsewhere in the text.
Figures and tables are placed inside floating environments, which is why a figure sometimes appears on a different page from where you typed it. That is normal: LaTeX moves floats to a sensible position rather than leaving large gaps. Give every figure and table a caption and a label, then refer to it by its label in the text, so that the reference updates automatically if the numbering changes. Keep figure files in the project folder, use clear file names, and check that every figure is legible at the size it will actually be printed.
Choose a clear naming convention for labels and stick to it. A scheme such as fig: for figures, tab: for tables, and sec: for sections makes cross-references easy to read in the source and easy to search when something breaks. Labels are never printed in the PDF, so a long, descriptive label costs nothing and saves confusion later.
References in LaTeX are normally managed with a separate bibliography file, in BibTeX format, in which each source is one entry with fields for author, title, year, and journal or publisher. In your text you cite a source by its entry key, and the compiler builds the reference list and formats it according to the bibliography style you choose. Changing the journal's style later is then a matter of changing one style name, not reformatting dozens of references by hand.
Reference managers can produce BibTeX entries for you, which saves typing and reduces errors. Our guide on reference management software explains how to organise your sources, and most managers can export a BibTeX file that LaTeX reads directly. Check exported entries against the original sources, because errors in author names, years, or page numbers propagate into your paper just as easily from a manager as from typing. For citation style rules themselves, see our guide on how to format references and citations.
Bibliography styles control how references appear, and journals often specify one. Common styles differ in whether author names are abbreviated, whether titles are emphasised, and how journal names are shortened. Changing the style name in your document changes the whole list at once, which is why keeping references in a BibTeX file, rather than typing the list by hand, is worth the initial effort.
LaTeX is not better for every paper, and choosing honestly saves frustration. A word processor is faster to learn, easier for short documents, and better when collaborators refuse anything else. LaTeX is stronger for long, structured, equation-heavy documents, and for papers where references, figures, and cross-references change repeatedly during revision. The table below compares the two on the points that matter most to a first-time author.
| Feature | Word processor | LaTeX |
|---|---|---|
| Learning curve | Low, familiar from the start | Higher at first, then fast |
| Equations | Built by hand, often fiddly | Typeset cleanly from commands |
| Numbering and references | Manual, breaks on edits | Automatic, updates on compile |
| Collaboration | Easy, track changes built in | Needs shared project or version control |
| Best for | Short papers, non-technical text | Theses, maths-heavy and long papers |
Almost every beginner meets the same small set of errors. A missing closing brace or a mistyped command name stops compilation, and the error message points to the line where the compiler noticed the problem, which may be a line or two after the actual mistake. Read the first error, check the lines just above it for an unclosed brace or environment, fix it, and compile again. Resist the urge to change many things at once while an error is unresolved.
Three other habits cause most remaining trouble. First, forgetting to compile twice after adding references or cross-references: LaTeX needs an extra pass to resolve them, so a question mark in place of a number usually means compile again. Second, fighting float placement by forcing figures into exact positions, which creates ugly gaps; accept the compiler's placement unless a journal's guidelines require otherwise. Third, pasting formatted text from a word processor into a LaTeX file, which imports hidden formatting; paste as plain text and reapply markup deliberately. With those habits fixed, most beginners find that LaTeX stops feeling like an obstacle and starts feeling like a tool.
When a package causes trouble, read its documentation before removing it. Most LaTeX packages are documented on the CTAN archive with examples, and the error usually comes from a missing option or a conflict with another package rather than from the package itself. Searching the exact error message online almost always finds someone who has met the same problem.
Collaboration in LaTeX works best when the whole team agrees on a workflow before writing begins. Decide whether you will share the project through an online editor or through version control, who owns each section, and how comments will be handled. A shared project in which everyone edits the same file at once without coordination produces conflicts just as surely as any other shared document.
Use comments in the source to discuss, not to argue in the margin. A short comment beside a paragraph, naming the question and the person it is for, keeps discussion attached to the text it concerns. Resolve comments as you go rather than letting dozens accumulate, because a manuscript with fifty open comments is a manuscript nobody wants to read.
Agree on packages and conventions early. If one author loads a package that changes the layout and another does not have it installed, compilation fails on one machine but not the other. Keep a single preamble, shared by the whole project, and add packages deliberately, with a note saying what each one is for. The same discipline applies to file names, figure formats, and bibliography keys.
For the final submission, compile the whole document from a clean copy and check the PDF page by page. Co-authored documents hide inconsistencies: different citation styles in different sections, figures numbered in the wrong order, and terminology that changes halfway through. A single read-through by one author, checking only consistency, catches most of them before an editor does.
Ready to publish your study? Submit your manuscript to Global Academic Publishers and follow the journal's author guidelines for the Global Journal of Veterinary and Animal Sciences.
No. LaTeX is a markup language, not a programming language. A small set of commands covers most of what a research paper needs, and you learn them by using them.
Overleaf offers a free plan that is enough for most individual papers, including collaboration on a small number of projects. Paid plans add features, but you do not need them to write a first paper.
Figures in LaTeX float to a sensible position so the document has no large gaps. This is normal behaviour. Refer to figures by label, not by page, so the text stays correct wherever they land.
LaTeX usually needs more than one compilation pass to resolve cross-references and citations. Compile again, and run BibTeX if you added references, before worrying that something is broken.
Many journals accept LaTeX submissions directly. If a journal requires Word, conversion tools exist, but equations, tables, and references often need checking afterwards, so allow time for that step.
It depends on the paper. For a short paper with little mathematics, a word processor is faster. For a thesis or a maths-heavy paper, learning LaTeX early pays off across the whole document.