Study · guide

BibTeX citation generator

By Alberto Gulotta · Updated 7 September 2026 · 11 min read

A bibtex citation generator is a different kind of thing from the other tools on this guide, and the difference matters before you use one. BibTeX is not a way of printing a reference. It is a way of storing one, in named fields, so that a separate program can print it in whatever style is asked for later.

That distinction is why BibTeX is the one format where a generator can be almost completely trustworthy. The other styles on this guide are typography: a comma in the wrong place is an error, and the only way to know where the comma goes is to read the manual. BibTeX has no typography. An entry is a type, a key and a list of named fields, and the question is not how it looks but whether the right fields are present.

The four types here are the ones that cover almost everything a student cites, and the documentation defines each in a sentence. An @article is an article from a journal or magazine. A @book is a book with an explicit publisher. An @incollection is, in the documentation’s own words, a part of a book having its own title — a chapter in an edited volume. And @misc exists, again quoting, for when nothing else fits.

Each type has required fields and optional ones, and the difference is real rather than advisory. Omitting a required field produces a warning when the bibliography is built, and the documentation is blunt about what that usually means: if the required information is not meaningful, you are using the wrong entry type. A web page filed as an @article will keep asking for a journal name, and the right answer is not to invent one — it is to file it as @misc.

The generator above marks the required field for each type as you switch between them. @article needs author, title, journal and year. @book needs author, title, publisher and year. @incollection needs all of those plus the book title it sits inside. @misc requires nothing at all, which is exactly what makes it the right home for the sources that have no obvious shape.

Two mechanical details that the tool handles and people typing entries by hand often do not. Names go in Surname, First form and are joined by the word and, never by commas — commas inside a name field mean something specific to BibTeX, and a list joined with them will be read as one person with a very long name. And page ranges are written with a double hyphen, which is how the typesetting engine is told to print an en dash.

The citation key is the one field with no right answer. It is the label you type in your document to cite the entry, it has to be unique within your bibliography, and beyond that it is yours. The tool proposes the first author’s surname followed by the year, which is the convention most reference managers use and is short enough to type. If you already have a scheme, the field is editable and your scheme wins.

There is a third class of field, and it explains a category of bug that is genuinely hard to find. Alongside required and optional there are ignored fields: anything BibTeX does not recognise for that entry type is silently dropped when the bibliography is built. The documentation treats this as a feature, and it is one — it means you can keep an abstract, a note to yourself or a library shelfmark inside the entry without breaking anything. But it has a sharp edge, stated plainly in the same paragraph: misspelling a field name results in its being ignored. A mistyped jornal does not produce an error. It produces a reference with no journal in it, and nothing anywhere says why.

That is the single best argument for building an entry in a form with named boxes rather than typing the braces by hand. A form cannot misspell a field name, because the names are not something you type. It is a small guarantee and it removes an error that is almost invisible once it has happened, which is the kind of error worth engineering away rather than watching for.

What this page will not claim is that a correct entry produces a correct reference. BibTeX stores what you give it and a bibliography style prints it, and the style can only print what is there. An entry missing its issue number will produce a reference missing its issue number, silently, in whatever format your department requires. The fields are the thing to check, and checking them here is easier than checking them in the finished document.

The rest of this guide, for when the next reference is in a different style: IEEE, Turabian, APSA, AMA, ACS and ASA. Every one of them is a working generator, and every one was built from a document that could be read and names the page it came from. Three of the seven took two attempts to source, and the pages say which and why.

Not covered here. It will not tell you the entry is complete. BibTeX prints what it is given; a missing issue number becomes a reference with no issue number, quietly.

It will not guess an entry type for you. The documentation is explicit that a source which does not fit a type usually belongs in a different one, and @misc exists for that.

It will not send anything anywhere. The generator runs entirely in the page.

And it will not carry an affiliate link to a reference manager. What holds instead is simple: the required and optional fields for every type here were read out of the BibTeX documentation.