Anonymous LaTeX submissions: authors, PDF metadata and supplements

BlogEasyLaTeXPublished

For a double-anonymous LaTeX submission, start with the venue's review template, then check the compiled PDF and every file reviewers will receive. Removing the title-page names leaves other places to inspect: acknowledgments, self-identifying prose, PDF properties, repository links, and supplementary files.

Keep a named version for later publication. A switch can produce both PDFs from one source, but the source still contains the information hidden in the review PDF. That distinction determines what can go into a submission archive.

A recent example: one source, several submission versions

Released on November 12, 2026, EcoFin.sty illustrates this approach for economics and finance working papers. Its documented mode = blind hides names, thanks, email addresses and ORCID identifiers, and clears the PDF Author field. It also provides modes for a separate title page and online appendix.

This is a useful version-management example. A journal or conference that mandates its own class still requires that class. The workflow below works independently of EcoFin.sty; the complete example uses standard article and hyperref.

1. Use your venue's anonymous mode first

Download the template for the correct year and track. Find its review versus camera-ready instructions before changing \author by hand.

For example, the ACM author guidance and acmart manual describe an anonymous option. Where a venue specifies this setup, the class declaration can be:

LaTeX
\documentclass[manuscript,review,anonymous]{acmart}

This is a declaration fragment, not a complete ACM paper. review and anonymous are separate options: a review layout alone does not imply anonymity. Keep the format required by your venue, which may differ from manuscript. In acmart, put acknowledgments in the acks environment so its anonymous-mode handling applies.

Other templates use different controls. ICML 2026, for example, prints author information only when its style is loaded with accepted. These are documented examples, not a shared command that works in every class. Recheck the output after any custom header or metadata settings.

2. Check where identity can appear

Illustration: inspect the manuscript and the files around it. A clean title page covers only one part of the review package.

SurfaceWhat to inspectTypical action
Title and running headsNames, affiliations, email, ORCID, logos, author notesUse the required anonymous template and inspect every page
Body and notes“Our previous work,” lab names, acknowledgments, grant identifiersUse neutral wording and the venue's rules for disclosures
PDF propertiesAuthor, title, subject, keywords, XMP metadataCorrect the generating source and inspect the new PDF
Links and figuresActual hyperlink destinations, usernames, badges, screenshots, embedded figure metadataUse permitted anonymous materials and regenerate identifying figures
Supplement and archiveAppendix PDFs, README, notebooks, file paths, comments, Git historyInspect a separate submission copy and only include required files

Required ethics, data-use or conflict-of-interest statements still need to be supplied through the venue's prescribed mechanism. If a required disclosure identifies the authors, ask the organizers how to provide it during anonymous review.

Keep relevant self-citations, with neutral prose

The ICML 2026 instructions ask authors to discuss their previous work in the third person. Its example paper says not to anonymize published self-citations in the reference list. For example, change “In our previous work, we introduced…” to “Smith et al. introduced…”, retaining the appropriate citation and explaining how the new work differs. “Smith” here is an illustrative surname, not a bibliographic record.

Unpublished related work can have different rules, including an anonymous copy in the supplement. Follow those instructions instead of replacing every self-citation with “Anonymous.”

Changing a link's visible text to “anonymous repository” leaves its destination intact. Check the URL and the destination's README, account name, commit history, notebook outputs and hosted files. Use an anonymous archive or repository only when the venue allows it. Preserve required third-party license notices; if these create an anonymization conflict, seek venue guidance rather than deleting them indiscriminately.

Preprint policies also vary. ICML 2026 permits preprints but forbids identifying the work as an ICML submission during review, and its anonymous submission must not refer to its non-anonymous online version. This is an example of that year's policy, not a rule for all venues.

3. Build anonymous and named PDFs from one source

Save this complete teaching example as main.tex. It uses pdfLaTeX, the article class, and the fontenc, geometry and hyperref packages. All identity details are fictional. Use it to learn the switch; retain your venue's actual class, margins and disclosure requirements in a real paper.

LaTeX
\documentclass[11pt]{article}\usepackage[T1]{fontenc}\usepackage[margin=1in]{geometry}\usepackage[hidelinks]{hyperref}​\newif\ifreviewcopy\reviewcopytrue % Change to \reviewcopyfalse for the named version.​\title{A Reproducible Analysis: A Versioning Example}\date{}\ifreviewcopy  \author{Anonymous Author(s)}  \hypersetup{pdfauthor={},pdfsubject={},pdfkeywords={}}\else  \author{Alex Example\thanks{Illustrative funding: EX-123.}\\    Example Institute\\\texttt{alex@example.org}}  \hypersetup{pdfauthor={Alex Example}}\fi\hypersetup{pdftitle={A Reproducible Analysis: A Versioning Example}}​\begin{document}\maketitle\begin{abstract}This teaching example builds review and named copies from the same source.The name, institution, email, and funding code are fictional.\end{abstract}​\section{Method}The shared analysis is described here. The review copy retains the method,results, and references needed to evaluate the work.​\ifreviewcopy  \paragraph{Code availability.}  An anonymized code archive accompanies this submission.\else  \paragraph{Code availability.}  Code is available at \url{https://example.org/project}.\fi​\ifreviewcopy\else  \section*{Acknowledgments}  We thank the Example Institute reading group.\fi\end{document}

With \reviewcopytrue, the PDF shows “Anonymous Author(s)”, an empty Author property, and the anonymous code-availability sentence. The named author block, funding footnote and acknowledgments are omitted. Changing the switch to \reviewcopyfalse restores them. The example does not create a code archive: include one only after preparing it, and make the availability statement match what you actually supply.

For a local TeX Live or MiKTeX installation, compile the review version with:

Shell
pdflatex -interaction=nonstopmode -halt-on-error -jobname=review main.tex

Then change the switch to \reviewcopyfalse and run:

Shell
pdflatex -interaction=nonstopmode -halt-on-error -jobname=named main.tex

Separate job names keep the outputs apart. Both versions of this example were compiled with TeX Live 2026 pdfLaTeX through TeXLive.net, and the PDF text and Author properties were checked. This was a standalone test, not a test of every publisher template or the EasyLaTeX compiler.

Illustration: maintain the paper in one source, then inspect the specific PDF and archive you intend to submit.

4. Inspect the PDF you will upload

In a PDF viewer, open Document Properties and inspect Author, Title, Subject and Keywords. With hyperref, pdfauthor controls the document information Author field. hidelinks only changes link appearance; it does not remove destinations or metadata. Classes can set properties themselves, including around \maketitle, so a preamble setting needs an output check.

PDFs can contain both document information and XMP metadata. Clearing pdfauthor alone is not a complete metadata-cleaning procedure. Check comments and attachments too. An opaque rectangle or white text over an author's name is not redaction: underlying text or objects may remain.

For a reproducible first inspection, install Python 3 and pypdf:

Shell
python -m pip install pypdf

Save this read-only script as inspect_pdf.py. It prints document information, the catalog's XMP stream, selected annotation fields including link destinations, attachment names, and any supplied identity terms it finds in those fields or extracted page text.

Python
"""Read-only PDF triage. Reports evidence, never certifies anonymity."""import jsonimport sysfrom pypdf import PdfReader​reader = PdfReader(sys.argv[1])text = "\n".join(page.extract_text() or "" for page in reader.pages)stream = reader.trailer["/Root"].get("/Metadata")xmp = stream.get_object().get_data().decode("utf-8", errors="replace") if stream else ""annotations = []for number, page in enumerate(reader.pages, 1):    for ref in page.get("/Annots", []):        item = ref.get_object()        entry = {"page": number}        for key in ("/Subtype", "/T", "/Contents", "/Subj"):            if key in item:                entry[key] = str(item[key])        action = item.get("/A")        if action:            action = action.get_object()            for key in ("/URI", "/F"):                if key in action:                    entry[key] = str(action[key])        file_spec = item.get("/FS")        if file_spec:            file_spec = file_spec.get_object()            entry["attached_file"] = str(file_spec.get("/UF", file_spec.get("/F", "")))        annotations.append(entry)​report = {    "info": {str(k): str(v) for k, v in (reader.metadata or {}).items()},    "xmp": xmp,    "annotations": annotations,    "attachment_names": list(reader.attachments),}haystack = " ".join((text + "\n" + json.dumps(report, ensure_ascii=False)).casefold().split())report["matched_terms"] = [    term for term in sys.argv[2:]    if " ".join(term.casefold().split()) in haystack]print(json.dumps(report, ensure_ascii=False, indent=2))

Run it against the review PDF, replacing the example terms with your authors' names, institutions, email addresses, usernames and grant identifiers:

Shell
python inspect_pdf.py review.pdf "Alex Example" "Example Institute" "alex@example.org"

For the review example, matched_terms is empty and the Author value is empty or absent; the named PDF contains the fictional identity terms. An empty result is a triage result, not an anonymity certificate. The script does not OCR figures, search the contents of embedded files, or exhaustively inspect every PDF object or metadata stream. Names can also be split or encoded in ways text extraction misses. Read the PDF and check the links manually.

The script was also checked on a deliberately contaminated copy with an author stored in XMP, a named annotation, an identifying URL and an attachment filename. Those fields appeared in its report. For an identified figure, re-export it from its original tool and inspect both its visible content and metadata; changing the manuscript's Author property does not clean every included asset.

5. Package only what reviewers should receive

A review switch hides the named branch in the PDF while leaving it readable in .tex. Before uploading, check whether the submission asks for PDF only, source files, or a separate code/data supplement.

  • For PDF-only review, submit the checked review PDF and any explicitly required separate files. A named title page belongs only in a designated editor-only field when requested.
  • If sources are required for reviewers, create a separate submission copy. Remove author-bearing branches, source comments, unused personal files, identifying filenames and unneeded build logs from that copy. Keep the private working master intact.
  • For a supplement, check each PDF's properties, code comments, notebook outputs, screenshots, absolute paths and archive filenames. A neutral top-level ZIP filename does not rename the files inside it.
  • Extract the final archive into an empty folder. Inspect its contents and, when source is requested, compile that copy to confirm the anonymization edits did not break the paper. Include the dependencies the venue requests, without adding the private master or .git history.

Avoid substituting screenshots of manuscript pages for a text PDF. It harms searchability and accessibility and can conflict with submission requirements.

6. Apply the same checks in EasyLaTeX

Use your venue's template in the project. Select the intended main file, verify the compiler in Editor Settings, and compile the anonymous version. After a successful current job, inspect the preview and download the PDF from the toolbar. See the project-to-PDF guide for the verified main-file, compiler and download workflow.

Run the PDF checks on the downloaded file. If you download the LaTeX project for a source submission, inspect the archive separately: an anonymous PDF does not establish that its source package is anonymous. The PDF metadata documentation explains the underlying settings.

Final submission checklist

  1. Confirm the current venue, year, track, template and anonymous-review rules.
  2. Inspect the review PDF's title, running heads, footnotes, figures, acknowledgments and disclosures.
  3. Check self-citation wording and the destinations and contents of code/data links.
  4. Inspect PDF properties, XMP, comments and attachments, then review supplements and any source archive.
  5. Upload the intended file and, when the system permits, download the uploaded copy to verify that it is the checked version.
  6. Keep a restoration list for acceptance: authors, affiliations, acknowledgments, funding, permitted public links and any required final-version declarations.

Frequently asked questions

Is deleting the LaTeX author command enough?

It addresses only part of the title block. Check the venue's anonymous mode, running heads, acknowledgments, metadata, links and submitted attachments as well.

Should every self-citation become “Anonymous”?

No. Many venues require normal citations to published work, phrased in the third person. Unpublished or concurrently submitted work can require a different procedure. Check the target venue's instructions.

Does an anonymous option anonymize my source ZIP?

It controls the generated document. The ZIP can still include names in the non-review branch, comments, filenames, metadata and history. Inspect a submission copy if sources are required.

Can I restore the author line after acceptance and stop there?

Also restore the required acknowledgments, funding, disclosures and links, switch to the final template settings, and verify the author information against the submission system.

Sources

Policy and documentation checked November 20, 2026. Use the current instructions for your own submission; the 2026 examples above are not a forecast of 2027 rules.