Track Data Hubs

Track data hubs are collections of external tracks that can be added to the UCSC Genome Browser. Click Connect to attach a hub and redirect to the assembly gateway page. Hub tracks will then show up in the hub's own blue bar track group under the browser graphic. For more information, including where to host your track hub, see our User's Guide.

Track Hubs are created and maintained by external sources. UCSC is not responsible for their content.

The list below can be filtered on words in the hub description pages or by assemblies.
Search terms: Assembly:
Displayed list restricted by above search terms 

When exploring the detailed search results for a hub, you may right-click on an assembly or track line to open it in a new window.

Display Hub Name Description AssembliesClick to connect and browse directly
ENCODE DNA Trackhub ENCODE Trackhub for DNA-based assays hg19, hg38, mm10
ENCODE integrative Trackhub ENCODE Trackhub for integrative results hg38, mm10
ENCODE RNA Trackhub ENCODE Trackhub for RNA-based assays hg19, hg38, mm10
UCSC Repeat Browser 2020 Update Human Repeat consensuses annotated with lifted tracks hg38reps, hg19, hg38

Enter hub URLs below to connect hubs. Hubs connected this way are not accessible to other users by default.

If you wish to share your hub you can create a session link. First, connect the hub and configure the tracks image as desired, then navigate to My Sessions (My Data > My Sessions). The resulting stable link can be added to publications and shared freely. You, as the author, also have the power to update the session contents freely. Alternatively, you may build a link with the hub URL to allow users to retain their browser configuration, connected hubs, and custom tracks.

See our public hub guidelines for information on submitting a new public hub.

No connected track or assembly hubs.

To connect a hub:

  • Enter its URL into the input box above and click 'Add Hub'.
  • Alternatively, you can go to the 'Public Hubs' tab on this page and connect one of the hubs that were submitted to us.
  • Another way to connect to hubs is via a direct connection link copied using the copy icon, shown on this page, when a hub is connected.
  • You can also connect to hub by following a short link to a saved session, created though the menu 'My Data > My Sessions', if the Genome Browser had connected hubs when the session was saved.

Create your own hub

For information on making track hubs, see the following pages:
You may also contact us if you have any issues or questions on hub development.

Check a hub for errors

  Load Example URL
Use the URL bar above to check a hub for errors. This will validate the hub's configuration files, including hub.txt, genomes.txt and trackDb.txt. It will also present a hierarchical tree of tracks with any errors in red. A hub with no errors still shows the tree which can be used to explore the track hierarchy. Hub error checking will always refresh the files and never use our remote file cache (see below).

Enable Genome Browser debugging modes

These apply to all connected hubs. By default, caching is activated and track load times are not shown, but you can change these settings while developing your hub:
File caching: ON  
Current setting: Always cache contents at UCSC. This means that data access is faster, but you cannot see the effect of changes to your files on the Genome Browser for at least 5 minutes.
For custom tracks, this affects only the remote formats (bigBed, bigWig, VCF+tabix, BAM, CRAM, bigPsl, HiC, etc), not text files (BED, VCF, PSL, etc), which are stored at UCSC.
Show load times: OFF  
Current setting: Show no timing measurements.