Use this web form to verify the format of any Flexible Image Transport System (FITS) data file on your local computer or on the web. The file will be uploaded and scanned for any violations of the requirements specified in the FITS Standard document. You may also download this FITSverify program and run it locally.The file size limit for this tool is 100 MB. The FITS Verifier was created by NASA's High Energy Astrophysics Science Archive Research Center (HEASARC). HEASARC FITS Verifier Select a FITS file to verify it directly in your browser. Files are processed locally and never uploaded. Print Header Contents (-l) Verification Report: Loading the verifier ... The fv FITS file viewer and editor may be used to examine the contents of the FITS file in greater detail.This form uses the FITSverify utility program that is freely available from HEASARC. When installed locally, FITSverify may be used to verify multiple files at once in batch mode.Please report any problems or questions about FITSverify to the ftools help desk. Error ListFITSverify tests whether a FITS file meets the requirements of Version 3.0 of the FITS Standard. It will test for any of the following error or warning conditions:Error ConditionsMandatory keyword not present or out of orderMandatory keyword has wrong datatype or illegal valueEND header keyword is not presentSum of table column widths is inconsistent with NAXIS1 valueBLANK keyword present in image with floating-point datatypeTNULLn keyword present for floating-point binary table columnBit column has non-zero fill bits or is not left adjustedASCII (American Standard Code for Information Interchange) TABLE column contains illegal value inconsistent with TFORMnAddress to a variable length array not within the data heapExtraneous bytes in the FITS file following the last HDU (Header Data Unit)Mandatory keyword values not expressed in fixed formatMandatory keyword duplicated elsewhere in the headerHeader contains illegal ASCII character (not ASCII 32 - 126)Keyword name contains illegal characterKeyword value field has illegal formatValue and comment fields not separated by a slash characterEND keyword not filled with blanks in columns 9 - 80Reserved keyword with wrong datatype or illegal valueXTENSION keyword in the primary arrayColumn related keyword (TFIELDS, TTYPEn,TFORMn, etc.) in an imageSIMPLE, EXTEND, or BLOCKED keyword in any extensionBSCALE, BZERO, BUNIT, BLANK, DATAMAX, DATAMIN keywords in a tableTable WCS keywords (TCTYPn, TCRPXn, TCRVLn, etc.) in an imageTDIMn or THEAP keyword in an ASCII tableTBCOLn keyword in a Binary tableTHEAP keyword in a binary table that has PCOUNT = 0XTENSION, TFORMn, TDISPn or TDIMn value contains leading space(s)WCSAXES keyword appears after other WCS keywordsIndex of any WCS (World Coordinate Systems) keyword (CRPIXn, CRVALn, etc.) greater than value of WCSNAXESIndex of any table column descriptor keyword (TTYPEn, TFORMn, etc.) greater than value of TFIELDSTSCALn or TZEROn present for an ASCII, logical, or Bit columnTDISPn value is inconsistent with the column datatypeLength of a variable length array greater than the maximum length as given by the TFORMn keywordASCII table floating-point column value does not have decimal point(*)ASCII table numeric column value has embedded space characterLogical column contains illegal value not equal to 'T', 'F', or 0Character string column contains non-ASCII text characterHeader fill bytes not all blanksData fill bytes not all blanks in ASCII tables or all zeros in any other type of HDUGaps between defined ASCII table columns contain characters with ASCII value > 127Warning ConditionsSIMPLE = FPresence of deprecated keywords BLOCKED or EPOCH2 HDUs have identical EXTNAME, EXTVER, and EXTLEVEL valuesBSCALE or TSCALn value = 0.BLANK OR TNULLn value exceeds the legal rangeTFORMn has 'rAw' format and r is not a multiple of wDATE = 'dd/mm/yy' and yy is less than 10 (Y2K problem??)Index of any WCS keyword (CRPIXn, CRVALn, etc.) greater than value of NAXIS, if the WCSAXES keyword is not presentDuplicated keyword (except COMMENT, HISTORY, blank, etc.)Column name (TTYPEn) does not exist or contains characters other than letter, digit and underscoreBinary table has PCOUNT > 0, but no variable-length array columnsCalculated checksum inconsistent with CHECKSUM or DATASUM keyword