Legislative intelligence / 90R
SESSION 2027View project ↗

Code of Criminal Procedure Art. 35.15: NUMBER OF CHALLENGES

1 bill in the 90th Legislature would change this section

Part of Code of Criminal Procedure Chapter 35, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Art. 35.15. NUMBER OF CHALLENGES. (a) In capital cases in which the State seeks the death penalty both the State and defendant shall be entitled to fifteen peremptory challenges. Where two or more defendants are tried together, the State shall be entitled to eight peremptory challenges for each defendant; and each defendant shall be entitled to eight peremptory challenges.

(b) In non-capital felony cases and in capital cases in which the State does not seek the death penalty, the State and defendant shall each be entitled to ten peremptory challenges. If two or more defendants are tried together each defendant shall be entitled to six peremptory challenges and the State to six for each defendant.

(c) The State and the defendant shall each be entitled to five peremptory challenges in a misdemeanor tried in the district court and to three in the county court, or county court at law. If two or more defendants are tried together, each defendant shall be entitled to three such challenges and the State to three for each defendant in either court.

(d) The State and the defendant shall each be entitled to one peremptory challenge in addition to those otherwise allowed by law if one or two alternate jurors are to be impaneled and two peremptory challenges if three or four alternate jurors are to be impaneled. The additional peremptory challenges provided by this subsection may be used against an alternate juror only, and the other peremptory challenges allowed by law may not be used against an alternate juror.

Acts 1965, 59th Leg., p. 317, ch. 722, Sec. 1, eff. Jan. 1, 1966. Amended by Acts 1973, 63rd Leg., p. 1127, ch. 426, art. 3, Sec. 4, eff. June 14, 1973; Acts 1983, 68th Leg., p. 4594, ch. 775, Sec. 3, eff. Aug. 29, 1983.

Subsecs. (a), (b) amended by Acts 1991, 72nd Leg., ch. 652, Sec. 5, eff. Sept. 1, 1991.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.