Bioinformatics Impact Factor

Bioinformatics has been remarkably stable in the 5.4-6.0 range for years. The 2021 bump to 6.9 reflected COVID-era bioinformatics tool citations (sequence analysis, variant calling), but the journal quickly settled back to baseline. This stability makes sense. Tool papers accumulate citations steadily over years, creating a consistent citation floor.

The five-year JIF of 7.1 is notably higher than the two-year figure, reflecting the long citation tail of computational tools.

In our pre-submission review work on manuscripts targeting Bioinformatics, three submission patterns account for most of the desk rejections we see.

Application Notes submitted as original research articles, or original research that belongs in Application Notes. Bioinformatics has a specific format for software tool descriptions (the Application Note) and a specific format for methodological advances. The decision between them is consequential and often misread. A paper that describes a new tool, its implementation, and benchmarks against existing software is an Application Note. If it's submitted as a full research article with extensive biological interpretation sections, reviewers treat the extra content as filler that dilutes the core contribution. Conversely, a paper proposing a new algorithmic framework with theoretical analysis, proof-of-concept validation, and systematic evaluation of assumptions belongs in full research, submitting it as a 1,000-word Application Note undersells it and gets rejected for insufficient rigor.

No biological validation on real experimental data. A recurring pattern we see is methods papers benchmarked entirely on simulated data or a single public reference dataset from several years ago. Bioinformatics reviewers specifically check whether the method was tested on data it wasn't designed for, whether performance claims hold on real messy experimental data, and whether the benchmark datasets reflect current experimental reality. Simulated-only validation reads as avoiding the hard test. Papers that include one reference dataset alongside simulated data but skip real single-lab experimental data face revision requests for extended validation, and those revisions can be extensive enough to effectively reopen the submission.

Software without accessible, usable code. The journal has explicit requirements for code availability, and "code available on request" is no longer accepted. We see manuscripts where the methodology is strong but the code is either private, inadequately documented, or exists as a proof-of-concept script rather than an installable tool. Application Notes especially require a working implementation with documentation sufficient for a computational biologist to run the tool on their own data. A manuscript that reaches review with a broken GitHub link, a repository with no README, or an environment that requires email contact to reproduce will fail review on those grounds alone regardless of the algorithmic quality.

Before submitting, a Bioinformatics format and code readiness check can identify whether your methodology section, benchmarking approach, and code availability meet Bioinformatics' specific requirements.

The journal has a specific editorial mission: methods and software for biological data analysis. That sounds broad, but the boundaries are clear.

What gets published:

• New algorithms for sequence alignment, variant calling, gene expression analysis, protein structure prediction, phylogenetic inference
• Software tools that solve a practical problem in biological data analysis
• Application Notes (2 pages, describing a specific tool or update with benchmarking)
• Machine learning methods applied to biological problems (not just ML on biological data as a testbed)
• Statistical methods for omics data analysis (differential expression, network inference, spatial transcriptomics)

What gets desk-rejected:

• Biological discoveries without a methods contribution. If the paper's main finding is "Gene X causes Disease Y" and you used standard tools to find it, this isn't a Bioinformatics paper.
• Machine learning papers that treat biological data as just another dataset. Editors look for biological insight, not just accuracy improvements on a benchmark.
• Database papers. These belong in NAR or specific domain databases.
• Papers describing minor updates to existing tools without substantial new functionality or performance improvement.
• Pipeline papers. Stringing together existing tools into a workflow is not enough unless the integration itself represents a methodological advance.

A specific pattern worth knowing: Bioinformatics reviewers will benchmark yManusights against existing alternatives. If you don't do this comparison yourself (thoroughly and fairly), reviewers will, and they'll be less charitable about it. Include comparisons against the state-of-the-art on standard benchmark datasets. Acknowledge where your method doesn't win. Reviewers respect honest benchmarking more than cherry-picked comparisons.

Application Notes are Bioinformatics' secret weapon. These are short papers (2 printed pages, roughly 1,000-1,300 words) that describe a specific software tool, including a brief description, benchmarking, and a link to the code.

Why Application Notes matter:

• They're faster to write, faster to review, and faster to publish
• They can accumulate massive citation counts (some of the most-cited papers in all of science are Bioinformatics Application Notes)
• They're accepted at a higher rate than full research articles
• They provide a citable reference for software that researchers would use regardless

If you've built a tool that people are already using informally, an Application Note is the fastest path to a citable publication in a Q1 journal. The key requirement: the code must be publicly available and documented.

Bioinformatics accepts approximately 20-25% of original research submissions. Application Notes have a higher acceptance rate, though exact figures aren't published.

Review process:

• Editorial triage: 1-2 weeks
• External review: 4-8 weeks (2-3 reviewers)
• First decision: 6-10 weeks total
• Reviewers have both computational and domain expertise
• One round of revision is typical

Bioinformatics reviewers are generally constructive but technically demanding. They will try to reproduce your results, run yManusights on their own data, and check your benchmarking methodology. Make sure your code works, your documentation is adequate, and your benchmarks are reproducible.

Bioinformatics charges $3,618 for open access publication. Authors can also publish under the subscription model with no APC (the paper will be behind a paywall for 12 months, then becomes free).

Oxford University Press has Read and Publish agreements with many institutions. If your university has an agreement, the APC may be covered. Check with your library before defaulting to the subscription option.

Submit if:

• You've developed a new algorithm or software tool for biological data analysis
• Your method outperforms existing approaches on standard benchmarks
• Your code is publicly available and documented
• You have a short, focused tool to describe (consider an Application Note)

Think twice if:

• Your paper is primarily a biological discovery (try PNAS or field-specific journals)
• You built a database (try NAR)
• Your method is a minor increment over existing tools (try PLOS Computational Biology or BMC Bioinformatics)
• Your paper combines methods with substantial biological findings (try Genome Biology)

Bioinformatics at 5.4 is deceptively positioned. The impact factor suggests a mid-tier journal. The h-index of 564 and 2.7 million citations tell a completely different story. For computational biologists and bioinformaticians, it's one of the most important journals in the field, the default venue for tool papers that the entire community will cite.

The Application Note format is particularly valuable. Few other journals offer a path to thousands of citations from a 2-page paper. If you build tools that biologists use, Bioinformatics is where you make them citable.

The impact factor for Bioinformatics measures average citations per paper over 2 years. It does not measure the quality of any individual paper, the prestige within a specific subfield, or whether the journal is the right fit for your work. A high IF does not guarantee your paper will be cited, and a lower IF does not mean the journal lacks influence in its specialty.

Impact factors also do not account for field-specific citation patterns. Journals in clinical medicine accumulate citations faster than journals in mathematics or ecology. Comparing IFs across fields is misleading.

Before choosing this journal based on IF alone, a Bioinformatics scope check can assess whether your manuscript fits the journal's actual editorial scope and suggest ranked alternatives.