A readable manuscript is not automatically ready for KDP. Check ordinary paragraphs, inline images, a table, and an unusually long paragraph as separate rendering questions, then keep local preview evidence separate from anything observed in Kindle tools.
The controlled sample has three chapters, two inline images, one two-column table, and one 604-character paragraph. Starting chapter counts are 51, 69, and 620 characters. The recorded layout is h2 with two open tabs. The title-specific run prepared and read the structure, but did not visually inspect horizontal preview, so the status is partial. The untouched three-chapter sample is the return point.
Split horizontal inspection into four observations
A product-independent review checks normal paragraph breaks and indentation first, image order and surrounding text second, the table’s two-column relationship third, and wrapping in the 604-character paragraph last. A single “looks fine” result can hide a table overflow or an image-specific spacing problem.
For each item, record the chapter, expected order, observed rendering, and source location to repair. Fix the manuscript or its image/table markup, not the preview surface. Reopen the same sample after a correction and make sure the repair did not move the problem into another chapter.
Run the same three chapters in a fixed order
Chapter 1 carries short prose and one image. Chapter 2 carries the second image and the two-column table. Chapter 3 carries the 604-character paragraph. Before previewing, confirm three chapters, two images, one table, and one long paragraph.
In horizontal mode, inspect ordinary prose, images, table, and long paragraph in that order. The table must preserve readable column relationships, not merely exist. The two images must appear in the expected order relative to the prose. The long paragraph must remain complete without unexplained gaps or overlap. Close and reopen the view, then confirm that chapter order and element counts remain unchanged.
Stage 4 established structure, not visual rendering
The eleven title-specific operations prepared all four test elements. Readback reported pattern=h2, open_tabs=2, linked_scroll=null, and chapter character counts of 51, 69, and 620.
Those values establish the controlled input. They do not show how paragraphs, images, the table, or wrapping looked in horizontal preview. Screen capture was outside the run, so structure preparation cannot be promoted to a visual pass.
Keep Rune Studio and KDP claims separate
Rune Studio’s public documentation says preview can switch between horizontal and vertical writing and update with edits. That is a Stage 3 capability, not visual evidence from this run.
A local preview also cannot certify Kindle rendering or KDP acceptance. After local inspection, the exported file needs a separate check in Kindle Previewer and against current KDP guidance. No external retailer check was performed here.
Next verification and stop lines
Open the unchanged three-chapter sample in Rune Studio’s horizontal preview and record all four observations. Then inspect the generated file in Kindle Previewer, keeping local and external results in separate columns.
Stop the upload if there are not two images, the table is not readable as two columns, the 604-character paragraph is incomplete, or chapter order changes. Return to the untouched sample and the specific source element. STUDIO-488 covers encoding, 494 image paths, 497 logical navigation, and 551 editor fonts. This article remains limited to horizontal rendering. The Rune Studio product page lists the current preview scope.
