> For the complete documentation index, see [llms.txt](https://overleaf-pro.ayaka.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://overleaf-pro.ayaka.space/latex/more-topics/40-multibib.md).

# Multibib

Multibib is a LaTeX package that can be used to create multiple bibliographies in a paper. It is useful for creating several bibliographies, for example one containing Journal articles, one containing textbook references, yet another one containing references to patents; and so on.

The package uses the \newcites command in order to create multiple headings and place appropriate citations under each heading. The package is called in the preamble using a standard command - in this case \usepackage{multibib}.

This is followed by the \newcites command, one instance for each type of bibliography desired.

For example two bibliographies, one for book sources and one for journal articles, can be created by using the following LaTeX sequence in the preamble:

```latex
\usepackage{multibib}
\newcites{book}{Book References}
\newcites{journal}{Journal References}
```

In the above example the first argument refers to the type of bibliography and the second argument creates the header for the bibliography. The two types of citation can then be used in one or more sentences. For example book and journal references can be placed within a sentence as follows:

```latex
This sentence cites a book here \footcitebook{Walpol:2005} and cites a journal \footcitejournal{Steinbeck:2013} here.
```

The bibliography is created by placing the following sequence at the end of the document or at the end of any desired section:

```latex
\bibliographystylebook{plain}
\bibliographybook{all}
\bibliographystylejournal{plain}
\bibliographyjournal{all}
```

This is followed by running bibtex once for every instance of bibliography to be created. In this case there are two, so bibtex is to be run twice as follows:

```latex
% bibtex book
% bibtex journal
```

Finally the `.tex` file has to be compiled, twice for this example. *Overleaf automatically executes and repeats these steps as needed, so you won't need to run these manually yourself.*

The following is an example of a complete LaTeX code with two bibliographies:

```latex
\documentclass{article}
\usepackage{multibib}
\newcites{book}{Book References}
\newcites{journal}{Journal References}

\begin{document}
One of the most authoritative treatises on the phenomenon of
surface plasmon resonance was written by \cite{Homola:2006}.
A journal article on the same subject was published by \cite{Merwe:2012}.
```

## Further reading

For more information see:

* [Multibib example in the Overleaf Gallery](https://www.overleaf.com/latex/examples/multiple-bibliographies-with-multibib/fzmrrgbcvqhf)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://overleaf-pro.ayaka.space/latex/more-topics/40-multibib.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.