Journal of High Energy Physics Submission Guide
A practical JHEP submission guide for high-energy physics authors deciding whether their arXiv-first manuscript fits SISSA keyword routing, SCOAP3 coverage, and the JHEP versus PRD or JCAP choice.
Readiness scan
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan before you submit. Catch the issues editors reject on first read.
Quick answer: This Journal of High Energy Physics submission guide is for authors preparing a JHEP paper through the SISSA/Springer route. The main checks are not cosmetic: your arXiv ID, TeX package, 2 to 4 JHEP keywords, abstract, and field framing need to make the high-energy physics audience obvious before editor routing begins.
JHEP is a strong target when the manuscript is native to high-energy physics: quantum field theory, string theory, collider phenomenology, formal theory, amplitudes, particle physics, or adjacent HEP work. If the paper is mainly cosmology, gravitation, or observational astrophysics, compare JCAP, PRD, ApJ, or MNRAS before upload. A JHEP submission readiness check can test whether the paper reads as JHEP, PRD, JCAP, or EPJC before you submit.
What official JHEP pages do and do not answer
The official JHEP and Springer pages answer the mechanics. They show that submissions go through the JHEP website at SISSA, that the journal is full open access and sponsored by SCOAP3, that authors need an arXiv article ID, and that the system uses selected keywords to route the paper.
Those pages do not decide whether your manuscript belongs in JHEP rather than Physical Review D, Journal of Cosmology and Astroparticle Physics, European Physical Journal C, Physics Letters B, or a narrower theoretical physics venue. That is the commercial and editorial decision this page owns: does the manuscript read like a JHEP paper before the upload system assigns it to an editor?
How this page was created
This page was created by checking JHEP's current SISSA author instructions, JHEP's published workflow page, Springer's current JHEP journal page, the Springer submission-guidelines route, SCOAP3 journal and FAQ pages, and local Manusights physics-routing pages for sibling contradiction checks. The original evidence here is the translation layer: official pages tell you the upload route, arXiv and keyword requirements, SCOAP3 cost route, and workflow markers, while this guide turns those facts into a JHEP-versus-PRD-versus-JCAP submission decision.
JHEP submission facts at a glance
Submission item | What to verify before upload | Why it matters |
|---|---|---|
Submission route | Use the JHEP website at SISSA | Springer links the official submit route to SISSA, not a generic Springer upload form |
arXiv ID | Have the arXiv article ID ready | JHEP says this is needed for SCOAP3 categorization if accepted |
Keywords | Choose 2 to 4 JHEP keywords | The system uses keywords to assign the preprint to the appropriate editor |
File package | Use clean TeX files, master file naming, figures, and attachments | SISSA can download from arXiv or process an uploaded archive, but compilation failure creates avoidable delay |
Template | Use the JHEP style or JHEPPUB package when possible | JHEP says the template can reduce production turnaround after acceptance |
Cost route | Check SCOAP3 coverage and article category | JHEP is fully sponsored by SCOAP3, and SCOAP3 says authors do not pay direct fees for supported journals |
Field fit | Decide JHEP versus PRD, JCAP, EPJC, PLB, or NPB before upload | The strongest JHEP papers speak to the high-energy physics community without forcing the editor to infer the audience |
JHEP's author pages reviewed for this guide do not publish a no fixed word limit or no fixed figure cap for ordinary initial submissions. The practical limits are still real: the abstract should fit on the first page, formulae and references should not be placed in the title or abstract, and JHEP has a front-matter warning for collaboration papers when author-list material exceeds 2 pages.
Should you submit to JHEP?
Submit to JHEP if the manuscript's natural reader is a high-energy physicist and the result is ready for a specialist HEP editor. Good fits include:
- formal high-energy theory
- quantum field theory
- string theory and holography
- scattering amplitudes
- collider phenomenology
- particle-physics models with a clear HEP audience
- theoretical or phenomenological work that the JHEP keyword list can route cleanly
Think twice if the paper is mainly:
- cosmology or astroparticle physics, where JCAP may be the more native SISSA title
- broad particles, fields, gravitation, or cosmology work that benefits from APS's PRD readership
- short, broad-physics work that should be tested against Physical Review Letters
- instrumentation or detector work whose strongest audience is an experimental-instrumentation journal
- mathematical physics with limited high-energy relevance
The practical test is simple: if the title, abstract, and first result do not make a JHEP editor assignment feel obvious, fix the framing or choose another venue first.
Readiness check
Run the scan against the requirements while they're in front of you.
See score, top issues, and journal-fit signals before you submit.
The arXiv and keyword step is not clerical
JHEP submission is unusually tied to the high-energy physics preprint culture. The SISSA instructions explain that authors can submit from arXiv or upload the files directly. The same guidance says authors need to provide an arXiv article ID, and that at submission they must characterize the work using keywords selected from the JHEP keyword list.
That means two documents have to agree:
If the manuscript says... | The submission package should make clear... |
|---|---|
This is a formal theory paper | Which HEP theory keyword lane should own it |
This is collider phenomenology | Which observable, process, or model class anchors the paper |
This is string theory or holography | Why the target reader is JHEP rather than a mathematical-physics venue |
This is cosmology-adjacent HEP | Why JHEP is better than JCAP or PRD |
This is experimental HEP | Whether the evidence reads as HEP physics rather than detector or instrumentation work |
Poor keyword choice is not just a metadata problem. It can send the paper to an editor whose expertise is adjacent but not exact. The fix is to write the abstract and choose the keywords together, not after the manuscript is already locked.
Across our JHEP pre-submission reviews
Across our JHEP pre-submission reviews, the most useful early signal is whether the manuscript's first page and metadata point to the same HEP community. The weak submissions usually have good physics somewhere inside them. The problem is that the editor has to infer too much from the title, abstract, arXiv category, JHEP keywords, and first figure or equation.
In our pre-submission review work, we see this as a routing problem rather than a formatting problem. Manusights internal analysis of JHEP-targeted physics manuscripts treats the first screen as a consistency test: arXiv record, JHEP keyword selection, abstract, first result, and bibliography all need to say the same thing about the intended referee pool.
The JHEP keyword-mismatch paper has a technically credible result but selects keywords that point to a different editor audience than the abstract does. The manuscript may read as collider phenomenology while the keywords emphasize formal theory, or it may motivate itself with cosmology while the actual contribution is a QFT calculation. The fix is to revise the abstract and keywords together so the editor can identify the right high-energy physics lane. Check whether your JHEP keyword route is defensible →
The PRD-or-JHEP ambiguity paper is strong enough for specialist physics review but unclear about community. PRD can be better when the manuscript spans particles, fields, gravitation, or cosmology and needs the APS umbrella. JHEP can be better when the work is squarely HEP and the relevant referees are likely to come from that community. The manuscript should make that choice visible in the introduction, not leave it to the cover note. Check whether JHEP or PRD is the better first target →
The arXiv-clean but journal-weak paper is already public and technically complete, but it has not been shaped for journal review. The TeX compiles, the arXiv record exists, and the result is real, yet the discussion does not state what the result changes for the JHEP reader. That is where a preprint becomes a weak submission: the paper is visible, but the journal claim is not. Check whether your arXiv preprint is ready for JHEP review →
The review tells you whether your paper passes that first-read fit test before submission. Reviews include a 60-day money-back guarantee, and we do not train AI models on your manuscript.
What to prepare before opening the JHEP system
Do not start the upload session while you are still deciding what the paper is. Build the package first.
Package item | Practical check |
|---|---|
arXiv record | The arXiv ID is ready and the public category matches the manuscript's field identity |
TeX source | The archive compiles cleanly and the master file is obvious |
Figures and attachments | Large tables, additional figures, and supplementary material are prepared as attachments when needed |
JHEP keywords | 2 to 4 keywords describe the real editor lane, not only broad HEP words |
Abstract | The abstract fits on the first page and avoids formulae and references |
Author metadata | Collaboration papers use the collaboration name in metadata where appropriate |
ORCID and author accounts | The corresponding author is registered and coauthor details are ready |
Cover note | The venue-fit argument explains JHEP rather than PRD, JCAP, EPJC, or PLB |
Required submission artifacts to prepare
JHEP's public instructions are not a generic biomedical-style checklist, so do not claim that every artifact below is mandatory for every paper. Use this as a pre-upload control list: prepare the item when it applies, and verify the live SISSA screen before final submission.
Artifact | JHEP-specific use |
|---|---|
Cover letter or cover note | State why the manuscript belongs in JHEP rather than PRD, JCAP, EPJC, PLB, or NPB |
Data availability statement | Include only when the work has data, code, simulations, or reusable analysis outputs that need an availability statement |
Ethics statement | Usually not relevant for formal theory, but check it for human, animal, detector-operation, or collaboration-governance edge cases |
Conflicts of interest | Prepare a clean disclosure even if the live SISSA form captures it separately |
Author contributions | Useful for multi-group or collaboration papers where contribution roles may need clarification |
Funding statement | Keep grant and collaboration funding language consistent with the manuscript and author metadata |
Supplementary information | Prepare supplementary files, large tables, figures, code notes, or technical appendices as attachments when needed |
ORCID | Make sure the corresponding author account and author identifiers are ready before upload |
If the paper is collaboration-authored, pay attention to metadata. JHEP's author guidance says collaboration papers should use the collaboration name in article metadata rather than inserting the entire author list there, and the full author-list layout has a specific March 2025 note when front matter exceeds two pages.
Article type and file choice
JHEP's author pages describe papers and technical reports as contribution types. Most authors targeting the journal are submitting a regular paper. The manuscript can be submitted from arXiv or through file upload, and TeX workflows dominate the field.
The file choice affects the review package:
Route | Use when | Watch for |
|---|---|---|
Submission from arXiv | The preprint is already posted and the TeX archive is clean | arXiv category, arXiv ID, JHEP keywords, and TeX master file still need to align |
Direct file upload | The authors are uploading the archive directly through SISSA | Compilation, master file naming, figure paths, and attachments become the risk points |
Technical report | The work is relevant technical information rather than a regular research paper | Editors may suggest conversion when a submitted work is not suitable as a regular paper |
The JHEP template is not a ranking signal and not a substitute for fit. Its value is practical: JHEP says using the style and template can reduce production turnaround for accepted papers.
Practical editorial timeline
JHEP publishes a workflow rather than a guaranteed decision clock. Treat this as planning guidance, not a promise: the source-backed hard point is that JHEP says referees should review within four weeks at most after the editor's request, while editor assignment and reviewer availability still create case-by-case variation.
Day 0: submission through SISSA
The author submits through the JHEP website, either by arXiv reference or file upload. The system assigns a preprint number used throughout the editorial procedure.
Days 1 to 7: file and keyword intake
The system processes the submission, checks the files, and uses the selected keywords to assign the preprint to an editor. Compilation problems, weak master-file naming, or mismatched keywords can slow the package before scientific review begins.
Weeks 1 to 3: editor fit and scope read
The editor examines the submitted preprint and decides whether it belongs in JHEP's high-energy physics scope and whether it should go to referees.
Weeks 3 to 8: referee review
JHEP's workflow page says referees should review papers in four weeks at most from the editor's request. In practice, reviewer availability and field specificity can still change the timeline.
Week 8 onward: decision, revision, or rerouting
The editor decides based on the reports. If the paper is sound but misrouted, the author may need to revise for another venue rather than keep pushing JHEP.
Stage | Practical timing | What to control |
|---|---|---|
Day 0 | SISSA submission | arXiv ID, files, keywords, metadata, and cover note are complete |
Days 1 to 7 | Intake and routing | TeX compiles, master file is named, keywords match the paper |
Weeks 1 to 3 | Editor assessment | Abstract and first result make the JHEP audience obvious |
Weeks 3 to 8 | Referee review | Claims, derivations, computations, and comparisons are reviewer-ready |
Week 8 onward | Decision or revision | The response plan addresses physics substance, not only formatting |
JHEP versus nearby physics venues
Question | JHEP | Physical Review D | JCAP | EPJC |
|---|---|---|---|---|
Best fit | Native high-energy physics papers, especially theory and phenomenology | Broader particles, fields, gravitation, and cosmology under APS | Cosmology and astroparticle physics | Broad HEP with European community strength |
Submission culture | SISSA system, arXiv-first, JHEP keyword routing | APS system and Physical Review routing | SISSA/IOP, cosmology and astroparticle keywords | Springer HEP venue |
Cost route | SCOAP3 sponsored, no direct author fee for supported articles | SCOAP3 coverage can apply to eligible HEP articles, but PRD is broader | SCOAP3 context for eligible articles; verify current route | SCOAP3 supported HEP publishing |
Main risk | Paper reads as adjacent physics rather than JHEP-native HEP | Paper is too formal or HEP-community-specific for the broader APS frame | Paper is general HEP rather than cosmology or astroparticle physics | Paper has a better natural home at JHEP or PRD |
The right answer is often not "highest impact factor." It is which editor and referee community will understand why the result matters with the least translation.
Common rejection triggers for JHEP submissions
The arXiv category and journal claim do not match. This specific failure pattern is avoidable: a paper posted as broad theory but submitted as JHEP phenomenology forces the editor to decide which reader community the authors actually want. Align the arXiv category, abstract, and keywords before submission.
The calculation is complete but the physics consequence is buried. HEP referees can follow technical derivations, but the paper still needs to say what the result changes: a bound, amplitude, cross section, model space, duality claim, observable, or field-theory interpretation.
The paper is really JCAP or PRD. Cosmology motivation does not automatically make a JHEP paper, and HEP methods do not automatically rule out PRD. If the central reader is a cosmologist, an APS field editor, or an astroparticle audience, route accordingly.
The TeX package creates friction. A paper can be scientifically ready and still slow down if the archive does not compile, the master file is unclear, or attachments are not prepared.
Submit If
- the manuscript's natural community is high-energy physics
- the arXiv ID, category, abstract, and JHEP keywords point to the same editor lane
- the first result, equation, figure, or table makes the physics consequence visible
- the TeX archive compiles cleanly and the master file is easy to identify
- the paper is a better fit for SISSA/JHEP than for PRD, JCAP, EPJC, PLB, or NPB
Think Twice If
- the abstract needs cosmology language to sound important but the calculation is general HEP
- the strongest equation is mathematically interesting but the physics consequence appears only in the discussion
- the selected keywords could route the paper to two different editor communities
- the arXiv category and the intended JHEP reader do not match
- the TeX archive has multiple possible master files, missing figures, or compilation warnings you have not checked
If the issue is venue choice, use the JHEP journal-fit scan. If the issue is whether the paper is polished enough for review, use the JHEP submission-readiness scan.
Pre-submission checklist for JHEP
- [ ] The arXiv ID is ready and the arXiv category supports the JHEP fit.
- [ ] The abstract fits on the first page and avoids formulae or references.
- [ ] The 2 to 4 JHEP keywords match the actual editor community.
- [ ] The TeX archive or arXiv source compiles cleanly.
- [ ] The master file name is clear when multiple
.texfiles exist. - [ ] Figures, large tables, and supplementary attachments are prepared.
- [ ] The cover note explains JHEP versus PRD, JCAP, EPJC, PLB, or NPB.
- [ ] The conclusion states the physics consequence, not only the technical result.
Frequently asked questions
JHEP publishes workflow guidance rather than a guaranteed decision clock. Its workflow page says referees should review papers in four weeks at most after the editor's request, but author-side planning should still allow for editor fit checks, reviewer availability, revision, and possible rerouting.
Prepare a clean TeX package, an obvious master file, figures and attachments, the arXiv ID, 2 to 4 JHEP keywords, and metadata that match the manuscript's field identity. JHEP encourages its style or JHEPPUB package because it can reduce production turnaround after acceptance.
Common rejection or delay triggers are weak JHEP scope fit, arXiv category and keyword mismatch, a buried physics consequence, a paper that really belongs at PRD or JCAP, and TeX files that do not compile cleanly.
For eligible high-energy physics articles, SCOAP3 says authors do not need to pay fees to publish in participating SCOAP3 journals. JHEP is listed by Springer as fully sponsored by SCOAP3, but authors should still follow the live JHEP and SCOAP3 instructions for the article category.
Yes. JHEP's author guidance says authors need to provide an arXiv article ID because JHEP articles are funded through SCOAP3 and need to be categorized accordingly if accepted.
Sources
- This page was created by checking the current JHEP author pages at SISSA, the Springer Journal of High Energy Physics journal and submission pages, SCOAP3 author guidance, and nearby Manusights physics-routing pages for sibling contradiction checks.
- JHEP author pages at SISSA
- JHEP submission workflow at SISSA
- JHEP home page at SISSA
- Springer Journal of High Energy Physics submission guidelines
- Springer Journal of High Energy Physics journal page
- SCOAP3 journals 2025 to 2027
- SCOAP3 FAQs
Before you upload
Choose the next useful decision step first.
Move from this article into the next decision-support step. The scan works best once the journal and submission plan are clearer.
Use the scan once the manuscript and target journal are concrete enough to evaluate.
Anthropic Privacy Partner. Your manuscript is never used to train any model.