`max_seq_len` controls one bound, what happens to examples that exceed it?

Attempt it

max_seq_len is the hard upper bound on the number of tokens in a single training sequence after tokenization and chat-template wrapping. Examples longer than the cap are truncated, almost always from the right end (suffix-truncated) by default.

The silent failure mode: right-truncation chops off the assistant response while leaving the prompt and system message intact. If most of your examples have long prompts and short responses, you may train on hundreds of sequences whose label positions are entirely masked out, the loss is technically valid but learns nothing about the actual task. The defensive setting is to pick max_seq_len large enough that the 95th-percentile full example fits, and to log how many examples are being truncated each epoch.

Your answer

**max_seq_len** is the maximum number of tokens in a single training sequence. After the tokenizer encodes the prompt and the chat template wraps it, the resulting token sequence has to fit inside this cap. If a sequence is shorter than the cap, it is usually padded with a special pad token (or packed with other short sequences). If a sequence is longer than the cap, the data loader has to drop tokens. The default behavior in nearly every framework is to **truncate from the right**, meaning the end of the sequence is chopped off until the remainder fits. In a typical chat training example with format (system, user, assistant), the assistant response sits at the right end. Right-truncation removes the response first. The system prompt and user message stay intact, but the part the model is supposed to learn from is gone. Because the loss mask only counts response positions, an example with its response truncated away contributes zero unmasked tokens to the loss. The training step still runs, the loss looks like a normal number, but that example taught the model nothing. The defensive practice is to set max_seq_len based on the 95th percentile of full example lengths and to log how many examples are being truncated each epoch.

**max_seq_len** caps the token count per training sequence after tokenization and chat templating. Overlong examples are right-truncated by default, which is where the silent failure hides. For a chat formatted example, the sequence is built as `[system tokens] + [user tokens] + [framing] + [assistant tokens]`. Right-truncation chops from the rightmost end, so the assistant tokens disappear first. The loss mask only marks assistant tokens as 1, so when those are gone the example has zero unmasked positions and the loss for that example is zero. A whole batch can be filled with examples like this without the loss curve looking wrong. The mean loss across the batch divides by the number of unmasked tokens, so an example contributing zero unmasked tokens does not push the mean either way. The training step runs, the optimizer updates, but the model effectively saw a no-op example. The practical defensive recipe: - Pick `max_seq_len` to cover the 95th percentile of full example length, not the average. - Log truncation rate per epoch so the metric is visible. - Use **left truncation** when you can: it preserves the assistant response by dropping the prompt prefix instead. - Or use sequence packing, which packs multiple short examples into one full-length sequence and reduces the pressure on the cap.

Quick reference

TL;DR

max_seq_len caps token count per training sequence; overlong examples are right-truncated by default, which silently chops the assistant response and leaves the loss with no real labels.

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

Imagine packing lunches for a school trip into identical lunch boxes. Each box has a fixed capacity, and the rule is that whatever does not fit gets thrown away from the top. You pack the sandwich first, then the fruit on top, then the dessert. When a lunch is too big and the box overflows, the dessert disappears first. If the dessert was the part the child actually loves, the lunch is now useless even though the box still looks full. max_seq_len is the lunch box size for training. The assistant answer is the dessert, the part the model is supposed to learn from. When the loader trims the end, the answer goes first while the system prompt and user message stay. The training step still runs, the loss number still looks fine, but the model learns nothing from that example.

Key concepts

Max sequence length Truncation Loss masking Sequence packing

Detailed answer & concept explanation

~10 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.

Sign in for 5 free unlocks/day or go Pro for unlimited. See Pro pricing.

Quick scan · 2–4 min

Everything important, quickly.

4 min: define max_seq_len, walk default right truncation behavior on chat data, show how it silently zeros the loss mask, and cover the defensive recipe of percentile-based caps, truncation logging, left truncation, and packing.

Real-world examples

Real products, models, and research that use this idea.

Hugging Face TRL SFTTrainer exposes max_seq_length and defaults to right truncation, which is why Llama 4 instruction tuning recipes also log the percentage of examples that hit the cap each epoch.
Axolotl provides a packed sequence option that bundles multiple short examples up to max_seq_len with cross-document attention masking, a default in the Mistral and Gemma 4 SFT configs.
DeepSeek V4 distillation recipes pick max_seq_len at the 95th percentile of full example length and use left truncation when the prompt tail is dispensable but the response must survive.
Unsloth tutorials walk users through inspecting the tokenized example length histogram before choosing max_seq_len for Llama 4 fine-tuning to avoid silent loss masking failures.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QWhy is logging truncation rate per epoch a critical signal, not just a nice to have metric?

Sign in or go Pro to see the approach for this follow-up.

QWhen does left truncation help and when does it hurt?

Sign in or go Pro to see the approach for this follow-up.

QHow does sequence packing change the picture and what new failure modes does it introduce?

Sign in or go Pro to see the approach for this follow-up.

Don't say this

Red flags and common mistakes that signal junior thinking. Click to expand.

Most common mistake

Setting max_seq_len based on average example length instead of the 95th percentile. You silently lose the assistant response from your longest examples and train on sequences that contribute nothing to the loss.

Sign in or go Pro to see all red flags and common mistakes. See Pro pricing.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.