Rendering modes
Local & remote files
Filemark can render a file right where you opened it — a local file:// path or a raw URL — instead of in the standalone app. This is “inject mode”, and each kind needs one permission.
Local files (file://)
Open a local document — file:///Users/you/notes.md — and Filemark renders it in the tab instead of showing raw text. For Chrome to let an extension read file:// pages you must turn on one switch:
- Go to
chrome://extensions. - Open Filemark → Details.
- Enable “Allow access to file URLs”.
Why a refresh re-reads from disk
file:// page has an opaque origin, so the in-page script can't re-fetch the file. The Reload button reloads the tab, which makes Chrome read the file fresh from disk — that's how edits show up.Remote files (https://)
Visit a raw .md/.json/.csv URL — a raw GitHub file, a gist, a docs file on someone's site — and Filemark renders it instead of the browser's plain-text view. This needs the remote-rendering permission, which you enable in one click from the Setup (rocket) button in the toolbar.
Filemark is careful here: a URL that merely ends in .json but actually serves HTML (e.g. a GitHub blob page) is left alone, so you never get hijacked into a blank viewer.
Sandboxed pages
Some hosts (raw gist, GitHub) serve content with a strict sandbox / opaque origin. Filemark still renders there, but storage-backed features fall back to chrome.storage (which works in that context) instead of IndexedDB (which is blocked). You shouldn't notice — it's handled automatically.
Open in the full app
From an injected viewer you can jump to the full Filemark app (with the sidebar, tabs, search, and panels) via the “Open in full Filemark” button in the toolbar.
Both gates in one place