Get your eNeuro paper right the first time: a ready-made structure with the right abstract and citations, so editors see your science, not formatting slips.
4.9
Authored by Sumalatha Gangadhar | Published on 10 August, 2026
Submitting to eNeuro goes smoothly when your draft already matches the journal's own rules. Editors screen new manuscripts against the eNeuro guide for authors before peer review, so formatting, structure, and required statements should be right on the first draft rather than repaired during upload. This template sets that structure up for you.
It is a manuscript shell aligned to eNeuro. It covers front matter, the abstract the journal expects, a body organized to the journal's article types, and a reference list in the journal's required style. Confirm current scope and article types on the eNeuro journal page before you draft.
Prepare the title, authors, affiliations, and ORCID iDs. Write the abstract to the journal's rule and word limit, organize the body to the article type, and apply the required reference style from the first citation. Complete every declaration (ethics, competing interests, funding, data availability) the eNeuro guide for authors lists, and cite figures and tables in order.
The common failure modes are formatting or reference style that does not match the guide for authors, missing required statements, and an incomplete portal checklist. Clear all three against the eNeuro guide for authors before you submit.
The shell mirrors what editorial staff check first: article-type fit, the abstract rules, required declarations, and the journal's reference style. For more detail see the author resources. When your draft is ready, upload it through the journal's submission system.
| Element | eNeuro requirement |
|---|---|
| Abstract | Unstructured abstract (no subheadings), 250 words maximum including citations. Should provide concise summary of objectives, methodology (including species and sex studied), key results, and major conclusions. Abstracts are not required for commentary, opinion, or review manuscripts |
| Main text | No overall length limit on manuscripts. Research articles: Introduction 750 words including citations, Discussion 3000 words including citations, Results no limit. Open Source Tools and Methods: 4500 words total with Introduction 500 words, Results 1000 words, Discussion 1000 words (all including citations). Commentaries: 3000 words. Opinions: 4000 words. Reviews: no length limit |
| Declarations | Ethics approval/consent as applicable; competing interests; funding; data availability |
| Figures/tables | Publication-ready; cited in order |
| Supplemental | Upload separately when used |
| Keywords | Not specified in the official author guidelines |
| References | Author-date citation style with alphabetical ordering. In-text citations as (Green, 1978) or (Brown and Black, 1979). Reference list alphabetical by first author surname, then chronological for same first author. Format: Author(s) (year) full title. Journal volume:pages. Author lists >20 should be cited as 'Author A et al.' |
| Peer review | Double-blind (identities of both authors and reviewers concealed throughout review process). If double-blind review is inappropriate for a manuscript, authors may email eneuro@sfn.org to inquire about single-blind review |
| Submission | eneuro.msubmit.net/submit |
Read the eNeuro guide for authors once before drafting and once before upload. Draft the abstract after results are stable. Set the reference style before adding citations. Keep a cover letter that states your contribution and fit to eNeuro in under a page.
Skim two or three recent eNeuro papers to calibrate depth and figure style. Make the novelty clear in the first two pages. Deposit data and code when the policy on the eNeuro journal page requires it. Disclose any preprint or conference version with identifiers in the cover letter.
Do one focused pass against the eNeuro guide for authors: scope, length, reference style, required declarations, and figure quality. Then submit through the journal's submission system.