Flex assays use probes that target protein-coding genes in the human, mouse, or rat transcriptome. Each probe consists of a pair of oligonucleotides that hybridize to the targeted transcript and are subsequently ligated.
Gene IDs and probe sequences are defined in the probe set reference CSV input file for cellranger multi. Three supporting files are provided per version: a BED file listing the reference genome coordinates for each probe, a CSV file listing probes with predicted off-target activity that are excluded from analysis by default, and a metadata TSV file that contains gene name and description for each of the probes. These files are described in detail on the Probe Sets Description page.
Frequently asked questions
1. Which probe set file version should I use for NextGEM or GEM-X Flex data?
- For NextGEM Flex v1, use the v1.1 probe sets.
- For GEM-X Flex v1, use the v1.1 probe sets.
- For GEM-X Flex v2, use the v2.0 probe sets.
2. Can the rat probe set be used with the Flex v2 Singleplex workflow?
No. Unlike the human and mouse probe sets, the rat probe set is only compatible with the Flex v2 Multiplex workflow and cannot be used with the Singleplex workflow. More details on library construction here.
3. What genes are excluded from the human, mouse, and rat probe sets?
The excluded genes are:
- TCR joining and majority of variable regions*
- IG joining and variable regions
- Ribosomal proteins
- Mitochondrial ribosomal proteins
- Read-through genes
- KIR and HLA genes (due to their inherent allelic diversity)
- Non-coding RNA
* Refer this Knowledge Base Article for details about variable region genes included in the rat probe set.
4. Which genes have 1-fold coverage versus 3-fold coverage in the probe set?
Most genes have 3-fold coverage. The genes with 1-fold coverage include highly expressed genes and mitochondrial protein coding genes. This design dampens the reads on highest expression genes. A very small fraction of genes with specificity issues during probe design have 1- to 2-fold coverage.
- Human probe set: ~7.5% genes have 1-fold coverage. ~5% of genes have more than three probes to cover all possible isoforms.
- Mouse probe set: ~6.6% genes have 1-fold coverage. ~1.7% of genes have more than three probes to cover all possible isoforms.
- Rat probe set: ~8.1% of genes have 1-fold coverage. ~1.0% of genes have more than three probes to cover all possible isoforms.
The information on the coverage for genes can be found in the probe set metadata TSV file. Learn more about fold coverage in this Knowledge Base article.
5. Are these probes expected to work equally well on pre-spliced mRNA from nuclei?
Most of the probes do not overlap splice junctions, so they should work well with pre-spliced mRNA from nuclei.
- Human probe set: ~14% of 54k probes span a splice junction by at least 10 bp and would be less likely to detect pre-mRNA.
- Mouse probe set: ~16% of 55k probes span a splice junction by at least 10 bp and would be less likely to detect pre-mRNA.
- Rat probe set: ~13% of 62k probes span a splice junction by at least 10 bp and would be less likely to detect pre-mRNA.
Users can find out whether a probe spans a splice junction by looking at the probe set BED file. If the value in the 10th column (blockCount) is more than 1, it means the probe spans a splice junction.
The region column of the probe set reference CSV file also indicates whether a probe spans a splice junction by at least 10 bp (spliced) or not (unspliced). Note that most genes have multiple probes (3-fold coverage, see question 4), and not all probes for one gene will cover the splice junction.
6. Can I use any probe set with any transcriptome reference?
No, not all probe sets are compatible with every transcriptome reference. Compatibility depends on the version of Cell Ranger you are using. Please refer to the table below for specific probe set and transcriptome reference compatibility.
Cell Ranger versions are backward compatible with earlier probe set file formats.
| Cell Ranger Version | Probe Sets | Transcriptome Reference |
|---|---|---|
| v10.0, v10.1 | • v1.1 (human) • v1.1.1 (mouse) • v2.0 (human, mouse, rat) | • GRCh38-2024-A • GRCm39-2024-A • mRatBN7.2-2024-A Optional for this Cell Ranger version. |
| v9.0 | • v1.1 (human) • v1.1.1 (mouse) | • GRCh38-2024-A • GRCm39-2024-A Optional for this Cell Ranger version. |
| v9.0 | • v1.0 • v1.0.1 | • GRCh38-2020-A • mm10-2020-A Optional for this Cell Ranger version. |
| v8.0 | • v1.0 • v1.0.1 | • GRCh38-2020-A • mm10-2020-A |
| v7.2 | • v1.0 • v1.0.1 | • GRCh38-2020-A • mm10-2020-A |
| v7.1 | • v1.0 • v1.0.1 | • GRCh38-2020-A • mm10-2020-A |
| v7.0 | • v1.0 | • GRCh38-2020-A • mm10-2020-A |
7. What changed in probe set v2.0 compared to v1.1?
- There is no change in the probe set file format between v1.1 and v2.0.
- For human probes, v2.0 and v1.1 use the same reference (GRCh38-2024-A). Some probes deprecated in v1.1 are re-included in v2.0 (<1% of probes), while others are removed from the v2.0 CSV. (v1.0 used GRCh38-2020-A.)
- For mouse probes, v2.0 and v1.1 use the same reference (GRCm39-2024-A). All probes deprecated in v1.1 are re-included in v2.0 (<1% of probes). (v1.0 used mm10-2020-A.)
- For rat probes, v2.0 is the first version, built on mRatBN7.2-2024-A.
8. What changed in probe set v1.1 compared to v1.0.1?
The main change is the file format: probe set v1.0.1 uses file format v2.0, while probe set v1.1 uses file format v3.0 which adds a gene_name field to the probe set reference CSV. As a result, probe set v1.1 requires Cell Ranger v9.0 or later; earlier Cell Ranger versions will fail.
9. What is the difference between the probe set version and the probe set file format version?
These are two independent version numbers, and they should not be confused:
- The probe set version (for example, v1.0, v1.1, or v2.0) identifies the content of the probe set — the probes, the genes they target, and the reference build used to design them. This is the version referenced throughout this page and the one you use to select the correct probe set for your assay.
- The probe_set_file_format version is a separate value found in the header of the probe set reference CSV (the
#probe_set_file_format=line). It specifies only which version of the CSV file format specification the file conforms to, not the biological content of the probe set.
The two numbers are unrelated and do not track each other. When selecting or citing a probe set, always use the probe set version, not the file format version.
For more details, see the Probe Set Reference CSV and Supporting Files page.
10. Would the human probe sequences work on non-human primate samples?
The human probe sets are designed based on the GENCODE basic transcript annotations for human and validated with human samples. We have not tested the human probe set with samples from other species (including primates), and the performance of the human probe set cannot be guaranteed for other species.
11. Can the mouse probe set be used on rat samples?
No. For optimal performance and accurate results, the officially supported rat probe set must be used on rat samples. Sequence divergence between the two genomes substantially reduces probe hybridization efficiency. Using a mouse probe set on rat tissue results in reduced per-cell sensitivity compared to the species-matched rat probe set.
- For new projects: We strongly recommend using Flex v2/Apex with the rat probe set to ensure maximum sensitivity and data integrity.
- For ongoing projects: For data comparisons within a single study, do not mix probe sets. Data generated using mouse probe sets cannot be directly compared to data generated with the rat probe set due to these differences in sensitivity.
12. Can custom probes be used with Flex assays?
Refer to the Custom Probe Design for Visium Spatial Gene Expression and Chromium Single Cell Gene Expression Flex Technical Note for general guidance on designing and ordering custom probes.
These Knowledge Base articles provide additional help for designing custom probes.