The Format Tax
This paper identifies that requesting structured output formats like JSON imposes a significant "format tax" that degrades reasoning performance in open-weight models primarily due to prompt instructions rather than decoding constraints, and demonstrates that decoupling reasoning from formatting through multi-pass generation effectively recovers this lost accuracy.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are a brilliant chef who can cook a perfect, five-star meal. You know exactly how to balance the flavors, the texture, and the presentation. Now, imagine a customer walks in and says, "I love your cooking, but I only want to eat if you serve the food on a very specific, rigid gold-plated tray with a strict rule: every fork must be placed at exactly 90 degrees, and you must describe the ingredients using only a specific list of words."
You try to do it. You focus so hard on placing the forks perfectly and using the right words that you accidentally burn the steak. The meal is ruined, not because you don't know how to cook, but because you were so distracted by the rules of the plate that you forgot the art of the food.
This is exactly what the paper "The Format Tax" discovers about Large Language Models (LLMs).
The Problem: The "Format Tax"
The authors found that when you ask an AI to give you an answer in a strict format (like JSON, XML, or LaTeX), its intelligence drops significantly. It makes more mistakes in math, science, and logic.
They call this drop in performance the "Format Tax." It's like a hidden fee you pay for formatting. You expect the AI to just "think" and then "write" in a box, but instead, the act of trying to write in the box makes it forget how to think.
The Big Misunderstanding: Blaming the Wrong Thing
For a long time, researchers thought the problem was the decoder (the part of the AI that builds the sentence one letter at a time). They thought, "The AI is trying to write a JSON file, so it's getting confused by the rules of the grammar, so it makes mistakes."
They tried to fix this by building "grammar police" (constrained decoding) that stops the AI from typing anything that breaks the rules.
The paper's big discovery: The grammar police aren't the problem. The problem is the request itself.
Think of it like this:
- The Decoder (Grammar Police): This is the waiter who checks if the plate is straight.
- The Prompt (The Request): This is the customer shouting, "Put the food on the gold tray!"
The paper shows that the moment the customer shouts the request, the chef (the AI) gets nervous and starts messing up the cooking. Even if you take away the grammar police (let the chef write freely), the chef still burns the food because they are so focused on the idea of the gold tray.
The "Tax" is paid at the prompt, not the decoder.
The Solution: Separate the Thinking from the Writing
So, how do we fix this? The paper suggests a simple strategy: Decouple Reasoning from Formatting.
Imagine the chef again. Instead of trying to cook and arrange the gold tray at the same time, we ask them to do it in two steps:
- Step 1 (The Kitchen): "Chef, just cook the meal. Don't worry about the tray. Just give me the delicious food in a messy pile on the counter." (The AI thinks freely and solves the problem).
- Step 2 (The Plating): "Okay, now take that pile of food and arrange it on the gold tray according to the rules." (The AI just reformats the answer).
The paper tested two ways to do this:
- The "Two-Turn" Method: You ask the AI for the answer in plain English first. Then, in a second message, you say, "Great! Now put that answer into a JSON box."
- The "Thinking" Method: You tell the AI, "Think about this deeply first (in a hidden scratchpad), and then give me the final answer in the box."
The Result: Both methods worked like magic. By letting the AI think freely first, they recovered almost all of the lost intelligence. The "Format Tax" disappeared.
The Good News: It's Fixable
The paper also looked at the newest, most powerful "closed" models (like the latest versions of GPT or Claude). These models don't seem to pay the tax. They can cook the meal and arrange the tray perfectly at the same time.
This suggests that the problem isn't that AI can't do it; it's just that the current open-source models haven't been trained well enough to ignore the distraction of the formatting rules yet.
Summary in a Nutshell
- The Issue: Asking an AI to follow strict formatting rules (like JSON) makes it dumber.
- The Cause: It's not the technical rules of the format; it's the mental distraction of trying to follow the rules while thinking.
- The Fix: Let the AI think first (freeform), then format the answer later.
- The Future: Newer models are learning to ignore the distraction, but for now, the best trick is to split the job into two steps: Think, then Format.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.