Bibliographic Metadata
- Document title
- Author names
- Publication year
- Abstract text
- Keywords
- Page count
Pull the title, authors, DOI, arXiv ID and reference list out of a PDF, right in your browser
Looking for the GROBID library itself? This is an independent website and is not affiliated with the GROBID project. The open-source GROBID software lives at github.com/kermitt2/grobid with official documentation at grobid.readthedocs.io. Our guides explain what GROBID is and how to run it with Docker and its REST API.
Processed locally in your browser. Maximum file size: 50MB
๐ก Best results with text-based (born-digital) PDFs. Scanned or image-only PDFs need OCR first. This is a lightweight heuristic extractor; for large-scale, high-accuracy parsing see the open-source GROBID library.
Transform your PDF data into any format you need - all processed locally in your browser
Structured data with all metadata & citations
Clean UTF-8 text file (.txt)
Formatted DOCX document
GitHub-flavored Markdown (.md)
Your PDFs never leave your computer. All processing happens locally in your browser.
No upload and no server queue. PDF.js parses the file in a web worker on your own machine.
After the first visit the app shell and libraries are cached, so the extractor keeps working without a connection.
No sign-up, no API limits, no upload quotas. Built on the open-source PDF.js library.
Practical guides on how PDF metadata is structured, how citation parsers actually work, and how to turn extracted records into a clean bibliography.
Where metadata lives inside a PDF, how heuristic extractors find titles and authors, and the failure modes worth knowing about.
How a parser splits a references section, labels each field, and keeps its hands off the ambiguous bits.
The persistent identifiers that make a citation resolvable โ DOI, ArXiv, PubMed, ORCID, ISBN, ISSN.
What to do when a PDF has no text layer: tools, accuracy expectations, and privacy considerations.
The architectural choices behind a privacy-first PDF extractor, from PDF.js to service workers.
An independent overview of the open-source GROBID library: what it extracts, the TEI XML output, and where it is used.
Start a local GROBID server, call the REST API with curl, and batch-process PDFs with the Python client.
CERMINE, AnyStyle, Nougat, Docling, Marker and browser tools compared for metadata and reference extraction.
What an arXiv ID is, the old and new formats, versions, and how arXiv IDs relate to DOIs.
Where a DOI hides in a paper, and how to look one up from the title when the PDF does not print it.
The practical differences between .bib, .ris, EndNote XML and CSL-JSON, and which to export.
Reference pages for BibTeX, RIS, CSL-JSON, Markdown, and DOCX, with notes on when to pick each.
No. GROBID Tools is an independent site. The GROBID library is an open-source project developed on GitHub at github.com/kermitt2/grobid, with documentation at grobid.readthedocs.io. This site offers a separate, lightweight in-browser extractor and guides about GROBID and bibliographic formats.
No. The PDF is opened with PDF.js inside your browser and the extracted data is generated locally. The site uses Google Analytics for page-level visit statistics, but file names, file contents and extracted text are never sent anywhere.
No. It uses lightweight heuristics (layout, font size and regular expressions) that run in the browser. GROBID itself is a Java service with trained models and gives more accurate, more structured results on large collections. See the guide on running GROBID with Docker.
JSON, plain text, Microsoft Word (.docx), Markdown, BibTeX (.bib), RIS (.ris) and CSL-JSON. Reference strings are exported as found in the PDF, with any DOI, year and URL detected in them, so check them before citing.
Only if the PDF already has a text layer. Image-only scans need OCR first; the tool warns you when it finds almost no text.
Last reviewed on October 3, 2026