Skip to main content
Ink·tab

10 platform limits, one screen

Korean resume 500 · X 280 · Instagram 2200 · Smart Store 50 · Naver title 40 byte. Live, in one place.

  • Korean resume — incl. spaces
    Saramin · some Incruit · Korean default
    113/500
  • Korean resume — excl. spaces
    Jobkorea · some public-sector
    90/500
  • X (Twitter)
    weighted · CJK = 2 · URL = 23
    188/280
  • Instagram caption
    code point — Hangeul / emoji = 1
    113/2200
  • Naver blog title
    EUC-KR byte · safe SERP margin
    189/40
  • Smart Store product name
    code point · Naver rule
    113/50
  • YouTube title
    code point
    113/100
  • LinkedIn headline
    code point
    113/220
  • Meta description
    Google SERP truncation boundary
    113/160
  • OG description
    KakaoTalk · Slack · iMessage cards
    113/60

Everything happens in your browser. Nothing is uploaded.

When to use it

You're drafting a Korean self-intro essay (자소서) and want to confirm the 500-char limit (with and without spaces) at the same time, weighing a single tweet in Korean against X's weighted-280 ceiling, or checking a Smart Store product name (50 chars) against a Naver blog title (40 EUC-KR bytes) against a YouTube title (100 chars) — all in one screen.

Ten platforms at once

| Platform | Unit | Limit | Notes | |---|---|---|---| | Korean resume (incl. spaces) | code point | 500 | Saramin, some Incruit, Korean default | | Korean resume (excl. spaces) | code point − ws | 500 | Jobkorea, some public-sector | | X (Twitter) | weighted | 280 | CJK = 2, URL = 23 | | Instagram caption | code point | 2,200 | Meta official | | Naver blog title | EUC-KR byte | 40 | Safe SERP margin | | Smart Store product name | code point | 50 | Naver rule | | YouTube title | code point | 100 | | | LinkedIn headline | code point | 220 | | | Meta description | code point | 160 | Google SERP truncation | | OG description | code point | 60 | KakaoTalk · Slack · iMessage cards |

Counting units

  • Code point — Unicode code point. Hangeul syllables, Han characters, and emoji each count as one.
  • Byte (EUC-KR approx.) — ASCII = 1, everything else = 2. True EUC-KR can't encode every character, but this approximation is the standard for Korean SEO usage.
  • Weighted (X) — Latin / general punctuation (cp < 0x250 or 0x2000–0x206F) = 1, everything else = 2. URLs (https?://) count as 23 regardless of length. A simplified twitter-text.

Gauge colors

  • Grey — under 80%
  • Brand accent — 80–100%
  • Red — over the limit

Privacy

Resume drafts, unpublished tweets, private product names, blog outlines — none of it leaves the page. Counting uses only JavaScript built-ins ([...text].length, TextEncoder, regex); no external libraries.

Not the right tool when

  • Body-length statistics (words, sentences, reading time) — that's N°XX text-stats. This tool is for limit checks across SNS, hiring, and SEO platforms.
  • Skipping markdown / HTML tags — this counts raw text. Render to plain in markdown preview first, then paste back here.
  • Excluding regions (code blocks, comments) — not supported. Everything is counted.

Text stays on the page

Resume drafts, unpublished tweets, private product names, blog outlines — none of it is uploaded. Counting uses just [...text].length, TextEncoder, and regex; zero external libraries.

Frequently asked questions

Why are there two rows for Korean resume?
Korean job sites all say '500 chars' but split on whether spaces count (Saramin, Incruit, Jobkorea differ). Showing both lets you stay safe regardless of which site you target.
Is X's CJK = 2 rule correct?
Yes — X's weighted-character rule is canonical. CJK ranges (Hangeul, Han, Japanese) count as 2; Latin ranges 1; URLs are 23 regardless of true length (t.co shortens). This tool counts cp < 0x250 or 0x2000–0x206F as 1, everything else as 2 — a simplified twitter-text. Accuracy is ~99% with rare emoji / surrogate-pair edge cases off by ±1.
Where does Naver blog title's 40-byte limit come from?
Naver blog has no posted limit, but search results truncate around 40–50 EUC-KR bytes (~20–25 Korean chars). 40 bytes is the safe SEO margin. Longer titles still publish but get cut off in SERPs.
How are emoji counted?
By code point (`[...text].length`) — one each. Emoji that take a UTF-16 surrogate pair still count as one. In byte mode (Naver), anything non-ASCII is approximated to 2 bytes. In X weighted, code points above the BMP weight as 2.
Is the meta description 160-char limit absolute?
It's Google SERP's typical truncation boundary. Mobile cuts shorter (~120 chars) and the cutoff varies by query and device. 110–160 is the safe range. The OG description 60 is the same idea — desktop card truncation on KakaoTalk, Slack, and iMessage.