Universal workbench

FITS Header & Dimension Inspector

Inspect bounded FITS primary-header cards, dimensions, and pixel metadata locally.

Device-onlyNo uploads. Ever.
Pipelines, branches, presets, naming, and detailed controls
Display
Help me choose the best output Suggested: FITS metadata JSON

Recommendations use the registered target format and tested fidelity classification. They never inspect or upload your content.

01Input
Drop files or a folder hereChoose FITS files or a folder — batch input is welcome
or paste content
File input required
02Configure & run
FITSFITS metadata JSON
structural conversion · single or batch
Conversion preflightSize, memory, engine, execution, and fidelity before you start
Input
0 B
Estimated peak memory
16 MiB
On-demand download
No large engine download
Execution
Responsive local worker
Fidelity
No lossy step declared
What to provideDrop one or more FITS files; this format cannot be pasted as plain text.What you’ll getProduces previewable FITS metadata JSON text and a correctly named download.
Output naming & batch behavior
Exampleoutput.fits.json
Pipeline 1 linear · 0 branches
Why use A → B → C?

A pipeline feeds each result directly into the next compatible converter. Use one when the destination needs an intermediate representation or when you want to inspect and normalize that middle format.

  • JSON → CSV → XLSX turns records into rows before building a workbook.
  • Markdown → HTML → DOCX resolves markup before creating a document.
  • SVG → PNG → PDF intentionally flattens vector artwork before placing it on a page.
Only type-compatible next steps are offered. Lossy steps are marked before you run them.
1FITS to FITS metadata JSONstructural

Add content above to start. Nothing leaves this browser.

Processing happens locally. Your file bytes are never sent anywhere.
About this utility

How to use FITS Header & Dimension Inspector

Inspect bounded FITS primary-header cards, dimensions, and pixel metadata locally.

What to provide

Drop the files described by this task. The selected converter validates signatures and processes them locally.

  1. Choose files or drag them into the local converter workbench. The source signature is checked before processing.
  2. Review the task-specific options, fidelity warning, memory estimate, and destination representation.
  3. Select “Convert on this device,” then preview, compare, download, or continue through a compatible in-memory handoff.

What the result means

The converter workbench provides previews, progress, cancellation, warnings, and individual or ZIP downloads.

Privacy and safety

This utility is loaded as browser code and processes your input only in this tab. OmniCastConverter has no upload endpoint and never stores your content, filenames, tokens, or secrets. Generated markup and code are shown as inert text and are never executed.

Limitations

  • The focused task reuses its tested converter contract; source-format fidelity and browser memory limits remain visible before execution.

Try the included example

Select “Load example” at any time to restore this tested sample.

(choose a local file)