Design
Why Korean product pages run so long
Korean detail pages are long because of how the space is divided, not taste — the channel draws name, price and reviews, leaving a seller one block of body images. Order, image count, mobile width.
Korean product detail pages are long because of how the space is divided, not because of taste. The sales channel already draws the product name, price, options and reviews, so the only area a seller fills is a single block of body images. Everything a brand wants to say gets pushed into that one block, and the page grew long. Move your home-market page over as it is and the problem is not only that it looks short — whole sections that page never had are simply missing.
How long is long — length and image count
The body is one column of images stacked vertically. Ten to thirty swipes on a phone is a common length, and the same content is uploaded as 10 to 30 separate files. Each file is cut at roughly 1,000 to 1,500px tall for two reasons — a taller file is heavier and loads late, and fixing one line later means rebuilding that whole file.
Add the heights up and 6,000 to 15,000px is common. Length itself is not the goal. Items with a lot to verify run long; items you can judge on sight finish short.
| Section | What goes in | Image count |
|---|---|---|
| Opening | One product shot and a one-line summary | 1 to 2 |
| Summary | 3 to 5 reasons to choose it | 2 to 4 |
| In use | How it is used and its size | 3 to 6 |
| Detail | Material, ingredients, functions | 3 to 8 |
| Measurements | Dimensions, capacity, colour table | 1 to 3 |
| Required items | Mandatory disclosures by category | 1 to 2 |
| Notices | Delivery, exchange, return | 1 to 2 |
What goes in, and in what order
One rule sets the order — the decision has to finish inside this page, without opening another screen. That is why delivery, exchange, return and certification, which many countries keep on separate pages, sit inside the body. Reasons to choose go near the top, facts to verify in the middle, and the things that stop an order near the bottom.
The first 3 images have to settle what the product is and who it suits. Further down is where people who already lean toward ordering come to check, so anything that could change a decision goes unread if you place it late.
For each product category, the information a listing must display is fixed by a government notice — it is called the product information disclosure notice. You do not have to hunt for the list. The channel's product registration screen lays those items out as empty fields, so filling the fields covers it. The fields change with the category you pick, so settle the category before you register.
Why is the text baked into the images
Channels allow only a narrow set of typefaces and layout controls in the body. When line breaks, weights and colours have to land exactly where you want them, an image is the faster route. Add a narrow screen that makes real tables hard to place as text, and putting sentences on top of images became the default. The page looks the way you drew it, but there is a cost.
Korean sets one character per square cell. On a narrow width, where the line breaks changes reading speed a great deal, and as live text that break point moves with the device and the font. As an image, the line breaks in the same place on every device — that certainty is the reason images win.
Where does text inside an image catch
| Where it catches | When it shows up | What to do now |
|---|---|---|
| Translation | When you add one more language | Keep the sentences in a separate document |
| Search | When only text fields are read | Key terms in product name, summary, option names |
| Reading | When zoomed or heard aloud | Pair alt text with a written summary |
| Edits | When one line of price or contents changes | Keep the source files with layers intact |
Translation catches hardest. Sentences inside a picture are invisible to automatic translation, so every language you add means re-typesetting 20 images if there are 20. Search crawlers do not read text inside an image as body copy either — the fields entered as text, such as product name, summary and option names, are nearly all that search sees. For someone listening to the page, the image area is simply empty.
How wide is the screen on a phone
Phone widths mostly fall between 360 and 430px — the unit a browser counts the screen in. Body image originals are usually built 860 to 1,000px wide, and that original is scaled down whole to fit the screen. A 1,000px original lands at about 39% on a 390px screen. Text set at 40px in the original reads at around 16px on the phone.
That is why a detail page built for a desktop screen falls apart at the text first when it is moved over unchanged. Set body text at 36 to 40px or more in the original, and even small notes at 28px or more. Width values differ by channel, so check that channel's own guidance once before you upload.
What carries over and what has to be rebuilt
| Item | Carries over | Rebuild |
|---|---|---|
| Product photo originals | Use as they are | — |
| Colour and logo rules | Use as they are | — |
| Text sitting on images | — | Typesetting as well |
| Typeface | Keep for numerals and Latin | A separate Korean face |
| Section order | — | Rebuilt for one page |
| Measurements | Figures stay | Add a cm measurement table |
| Required disclosures | — | Matched to the category fields |
Latin typefaces do not contain Korean characters. For the Korean edition, pick one Korean face with a comparable range of weights and keep numerals and Latin in the original face; the overall impression stays close. Photos usually do not need reshooting, but if no shot shows the size in someone's hand, prepare that one shot.
What to do today
Open the detail page you sell today on a phone and count how many images have text inside them. Then check whether the source files for those images still exist with their layers intact. Thirty minutes is enough. Those two numbers are exactly the volume you will re-typeset for the Korean edition.
