ACS Nano Submission Process
ACS Nano's submission process, first-decision timing, and the editorial checks that matter before peer review begins.
Readiness scan
Before you submit to ACS Nano, pressure-test the manuscript.
Run the Free Readiness Scan to catch the issues most likely to stop the paper before peer review.
Resolve nanoscale consequence before upload mechanics
Connect nanoscale advance, characterization, mechanism, benchmark, realistic function, and failure.
- 01Assess
Write a bounded 150-word significance case.
- 02Prove
Map claims to figures, controls, and failures.
- 03Upload
Reconcile files, declarations, data, and authors.
Key numbers before you submit to ACS Nano
Acceptance rate, editorial speed, and cost context, the metrics that shape whether and how you submit.
What acceptance rate actually means here
- ACS Nano accepts roughly ~8.4% of submissions, but desk rejection runs higher.
- Scope misfit and framing problems drive most early rejections, not weak methodology.
- Papers that reach peer review face a different bar: novelty, rigor, and fit with the journal's editorial identity.
What to check before you upload
- Scope fit: does your paper address the exact problem this journal publishes on?
- Desk decisions are fast; scope problems surface within days.
- Cover letter framing: editors use it to judge fit before reading the manuscript.
How to approach ACS Nano
Use the submission guide like a working checklist. The goal is to make fit, package completeness, and cover-letter framing obvious before you open the portal.
Stage | What to check |
|---|---|
1. Scope | Manuscript preparation |
2. Package | Submission via ACS system |
3. Cover letter | Editorial assessment |
4. Final check | Peer review |
Quick answer: The ACS Nano submission process begins in the current ACS Publishing Center. Before upload, make one sentence connect the nanoscale advance, the evidence that verifies it, and the consequence that makes it matter. The current ACS Nano guidance says that editors send manuscripts they consider within scope and of interest to the journal for external evaluation; that makes a legible fit and evidence route more useful than a longer formatting checklist.
Evidence basis: We reviewed the official ACS Nano author guidelines, ACS Nano journal page, and ACS Publishing Center on August 31, 2026. The live ACS instructions control the submission. The diagnostic maps below are Manusights editorial judgment, not a private editorial policy or acceptance forecast.
Check whether the nanoscale claim and evidence package agree.
Make the editor's initial question answerable
Package element | Reader question it answers | Hold signal |
|---|---|---|
Title, abstract, and first figure | What is the nanoscale advance and why does it change a decision? | The consequence appears only after a long synthesis narrative |
Characterization and controls | What property, structure, or mechanism is actually established? | One technique or selected example carries the entire inference |
Comparator and benchmark | Compared with what plausible alternative is the claimed improvement meaningful? | The benchmark is incomplete, mismatched, or unexplained |
Supporting Information | Can a specialist inspect the methods, data, and edge cases supporting the main result? | Decisive controls or analysis cannot be located |
Reviewer route | Which expertise is needed to test the central claim? | The paper presents several unrelated identities with no clear center |
Worked example: a high-performance material claim
An article reports improved device performance. The upload is stronger when the main file identifies the operating condition and comparator, the figures show variability and limitation, the Supporting Information exposes the measurement and control details, and the cover letter states the nanoscale mechanism only as far as the evidence supports it. A high value alone is not the complete claim.
Use the current official route, not a remembered workflow
ACS Nano directs authors to the ACS Publishing Center. Its current author guidance asks authors to use the required submission workflow, encourages the ACS Author Checklist, and says to submit manuscript-related work as Review-Only Material when appropriate. It also asks authors to suggest six to eight reviewers and identify one or more Editors whose expertise matches the manuscript. Confirm every live field, policy, article-type rule, and disclosure at the point of upload.
We did not find current official guidance naming a separate transparent, portable, or open peer-review feature for ACS Nano in this review. That is an availability limit, not evidence that no such program can ever exist; use the current author guidance if the review model matters to the submission decision.
- Manuscript and title page matched to the current article type.
- Concise cover letter explaining the nanoscience contribution, evidence boundary, and journal fit.
- Figures and legends that disclose controls, scale, uncertainty, and the comparator behind the main claim.
- Supporting Information or Review-Only Material with methods, characterization, data, code, and analysis needed for the central result.
- Data availability statement, conflicts of interest, funding statement, author contributions, permissions, and ethics documentation where relevant.
- Suggested reviewers and suitable Editor expertise, checked against the current guidance and free of conflicts.
Treat reviewer routing as an evidence problem
The official ACS Nano guidance says external reviewers evaluate originality, technical quality, clarity, and significance. It does not publish a case-specific timetable or a private desk-rejection rate that a guide can honestly promise. Use this caveated map to organize the work, not to predict a result:
- Upload and record check: current files, disclosures, and article-type conditions are reconciled.
- Editorial assessment: scope, interest, and the central evidence route become visible to the handling editor.
- External evaluation: reviewers test originality, technical quality, clarity, and significance.
- Decision or revision: the editor's communication defines the individual manuscript's action.
Review figures, benchmarks, and claim boundaries before submission.
Repair the failure pattern, not the label
A characterization list is mistaken for an evidence chain. Name which measurement establishes each structural, compositional, functional, or mechanistic statement. Where several accounts remain possible, say so.
The headline outruns the comparator. A table of published values is only useful when operating conditions, sample definitions, uncertainty, and relevance to the claim are comparable. Explain the boundary instead of selecting the easiest number.
The Supporting Information stores proof without routing it. Point from every important result to the method, raw result, control, or limitation a reviewer needs to inspect. A file dump is not an audit trail.
The suggested-reviewer list reveals no center of gravity. The author guidance allows suggestions; choose expertise that can test the actual claim rather than covering every adjacent field.
Readiness check
Run the scan while ACS Nano's requirements are in front of you.
See how this manuscript scores against ACS Nano's requirements before you submit.
Compare the owner before upload
Decision question | ACS Nano | ACS Applied Materials & Interfaces | Nano Letters |
|---|---|---|---|
Main owner | Nanoscale advance whose evidence and consequence form one clear contribution | Materials and interface work with an application or engineering center | A concise nanoscience contribution with an identifiable fundamental advance |
Evidence check | Originality, technical quality, clarity, and significance are inspectable | Application evidence and material-interface reasoning remain central | The novel nanoscale finding remains clear without overextended application framing |
Hold signal | The manuscript is a standard material application with no explained nanoscale contribution | The work is primarily a broad nanoscience discovery | The manuscript needs a fuller methods or application argument than the target supports |
This is a routing boundary, not an acceptance forecast. Verify each journal's live scope and instructions before choosing a destination.
Pre-submission checklist
- The current ACS Nano article type, author checklist, declarations, and upload fields are reconciled.
- Every central claim points to its figure, comparator, method, and limiting condition.
- Suggested editor and reviewer expertise map to the one main contribution; conflicts are checked.
- Author contributions, competing-interest statement, data availability statement, and any relevant ethics statement agree across files.
Submit if
Build a claim-to-file map before final upload
For each headline result, list the main figure, the supporting method or characterization file, the comparator, and the limiting condition. This lightweight map catches a common package defect: the manuscript makes a precise nanoscale claim but the evidence needed to inspect particle definition, interface, calibration, uncertainty, or reproducibility is scattered across an unlabelled supplement.
The map should also test the paper’s journal boundary. If the central contribution is an application result, state where the nanoscale advance changes the interpretation. If the contribution is mechanistic, state which measurement actually distinguishes the proposed mechanism from alternatives. This is not an ACS Nano editorial rule or an outcome forecast. It is a Manusights way to make the evidence trail visible before a reviewer or editor has to reconstruct it.
For a materials paper, the useful record often includes sample identity, processing history, the relevant morphology or structure readout, the functional measurement, and a like-for-like baseline. For a biological nanoscience paper, it may instead connect particle definition, dose or exposure condition, assay controls, and the boundary on the claimed mechanism. The point is not to add a generic checklist. It is to make the one contribution on which journal fit depends auditable in the main manuscript package.
- The title, abstract, first figure, benchmark, and evidence appendix support the same bounded claim.
- A specialist can identify the controls and source material needed to check the central result.
- Suggested reviewer expertise corresponds to the paper's real intellectual center.
- The current ACS Nano guidance has been checked immediately before upload.
Think twice if
- The evidence is sufficient to describe a material but not the claimed mechanism or consequence.
- A comparison set removes the context needed to judge the stated improvement.
- Decisive controls, raw data, code, or analysis are not routed from the main result.
- The paper belongs more naturally to an applications, materials, catalysis, device, or biology owner.
Frequently asked questions
Use the current ACS Publishing Center and ACS Nano author guidance. Confirm article type, files, declarations, reviewer information, and any live checklist requirements at upload.
Do not use a generic guide as a timeline promise. Editorial and reviewer timing depends on the individual manuscript; use the live record and editor correspondence.
The official guidance says editors send papers they consider within scope and of interest for external evaluation. Make novelty, technical quality, clarity, and significance inspectable from the main package.
The current author guidance asks authors to suggest six to eight reviewers and identify one or more Editors whose expertise matches the manuscript. Recheck the live instructions before submitting.
Use the current guidance and include the material needed to evaluate the central claim, such as methods, controls, data, code, characterization, and extra analysis when relevant.
Sources
- 1. ACS Nano author guidelines, American Chemical Society.
- 2. ACS Nano journal page, American Chemical Society.
- 3. ACS Publishing Center, American Chemical Society.
Final step
Submitting to ACS Nano?
Run the Free Readiness Scan to see score, top issues, and journal-fit signals before you submit.
Target journal ACS Nano
Private API processing. Your manuscript is not used to train models.
See example reportsPut the guidance to work
Turn the guide into a complete submission package.
Use one final checklist, then verify the journal rule that controls the files, declarations, and reporting details you will submit.
Where to go next
Start here
Same journal, next question
- ACS Nano Submission Guide: Scope, Format & Tips (2026)
- How to Avoid Desk Rejection at ACS Nano
- ACS Nano Pre Submission Checklist: 12 Items Editors Verify Before Peer Review
- ACS Nano Review Time: What Authors Can Actually Expect
- ACS Nano 'Under Review': What Each Status Means and When to Expect a Decision
- ACS Nano Acceptance Rate: What Authors Can Use