Upload your track hub files to UCSC and view your bigBed, bigWig, BAM, VCF, and other supported files -- no need to rely on third-party hosting services such as Dropbox, Google Drive, or AWS.
Each account is allocated 10 GB of storage. While we strive to maintain uninterrupted access, please maintain your own backups. Data persistence over the long term is not guaranteed. To request additional storage space, please contact us.
There are three primary ways to upload your files:
If a hub.txt file is not provided when uploading the data files, a hub.txt file is automatically generated. The generated hub.txt file is configured with the useOneFile trackDb setting, and as a result, each hub is limited to a single genome assembly.
Hub Space also accepts the standard multi-file hub layout: a hub.txt
that references a separate genomesFile (typically
genomes.txt), with one trackDb file per genome. Include
hub.txt, genomes.txt, every referenced trackDb, and any 2bit files
in the same upload, and Hub Space will derive each file's assembly
from the hub definition. For more complex multi-file hubs, the
hubtools
command-line uploader remains the recommended path.
Editing the generated hub.txt file is not yet supported. To customize the hub configuration or data display, replace the generated hub.txt file with your own version after uploading the data files.
By default, your most recently used genome assembly is selected after choosing which files to upload. Use the popular assemblies drop-down menu or the search box to select another genome assembly.