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.

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.

No Public Track Hubs found that match search criteria.

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.

URL:
Display	Hub Name	Description	AssembliesClick to connect and browse directly. Click copy icon to copy URL to clipboard for sharing.
	CEMT (CEEHRC)	Epigenomic Data tracks from BCGSC, Vancouver, B.C.	hg38, hg19
		ERROR: Couldn't open https://hgwdev.gi.ucsc.edu/~markd/t2t/T2T-CHM13/hub.txt Debug Help
	T2T CHM13 Dev	T2T CHM13 Development Assembly Hub	[+] GCA_009914755.4, t2t-chm13-v1.1...
	Track Collections	Track Collections	hg19

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

Hub URL: 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: