Skip to content
Advertising & partnerships4 tools in English
Something useful for sellers?Tell us about a product or service that could help people using these tools.
Get in touch contact@woorihomecost.com

Seller ToolsEveryday tools

Bulk Product Title Length Checker — CSV and Excel

Check product titles in a list, CSV or Excel table against character and UTF-8 byte limits. Keep original rows and SKU columns, compare prefixes, and export the full result.

How it works · Examples · Limits

Start with the right input

  1. A simple list: use one title per line. Empty lines remain as empty-title records so you can find them. Use a table if a title itself contains a line break.
  2. A CSV: the first row needs distinct column names. Choose the title column and, if useful, a SKU column. Other source columns stay with the result. The input accepts comma-separated CSV; it does not guess tab or semicolon delimiters.
  3. A TXT or CSV file: open the file, check the preview, then apply it. UTF-8 is the default. If the text is wrong, choose EUC-KR / CP949, UTF-16LE or UTF-16BE to match the file and read it again. Changing the encoding choice does not rewrite pasted text or a file you already applied. If your browser cannot strictly read the chosen encoding, save a UTF-8 copy in the source application and open that copy instead.
  4. An Excel workbook: use the separate .xlsx chooser and review the table as described below. After applying it, connect the title and optional SKU columns.

Remove customer details and other unnecessary columns before importing. Selecting a file or reviewing a table does not replace the current input until you apply it.

Check an Excel table before applying it

Open an .xlsx file up to 5 MiB. Older .xls files, macro-enabled .xlsm files and password-protected workbooks are not supported.

  1. Choose the worksheet, header row, last row, first column and last column. Leave out introductory notes, totals and unrelated columns. If the headers are in row 3, data begins in row 4.
  2. Correct empty or duplicate column names in the review. The selected data range can contain up to 10,000 rows and 50 columns, excluding the header row. Its converted CSV must also fit within 5 MiB. The tool does not silently shorten a range that is too large.
  3. Compare the stored and displayed examples for each column. Text SKU 00123 stays 00123. A numeric value 123 formatted to display as 00123 needs the displayed-value choice to keep those zeros. A long numeric identifier may already have lost precision in Excel; the tool cannot restore missing digits.
  4. Check the date and number choices. Automatic date conversion uses the workbook’s date system and includes a stored time when present. You can instead choose the stored numeric value or displayed text. Hidden rows and columns inside the selected range are included.
  5. If formulas are present, acknowledge that the tool uses calculation results saved in the file. It does not recalculate formulas. Missing or error results block application; recalculate and save the workbook in Excel, or prepare a values-only table.
  6. Review the preview, then apply the table. The preview shows the first 20 data rows; validation checks the whole selected range. Open a shortened cell to read its full contents. Merged cells that overlap the range must be unmerged or excluded in the source.

Applying the table keeps the current length-checking conditions. Cancelling the review keeps your current input and results. Editing the applied input by hand removes its worksheet-row mapping, because the tool can no longer confirm which original cells the edited rows represent.

Choose what a character means

You can count visible characters, Unicode code points or UTF-16 code units. These are different measurements. For example, a joined emoji or an accented letter made with a combining mark can occupy more than one code point while appearing as one character. Visible-character counting and prefix suggestions require the browser’s grapheme-segmentation support.

UTF-8 bytes measure the decoded title as UTF-8 text. They are not the original byte size of a CP949 or UTF-16 file. Excluding whitespace also excludes tabs and line breaks for measurement. Choosing LF or CRLF changes the counting copy, while the original title remains unchanged. The result distinguishes measured UTF-8 bytes from the original title’s UTF-8 bytes.

Set a limit that matches your listing field

Enable character and byte limits separately. An enabled limit accepts an integer from 0 through 10,000,000. Zero means zero; turn off the checkbox when you do not want that check. With both limits off, a title is counted only and is not marked as having passed a limit.

You can explicitly load a field-specific reference for Coupang, Amazon.com, eBay, Etsy, Google Merchant Center or Shopify. The references cover seven fields across six platforms and were checked on 2026-10-16. Loading one sets code-point counting, includes whitespace, keeps original line breaks and turns off the byte check. It leaves your list and column mapping in place, but you need to run the check again.

The Amazon.com reference is 75 characters for non-media titles from 2026-07-27. The Shopify reference is 70 characters for the product SEO title, not the ordinary product title. Read the market, field, exclusions and official link beside the selected reference. The sources do not establish every platform’s detailed emoji-counting behaviour; this tool uses a code-point count as a reference. You can edit the conditions to match the actual field you are working on.

Read the result before changing a title

  • Over limit: at least one enabled limit is exceeded.
  • Within limit: all enabled checks are satisfied under your chosen counting settings.
  • Empty title: the title is empty or contains only whitespace. It is retained for review.
  • Needs attention: the row could not be checked normally. Read its explanation before using the result.
  • Count only: both limits were off. Measurements are shown without a pass decision.

The screen previews up to 50 results. The summary still covers the full input, and exports include every row in the selected scope. Original data-row and physical-line references help you locate a CSV record; Excel imports also identify the original worksheet row.

A worked example

The title A€😀 contains 3 visible characters, 3 code points, 4 UTF-16 units and 8 UTF-8 bytes. With whitespace included, a visible-character limit of 3 and a byte limit of 7, it fits the character limit but exceeds the byte limit by 1.

A separate prefix suggestion can keep A€: 2 visible characters and 4 UTF-8 bytes. Both enabled limits are checked again. The original A€😀 stays beside it. If you turn both limits off, the same title is counted only. If you enable a character limit of 0, it exceeds that limit by 3.

Use suggestions as a starting point

Generate prefixes separately after checking. The tool stops at a whole grapheme boundary and verifies the enabled limits again; it does not rewrite the source title. It may suggest an empty prefix if the first complete character does not fit.

This is a length-based cut, not a rewrite that understands your product. Check model numbers, sizes, options and required wording yourself. A suggestion does not promise the longest possible text or acceptance by a marketplace. Length checks do not cover prohibited words, title-quality rules or required listing information.

Save results and reuse a column mapping

Choose all records or the current category, then export CSV or JSON, or copy a table. Exports are not limited to the 50-row screen preview. The full summary and conditions remain distinct from the selected rows.

JSON preserves the selected source cell values. Excel-derived JSON also includes the filename, worksheet, selected range and original-row mapping. It is not a backup of workbook formatting, formulas or the complete XLSX, so keep your original workbook.

CSV adds an apostrophe where needed to reduce spreadsheet-formula execution; a copied table also replaces tabs and line breaks inside cells with spaces. These formats preserve usable values rather than reproducing the original file byte for byte. Import SKU columns into Excel as text when leading zeros matter. Result files use UTF-8.

For a CSV layout you use often, explicitly save the title and optional SKU column mapping. On the next table, select the saved mapping, compare it with the current column names, then apply it. Selection alone does not change the input. Names must match exactly; similar or missing names are not guessed. If the saved mapping had no SKU column, applying it also leaves SKU unconnected.

Korean and English versions share these saved mappings in the same browser. The bulk title, order-profit and SKU-quantity tools share a maximum of 20 mappings. A saved mapping contains its name, connected column names and roles, tool/context identifiers, record versions and timestamps. Source rows, title and SKU values, files, filenames, results, suggestions and checking conditions are not saved.

The mapping backup is a separate JSON file for all three tools, with a 128 KiB (131,072-byte) import limit. Review names and column labels before sharing it. Restoring a backup does not apply a mapping to the current table. Deleting all mappings clears the three tools’ mappings together, while fee settings and other tools’ records remain.

Input limits and interrupted work

The original TXT/CSV file and decoded UTF-8 input each have a 5 MiB limit. Pasted input has the same decoded limit. A list or CSV can contain up to 10,000 data rows; CSV can have up to 50 columns. Empty titles count toward the row limit.

A TXT/CSV title over 64 KiB (65,536 bytes) is left as a needs-attention row while other rows continue. An XLSX cell over that size blocks table application so you can fix the source first. A small compressed workbook can still exceed expanded-content or cell limits; save only the needed table in a new workbook and try again.

Invalid CSV structure, encoding or whole-input limits need correction before a result can be made. UTF-32, Word/PDF content extraction and CP949/UTF-16 title-byte counting are not supported here. The tool does not fetch live platform limits every time it runs.

Cancelling, changing input or conditions, or leaving the tool prevents partial work from appearing as a completed result. Inputs, files and results are processed in your browser without being uploaded or kept for your next visit. Save any result you need before reloading or switching tools. Explicitly saved column mappings are the exception described above; see the privacy policy.

References and related tools

For one title, use the character and byte counter. Return to English tools or report a problem.