# Fastq unavailable -- Tool does not recognize inputs? How to check why **URL:** \ **Category:** Resources\ **Tags:** metadata, igv, fastqsanger, datatype, resources, single-cell\ **Created:** [October 28, 2022, 7:23pm UTC](https://help.galaxyproject.org/t/fastq-unavailable-tool-does-not-recognize-inputs-how-to-check-why/8925 "2022-10-28T19:23:26Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\ **Post date:** [October 28, 2022, 8:43pm UTC](https://help.galaxyproject.org/t/fastq-unavailable-tool-does-not-recognize-inputs-how-to-check-why/8925/2 "2022-10-28T20:43:50Z")
Hi @TTP Most tools in Galaxy expect reads in `fastqsanger` or `fastqsanger.gz` format and with one of those datatypes assigned. Those datatypes represent a specific type of quality score scaling: Sanger Phred +33. This is produced by Illumina 1.8+ pipelines. PacBio used Phred+33 scaling to start with and now the scaling is neutral. You can double check with a tool like **FastQC** or **FASTQ info** to see what those report. There are some tools that expect just `fastq` or `fastq.gz` (scaling unspecified). But if you are ever not sure what datatype(s) a tool accepts as input, any tool not just those that accept reads, try this: 1. Create a new empty history 2. Load up the tool form 3. Review the input datatypes listed in the tool form’s input area 4. Note: A tool could have more than one input area and this works for all user-supplied inputs from the history. **Example** ![what-datatype-is-accepted-input](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/e/e526ccad7216bc30f1408215478e172bbae0cda4.png) --- _[View the full topic](https://help.galaxyproject.org/t/fastq-unavailable-tool-does-not-recognize-inputs-how-to-check-why/8925)._