Meridian app icon

Your deep sky imaging archive — cataloged, visualized, and searchable. Native on Apple Silicon.

Get Meridian on the Mac App Store

$34.99, one-time purchase. Requires macOS 14 or later.

Your imaging archive deserves better than a folder of folders.

After years of imaging, your data is scattered across drives, naming conventions have drifted, and you can't remember which equipment you used for that one session two years ago. Finding a specific sub from a specific night means clicking through folder after folder, hoping your file names are descriptive enough. If you shoot with a smart telescope the problem arrives faster: a Seestar or a DWARF can fill a drive in a single season, and the folders it leaves behind tell you very little about what you actually captured.

Meridian is a native macOS deep sky archive manager from Mac Observatory, built for exactly this problem. Point it at your imaging folders and it reads every FITS and XISF header, identifies each target by its sky coordinates across 20 astronomical catalogs, groups your frames into sessions, and builds a searchable, visual catalog of everything you have ever shot.

You don't have to reorganize your whole archive first. Meridian reads whatever structure you already have, and it never modifies your files: no moving, no renaming, no rewriting headers. It only reads them. There is one organizing decision that genuinely matters, though, and it is worth two minutes before you scan. That is the next section.

One folder per object. That is the structure Meridian needs.

Meridian identifies your targets from the coordinates in your headers, but it uses your folders to decide which frames belong together. It steps over any folder named for a year, then treats the next folder down as a single target and reads everything beneath it. So that folder needs to be an object.

Get that one level right and everything else is yours to arrange however you like.

Astrophotography/ point Meridian here └── 2026/ optional: year folders are stepped over ├── M90/ one folder per object │ ├── Light/ everything below here is up to you │ │ └── 2026-04-19_Ha_300s_0001.fits │ ├── Calibration/ or leave masters loose, either works │ ├── M90.tif the target's final image │ └── M90.psd └── NGC 3718/ next object, same pattern └── ...

Don't sort by equipment or object type above your objects.

This is the most common way an archive confuses Meridian, and it fails quietly. In 2026/Redcat/M90/ the target becomes "Redcat", and every object you ever shot with that scope merges into one entry. Same with 2026/Galaxies/M90/. If you want to group by rig or by type, do it above the year rather than below it. You don't need equipment folders anyway: Meridian already tracks your gear from the headers and lets you filter by it.

What is flexible inside an object folder

Almost everything. Subfolder names are invisible to Meridian, so Light, Subs, Raw, or one folder per filter all work identically, at any depth. Calibration masters can live in a Calibration folder or sit loose beside your frames. Finished images belong in the object folder, where Meridian associates them back to the frames that produced them. Sessions, filters, exposure times, and equipment all come from the headers rather than from the layout.

If an object folder does end up holding frames aimed at very different parts of the sky, Meridian warns you instead of guessing. It never splits a folder, never renames anything, and never modifies a file. For a fuller walk through archive organization, see my guide to organizing an astrophotography data library.

Your equipment comes from your headers.

Meridian builds your entire equipment list out of what your capture software wrote into the FITS headers: telescope, camera, focal length, and pixel size. No manual entry, no setup screen. It also tolerates the small stuff, so a rig that reports 754 mm one night and 756 mm the next stays a single profile instead of fragmenting into three.

Fill it in once

Enter your telescope and camera names in your capture software and they flow into Meridian automatically, for every session from then on.

Got it wrong? Fix it after

Rename the scope or the camera on any data set, and choose whether the change applies everywhere that profile is used or only to that one session.

Wrote nothing at all?

If neither the telescope nor the camera made it into the headers, there is nothing for Meridian to attach a name to and that session stays unattributed. This is why step one is worth five minutes tonight.

Object Recognition

41,730 objects across 20 catalogs, resolved automatically.

Meridian identifies each target from the pointing coordinates in your FITS and XISF headers, then resolves it against a built-in database spanning 20 astronomical catalogs. Because it works from where the telescope was actually aimed rather than trusting the name someone typed, it finds the right object even when the header is wrong, blank, or full of a previous owner's shorthand.

Tier 1: Core Catalogs

Messier 110NGC 7,840IC 5,386Caldwell 109

Tier 2: Extended Catalogs

Sharpless 313Barnard 349Abell 4,159Collinder 471

Tier 3: Advanced Catalogs

vdB 158LBN 1,125LDN 1,802Arp 338Hickson 100Melotte 245Ced 215RCW 182Gum 84

M42 = NGC 1976 = Sh2-281 = LBN 974. Meridian knows they are all the same object and groups your data accordingly.

Every target you've ever shot. Everything about it in one place.

Meridian organizes your archive by astronomical object, not by folder, not by date, not by file name. The Catalog view gives every target a dedicated page: your finished image as the hero, total integration time, a per-filter breakdown, the full session history, and every equipment setup you have used on it.

Finished images get associated back to the frames that produced them, so the picture you posted and the eleven nights of data behind it stay connected even when they live in different folders on different drives.

Sort by integration time, filter count, or date. Filter by catalog, object type, constellation, or equipment. Press Command-K to jump to any target instantly. Your archive becomes a living reference of everything you have captured.

Know what to shoot tonight, before you set up.

The Wish List view turns your archive into a planning tool. Build a target list, check altitude and transit times for your location, compare field of view against your equipment, and plan sessions across multiple imaging sites. Because Meridian already knows what you have shot, it also knows what you are short on: the targets you have started and never finished are right there next to the ones you have never tried.

Visibility Data

Altitude, azimuth, transit time, and hours above horizon for every target on your wish list.

FOV Comparison

See how targets fit your sensor and telescope combination before committing to a session.

Multi-Site

Save multiple imaging locations and switch between them for accurate visibility calculations.

Wish List

Build and maintain a list of targets you want to image, with visibility recalculated for the current night.

Built for the Mac from the ground up.

Meridian is written entirely in Swift and SwiftUI, and ships as a universal binary that runs natively on both Apple Silicon and Intel. It uses SwiftData for its local database and Metal for GPU-accelerated thumbnail rendering. It is not a port, not an Electron wrapper, not a web app in a frame. It is a real Mac app, built with Apple's own frameworks and nothing else.

Full dark mode support. Keyboard shortcuts for everything. A Quick Look extension that previews FITS and XISF files directly in Finder, even when Meridian is not running, and Spotlight integration that makes your archive searchable from anywhere in macOS. Your imaging data stops being an opaque pile of files and becomes something the rest of your Mac can see.

What Meridian Can Do

One app. Every feature included. Zero file modifications.

Statistics Dashboard

Eight sections of imaging analytics: activity timelines, filter usage, sky coverage, equipment stats, and more.

Interactive Sky Map

Powered by Aladin Lite. See every target you have imaged plotted on an interactive sky survey.

Source File Triage

See exactly which files were skipped and why, and overrule the decision per file or per folder.

Equipment View

Every telescope, camera, and filter pulled automatically from FITS headers, with the targets shot on each.

Star Extraction & Seeing

HFR and FWHM analysis across your subs. Track seeing conditions and focus quality over time.

Session Grouping

Loose frames are grouped into the nights they were shot, so integration time adds up on its own.

Live File Watching

FSEvents monitoring. New files appear in your catalog automatically as they are written to disk.

Hybrid Plate Solving

Solves locally with ASTAP for frames missing coordinates. Astrometry.net cloud rescue is opt-in.

Final Image Association

Your finished picture stays linked to the frames behind it, even across different folders and drives.

Auto-Stretched Thumbnails

Midtone Transfer Function stretch on every thumbnail. See your data, not black rectangles.

Quick Look & Spotlight

Preview FITS and XISF in Finder with spacebar, and search your archive from anywhere in macOS.

Strictly Read-Only

Meridian never writes to, moves, renames, or modifies your imaging files. Your data stays exactly where it is.

Everything you've ever photographed mapped on the sky.

Compatibility

File Formats

FITSXISFTIFFJPG / PNGPSD

Works With

N.I.N.A.SGProAPTKStars / EkosASIAIRSeestarDWARFPixInsightAstro Pixel ProcessorSirilASTAP

Requirements

macOS 14+Apple Silicon & Intel

Pricing

One price. Every feature.

No subscriptions. No tiers. Buy once, own it forever.

Everything included

Meridian

$34.99

One-time purchase. Every feature included.

  • Folder scanning, indexing, and cataloging
  • Object resolution across 20 catalogs
  • Auto-stretched MTF thumbnails
  • Quick Look extension for FITS and XISF
  • Live file watching with FSEvents
  • Source file triage and reclassification
  • Interactive sky map (Aladin Lite)
  • Wish list and visibility planning
  • Statistics dashboard
  • Star extraction and seeing analysis
  • Equipment tracking from FITS headers
  • Final image association
  • Local plate solving with optional cloud rescue
  • Spotlight integration and multi-site support
Get Meridian on the Mac App Store

Includes Family Sharing for up to six people. No subscription, no in-app purchases.

Mac Observatory Suite

Built for the Mac. Built for Astronomers.

Native macOS apps filling the gaps the astronomy community has been waiting for.

The Observing Workflow   Look Up → Capture → Process → Archive

Transit
Astronomical Events
Mac App Store
Laminar
Planetary Capture
Mac App Store
Strata
Stack & Sharpen
Public Beta
Meridian
Deep Sky Archive
Mac App Store

It starts with Transit: live conditions and tonight's events tell you whether the sky is worth it. From there the planetary chain takes over, with Laminar capturing and Strata stacking and sharpening on the GPU. Meridian covers the other half of the hobby, turning a deep sky imaging archive into a catalog you can actually search.

Guiding Diagnostics   Free & Open Source

Ephemeris
PHD2 guide log viewer: multi-session periodograms and orthogonality readouts, native on your Mac.

Swift & SwiftUI · Apple Silicon Native · Metal GPU · No Subscriptions

Frequently Asked Questions

Common questions about cataloging and managing a deep sky imaging archive on macOS.

What does Meridian actually do?+
Meridian is a native macOS deep sky imaging archive manager from Mac Observatory. You point it at the folders where your imaging data already lives, and it reads the FITS and XISF headers in every file, works out which astronomical object each frame is pointed at, groups those frames into targets and sessions, generates thumbnails you can actually see, and presents the whole archive through six views: Catalog, Source Files, My Sky, Wish List, Equipment, and Statistics. It is a librarian for data you already have, not a processing tool and not a capture tool.
Do I need to reorganize my folders before I can use it?+
Mostly no, with one exception worth knowing about. Meridian reads whatever structure you already have, and it identifies targets from the coordinates in your headers rather than from folder names, so years of drifted naming are exactly what it was built for. Subfolder names inside a target folder are invisible to it: Light, Subs, Raw, or one folder per filter all work identically, at any depth. The one thing that matters is that the first folder under the folder you point Meridian at, after any year folder, should be an object. If your archive is sorted by telescope or by object type at that level instead, everything underneath merges into a single target. If that is how yours is arranged, it is worth restructuring that one level before you scan. Everything else can stay exactly as it is.
Does Meridian modify my imaging files?+
Never. Meridian is strictly read-only against your archive. It reads FITS and XISF headers and image data to build its catalog, but it never writes to, moves, renames, or modifies your files in any way. The catalog and the thumbnails are derived data stored separately, so deleting something inside Meridian removes it from Meridian's records and leaves the file on disk untouched. Your archive stays exactly where it is, exactly as it is.
How much does Meridian cost, and is there a trial?+
Meridian is $34.99 on the Mac App Store. That is a single one-time purchase with every feature included from day one: no subscription, no tiers, no in-app purchases, and no paid upgrades to unlock parts of the app. There is no free trial. Family Sharing is enabled, so up to six people in your family can use one purchase.
Does Meridian work on Intel Macs?+
Yes. Meridian ships as a universal binary and runs natively on both Apple Silicon and Intel. The real limit is the operating system, not the processor: Meridian requires macOS 14 or later, which on the Intel side means roughly 2018 and newer machines. One honest caveat. Meridian is built and tuned on Apple Silicon, and some of its GPU work, including thumbnail auto-stretch and star extraction, is written around the shared memory architecture Apple Silicon provides. On Intel those steps involve a real memory copy, so they will be slower, and they fall back to the CPU if the GPU path is unavailable. I have not done a full test pass on Intel hardware yet. If you are running Meridian on an Intel Mac and something misbehaves, email me and I will fix it.
What Mac do I need to run Meridian?+
Any Mac running macOS 14 Sonoma or later. That covers every Apple Silicon Mac (M1, M2, M3, M4, and later) and Intel Macs from roughly 2018 onward, including the 2018 MacBook Pro and Mac mini, the 2019 MacBook Air and iMac, the iMac Pro, and the 2019 Mac Pro. Storage matters more than raw speed here: your archive can live on any mounted volume, and Meridian's own catalog and thumbnail cache are small by comparison.
Does it work with data from N.I.N.A.?+
Yes. Meridian reads standard FITS headers including those written by N.I.N.A., and extracts target names, filter information, exposure details, equipment data, and coordinates. It also works with data from SGPro, APT, KStars/Ekos, ASIAIR, PixInsight, Astro Pixel Processor, and Siril. Because it identifies targets from coordinates first rather than trusting the object name in the header, it copes well with archives assembled from several different capture tools over the years.
Does Meridian work with Seestar, DWARF, and other smart telescopes?+
Yes. Smart telescopes like the ZWO Seestar and the DWARF series write standard FITS files, and Meridian reads them the same way it reads data from any other source. It also reads TIFF, so stacked output sits alongside the subframes it came from. This is one of the gaps Meridian was built to fill: smart telescopes accumulate sessions fast, and there has been almost nothing on the Mac that makes sense of what you have actually collected over a season.
Does Meridian catalog planetary and lunar work?+
Yes, for your results. Name a folder for the object, such as "Jupiter 2026-04-19" or "Sun 11-6-2026", and Meridian recognizes it: the eight planets, the Moon, the Sun, and comets by name. Your finished images are associated with that target, and it appears in the Catalog and Statistics views alongside your deep sky work. Solar system targets do not appear in My Sky or the Wish List, since both are built on the deep sky reference catalog. Meridian also does not index SER video, which is deliberate: planetary capture files run to tens of gigabytes each and dozens per night, and almost nobody keeps them. What you archive is the stack, and that is what Meridian catalogs. One tip: use a space rather than an underscore between the object name and the date, since that is how the folder name is parsed.
Do I need ASTAP, and what is the plate solving for?+
Only if you have frames that need it. Meridian identifies targets from the pointing data already in your headers, which covers most modern archives. Plate solving is the fallback for frames that arrived without usable coordinates, common in older data or files that have been through a processing tool that stripped the headers. Meridian solves locally using ASTAP if you have it installed, which is free, fast, and keeps everything on your machine. If a frame will not solve locally, you can optionally send it to Astrometry.net. That cloud path is strictly opt-in and off by default: storing an API key alone does not authorize uploads, and nothing leaves your Mac until you say so.
Does Meridian need an internet connection?+
No. Scanning, cataloging, object resolution, thumbnails, statistics, and visibility planning all run entirely offline against a reference database bundled with the app. Two features reach the network if you use them: the My Sky view loads survey imagery from Aladin Lite, and cloud plate solving sends individual frames to Astrometry.net, which is opt-in. Meridian collects no data about you at all, which is what the App Store privacy label reflects.
How is Meridian different from PixInsight or Siril?+
They solve different problems and most people will use both. PixInsight and Siril are processing tools: they calibrate, register, stack, and stretch your data into a finished image. Meridian does none of that, deliberately. It answers the questions that come before and after processing, such as what have I actually shot, how many hours do I have on this target, which filters am I short on, what did I use to shoot it, and where did that finished image come from. Think of it as the library rather than the darkroom.
How long does the initial scan take?+
It depends on how many files you have and how fast the storage is, so a large archive on a network volume takes considerably longer than a few hundred frames on an internal SSD. The scan runs in the background and the catalog fills in progressively, so you can start exploring before it finishes rather than waiting at a progress bar. After the first pass, launches are near instant because Meridian only processes files that are new or changed.
Can I use it with external drives and NAS volumes?+
Yes. Meridian works with any mounted volume, including internal drives, external SSDs, USB drives, and NAS shares. If a drive is disconnected and later reconnected, Meridian picks up where it left off rather than rescanning from scratch, and the catalog entries for offline data remain visible in the meantime so you can still see what you have on a drive that is currently unplugged.
Does the Quick Look extension require the app to be running?+
No. The Quick Look extension is a standalone system extension that works independently. Once Meridian is installed, you can press spacebar on any FITS or XISF file in Finder to see a preview, even when Meridian itself is not running. Meridian also registers with Spotlight, so your archive becomes searchable from anywhere in macOS.