Help

Troubleshooting

The usual suspects and how to fix them. Still stuck? Open an issue on GitHub — link at the bottom.

A local file shows raw text, not the rendered view

Filemark needs file-URL access. Go to chrome://extensions → Filemark → Details → enable “Allow access to file URLs”, then reload the tab.

A remote raw file isn't rendering

Enable remote rendering from the Setup (rocket) button in the toolbar. Note that only raw files render — a GitHub blob page (HTML that happens to end in .json) is intentionally left alone.

My edits don't show up

For a file:// document, click Reload — a local page can't re-fetch itself, so reloading makes Chrome read the file fresh from disk. Or turn on auto-refresh to poll for changes.

A CSV downloads instead of opening

Make sure the CSV format is enabled on the options page. On file://, CSV/TSV are intercepted so they render instead of downloading; if you disabled that format, Chrome's default download behavior returns.

Something looks off on a gist / raw GitHub page

Those pages are sandboxed (opaque origin). Filemark renders there and automatically uses chrome.storage for any saved state (IndexedDB is blocked in that context). If a feature seems limited on such a page, opening the file in the full app avoids the sandbox.

The page didn't update after an extension update

Chrome auto-updates the extension in the background. Already-open injected viewer tabs keep the old code until you reload those tabs — so reload the tab to pick up a new version.

Still stuck?

Open an issue at github.com/thesatellite-ai/filemark/issues with the file type, the URL or path, and what you expected — it really helps.