obsidian:// URI Scheme Complete Guide — All Actions and Pitfalls

name of new is the new note name, and the storage destination is left to the "Default location for new notes" of Obsidian. file is a value that includes the storage destination from the Vault route. The official states that file takes precedence over name, and I:N2 also saved it to the file specified destination. In S:N01, only name is stored in a pre-set default folder.

obsidian://new?vault=Practice&file=Inbox%2FURI-test&content=Hello%20World

If you want to leave the existing text and add it, pass append=true. I:N3 retained the existing text and added it. overwrite=true is specified to replace the existing text, and there is a separate original text/stored record in I:N5. The official statement says "overwrite only if append is not set", and it was added in both specifications of S:N03. There is no need to mix overwriting specifications with daily text additions.

obsidian://new?vault=Practice&file=Inbox%2FURI-test&content=Another%20line&append=true

silent=true's I:N4 maintained the displayed notes while creating a saved file. clipboard=true's S:C01/C02/C03 saves the author text of the dedicated screen to new/daily/unique. The clipboard text was saved in S:C04, which also passed content at the same time. This set of priority results cannot be extended to all forms of all terminals.

An example of combining text and properties

S:M03 passed the documented new, append, and content to the existing author note. In the actual saved file, the title is the value of the added side, the existing kept is retained, the tags contain both, and the body is added to the end. The following is the full text of Markdown saved by 121bytes. I have not tried types, duplicate keys, and complex YAML other than this group.

---
title: 追加の題
kept: 元の値
tags:
  - 初期
  - 追加
source: URI
---

元の本文。

追加の本文。

Download the original Markdown of S:M03

Creating a new absolute path is not included in the success story

The official new section describes a globally absolute path. S:N02 did not create a file when conflicting vault/name/file parameters were also supplied. A separate trial, T:P1, supplied only path and content for a file that did not yet exist inside the registered author-created Vault. After 6 seconds, the target file still did not exist and the index remained on screen. This records one Linux app invocation path; it does not establish the cause or a defect across all environments.

For a heading, include ノート名#見出し in the file value; for a block, include ノート名#^block-id, then encode that value. I:O5 confirmed navigation to a heading in the author’s note. Block IDs use only letters, digits and dashes, following the character rules in the archived Internal links documentation.

ノート/長い対象 メモ#^target-01
↓ fileの値をエンコード
%E3%83%8E%E3%83%BC%E3%83%88%2F%E9%95%B7%E3%81%84%E5%AF%BE%E8%B1%A1%20%E3%83%A1%E3%83%A2%23%5Etarget-01

The initial S:O01 used an author-created sample, ^著者block, containing Japanese text. It did not yield valid evidence of the scroll position. We did not count this as a product failure. We added T:B1, using a valid ^target-01 in a long note in a separate Vault. Opening the URI from a separate index note opened the target note and brought the previously off-screen paragraph into view.

In the actual reading, the top of the target paragraph was from 1905.65625px to 467.59375px (display height 1000px), and the scrollTop was 1438. The original 2Markdown is unchanged with bytes and SHA256. The previous position, the standard of another note, and the movement are left on three screens.

# 長い対象 メモ

確認前の著者段落 1。この文章は移動位置を確かめるための短文です。

確認前の著者段落 2。この文章は移動位置を確かめるための短文です。

確認前の著者段落 3。この文章は移動位置を確かめるための短文です。

確認前の著者段落 4。この文章は移動位置を確かめるための短文です。

確認前の著者段落 5。この文章は移動位置を確かめるための短文です。

確認前の著者段落 6。この文章は移動位置を確かめるための短文です。

確認前の著者段落 7。この文章は移動位置を確かめるための短文です。

確認前の著者段落 8。この文章は移動位置を確かめるための短文です。

確認前の著者段落 9。この文章は移動位置を確かめるための短文です。

確認前の著者段落 10。この文章は移動位置を確かめるための短文です。

確認前の著者段落 11。この文章は移動位置を確かめるための短文です。

確認前の著者段落 12。この文章は移動位置を確かめるための短文です。

確認前の著者段落 13。この文章は移動位置を確かめるための短文です。

確認前の著者段落 14。この文章は移動位置を確かめるための短文です。

確認前の著者段落 15。この文章は移動位置を確かめるための短文です。

確認前の著者段落 16。この文章は移動位置を確かめるための短文です。

確認前の著者段落 17。この文章は移動位置を確かめるための短文です。

確認前の著者段落 18。この文章は移動位置を確かめるための短文です。

確認前の著者段落 19。この文章は移動位置を確かめるための短文です。

確認前の著者段落 20。この文章は移動位置を確かめるための短文です。

確認前の著者段落 21。この文章は移動位置を確かめるための短文です。

確認前の著者段落 22。この文章は移動位置を確かめるための短文です。

確認前の著者段落 23。この文章は移動位置を確かめるための短文です。

確認前の著者段落 24。この文章は移動位置を確かめるための短文です。

確認前の著者段落 25。この文章は移動位置を確かめるための短文です。

確認前の著者段落 26。この文章は移動位置を確かめるための短文です。

確認前の著者段落 27。この文章は移動位置を確かめるための短文です。

確認前の著者段落 28。この文章は移動位置を確かめるための短文です。

確認前の著者段落 29。この文章は移動位置を確かめるための短文です。

確認前の著者段落 30。この文章は移動位置を確かめるための短文です。

確認前の著者段落 31。この文章は移動位置を確かめるための短文です。

確認前の著者段落 32。この文章は移動位置を確かめるための短文です。

確認前の著者段落 33。この文章は移動位置を確かめるための短文です。

確認前の著者段落 34。この文章は移動位置を確かめるための短文です。

確認前の著者段落 35。この文章は移動位置を確かめるための短文です。

確認前の著者段落 36。この文章は移動位置を確かめるための短文です。

確認前の著者段落 37。この文章は移動位置を確かめるための短文です。

確認前の著者段落 38。この文章は移動位置を確かめるための短文です。

確認前の著者段落 39。この文章は移動位置を確かめるための短文です。

確認前の著者段落 40。この文章は移動位置を確かめるための短文です。

確認前の著者段落 41。この文章は移動位置を確かめるための短文です。

確認前の著者段落 42。この文章は移動位置を確かめるための短文です。

## 対象の節

ブロック移動を確認する著者用本文です。 ^target-01

Download the complete long-form original Markdown for T:B1

The short form obsidian://vault/Vault名/ノート名 and obsidian:///絶対パス are abbreviations for open. S:H01/H02 each displayed the author notes. Check the handling of values in Japanese, spaces, and separators in the same way as normal parameters.

It is officially stated that daily requires Daily notes, and unique requires a Unique note creator core plug-in. The first time I:D1/U1 could not create a file and left the failure record as it was. In another later plan, we prepared a storage folder for a real author and observed I:D2 to create a daily file from the index and I:U2 to create a proper name file. We do not determine that this assumption change is the only cause of failure.

obsidian://daily?vault=Practice&content=Daily%20entry
obsidian://unique?vault=Practice&content=Unique%20entry

The archived official text states that daily accepts the same parameters as new. However, in S:D01/D02/D03, the destinations specified by name, file and path were not created; the content was appended to 日次/2026-09-30.md in the Daily notes settings instead. These observations support using new for a new note with a specified name and daily for input to a daily note, while checking the actual file to confirm the final save destination.

S:D04 was saved daily while maintaining the index display in silent. S:D05 retained the original text by specifying both append and overwrite, but since daily without a flag was also added, the contribution of append alone and the operation of overwrite alone have not been confirmed.

The official explains that the return to x-success includes name (no extension), url (obsidian URI), and desktop file (file URI). It is different between the success of saving and the fact that the caller has received the return. S:X01/X02/X03 observed the storage of the note, but there was no reception in the author's localhost HTTP recipient. The prepared BROWSER adapter has not been executed, and the OS and caller handoff have not been confirmed.

The official documentation states that hook-get-address for Hook returns to x-success when supplied; otherwise, it copies the current note’s Markdown link to the clipboard. In S:K01, the author’s clipboard sentinel remained unchanged, and S:X04 received no callback. Hook itself was not run. With the nonexistent Vault in S:X05, the actual “Vault not found” dialog appeared, but no x-error was received. We do not interpret an error dialog as callback success or as proof of a product defect affecting all callbacks.

The confirmation date is September 30, 2026 UTC. Using the officially distributed Obsidian AppImage1.13.7, using a Linux app deployed in an existing environment, both the app and the Installer were read as 1.13.7 on the actual General screen. Start the app URI reception with CLI, and the note standard selection and setting screen is an actual GUI operation. Auxiliary API is used for initial settings/layout and reading DOM, metadata, and saved status, and does not replace file creation/addition/block movement with API writing. The clipboard was prepared with API to assist only the author's text of the dedicated DISPLAY.

The text, screen, and JSON were saved without processing, and bytes/SHA256 were fixed in the receipt of each GUI verification. The first failure or invalid author samples have not been erased. The image and download of this article is a copy of the original byte. The OG image also uses the original PNG after the block move, and does not generate a fictional UI. After running, the own app/Xorg process records the termination 0 and confirms the release of DISPLAY78 and CDP9229 separately.

• Obsidian official URI original text (fixed commit) / acquired original text
• Official Internal links: Valid block ID / Original
• Official Properties original / Daily notes original / Unique note creator original
• I original 19 receipt / S additional 37 receipt / T target 2 receipt

The receipt above identifies the scope of the original private records. The selected files copied into this article do not constitute distribution of the entire archive. This verification does not evaluate search indexing, search traffic, synchronization, productivity, or the success of SimpleMemo features.

The original's matching range and verification conditions. The fixed 38 item is an input record, distinguishing between the finite effect observation of the 24 item and the lack of the 14 item.

specification, you can assemble the value with the URI generator and check the storage destination and text in a short note for work. If you stop at the startup stage, go to shortcut handling guide. If you want to select the entire input method to Obsidian, proceed to Obsidian configuration guide.