DEXSeq is a statistical software package designed for differential exon usage (DEU) analysis, a method that detects shifts in the relative inclusion or exclusion of specific exons between experimental conditions. Unlike standard differential gene expression tools that aggregate all isoforms into a single gene-level count, DEXSeq models counts for disjoint exonic parts, allowing it to identify alternative splicing events and transcriptional regulation that would otherwise be masked.
Glossary
DEXSeq

What is DEXSeq?
DEXSeq is an R/Bioconductor package that tests for condition-dependent changes in the relative usage of individual exonic regions using a generalized linear model framework.
The package fits a generalized linear model (GLM) with a negative binomial distribution to account for overdispersion in RNA-seq count data. It tests for an interaction between condition and exon, asking whether the change in expression for a specific exon differs significantly from the gene's overall expression change. This approach provides robust statistical inference for identifying condition-specific isoform switching.
Key Features of DEXSeq
DEXSeq is an R/Bioconductor package that tests for condition-dependent changes in the relative usage of exonic regions using a generalized linear model framework.
Exon-Centric Counting
Unlike gene-level tools, DEXSeq partitions genes into non-overlapping exonic counting bins. Each bin corresponds to a unique exonic region, allowing the model to detect differential exon usage (DEU) independently of overall gene expression changes. This granularity captures isoform switching that gene-level analysis masks.
Generalized Linear Model Framework
DEXSeq employs a negative binomial GLM with an interaction term between exon and condition. This design simultaneously models:
- Condition effect: Overall expression change
- Exon effect: Baseline exon inclusion levels
- Interaction term: The parameter of interest, testing whether the condition effect differs per exon This structure controls for gene-level expression changes, isolating true differential exon usage.
Dispersion Estimation and Shrinkage
The package estimates exon-specific dispersions using Cox-Reid profile-adjusted likelihood, then applies empirical Bayes shrinkage to stabilize estimates. A mean-dispersion trend is fit across all counting bins, and individual estimates are shrunk toward this trend. This borrowing of information across exons prevents inflated false positives from highly variable, low-count bins.
Visualization of Differential Exon Usage
DEXSeq provides built-in plotting functions to visualize results:
- Transcript annotation plots: Display known isoforms alongside the gene model
- Expression plots: Show normalized counts per exon across conditions
- Fitted expression plots: Overlay the GLM fitted values with confidence intervals
- MA plots: Visualize the relationship between mean count and fold change per exon These diagnostics help researchers validate computational findings against known transcript structures.
Integration with Bioconductor Ecosystem
DEXSeq operates within the Bioconductor framework, accepting input from standard alignment and quantification pipelines:
- HTSeq-count output in exon-level mode
- featureCounts with exon-level annotation
- Rsubread alignments Results are stored as DEXSeqResults objects, compatible with downstream tools like GenomicRanges for annotation overlap and rtracklayer for exporting to genome browsers.
Multiple Testing Correction for Exons
DEXSeq applies the Benjamini-Hochberg procedure to control the false discovery rate across all tested exonic regions. The package also implements independent filtering to remove exons with very low counts before p-value adjustment, increasing detection power. Per-gene adjusted p-values are reported to identify genes with at least one differentially used exon, while per-exon adjusted p-values pinpoint the specific regions.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Clear, technical answers to the most common questions about DEXSeq, the R/Bioconductor package for detecting differential exon usage from RNA-seq data.
DEXSeq is an R/Bioconductor package designed for differential exon usage (DEU) analysis, which tests for condition-dependent changes in the relative expression of individual exonic regions within a gene. Unlike standard differential gene expression tools that aggregate all reads mapping to a gene, DEXSeq partitions reads into non-overlapping exonic counting bins and fits a generalized linear model (GLM) with an interaction term between condition and exon to determine if the ratio of exon-level counts relative to overall gene expression differs between experimental groups. The model uses a negative binomial distribution to account for overdispersion in count data and applies empirical Bayes shrinkage to stabilize dispersion estimates, particularly for exons with low counts. This approach allows researchers to identify alternative splicing events, isoform switches, and other post-transcriptional regulatory mechanisms that differential gene expression analysis alone would miss.
Related Terms
Core concepts and complementary tools in the differential transcript usage analysis workflow.
Differential Transcript Usage (DTU)
The biological phenomenon that DEXSeq is designed to detect. DTU refers to condition-dependent shifts in the relative abundance of alternative mRNA isoforms from the same gene. Unlike differential gene expression, which measures total transcriptional output, DTU captures regulatory mechanisms like alternative splicing, alternative promoter usage, and alternative polyadenylation that change isoform proportions without altering overall gene-level counts.
DEXSeq Workflow: Count Binning
DEXSeq partitions each gene into non-overlapping exonic counting bins rather than full transcripts. This design avoids the statistical challenges of isoform-level quantification uncertainty. Key steps:
- Flatten gene models into disjoint exonic regions
- Count reads overlapping each bin per sample
- Fit a generalized linear model (GLM) testing for condition-bin interaction terms
- A significant interaction indicates differential exon usage between conditions
DEXSeq vs. DEXSeq-VM
The original DEXSeq uses a negative binomial GLM with per-exon dispersion estimation, similar to DESeq2. DEXSeq-VM is a faster variant that employs a variational Bayes approach to approximate posterior distributions, dramatically reducing computation time for large experiments. Both test the same null hypothesis: that the relative usage of an exonic region does not change between conditions.
Alternative Splicing Detection Tools
DEXSeq belongs to a family of count-based DTU tools. Complementary approaches include:
- rMATS: Uses junction reads and a hierarchical framework to detect five splicing event types
- SUPPA2: Leverages transcript-level quantifications (e.g., Salmon, kallisto) to compute percent-spliced-in (PSI) values
- LeafCutter: Focuses exclusively on intron excision ratios from junction reads, enabling cluster-level splicing analysis
- MAJIQ: Builds local splice graphs to detect complex, unannotated splicing variations
Visualization: DEXSeq Results
The plotDEXSeq() function generates gene-level visualization showing:
- Normalized counts per exonic bin for each condition
- Fitted expression estimates from the GLM
- Flattened gene model with annotated transcripts below
- Significance annotations marking bins with significant differential usage This plot is essential for confirming that detected DTU events correspond to interpretable isoform switches rather than technical artifacts.
Downstream Functional Analysis
After identifying genes with significant differential exon usage, common follow-up analyses include:
- Domain annotation: Determine if differentially used exons encode functional protein domains (e.g., kinase domains, transmembrane regions)
- Nonsense-mediated decay (NMD) prediction: Assess whether exon skipping introduces premature stop codons
- Motif enrichment: Search for RNA-binding protein motifs near regulated exons to infer splicing regulators
- Integration with eQTL data: Overlap DTU events with genetic variants to identify splicing quantitative trait loci (sQTLs)

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us