How to use
1) Paste your text → 2) Set intervals & tags → 3) Run (shortcut: Ctrl/⌘ + Enter)
Input
Options & Run
👉 Tip: No automatic spaces are added. If you want a space, include it in your template or tag (e.g., template {TAG} to add one leading space).
FAQ
What’s the difference between line and byte intervals?
Line mode counts lines (e.g., every 30 lines). Byte mode counts UTF‑8 bytes (e.g., every 1024 bytes). Note that many non‑ASCII characters occupy multiple bytes.
“Friendly” vs “Exact” in byte mode
Friendly snaps to the start of the next line, keeping text readable. Exact inserts at the exact byte boundary (without splitting multibyte characters).
Insert tag at beginning
When enabled, the first tag (with your template applied) is inserted at the very start (byte 0 / line 1). With “avoid duplicates” on, it skips if the text already starts with the same tag.
Inline insert (no line break)
Append the tag directly to the current line instead of creating a new line. No spaces are added automatically—add them in your template if needed.
Add line break after tag
Forces a newline right after every inserted tag. Combining with inline insert gives ...text{TAG}\nNext line....
What does the {TAG} placeholder do?
{TAG} is replaced with your Tag 1/2/3 values in rotation. Example: template --{TAG}-- with Tag 1 = [A] becomes --[A]--.
Skip first lines/bytes
Skip a header or front matter: start tagging after the first N lines/bytes.
Avoid duplicates & Trim
Avoid duplicates skips insertion if the exact tag text is already present at that point. Trim removes leading/trailing whitespace on the inserted tag line.
Normalize line endings (LF/CRLF)
Different OSes use different line breaks. Normalize them to avoid formatting issues across platforms.
How does 3‑tag rotation work?
They cycle as Tag 1 → Tag 2 → Tag 3 → Tag 1… Empty tag fields are skipped.
Are my settings saved?
Yes. Options and tag values are saved to localStorage and restored on reload. Use Reset to clear.
Is it safe with UTF‑8 characters?
Yes. In Exact mode, insertion only happens at UTF‑8 code point boundaries—no character is ever split.
Contact
Questions or suggestions? Email us.
Email: thenaom@naver.com