Add your FITS file
Drop one or more .fits files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Converting a .fits font to .png repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Converting a .fits font to .png repackages the same glyphs and metrics for a different delivery target. A .fits file is the standard data format of astronomy: one or more header-data units, each a block of human-readable 80-character keyword cards followed by an N-dimensional array or a table. Essentially every professional telescope and space observatory writes it, and the format has been backwards-compatible since 1981.
A .png file is a losslessly compressed raster image with full 8-bit alpha transparency, making it the standard choice for graphics that must stay pixel-perfect. Screenshots, logos, UI assets, and diagrams are the classic .png territory, since sharp edges and flat color survive without compression artifacts. For this route the practical draw is perfectly lossless, so files can be opened and re-saved indefinitely and true 8-bit (or 16-bit) alpha channel — balanced against photographic content produces files several times larger than JPEG or WebP, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .fits, the 2880-byte block padding wastes space and reflects hardware nobody has used in decades. Switching to .png buys you perfectly lossless, so files can be opened and re-saved indefinitely, which is why it is the better fit for screenshots and screen recordings exported as stills. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | Flexible Image Transport System (.fits) | PNG image (.png) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Lossless — every pixel or sample is preserved exactly |
| How it stores data | headers are ASCII cards of exactly 80 characters, in the form KEYWORD = value / comment, padded into 2880-byte blocks — a size inherited from magnetic tape | uses DEFLATE compression preceded by per-scanline prediction filters (None, Sub, Up, Average, Paeth) |
| Strongest at | telescope and space-observatory imagery and spectra | screenshots and screen recordings exported as stills |
| Weak spot | the 2880-byte block padding wastes space and reflects hardware nobody has used in decades | photographic content produces files several times larger than JPEG or WebP |
| Metadata | header cards, including WCS and instrument keywords, are read and exported into the JSON output; PNG carries no channel for them, which is why the loss is stated rather than assumed obvious | text metadata lives in tEXt/iTXt chunks and XMP can be embedded there; standardized EXIF arrived late via the 2017 eXIf chunk, so many tools still drop EXIF when writing PNG |
Drop one or more .fits files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .png in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if PNG is selectable, the route is real and validated.
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid PNG file. Outputs keep the original filename with the .png extension.
Since fits is lossless-oriented and png is lossless-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .png itself requires.
Yes — the .fits file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Every modern browser has rendered PNG with full alpha since Internet Explorer 7 fixed its transparency bug in 2006, and native OS support is universal on Windows, macOS, Linux, iOS, and Android. It is also the required format in many contexts, such as iOS app icons and favicon fallbacks.
It depends on the content: uses DEFLATE compression preceded by per-scanline prediction filters (None, Sub, Up, Average, Paeth). Convert one representative file first and compare before batch-processing a large set.
In .fits, header cards, including WCS and instrument keywords, are read and exported into the JSON output; PNG carries no channel for them, which is why the loss is stated rather than assumed obvious. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.