- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
- The paper approaches PPT slide generation and editing as an image generation problem rather than a PowerPoint manipulation problem.
- The paper formulates slide creation as a “unified conditional visual synthesis problem.”
Critical strengths
- Lines 42–44: I agree with the authors’ observation that the image distributions of general image generators and presentation slides are different.
- The paper explores slide generation and editing from an image-generation perspective, rather than treating them solely as PowerPoint manipulation tasks. This is an interesting direction.
Critical weaknesses
-
Lines 46, 135–146: The discussion of slide benchmarks should cite relevant prior work, including Talk to Your Slides: High-Efficiency Slide Editing via Language-Driven Structured Data Manipulation and EditPPT: Faithful Long-Deck Slide Editing via Structured....
-
Line 49: The paper describes slide creation as a “unified conditional visual synthesis problem,” but it is unclear what exactly is being unified.
-
I am not sure whether editing generated slide images should be referred to as “slide editing.” I think “image editing” may be a more appropriate term. “Slide editing” sounds more like editing individual objects within a PowerPoint slide.
-
Line 88: The paper itself refers to some operations as “deterministic PPTX transformations.” Given this, I wonder how redundant the slide-native data engine is in practice. It would be helpful to provide statistics showing how often or to what extent this component is actually needed.
-
In PPT slide editing, iterative editing is inevitably needed. For example, with Nano-Banana-2, repeated iterations in PowerPoint slide generation can cause text to become corrupted or image quality to gradually degrade. I wonder whether the proposed model exhibits similar behavior.
-
I am not suggesting that the authors necessarily need to eliminate this phenomenon, but I believe such behavior, if present, should be reported as a limitation of the paper.
-
Section 6.5: The title “More Analysis” sounds somewhat awkward. It may be better to separate the two analyses into Sections 6.5 and 6.6, or use a title that captures what the two analyses have in common.
-
The most critical weakness is the evaluation setup. Evaluating the authors’ main system primarily on a benchmark created by the authors themselves weakens the credibility of the evaluation.
-
The proposed method should also be sufficiently evaluated on the other existing benchmarks cited in the paper.
-
Figure 5: Looking closely at the slide example in the Generation Evaluation box, the rightmost 3×5 input image becomes a generated slide with labels (a), (b), ..., (e) for the columns.
-
The most noticeable weakness of the generated slide in Figure 5, in my view, is that the Figure 5 caption is center-aligned rather than justified. However, the current benchmark structure does not appear to evaluate this type of formatting issue.
-
Evaluation criteria for slides may vary considerably depending on the slide and the evaluator. This raises concerns about whether rubric-based evaluation alone is sufficient.
-
OCR results are unlikely to contain detailed information about the precise locations of text. Therefore, for slides where text placement is important, it is unclear whether OCR-based evaluation is truly effective.
-
There also appears to be substantial overlap between the OCR-based evaluation and the GPT-4.1-based evaluation. GPT-4.1 may already cover many of the aspects being assessed through OCR, and potentially additional aspects as well.
Questions for authors
-
Line 49: The paper formulates slide creation as a “unified conditional visual synthesis problem.” What exactly is being unified in this formulation?
-
Do the authors consider editing a generated slide image to be “slide editing” rather than “image editing”? Since “slide editing” usually suggests manipulating individual objects within a PPT/PPTX file, I would appreciate clarification on the terminology.
-
Line 88: Given that the paper itself refers to certain operations as “deterministic PPTX transformations,” how redundant is the slide-native data engine in practice? Do the authors have statistics quantifying how often this component is required?
-
Does the proposed model suffer from degradation under repeated iterative editing? For example, repeated edits with Nano-Banana-2 in PowerPoint slide generation can lead to corrupted text or progressively degraded image quality. If similar behavior occurs in the proposed system, could the authors report it as a limitation?
-
More fundamentally, is treating PPT slide generation and editing as an image-generation problem really the right direction?
-
Systems such as OpenAI’s GPT and Claude can directly manipulate PowerPoint applications and support detailed editing. Compared with this direction, what are the advantages of solving slide generation and editing through image generation, and why is this formulation preferable?
-
Slides are fundamentally designed to be presented and edited by people in tools such as Google Slides or PowerPoint. They may also include animations in which individual objects appear sequentially. Since the proposed image-based formulation cannot represent such characteristics, how do the authors view this limitation?
-
Figure 5: Were the (a), (b), ..., (e) labels in the generated slide explicitly specified in the instruction? If so, does the evaluation framework verify whether such details are correctly generated?
-
If alignment and other detailed layout issues, such as the center-aligned caption in Figure 5, are not captured by the current benchmark, how can the benchmark adequately evaluate slide quality when the criteria may vary across slides and evaluators?
-
For slides in which the exact position of text is important, how effective is OCR-based evaluation, given that OCR results may not capture detailed spatial information?
-
Would it be more appropriate to evaluate these aspects directly using a VLM such as GPT-4.1? Since GPT-4.1 is already used in the evaluation, what is the motivation for separately using OCR, and what does OCR measure that is not already captured by GPT-4.1?
I reviewed the paper without using AI, so there may be points I have missed. I will raise my score if the authors provide sufficient and convincing explanations. Thank you.
8 comments
W5, W6, Q4: Iterative editing
W5. In PPT slide editing, iterative editing is inevitably needed. For example, with Nano-Banana-2, repeated iterations in PowerPoint slide generation can cause text to become corrupted or image quality to gradually degrade. I wonder whether the proposed model exhibits similar behavior.
W6. I am not suggesting that the authors necessarily need to eliminate this phenomenon, but I believe such behavior, if present, should be reported as a limitation of the paper.
Q4. Does the proposed model suffer from degradation under repeated iterative editing? For example, repeated edits with Nano-Banana-2 in PowerPoint slide generation can lead to corrupted text or progressively degraded image quality. If similar behavior occurs in the proposed system, could the authors report it as a limitation?
Yes, and we now report it. We added a supplementary experiment with eight 20-round editing chains on text-dense slides from VisSlideBench-Edit, alternating a local edit (title color, one word, paragraph font, keyword bolding, or background color) with a request to undo it, each round taking the previous output as input. A round trip that changes only the title color leaves the slide essentially unchanged, but text-level edits (replacing a word, changing a paragraph's font) begin to corrupt small body text, later rounds do not repair it, and the errors accumulate; by round 20, small body text is largely garbled or missing in most chains, consistent with what the reviewer observes for Nano-Banana-2. This follows from regenerating the full slide in every round with a model trained on single-round editing pairs. We report it as a limitation in Appendix E and show a representative chain in Appendix H. In the hybrid workflow of Appendix H, text is rebuilt as native PPTX objects, so later text edits do not pass through repeated image regeneration.
W7: Section 6.5 title
W7. Section 6.5: The title "More Analysis" sounds somewhat awkward. It may be better to separate the two analyses into Sections 6.5 and 6.6, or use a title that captures what the two analyses have in common.
Thank you. We have split it into Section 6.5 (Verifier-Guided Test-Time Scaling) and Section 6.6 (Robustness to Prompt Format).
W8, W9: External evaluation
W8. The most critical weakness is the evaluation setup. Evaluating the authors' main system primarily on a benchmark created by the authors themselves weakens the credibility of the evaluation.
W9. The proposed method should also be sufficiently evaluated on the other existing benchmarks cited in the paper.
We agree that results on our own benchmark need external support. InfoVis is now evaluated on four benchmarks that we did not construct, covering single-slide generation, slide image editing, and the document-to-slide workflow. BizGenEval is reported in the paper; SlidesBench and TSBench are supplementary experiments, now reported in Section 6.3 (Table 4) and Appendix H; on SlidesGen-Bench, we re-ran the workflow with full-length decks and added the content track.
BizGenEval (single-slide generation). On the Slides domain of BizGenEval (Li et al., 2026), InfoVis reaches 46.0 / 79.8 on the hard / easy splits, the best result among the open-source models in this comparison and ahead of several proprietary systems (Table 2 of the paper).
SlidesBench (single-slide generation). SlidesBench (Ge et al., 2025) scores generated slides against reference slides (reference-based, RB) and on their own (reference-free, RF). We evaluate four image models under the same protocol on its food subset (32 slides, detailed instructions with images). InfoVis scores 68.2 overall, above Qwen-Image-Edit-2511 (64.5) and its base model FLUX.2-klein-base-9B (64.1) (Table A).
Table A. SlidesBench results. For the rows we evaluated, on the food subset (32 slides), Overall is the mean of the eight RB and RF metrics. †: all values, including Overall, as reported by Ge et al. (2025) on the full test set (195 slides), which are only indicative.
| Method | Execution (%) | RB Element | RB Content | RB Color | RB Position | RF Text | RF Image | RF Layout | RF Color | Overall |
|---|---|---|---|---|---|---|---|---|---|---|
| Nano-Banana-2 | 100.0 | 74.3 | 60.0 | 20.3 | 77.7 | 73.1 | 82.5 | 91.9 | 86.9 | 70.8 |
| InfoVis (ours) | 100.0 | 74.9 | 58.2 | 20.7 | 76.8 | 65.6 | 76.2 | 87.5 | 85.6 | 68.2 |
| Qwen-Image-Edit-2511 | 100.0 | 73.6 | 55.6 | 21.0 | 76.8 | 56.9 | 76.2 | 75.0 | 81.2 | 64.5 |
| FLUX.2-klein-base-9B | 100.0 | 73.7 | 50.9 | 21.3 | 76.8 | 52.5 | 71.9 | 81.9 | 83.8 | 64.1 |
| AutoPresent without SlidesLib† | 79.0 | 67.7 | 79.7 | 10.9 | 75.9 | 45.3 | 62.7 | 54.2 | 60.9 | 45.2 |
| AutoPresent with SlidesLib† | 84.1 | 84.2 | 92.2 | 18.1 | 67.2 | 47.8 | 73.2 | 58.6 | 64.7 | 55.0 |
TSBench (slide image editing). TSBench (Jung et al., 2026) is the slide-editing benchmark released with Talk to Your Slides; its slides and instructions are independent of our data pipeline. Its instructions are written for PPTX-editing agents, so we rewrite each one into an explicit execution instruction with an LLM (DeepSeek-V4.1-Flash), and all four image editors receive the same rewritten instructions. We evaluate the 263 instructions executable on a single slide image, and GPT-4.1 scores each output with the benchmark's prompts. InfoVis outperforms Qwen-Image-Edit-2511 and FLUX.2-klein-base-9B in total score, most clearly in text quality (4.30 vs. 3.51 and 3.77) and instruction adherence (4.12 vs. 3.44 and 3.64; Table B).
Table B. TSBench results on the 263 instructions executable on a single slide image (GPT-4.1 judge with the benchmark's prompts; each score 0–5, Total out of 30).
| Editor | Instruction adherence | Visual quality | Text quality | Image quality | Layout quality | Color quality | Total |
|---|---|---|---|---|---|---|---|
| Nano-Banana-2 | 4.73 | 4.74 | 4.75 | 4.95 | 4.84 | 4.95 | 28.96 |
| InfoVis (ours) | 4.12 | 4.15 | 4.30 | 4.90 | 4.64 | 4.88 | 26.99 |
| FLUX.2-klein-base-9B | 3.64 | 3.98 | 3.77 | 4.94 | 4.58 | 4.89 | 25.80 |
| Qwen-Image-Edit-2511 | 3.44 | 3.38 | 3.51 | 4.62 | 3.96 | 4.83 | 23.73 |
We thank the reviewer for the careful, line-by-line review and for the constructive comments on terminology, iterative editing, external evaluation, the evaluation protocol, and the image-based formulation. We number the weaknesses (W1–W14) and questions (Q1–Q11) in the order they appear in the review and address each point below; all changes in the revised paper are marked in blue, and the new experiments are in the new Appendix H; table numbers refer to the revised paper.
W1: Citations
We now cite and discuss Talk to Your Slides (Jung et al., 2026) and EditPPT (Kim et al., 2026) in Section 2 and add them to Table 8.
W2, Q1: What is unified
"Unified" refers to two things. First, the task formulation: all four tasks share one interface, y = Gθ(x, I), and differ only in the role of the optional images I, which are absent in text-to-slide generation and are the template slide image, the embedded asset images, and the slide image to be edited in the other three tasks. Second, the model: a single set of model weights performs well on all four generation and editing tasks. We have revised the paragraph at line 49 to state this explicitly.
W3, Q2: Terminology
We agree. Our model edits rendered slide images rather than objects in a PPTX file, so we now use "slide image editing" for this task in Section 1, Section 3.1, and Table 8, consistent with the title, and state this distinction in Section 3.1.
W4, Q3: Data engine and PPTX transformations
We apologize for the confusing wording. The "slide-native data engine" is our name for the entire data construction pipeline, which builds both generation and editing data. "Deterministic PPTX transformations" refers to one component of it: we construct image editing pairs by executing edits on PPTX files with code and rendering the result, so each target image is exact and reproducible, unlike methods that construct editing data by synthesizing targets with an image generator. Editing pairs make up about 16% of the continual-pretraining data (Table 7). We have revised line 88 to "code-executed PPTX edits" and clarified the terminology in Section 3.2.