AI Tech Inspire

ICLR 2027 LaTeX Tables: Can You Use footnotesize and resizebox Safely?

If you’re polishing an ICLR 2027 paper and wrestling with table formatting, you’re not alone. The tension is real: keep everything legible and professional while staying inside strict style rules. At AI Tech Inspire, we spotted a recurring question from authors: how far can you go with \footnotesize and \resizebox without risking a formatting flag—or worse, a desk rejection?

Fast facts from the submission scenario

  • Paper uses the official ICLR 2027 LaTeX style without changing margins, page size, or global fonts.
  • Some main-text tables are set in \footnotesize.
  • Two wide tables are wrapped in \resizebox{\linewidth}{!}{...} to fit the column width.
  • Official instructions advise not changing font sizes, with a possible exception for references.
  • The style file appears to define \small and \footnotesize at the same size.
  • Main concern: \resizebox may scale the table (and its text) further.
  • Open questions: Is \footnotesize acceptable inside tables? Is \resizebox acceptable if legible? Could either realistically cause a desk rejection?
  • Preference for answers grounded in ICLR policy or direct AC/reviewer experience.

What the rules usually mean in practice

While each year’s call for papers can evolve, most top-tier ML venues take a pragmatic stance: don’t tweak the style file, margins, or global font; keep everything readable; and avoid tricks that stuff more content per page. In that spirit:

  • \footnotesize in tables is commonly used to improve layout density. If the style file sets \small and \footnotesize to the same size, calling \footnotesize won’t actually shrink text—so there’s no practical change to font size, just a local declaration.
  • \resizebox horizontally scales everything in the table—text, rules, symbols. That’s the risky part, because it can push text below a de facto minimum readable size even if the table fits the width.

Key point: even if no rule explicitly bans smaller text inside tables, the general expectation is that all content must be readable on standard displays or printouts without zoom. If your scaling makes numbers look like fine print, you’ve crossed the line—regardless of whether the style technically allows it.

Could this cause a desk rejection?

Hard truth: the easiest desk rejections come from clear, objective violations—modifying margins, exceeding page limits, breaking anonymity, or using a non-compliant style. Tables are a subtler case. Based on norms observed across major ML conferences:

  • Low risk: Using \footnotesize if it doesn’t change size under the official style, or if the text remains plainly legible and within expected norms.
  • Moderate risk: Using \resizebox to force-fit a wide table if it drives font sizes down to the point where readers must zoom to read. Any sign of squeezing more content than the format permits can raise flags.

Some venues run automated checks on PDF fonts and sizes; others rely on human spot checks. Either way, readability and fairness (no space hacks) are the spirit of the rule. Desk rejection is unlikely for a clearly legible table in a standard style, but it’s not impossible if scaling is aggressive.

Practical heuristic: If you need 125% zoom on a laptop to read the table comfortably, it’s probably too small.

Safer alternatives to keep tables crisp (without shrinking text)

Before reaching for \resizebox, try these layout-first strategies that respect the style and keep fonts honest:

  • Use booktabs and lean rules (\toprule, \midrule, \bottomrule) to reduce clutter and improve readability.
  • Reduce horizontal padding: \setlength{\tabcolsep}{4pt} (or slightly lower if still readable). This tightens columns without shrinking text.
  • Increase line spacing inside tables: \renewcommand{\arraystretch}{1.05} for a cleaner look that can offset narrower columns.
  • Let columns flex: adopt tabularx with X-type columns to auto-balance widths instead of scaling the whole table.
  • Break long headers with makecell or manual line breaks: \makecell{Validation\\Accuracy}.
  • Rotate only the header text (not the whole table) with \rotatebox for space-heavy labels like dataset names.
  • Use siunitx to align numbers at the decimal point. Tighter columns keep the table compact without font changes.
  • Abbreviate wisely: provide a legend below the table or in the caption so columns can use short labels.
  • Split mega-tables: keep the essential slice in the main paper, and move the full version to the appendix.
  • Wrap long text columns with p{width} or m{width} to avoid sprawl while maintaining font size.

These techniques signal that you’re optimizing layout, not gaming space limits—exactly the kind of attention to detail reviewers appreciate.

When (and how) to use resizebox

If a table is only slightly too wide and all other tactics are exhausted, a cautious \resizebox{\linewidth}{!}{...} can be acceptable—provided the result is clearly legible at 100% zoom on a typical 13–15 inch laptop. Guardrails to follow:

  • Aim for minimal scaling (e.g., 95–98%). If you find yourself at 80% or lower, reconsider the design.
  • Prefer structural fixes first (column wrapping, abbreviations, tabularx).
  • Don’t use \resizebox to pack more rows/columns than reasonably fit; that’s a red flag.
  • Ensure vector fonts are embedded and not rasterized; tiny rasterized text is an instant readability fail.

Quick self-audit before submitting

  • 100% zoom legibility test: can someone read the smallest numbers without squinting on a standard laptop?
  • Print-to-PDF check: if available, run a preflight or simply “print” to see if thin table rules or tiny digits disappear.
  • Column density sanity check: if your table squeezes 20+ columns in a single-column layout, you likely need to split it.
  • Caption clarity: does the caption explain abbreviations so headers can be shorter?
  • Bold/italics restraint: use \textbf and \emph sparingly; heavy styling can worsen readability at small sizes.
  • Appendix migration: move extended ablation tables and exhaustive benchmarks to the appendix; keep the main table business-critical.

Power-user tip: to verify fonts are embedded and scalable, run a PDF inspection tool. On many systems, a quick check via a PDF viewer’s properties or a command-line utility will confirm font embedding. If fonts aren’t embedded or appear as bitmaps, regenerate the PDF with standard LaTeX engines and avoid exotic pipelines that rasterize pages.

Why this matters for developers and engineers

Table design isn’t just aesthetics; it’s about signal-to-noise. For developers and engineers sharing reproducible results—latency breakdowns across CUDA kernels, model performance across datasets, or ablations over optimizer settings—the table is often the first artifact readers scan. A legible table:

  • Makes comparisons effortless and trustworthy.
  • Reduces misread values and reviewer frustration.
  • Signals discipline in reporting, which indirectly boosts credibility of the whole paper.

Equally, a table forced into a column with micro-fonts can make strong results look dubious. When in doubt, prioritize clarity over density and link to a comprehensive appendix or repository for the full matrix of results (e.g., a supplemental CSV or notebook).

Bottom line from AI Tech Inspire

Using \footnotesize inside tables is typically safe if it doesn’t materially shrink text under the official style. \resizebox can be acceptable when used sparingly and only if the output remains clearly legible at 100% zoom. The real risk begins when scaling turns tables into fine print or appears to circumvent space limits.

ICLR policies can evolve, so the safest path is to re-check the 2027 author guidelines and the provided style file, keep readability front and center, and prefer structural table improvements over global scaling. If a wide table is essential, keep the main paper’s version readable and move the exhaustive variant to the appendix. That balance respects both the letter and the spirit of format compliance—and keeps your work reviewer-friendly.

Recommended Resources

As an Amazon Associate, I earn from qualifying purchases.