Prepare a submission package

Verify the final PDF and collect reproducible source files without omitting manuscript dependencies.

Prepare the exact artifacts requested by the venue: often a final PDF, source archive, figures, bibliography data, and supplemental files. The in-browser preview is evidence during writing; the downloaded files are what you submit.

Freeze a candidate#

Choose the deliverable deliberately: Download PDF supplies the rendered paper; Download document supplies one paper's source archive; Project actions → Export ZIP supplies the entire project tree. A venue may require more than one of these.

Stop broad edits long enough to establish one reviewable state. Open and compile the paper you intend to submit, resolve current errors and unexplained warnings, and save a named version such as Submission 1. Coordinate this pause with active coauthors so later edits are not mistaken for part of the candidate.

Record that paper's root file, engine, TeX Live snapshot, and venue mode (anonymous, review, or camera-ready). If the submission system assigns an ID or changes the required mode, make that change in a new named version.

Inspect the PDF as a reader#

Download and open the ordinary or accessible PDF outside CorTeX. Check:

• title, authorship or anonymization, affiliations, abstract, and metadata;
• page count, paper size, margins, fonts, and two-column layout;
• equations, references, citations, bibliography, and hyperlinks;
• figure resolution, color meaning, captions, alt text, and table readability;
• appendices, acknowledgments, disclosures, and supplemental references.

Search the PDF for ??, placeholder text, TODO markers, and sample template content. Confirm that the downloaded file reflects the latest successful compile rather than an older PDF retained after an error.

Verify the source archive#

For a single LaTeX document, choose Download document from its file row menu. CorTeX compiles it and packs only what that compile reads, with a shared bibliography or class file brought in and the references to it rewritten so the archive can compile on its own. If compilation fails, CorTeX reports that it is downloading the folder as it stands instead; that fallback may omit dependencies outside the folder. Resolve the failure or supply and verify those files before submission. Check the archive rather than the project: open it and confirm no private note, unused large asset, local credential, or review-only file travelled with the document.

To send a whole project instead, do not clean the live collaborative project by deleting private notes. From the named version, use Copy to new project to make a submission-only project, or export a ZIP and import it as a separate project. Remove private material only from that copy, and keep every .tex, .bib, class/style, font, image, data, and supplemental file the main document needs; do not remove a dependency simply because TeX Live also has a file with the same name. Then choose Project actions → Export ZIP, and name the project and archive so a coauthor cannot confuse them with the live manuscript.

Test the archive before submission: inspect its paths, import it into a separate project if practical, select the same profile and main file, and compile. This catches missing local assets, capitalization differences, and assumptions about your original project state.

Keep evidence after upload#

Compare the venue's generated proof with the PDF you inspected. Keep the named CorTeX version, submitted PDF, submitted ZIP, and confirmation together under your research record policy. A named version stays fixed while the live manuscript can continue changing. Save a later named version for corrections or another venue so the submitted candidate remains identifiable.

The package is ready when the downloaded PDF passes visual and structural review, a clean copy builds from the source archive, and both correspond to one named project version. Return to Version history if you need to recover the exact candidate.