Citing research software in your paper is essential for reproducibility and giving credit to developers, and the best approach depends on the journal's guidelines, the software's licensing, and whether a formal citation is provided by the developers. Start by checking the software's documentation, repository (e.g., GitHub, Zenodo), or official website for a preferred citation—many developers explicitly request a specific paper, DOI, or version string. If no citation is provided, follow the journal's style (APA, MLA, Chicago, etc.) and treat the software like a digital object: include the author/developer name, the software title, the version number, the year of release, and the publisher or URL. For example, in APA 7: Author/Developer. (Year). Software Name (Version x.x) [Computer software]. Publisher or URL.
Key steps to get it right:
- Check for a software citation file or DOI: Many tools now include a
CITATION.cfffile or a DOI via Zenodo—use these if present, as they are the most accurate and preferred by the developers. - Cite the version you actually used: Software evolves quickly; an old version may not reproduce your results. Always note the version number in the citation and, if possible, in your methods section.
- Follow the journal's software citation policy: Some venues (e.g., Nature, JOSS) have specific requirements, such as citing the software paper and the code repository separately. If the journal is silent, err on the side of including both the software and the underlying algorithm paper.
- Mention it in the methods, not just the references: Briefly state the software name, version, and any key parameters in your methodology so readers can replicate your workflow without hunting through your reference list.
- For non-standard or in-house software: If you wrote the code yourself, cite it as a personal communication or provide a repository link, and consider archiving it on a platform like Zenodo to get a permanent DOI.
If you're juggling many citations for tools and papers while writing, WisPaper's TrueCite can automatically verify sources and correctly format every software reference you add in your target style, catching missing versions or broken DOIs before submission. This saves you from the common pitfall of citing a software paper that doesn't exist or pointing to an outdated release.
Finally, remember that citing software isn't just a formality—it's a scientific record. A thorough citation helps peers trust your results, compare methods, and build on your work, which is why top-tier journals increasingly enforce strict software citation standards. When in doubt, include more detail rather than less, and always double-check the citation against the developer's latest instructions.
