GFF3 features to JSON
Export GFF3 features as JSON while retaining the source coordinate convention and raw annotation fields.
Drop your files here
Make something new. Keep everything private.
Multiple files welcome · processed one at a time
Select a tool to see its supported formats and conversion limits. Large files may exceed your browser’s memory.
Before processing large files
On phones and tablets, start with files under 20 MiB and keep this tab in the foreground. Video, OCR and 3D operations can use several times the input size in memory. Desktop browsers generally have more room, but the 128 MiB job limit is not a guarantee that every file will fit. Smaller batches reduce memory pressure.
Supported input formats
- General Feature Format version 3 (.gff)
- General Feature Format version 3 (.gff3)
Output format
JavaScript Object Notation (.json)
Support applies to this conversion direction. Check the limits below for features that may change or be discarded.
Compare all supported formats and conversion limits →How to use GFF3 features to JSON
- Add your supported file using the chooser or drop zone.
- Review the settings and conversion limits before processing.
- Select Convert files, then download the result.
What to expect
- UTF-8, uncompressed input only, maximum 64 MiB, 100,000 records and 2 million cells. No assembly or coordinate-system conversion. Missing values remain literal dots; CSV cells are not sanitized for spreadsheet formulas.
- Requires ##gff-version 3 and nine tab-separated columns. Coordinates remain 1-based, inclusive. Attributes stay literal encoded text. Directives/comments are retained in JSON metadata; embedded ##FASTA sequence is omitted.
Engine: Local genomic table parser. The engine may need a first-use download. Your file stays in this browser session.Check conversion engines and offline requirements.
About this conversion
Is gff3 features to json free?
Yes. This tool runs on your device without an account or a conversion fee.
Are files uploaded during conversion?
File processing happens locally in your browser. Engines may download their code on first use; your input files are not sent to a conversion server. Read how file privacy works.
What if conversion fails?
Check that the file matches a supported input, review the engine’s limitations and try a smaller representative file. If the engine cannot load, check its engine assets and browser requirements. The app reports failures without switching to a remote converter.
Continue with your output
These tools accept this tool’s output format. Each step has its own settings and fidelity limits.
- Numeric data to HDF5
Create a single selected HDF5 dataset from a numeric matrix or an exported JSON envelope.
- JSON to CSV
Convert JSON locally with an explicit structured-data mapping.
- JSON to TSV
Convert JSON locally with an explicit structured-data mapping.
- JSON to YAML
Convert JSON locally with an explicit structured-data mapping.
- JSON to XML
Convert JSON locally with an explicit structured-data mapping.
- JSON to SQLite database
Create a portable, single-table SQLite database from JSON records.
More scientific tools
- GFF3 features to CSV
Export GFF3 features as CSV while retaining the source coordinate convention and raw annotation fields.
- HDF5 dataset to JSON
Select one numeric HDF5 dataset and export its values locally.
- HDF5 dataset to CSV
Select one numeric HDF5 dataset and export its values locally.
- Inspect FASTA sequences
Summarize FASTA record lengths and sequence symbol counts locally.
- FASTA to CSV
Export FASTA identifiers, descriptions and sequence strings to CSV.
- FASTA to JSON
Export FASTA identifiers, descriptions and sequence strings to JSON.