FluxMarkdown works as a macOS QuickLook extension, which means it depends on several system-level registrations to function correctly. When something goes wrong, the symptoms can look identical — a plain-text preview — even when the underlying cause is completely different. Work through the sections below in order, starting with the simplest fix first.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/xykong/flux-markdown/llms.txt
Use this file to discover all available pages before exploring further.
"App is damaged" or "Unidentified developer" warning
"App is damaged" or "Unidentified developer" warning
macOS attaches a quarantine attribute to apps downloaded from the internet. This attribute causes Gatekeeper to block FluxMarkdown before it can register its QuickLook extension.Open Terminal and run:This removes the quarantine flag from the app and all files inside it. After the command completes, launch FluxMarkdown normally from Applications. You should not see the warning again.
This command is safe and only removes the quarantine metadata Apple attaches to downloaded files. It does not modify the app itself.
Preview still shows plain text (QuickLook cache not updated)
Preview still shows plain text (QuickLook cache not updated)
macOS caches QuickLook plugin metadata aggressively. Even after FluxMarkdown is correctly installed, the cache may continue routing Wait a few seconds for Finder to relaunch, then select a
.md files to the built-in plain-text previewer.Reset the QuickLook cache and restart Finder with:.md file and press Space. If the preview is still plain text, continue to the next section.QuickLook extension not registered
QuickLook extension not registered
macOS requires the host app to be launched at least once before the system registers its embedded QuickLook extension. The extension will not appear in the plugin registry until that first launch occurs.Step 1 — Launch the appOpen FluxMarkdown from your Applications folder. The welcome window appearing is sufficient; you do not need to open a file.Step 2 — Confirm the extension is registeredRun the following command in Terminal:Look for an entry containing
MarkdownPreview or markdownquicklook. If you do not see it, continue to step 3.Step 3 — Enable the extension in System Settings- Open System Settings
- Go to Extensions → Quick Look
- Make sure the FluxMarkdown or MarkdownPreview entry is checked
Extension is registered but preview is still plain text
Extension is registered but preview is still plain text
When For the standard release build, follow these steps to restore correct behaviour:
pluginkit confirms that the extension is registered but Finder still shows plain text, the cause is usually LSHandlerRank. macOS selects the QuickLook extension based on which application is declared as the Owner handler for the Markdown UTI. If FluxMarkdown is only registered as an Alternate handler, macOS ignores it in favour of the system’s built-in plain-text previewer.FluxMarkdown declares itself as LSHandlerRank = Owner for Markdown files. If you are running a custom or development build, verify that Sources/Markdown/Info.plist contains:Rebuild and reinstall
Download the latest DMG from GitHub Releases and drag FluxMarkdown to Applications, replacing the existing copy.
Launch the app once
Open FluxMarkdown from Applications so macOS re-registers it as the Owner handler for
.md files.Preview works sometimes but not consistently
Preview works sometimes but not consistently
Intermittent plain-text previews are almost always a stale QuickLook cache issue. macOS may fall back to the system previewer for certain files or after waking from sleep.Clear the cache and restart Finder:If the problem recurs after every restart, check that no other Markdown QuickLook plugins (such as
QLMarkdown or qlmarkdown) are installed alongside FluxMarkdown. Conflicting plugins can cause macOS to choose inconsistently between them.Diagrams (Mermaid) not rendering
Diagrams (Mermaid) not rendering
If your preview loads correctly but Mermaid diagrams appear as raw code blocks instead of rendered diagrams, Mermaid rendering may be disabled in Settings.
- Open FluxMarkdown
- Press Cmd+, to open Settings
- Go to Rendering
- Make sure Mermaid is toggled on
.mmd files.Mermaid diagrams that contain
\n in unquoted node labels (e.g. A[line1\nline2]) are handled automatically — you do not need to quote the labels manually.Math expressions (KaTeX) not rendering
Math expressions (KaTeX) not rendering
If inline or block math expressions such as
$E = mc^2$ appear as raw text, KaTeX rendering may be disabled.- Open FluxMarkdown
- Press Cmd+, to open Settings
- Go to Rendering
- Make sure KaTeX is toggled on
$) and block math (wrapped in $$ or a tex code fence). KaTeX is loaded lazily — documents without math expressions are not affected by enabling this setting.Advanced diagnostics
If the steps above do not resolve the issue, the following Terminal commands provide lower-level diagnostic information. Check which QuickLook handlers are active for Markdown files:.md file in another window to trigger log output):
pluginkit shows the extension but previews still fail, the logs from log stream will usually reveal whether the extension is being loaded and what error, if any, is returned.
FAQ
Answers to frequently asked questions about installation and features.
Auto-update
How FluxMarkdown keeps itself up to date via Sparkle.