<p>It’s a matter of preference I guess but I recommend the <a href="http://grch37.ensembl.org/index.html" rel="noreferrer"><strong>Ensembl</strong> builds</a>. Decide whether you want the toplevel or primary assembly, and whether you want soft-masked, repeat-masked or unmasked files. The naming schema is very straightforward; the combinations are described in the <a href="ftp://ftp.ensembl.org/pub/release-75/fasta/homo_sapiens/dna/README" rel="noreferrer"><code>README</code> file</a>, and all files <a href="ftp://ftp.ensembl.org/pub/release-75/fasta/homo_sapiens/dna/" rel="noreferrer">reside in one directory</a>.</p>

<p>For example, if you want the unmasked primary assembly, the file to download would be <a href="ftp://ftp.ensembl.org/pub/release-75/fasta/homo_sapiens/dna/Homo_sapiens.GRCh37.75.dna.primary_assembly.fa.gz" rel="noreferrer"><code>Homo_sapiens.GRCh37.75.dna.primary_assembly.fa.gz</code></a>.</p>

<p>As for <strong>GoldenPath/UCSC</strong>, there’s no need to download and concatenate separate chromosomes (contrary to what the other answer said); you can download the whole (toplevel) reference <a href="http://hgdownload.soe.ucsc.edu/goldenPath/hg19/bigZips/" rel="noreferrer">from the <code>bigZips</code> directory</a>; from the <code>README</code>:</p>

<blockquote>
  <p>This directory contains the Feb. 2009 assembly of the human genome (hg19,
  GRCh37 Genome Reference Consortium Human Reference 37 (GCA_000001405.1)),
  as well as repeat annotations and GenBank sequences.</p>
</blockquote>

<p>There are essentially three options here:</p>

<ol>
<li><code>chromFa.tar.gz</code>, which contains the whole genome in one chromosome per file;</li>
<li><code>chromFaMasked.tar.gz</code>, the same with repeats masked by <code>N</code>;</li>
<li><code>hg19.2bit</code>, which is the whole genome in one file, but needs to be extracted using the utility program <code>twoBitToFa</code>, which needs to be downloaded <a href="http://hgdownload.cse.ucsc.edu/admin/exe" rel="noreferrer">separately</a>.</li>
</ol>

<p>In any case, I always download the reference and build my own index for mapping, since this allows me more control; not everybody might need this much control, but then building the index once is fairly fast anyway.</p>

CC BY-SA 3.0
2017-06-01T19:53:44.980Z
I think this triggers another question "what's the difference between different versions of the same genome build?". The question's answer should include the difference between DNA and RNA-seq/functional genomics analysis.

In the DNA/variant world, people will generally stick to whatever the large sequencing projects/Heng Li decides is "best". In the RNA-seq/functional genomics world, careful curation of genomes is important, depending on the read mapper and also what downstream tools support (larger set of tools means longer tail of less used tools having idiosyncratic requirements).
Manuel
CC BY-SA 3.0
2017-06-01T09:38:53.087Z
2017-06-01T09:49:08.560Z
2017-06-01T09:49:08.560Z
Konrad Rudolph
<p>tl;dr: Just use the either the downloads on the <a href="http://bowtie-bio.sourceforge.net/bowtie2/index.shtml" rel="noreferrer">Bowtie2 homepage</a> or the <a href="https://support.illumina.com/sequencing/sequencing_software/igenome.html" rel="noreferrer">Illumina iGenomes</a>. Or just uncompress and concatenate the <a href="http://hgdownload.soe.ucsc.edu/goldenPath/hg19/chromosomes/" rel="noreferrer">FASTA files found on UCSC goldenpath</a> and then build the index.</p>

<p>A bit longer answer:</p>

<p>There are two components to "genome for a read mapper" such as Bowtie or BWA.</p>

<p>First, you need to choose the actual sequence (genome release such as GRCh37/hg19 or GRCh38/hg38). There are patch releases such as GRCh37.p3 where some bases might be exchanged and depending on the release, some "unmapped" loci contigs might be added, but generally GRCh37.p1 is roughly the same as GRCh37.p2, for example. Usually, people have agreed on some specific patch version for each read and use this for read mapping.</p>

<p>Generally, there is the UCSC flavour hg19/hg38 etc. and the NCBI/GRC flavour GRCh37, GRCh38 etc. (similar with mouse). UCSC has no versioning besides the genome release and (to the best of my knowledge) does not update the genome sequence after releasing a hg19 FASTA file.</p>

<p>Second, you have to build the index files for each genome. Depending on the read mapper you use, you might or might not need the original FASTA files for the alignment. For Bowtie and Bowtie 2, you don't need the original FASTA files after building the index as Bowtie 1/2 can reconstruct the sequence "on the fly" from the index files.</p>

<p>HTH</p>

CC BY-SA 3.0
2017-06-01T19:23:18.770Z
I don't know how I managed to miss the download on the bowtie homepage. Hope this helps someone else!
EMiller
CC BY-SA 3.0
2017-05-31T23:21:53.943Z
2017-05-31T23:21:53.943Z
Manuel
<p>How do I download a reference genome that I can use with bowtie2? Specifically HG19. On UCSC there are a lot of file options.</p>

<human-genome><reference-genome><genome-sequencing>
Downloading a reference Genome for Bowtie2
# Downloading a reference Genome for Bowtie2

(Asked by: username_0 on 2017-05-31)

How do I download a reference genome that I can use with bowtie2? Specifically HG19. On UCSC there are a lot of file options.

**Tags:** human-genome, reference-genome, genome-sequencing

---

## 2 answers

### Answer by username_2 on 2017-05-31. Score: 9 | Accepted answer

tl;dr: Just use the either the downloads on the [Bowtie2 homepage](http://bowtie-bio.sourceforge.net/bowtie2/index.shtml) or the [Illumina iGenomes](https://support.illumina.com/sequencing/sequencing_software/igenome.html). Or just uncompress and concatenate the [FASTA files found on UCSC goldenpath](http://hgdownload.soe.ucsc.edu/goldenPath/hg19/chromosomes/) and then build the index.

A bit longer answer:

There are two components to "genome for a read mapper" such as Bowtie or BWA.

First, you need to choose the actual sequence (genome release such as GRCh37/hg19 or GRCh38/hg38). There are patch releases such as GRCh37.p3 where some bases might be exchanged and depending on the release, some "unmapped" loci contigs might be added, but generally GRCh37.p1 is roughly the same as GRCh37.p2, for example. Usually, people have agreed on some specific patch version for each read and use this for read mapping.

Generally, there is the UCSC flavour hg19/hg38 etc. and the NCBI/GRC flavour GRCh37, GRCh38 etc. (similar with mouse). UCSC has no versioning besides the genome release and (to the best of my knowledge) does not update the genome sequence after releasing a hg19 FASTA file.

Second, you have to build the index files for each genome. Depending on the read mapper you use, you might or might not need the original FASTA files for the alignment. For Bowtie and Bowtie 2, you don't need the original FASTA files after building the index as Bowtie 1/2 can reconstruct the sequence "on the fly" from the index files.

HTH

> **Comments:**
> **username_0**: I don't know how I managed to miss the download on the bowtie homepage. Hope this helps someone else!  

---

### Answer by username_1 on 2017-06-01. Score: 11

It’s a matter of preference I guess but I recommend the [**Ensembl** builds](http://grch37.ensembl.org/index.html). Decide whether you want the toplevel or primary assembly, and whether you want soft-masked, repeat-masked or unmasked files. The naming schema is very straightforward; the combinations are described in the [`README` file](ftp://ftp.ensembl.org/pub/release-75/fasta/homo_sapiens/dna/README), and all files [reside in one directory](ftp://ftp.ensembl.org/pub/release-75/fasta/homo_sapiens/dna/).

For example, if you want the unmasked primary assembly, the file to download would be [`Homo_sapiens.GRCh37.75.dna.primary_assembly.fa.gz`](ftp://ftp.ensembl.org/pub/release-75/fasta/homo_sapiens/dna/Homo_sapiens.GRCh37.75.dna.primary_assembly.fa.gz).

As for **GoldenPath/UCSC**, there’s no need to download and concatenate separate chromosomes (contrary to what the other answer said); you can download the whole (toplevel) reference [from the `bigZips` directory](http://hgdownload.soe.ucsc.edu/goldenPath/hg19/bigZips/); from the `README`:

> This directory contains the Feb. 2009 assembly of the human genome (hg19,
> GRCh37 Genome Reference Consortium Human Reference 37 (GCA\_000001405.1)),
> as well as repeat annotations and GenBank sequences.

There are essentially three options here:

1. `chromFa.tar.gz`, which contains the whole genome in one chromosome per file;
2. `chromFaMasked.tar.gz`, the same with repeats masked by `N`;
3. `hg19.2bit`, which is the whole genome in one file, but needs to be extracted using the utility program `twoBitToFa`, which needs to be downloaded [separately](http://hgdownload.cse.ucsc.edu/admin/exe).

In any case, I always download the reference and build my own index for mapping, since this allows me more control; not everybody might need this much control, but then building the index once is fairly fast anyway.

> **Comments:**
> **username_2**: I think this triggers another question "what's the difference between different versions of the same genome build?". The question's answer should include the difference between DNA and RNA-seq/functional genomics analysis.  In the DNA/variant world, people will generally stick to whatever the large sequencing projects/Heng Li decides is "best". In the RNA-seq/functional genomics world, careful curation of genomes is important, depending on the read mapper and also what downstream tools support (larger set of tools means longer tail of less used tools having idiosyncratic requirements).  

---

