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.

Assembly:
Display Hub Name Description AssembliesClick to connect and browse directly
FANTOM5 RIKEN FANTOM5 Phase1 and Phase2 data hg38, hg19, mm10, rn6
PhyloCSF Evolutionary protein-coding potential as measured by PhyloCSF hg19, hg38, mm10
Translation Initiation Sites (TIS) Translation Initiation Sites (TIS) track hg19

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.

Display Hub Name Description AssembliesClick to connect and browse directly
DeepRibo DeepRibo predictions made by DeepRibo [+] eschColi_K12, baciSubt2...

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.