Export Formats
What you get when you download a report
All downloads come from the report header, and all describe the iBGCs in your shortlist. There are four formats, each suited to a different next step.
GenBank zip (.gbk files)
A zip archive of GenBank files — one per source BGC prediction, grouped into a folder per iBGC. Each file carries the cluster’s annotations (BGC/region features and the coding genes).
Use it for downstream genomics tools: re-running antiSMASH, feeding a synthesis or primer-design pipeline, loading into a genome browser, or sharing the raw clusters with a collaborator. This is the export most directly tied to wet-lab follow-up.
iBGC table (TSV)
A tab-separated table, one row per iBGC, with the columns from the report’s iBGC results table — accession, assembly, organism, phylum, biome, size, novelty, domain novelty, GCF, class, source tools, and contig coordinates.
Use it for spreadsheets, filtering and sorting in Excel/R/Python, or merging with your own metadata. This is the format for tabular analysis and record-keeping.
JSON
A tidy JSON bundle of the report data: metadata plus the underlying tables (iBGCs, assemblies, domain composition, GCF distribution, and summary stats), reshaped to be analysis-friendly rather than chart-oriented.
Use it for programmatic work — loading the full shortlist into a script or notebook with all the derived summaries intact.
HTML
A single, self-contained HTML file reproducing the report page — tables and interactive charts — that works offline in a browser with no server.
Use it for archiving a snapshot, attaching to a report or email, or sharing with someone who doesn’t have access to the platform.
Choosing a format
| You want to… | Use |
|---|---|
| Take clusters into annotation/synthesis tools | GenBank zip |
| Sort, filter, or merge in a spreadsheet | iBGC TSV |
| Process the full shortlist in code | JSON |
| Archive or share a fixed snapshot | HTML |