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 search terms: RefSeqFE

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
RefSeqFE Hub NCBI RefSeq Functional Elements interactions and features hg38, mm10, mm39

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.

Contact us if you wish to submit a hub to the list of public hubs.

No Unlisted Track Hubs

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

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  
The current status always caches 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, tabix, BAM, CRAM, etc), not text files (BED, PSL, etc), which are stored at UCSC.
Load times: OFF  
Show no timing measurements.