Do you need Obsidian Publish?
Compare Quartz and hosting options

This table is not a ranking that compares all functions. Being able to build with Quartz does not mean the same service features as Publish or successful delivery from GitHub Pages.

Instead of the user's storage room, we prepared three fictional Japanese Markdown and one SVG created by the author directly. Frontmatter's title/tags/date, wiki link, and attachment are eligible. The date is a fixed value in the fixture, not the web publication date.

fixture/
  index.md
  手順/確認.md
  参考.md
  assets/fixture-diagram.svg

index → 手順/確認 → 参考 → index

The full text of the entrance file is 340 bytes. This is not a record created by the Obsidian editor.

---
title: 著者作成の公開前メモ
tags: [検証]
created: 2026-09-30
modified: 2026-09-30
---

# 著者作成の公開前メモ

これはローカルビルドのための架空の短文です。利用者の記録ではありません。

次は [[手順/確認|確認ノート]] を開きます。

![[assets/fixture-diagram.svg]]

1. I checked the v4 branch of the official Quartz and deployed the source archive of commit d25a6eabf96751ffca56f8a8139272def7a65041 in scratch.
2. Checked the build process of README, MIT license, package.json, package-lock.json, and CLI. The package version is 4.5.2, and the required version is Node 22 or higher and npm 10.9.2 or higher. The actual environment was Node 24.19.0 and npm 11.9.0.
3. npm ci was executed with a fixed lockfile. 491 packages are installed and exit 0. The 597 entries of lockfile are records that include dependencies such as compatible OS, and do not mean the same as the number of installation displays. The bytes of the original lockfile have not changed.
4. I changed my private settings and created it with Quartz CLI for three notes. The following will explain the setting change and the first failure.

The form of the executed command is as follows. The input and output folder in the example specifies the location you have prepared.

npm ci --no-audit --no-fund
node quartz/bootstrap-cli.mjs build   --directory /path/to/fixture   --output /path/to/generated   --concurrency 1

The execution log leaves the absolute path in scratch and the isolated npm cache designation. The path shown here is a replacement for explanation. A command that omits audit does not mean that it has passed a dependent security audit. The article is not a record of the deployment procedure to a public server.

Changed settings in this local example

Both builds exit 0, each 20 file was generated. I leave a record of the initial creation and the failed browser, and check the product after the configuration change in a separate folder. It does not extend to the conclusion that the standard Quartz does not communicate externally or the compatibility of formulas.

I opened the product on the local server and checked the four widths of 320/390/768/1440 px. I read the title, Japanese text, verification tag, and SVG, and actually clicked on the entrance → confirmation → reference → entrance at each width. It is a limited confirmation of a total of 12 clicks.

For all eight generated files—three HTML files, one CSS file, two JS files, contentIndex, and an SVG—the bytes and SHA256 of the actual localhost HTTP responses matched the generated originals. The attached SVG also matched its input original. At the four tested viewport widths after the settings change, there was no horizontal overflow and no console, page, or resource error on the tested page.

Graphs and backlink widgets in the image are displayed, but I haven't tried all of their functions. Since the body heading was also written in the fixture, it overlaps with the title of the article on the Quartz side. It is not counted as proof of current fee confirmation, SEO performance, large Vault, and web publication.

The following file is the same bytes as the original actual build input. Keep the relative path of the table and manage the attachments you refer to together with Markdown. The capture on the reader's side and the build of another environment have not been verified.