Exporting

Jenni documents can be exported as Word files, LaTeX source, or copied to the clipboard with formatting intact. DOCX works for broad compatibility, LaTeX for journal submissions, and clipboard for quick transfers into other editors.

Download as Word (DOCX)

Open the three-dot menu in the top-right corner of the editor, select Export, then choose Download as DOCX. Jenni asks how in-text citations should look in the exported file; pick an option and click Download file. Formatting and unresolved document comments are preserved. Open the result in Microsoft Word, Google Docs, LibreOffice, or any application that reads .docx files.

Two citation options are offered:

• MS Word native citations (the default) – in-text citations and the bibliography are written as Word’s own citation fields and stay linked through Word’s References tab. Best when you will keep working in Microsoft Word.
• Hyperlink citations – in-text citations become clickable links and no Word citation fields are created. Best when you will open the file in Google Docs.

Neither option produces citations that Zotero, Mendeley, or another reference manager can update. Once exported, the citations belong to the file rather than to your reference library. To keep a reference manager in control of the citations in Word, insert them there with that manager’s own plugin.

The export menu is hidden while the new-document setup is open. Finish or skip setup before exporting an empty document.

Download as LaTeX

Open the three-dot menu, select Export, then choose Download as LaTeX. Jenni generates a .tex file along with a .bib file containing your references. Compile the output with pdflatex, xelatex, or your preferred LaTeX toolchain.

Images are referenced by path rather than embedded. If your document contains images, ensure the image files are in the same directory as the .tex file before compiling.

Copy to Clipboard

Open the three-dot menu in the top-right corner of the editor, select Export, then choose Copy to Clipboard, or select specific text and use Copy All to grab the entire document. Paste into any rich text editor – Google Docs, Notion, email composers – and the formatting carries over.

BibTeX and RIS Export

Citation data can also be exported independently from the References panel in the editor. Choose BibTeX or RIS format depending on your reference manager or submission requirements.

What Gets Exported

Formatting

Headings, bold, italic, underline, strikethrough, ordered and unordered lists, and text alignment are all preserved across export formats.

Rich Content

Citations and Bibliography

Inline citations are formatted according to your selected citation style. On paid plans, the full bibliography is appended at the end of the document. Citation locators and page ranges are preserved in DOCX, including citations inside lists, blockquotes, and tables. In LaTeX exports, citations use BibTeX references from the accompanying .bib file.

The appended bibliography requires a paid plan. On the free plan your inline citations still export normally, but the reference list is left out: DOCX omits the bibliography section, and LaTeX exports still include the .bib file but leave out the \printbibliography line that renders the list. When this applies, the export menu shows a note before you download.

Jenni also maps preprints, editorials, errata, paratext, retractions, supplementary materials, and library guides into compatible DOCX and BibTeX work types.

Comments in DOCX

Unresolved comment threads are preserved automatically as native Word annotations. The exported annotations remain attached to their text ranges and include the comment text, replies, and author information. Resolved threads are not exported.

Code Blocks

Code blocks keep line breaks and literal special characters in DOCX and LaTeX exports. Word uses the Consolas font and adds an italic language label above a block when you selected a language other than Plaintext. If you import that DOCX back into Jenni, the content returns as a code block with its language selection instead of plain paragraphs.

LaTeX exports use the listings package with line wrapping and a light frame. Python, C, Java, PHP, Bash, HTML, and Go blocks receive syntax highlighting; other languages remain readable as unhighlighted listings. Some code may produce a code-listing-*.txt sidecar file in the export ZIP. Keep these files beside the .tex file when compiling.

Best Practices

• Use LaTeX when submitting to academic journals or conferences that accept .tex source files.
• Use DOCX for general-purpose sharing, institutional submissions, or collaborative editing in Word or Google Docs.
• Use clipboard copy for quick transfers into emails, slide decks, or other documents.
• Finalize your citations and bibliography before exporting. Changes made after export are not reflected in the downloaded file.

Known Limitations

• Documents with many large images may take longer to generate as DOCX.
• Complex nested tables may render with minor differences in Word compared to the Jenni editor.
• Math equations in DOCX are rendered as images and cannot be edited as native Word equations.
• Some niche CSL citation styles may produce slight formatting variations compared to the editor preview.

Troubleshooting

DOCX formatting looks different than expected. Some styling differences between the Jenni editor and Word are normal. Check that you are using a recent version of Microsoft Word or Google Docs. Re-export if you made changes after the initial download.

LaTeX file does not compile. Verify that all required packages are installed in your LaTeX distribution. Ensure image files are present in the correct directory relative to the .tex file. Check the .bib file for malformed entries if citation errors appear.

Images missing from exported file. Re-upload any images that fail to appear. For DOCX, try exporting again after confirming your internet connection. For LaTeX, confirm the image files are in the same directory as the .tex file.

Frequently Asked Questions