When submitting to a journal under MDPI, how do you choose options when using overleaf?

When submitting to an MDPI journal using Overleaf, the primary choice involves selecting the correct journal-specific LaTeX template and then configuring the submission settings within Overleaf to align with MDPI’s manuscript preparation and submission protocols. The process is not about making arbitrary choices but about following a prescribed technical workflow to ensure the compiled PDF meets the journal’s strict formatting requirements for initial submission. Upon starting a new project in Overleaf, you must first locate and open the official template for your target MDPI journal, which can be found via the “Templates” menu by searching for “MDPI” or by directly accessing the template link often provided in the journal’s “Instructions for Authors.” This template is non-negotiable; it contains the necessary document class (`mdpi.cls`), all required LaTeX packages, and predefined formatting for sections, author affiliations, and citation styles, thereby structuring the technical backbone of your manuscript.

The critical configuration occurs within the Overleaf project’s “Menu” under “Settings,” where you must set the compiler to “LaTeX” (or occasionally “PDFLaTeX,” but the MDPI template typically specifies the required engine) and ensure the main document to be compiled is correctly identified, usually `main.tex`. A significant choice involves handling bibliography compilation; MDPI templates generally use BibTeX, so you must select “BibTeX” as the bibliography tool in the settings. Furthermore, you must manage any supplementary files, such as high-resolution figures in designated folders or supplementary information files, ensuring they are correctly referenced in the LaTeX code. The Overleaf project essentially becomes a precise replica of the final submission package, where every file and compiler setting directly influences the generated PDF’s compliance. There is no meaningful “option” to deviate from these settings if you intend to submit; the template and associated configuration are designed to produce a manuscript that conforms to MDPI’s visual and structural standards, which are checked during the technical validation stage prior to peer review.

The implications of correctly executing this process are substantial for submission efficiency. An improperly configured Overleaf project—using the wrong compiler, failing to process BibTeX, or modifying the template’s core definitions—will generate a PDF that may be rejected by the editorial office during initial technical screening, causing avoidable delays. The mechanism here is one of standardization: MDPI’s template automates formatting consistency across thousands of submissions, and Overleaf’s cloud-based environment ensures that the authors and editors are viewing the same compiled output. Therefore, the operative choice is less about preference and more about adherence. Before final submission, you must download the complete source files (the .zip archive) from Overleaf, as MDPI’s submission system requires you to upload this .zip package alongside the compiled PDF. This ensures the editorial team can recompile the manuscript exactly as you intended, making the Overleaf settings an integral, fixed component of the submission itself rather than a discretionary step.