1<!DOCTYPE html> 2<html lang="en"> 3<head> 4 <meta charset="UTF-8"> 5 <meta name="viewport" content="width=device-width, initial-scale=1.0"> 6 <title>About GROBID Tools: Independent PDF Extractor, Not the Official GROBID</title> 7 <meta name="description" content="Who runs GROBID Tools, what the in-browser PDF extractor does, and how it relates to the open-source GROBID library (it is independent and unaffiliated). Links to the official GROBID GitHub and docs."> 8 <meta name="last-modified" content="2026-10-03"> 9 <meta property="og:type" content="website"> 10 <meta property="og:url" content="https://grobid.org/about"> 11 <meta property="og:title" content="About GROBID Tools"> 12 <meta property="og:description" content="Browser-based PDF metadata and citation extraction. Files never leave the user's device."> 13 <meta property="og:updated_time" content="2026-10-03"> 14 <link rel="canonical" href="https://grobid.org/about"> 15 <link rel="icon" type="image/svg+xml" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'%3E%3Ctext y='.9em' font-size='90'%3Eð%3C/text%3E%3C/svg%3E"> 16 <link rel="stylesheet" href="/css/site.css"> 17<!-- Google tag (gtag.js) -->
vendor: 64 bytes, lines 17-18
17 18<script async src="https://www.googletagmanager.com/gtag/js?id=
18G-H1FWND0S6P
vendor: 12 bytes, line 18
18"></script>
19<script> 20
vendor: 134 bytes, lines 20-24
20window.dataLayer = window.dataLayer || []; 21 function gtag(){dataLayer.push(arguments);} 22 gtag('js', new Date()); 23 24 gtag('config', '
24G-H1FWND0S6P
vendor: 4 bytes, line 24
24');
25</script>
25 26</head> 27<body> 28 <nav class="site-nav" aria-label="Primary"> 29 <div class="site-nav-inner"> 30 <a href="/" class="brand">ð GROBID Tools</a> 31 <ul> 32 <li><a href="/">Extractor</a></li> 33 <li><a href="/guides/what-is-grobid">What is GROBID?</a></li> 34 <li><a href="/guides/">Guides</a></li> 35 <li><a href="/formats/">Formats</a></li> 36 <li><a href="/about">About</a></li> 37 <li><a href="/contact">Contact</a></li> 38 </ul> 39 </div> 40 </nav> 41 42 <main class="doc-page"> 43 <h1>About GROBID Tools</h1> 44 <p class="meta">Last reviewed on October 3, 2026</p> 45 46 <p>GROBID Tools is a small, focused web utility for extracting bibliographic metadata and citation data from PDF documents. The entire pipeline â file reading, text extraction, metadata heuristics, and export generation â runs inside the visitor's browser using PDF.js and pdf-lib. Nothing about a chosen file is uploaded to a server.</p> 47 48 <h2>Who the site is for</h2> 49 <p>The tool is built for readers who routinely handle academic and technical PDFs and want a fast way to pull structured information out of them without installing software or sending the file to a remote service. Typical visitors include:</p> 50 <ul> 51 <li>Researchers building reading lists, literature reviews, and reference libraries.</li> 52 <li>Graduate and undergraduate students assembling bibliographies for theses, essays, and lab reports.</li> 53 <li>Librarians, archivists, and information professionals organising collections of digital papers.</li> 54 <li>Developers and data engineers who want a quick way to inspect what is actually inside a PDF before writing parsing code of their own.</li> 55 </ul> 56 57 <h2>What the tool covers</h2> 58 <p>The extractor focuses on the structured information that is most useful when working with scholarly and technical PDFs. That includes the document title, author names, publication year, abstract, keywords, page count, and persistent identifiers such as DOI, ArXiv ID, PubMed ID, and ISBN where they appear. The tool also attempts to detect a references section and split it into
58individual citations, pulling out DOIs and URLs per entry where they are present.</p> 59 <p>Outputs can be exported to JSON, plain text, Markdown, Microsoft Word (.docx), BibTeX, RIS and CSL-JSON. The export step also runs in the browser, so the file never travels over the network.</p> 60 61 <h2>Editorial approach</h2> 62 <p>The written guides on this site explain how PDF metadata is structured, how citation parsing actually works in practice, and what to expect when an automated tool encounters a messy or scanned document. The goal is to set realistic expectations: heuristic extraction is useful, but it is not a substitute for hand-curated metadata when accuracy is critical.</p> 63 <p>Articles are written from working experience with PDF tooling and from public, well-established documentation about formats such as BibTeX, RIS, CSL-JSON, and the PDF specification itself. Where a topic touches on a specific external service or standard, the relevant primary source is linked.</p> 64 65 <h2>How content is produced</h2> 66 <p>Every guide and reference page on the site is reviewed before publication and dated with a "Last reviewed on" line so readers can see how recently the information was checked. When formats, identifiers, or browser APIs change in a way that materially affects the guidance, the page is revisited and the date updated. Pages that no longer reflect current practice are corrected, marked as historical, or removed.</p> 67 68 <h2>Privacy by default</h2> 69 <p>The product decision that drives the site is simple: a researcher should be able to inspect a PDF without trusting a remote operator with its contents. That decision shapes the architecture (everything in the browser), the offline support (the page registers a service worker so it keeps working without a network connection), and the analytics (Google Analytics records page-level visit statistics such as pages viewed and device type; no file contents, file names, or extracted text are ever transmitted). The full data practice is described on the <a href="/privacy">privacy page</a>.</p> 70 71 <h2>Independence</h2> 72 <p>GROBID Tools is an independent project. It is not affiliated with, endorsed by, or maintained by the developers of GROBID, nor with any publisher, university, or commercial reference manager. The name reflects the shared problem space â extracting structured information from scholarly PDFs â not a partnership.</p> 73 <p>The in-browser extractor on this site does <strong>not</strong> run GROBID. It uses lightweight heuristics on top of PDF.js. If you are looking for the GROBID library itself:</p> 74 <ul> 75 <li>Source code and releases: <a href="https://github.com/kermitt2/grobid" rel="noopener">github.com/kermitt2/grobid</a></li> 76 <li>Official documentation: <a href="https://grobid.readthedocs.io/" rel="noopener">grobid.readthedocs.io</a></li> 77 <li>Our independent explainers: <a href="/guides/what-is-grobid">What is GROBID?</a>, <a href="/guides/grobid-docker-and-api">Running GROBID with Docker and the REST API</a>, and <a href="/guides/grobid-alternatives">GROBID alternatives</a>.</li> 78 </ul> 79 80 <h2>Contacting the site</h2> 81 <p>Corrections, broken-link reports, and feedback are welcome. The <a href="/contact">contact page</a> lists the current address.</p> 82 </main> 83 84 <footer> 85 <div class="footer-inner"> 86 <nav class="footer-links" aria-label="Site policies"> 87 <a href="/about">About</a> 88 <a href="/contact">Contact</a> 89 <a href="/privacy">Privacy</a> 90 <a href="/terms">Terms</a> 91 <a href="/cookies">Cookies</a> 92 <a href="/disclaimer">Disclaimer</a> 93 </nav> 94 <p>© 2026 GROBID Tools. Built with PDF.js running in your browser. Independent site, not the official GROBID project.</p> 95 </div> 96 </footer>
97<script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba1788362987495" integrity="sha512-iIg7k2xntmwu6/uSb5tpc/hySgZc4eoL31yB29W6tJFo2akwjPWcEqnCEdJvGexCL0KEQwVYv5BlowfhVz26hg==" data-cf-beacon='{"version":"2024.11.0","token":"ff07b682413a49e1bea5aa049f7b54fc","r":1,"spa":2}' crossorigin="anonymous"></script>
97 98</body> 99</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.