Initial height should reflect expected input volume
Aliases: textarea rows · starting height · volume signifier
What it is
The visible line count of a textarea at first sight is read as a forecast of how much to write. That opening window is an initial-height volume cue. Two lines look like a one-sentence note; eight lines look like a paragraph or a short letter. The cue is how much the control appears to hold at arrival, not whether it will grow while typing, and not whether a corner can be dragged.
Why it happens
People treat the visible window as capacity. A short window elicits short answers: review reasons, return notes, and ticket comments collapse to one sentence even when the system allows more. A tall window raises the floor of effort—the empty space itself looks like assigned length, so some pad to fill it and others delay because it looks like an essay. Single-line fields cue length with width; textareas cue paragraph volume with height. These are not the same signal. If every textarea is three lines, volume differences vanish and people guess from labels that usually say “describe” without a quantity.
Studying it
Pair the same prompt with two-, five-, and ten-line starting heights; compare word count, paragraph count, time, and self-reports of “how long they want.” Factors: task type (rating rationale versus incident narrative), an extra length range, the blank-page effect. Outcomes: whether length lands in a useful band, short answers rejected, long answers clipped. Lab participants know they are watched and write longer than live support forms; the product’s median submitted length is the calibration target.
Where it stops holding
Mobile viewports are short; a ten-line start can push Submit off-screen, so the volume cue fights reachability. Browser conversion of rows into pixels shifts with font scaling, so a “five-line” mock can become two screens. For genuinely open-ended writing—journals, code, mail bodies—initial height is a viewport, not an assignment; eight lines for a paper misleads. For read-only previews of existing long text, height should follow content, not expected input.
Applying it
- Set starting rows to the volume the business actually needs: two or three for a one-sentence reason, six to eight for an incident or introduction; do not default the whole product to three.
- Check the first screen: after label and submit, the primary action should remain in view, especially on phones.
- Recalibrate from live length distributions: if median answers are far shorter than the window, shrink; if one-liners keep failing review, grow.
- Verify by removing “write at least N characters” and changing height only; the new median length should move toward the useful band.