Statute of Limitations for Murder / First-Degree Murder in Ohio
5 min read
Published March 22, 2026 • By DocketMath Team
Overview
In Ohio, the “statute of limitations” (often shortened to “SOL”) sets a deadline for when the state can file a criminal charge. For most serious offenses, Ohio’s approach is straightforward: first-degree murder has no limitation period in many circumstances, meaning the prosecution is not time-barred the way it is for less serious crimes.
That said, Ohio’s limitations rules are codified and include specific mechanics and exceptions in Ohio Rev. Code § 2901.13. DocketMath’s statute-of-limitations calculator can help you translate those rules into a deadline (or confirm whether none applies) by turning the legal rule into an output you can work with.
Note: Even when a limitations period is “not time-barred,” timing can still matter for other reasons (for example, evidence availability and procedural deadlines). This page explains the SOL framework, not the full case timeline.
Limitation period
For murder / first-degree murder in Ohio, the limitations rule you’ll see reflected in DocketMath is:
- SOL Period: 0.5 years
- Source rule set: Ohio Rev. Code § 2901.13 — exception V3
In other words, within the § 2901.13 framework, DocketMath’s calculation for this offense category reflects a 0.5-year window tied to the relevant exception pathway.
How to think about “0.5 years” in practice
A “half-year” deadline can be easy to misunderstand if you’re expecting a number of days. For calculator use, treat it as a time window measured from the starting date selected in the tool. The most common starting points in limitations calculations are tied to the event date or a charging-trigger date—DocketMath guides you through the correct inputs for the scenario you’re evaluating.
Here are common workflow checkpoints:
- Choose the offense category that matches your case research.
- Select the starting date the tool expects (the “clock” start).
- Apply the SOL length (here, 0.5 years) with the applicable exception logic.
What changes the output?
Your SOL output changes based on at least two categories of inputs:
- Which § 2901.13 exception applies
- Which date you use as the clock start
To get the most accurate result, ensure your offense selection matches the category that triggers the same limitation rule as § 2901.13’s exception you’re modeling.
Pitfall: Using the wrong “clock start” date is the most common reason calculators produce a deadline that doesn’t match the legal theory you intended to test.
Key exceptions
Ohio Rev. Code § 2901.13 doesn’t just state a single universal deadline; it builds a limitations framework with exceptions. For the murder / first-degree murder rule modeled here, the relevant exception is listed as:
- Exception V3 within Ohio Rev. Code § 2901.13
Why exceptions matter
Exceptions can do two practical things:
- Shorten the limitations window (as reflected by the 0.5-year result in this rule set).
- Shift the applicability of the limitations rule depending on circumstances tied to the prosecution’s timing.
Because exceptions are embedded in statutory text, they often determine whether the SOL clock:
- applies at all,
- applies differently,
- or uses a different computation approach than a default rule.
Checklist for exception alignment
Before you rely on a calculated deadline from DocketMath, check:
Statute citation
The governing authority for Ohio’s criminal limitations framework in this context is:
- Ohio Rev. Code § 2901.13
- SOL Period (as modeled here): 0.5 years
- Exception: V3
Source (statutory text):
https://codes.ohio.gov/assets/laws/revised-code/authenticated/29/2901/2901.13/7-16-2015/2901.13-7-16-2015.pdf
Use the calculator
Use DocketMath’s statute-of-limitations tool to compute a SOL deadline (or confirm whether a deadline applies through the modeled exception logic): statute-of-limitations.
Inputs you should expect to use
While exact fields can differ depending on how the tool is configured for your scenario, your typical inputs are:
- Jurisdiction: Ohio (US-OH)
- Offense category: murder / first-degree murder (modeled to the applicable § 2901.13 exception pathway)
- Clock start date: the date the “limitations clock” begins under the rule you’re applying
Output you should expect
Given the rule set used for this page:
- The tool applies Ohio Rev. Code § 2901.13
- The calculation yields an SOL window of 0.5 years (exception V3)
As a practical matter, the calculator output will give you a computed deadline based on your selected start date. If you change the starting date by weeks or months, the computed deadline will shift accordingly.
Quick “change the input, see the effect” example
Use the same offense and jurisdiction, then change only the clock start date:
- If the clock start date moves later, the SOL deadline moves later.
- If the clock start date moves earlier, the SOL deadline moves earlier.
- If you switch exception logic (for example, to a different exception pathway than V3), the limitation period length or applicability may change, which can materially change the deadline.
Warning: This page summarizes the SOL rule set used for the calculator output. Criminal procedure involves additional doctrines and jurisdiction-specific practice—use the tool for SOL timing, not for a complete case strategy.
Related reading
- Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
- Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
- Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator
