ZYVOPMulti-Platform Sync
SeriesAI NewsWhy ZyVOPJoin Discord
LoginGet Started
ZYVOPMulti-Platform Sync

The Developer Publishing Hub. Write once, publish everywhere, and make your work citation-ready with built-in SEO, AEO, and GEO discovery support. Zero reader paywalls.

Content

  • Categories
  • Tags
  • Badges
  • Leaderboard
  • Write Article
  • Newsletter

Company

  • About Us
  • Why ZyVOP
  • Developer API & CLI
  • Write for Us
  • Contact

Connect

  • Privacy Policy
  • Terms of Service
  • Cookie Policy
  • DMCA Policy
  • Code of Conduct

© 2026 ZyVOP. Developer Publishing Hub.

Zero paywalls · Full content ownership
All systems operational
HomeCase StudiesGoogle Slides AI is laughably bad
Case Studies

Google Slides AI is laughably bad

Google Slides offered to beautify my slide, then handed me back an image... The model isn't the problem here. The file format is.

Michael Salim
Michael Salim
Founder & Engineer of TheOpenPresenter
September 4, 2026
3 min read
Google Slides AI is laughably bad
#Programming#open-source#AI#webdev#AI agents#LLM#JavaScript#TypeScript#Google

💡 TL;DR & Key Takeaways:
**TL;DR**
Google Slides’ new “Beautify” AI merely snapshots a slide as an image, exposing how legacy slide file formats hinder true AI‑driven editing. Simpler, plain‑text formats (e.g., single‑file HTML slides) could unlock seamless, editable AI enhancements.

- The “Beautify” button converts editable content into a static image, preventing further modifications.
- Complex, backward‑compatible slide data models limit AI integration, forcing developers to choose quick visual fixes over genuine content manipulation.
- Projects like Bento, which store slides in a single HTML file, demonstrate how a lightweight, human‑readable format can enable more powerful, editable AI features.

I was making a slide in Google Slides recently when a small button appeared at the bottom: Beautify the slide.

When I clicked it, it made an image instead of updating my slides directly 🤦

I think that says something bigger about AI in office apps. The model is not the main problem. The file format is.

I thought it might have improved

A few months ago, I spent some time trying AI features in office apps. I tried Google Slides and Sheets to see what they could do. They were clunky and didn't help at all. But they were experimental so that made sense. I even had to go out of my way to enable them.

This time, I didn't have to look for anything. Google Slides added a panel on the right with templates and AI features, and this "Beautify" button appeared suddenly. Since Google was now putting it in front of me, no reason not to try it!

I had a normal slide with a heading and body, nothing too interesting. I expected Beautify to maybe move things around, fix the spacing, line up the boxes, or choose better sizes.

Instead, it generated an image from my slide with "improvements".

The result looks... fine. But it's now a picture. Meaning I can't move it, correct any typo, or any other adjustment I see fit.

My theory: the format is the constraint

AI models are very powerful nowadays. If they can generate pictures & videos, they can surely work with slides.

However, the data model of these slides are probably a large legacy structure with years of edge cases in it, and you have to guarantee you won't corrupt a billion existing documents.

For the image path, all they need to do is take a screenshot and hook it up to their existing model. Done, shipped in a quarter.

Example of AI working with plain format

I saw a project called Bento posted a few weeks ago. It's slides in a single HTML file. I think there's 2 things great about it:

  1. Everything bundled into one

  2. The data model is simple for both humans and AI

In fact, the HTML file already includes prompts for an LLM to know how to work with the file.

I think moving forward, having a simple data model is the future of most AI powered apps. Don't get me wrong, it's already very important without AI. But I think it's going to get even more so.

Slideshow apps need a standard format

If you've had to do anything programmatic with PowerPoint before, you know how much of a pain it can be. This is the hidden cost of proprietary software. Of course Google slides is not much better. I wrote an article on my journey to reverse engineer Google slides here.

We need a shared data model for slide apps

There are already some of course. ODP has existed for decades. The problem is it's not built for the AI age.

I am making one more format anyway.

xkcd 927

Yes I know, another one?

I'm building the future of presentation software called TheOpenPresenter. And the data model should be simple enough that a person can read it and an AI can work with it. Bento was a good example of how simple it can be.

I'm also not going to pretend I can make a new industry standard happen. Lots of smarter people have tried for a long time. First I need to make something that works well in TOP. If it stays simple, works well with AI, and proves useful outside TOP, maybe I can extract it into its own project later. Maybe then other people will want to use it too.

See it working

TheOpenPresenter stores its presentations as plain JSON today and I've recently hooked it up into AI.

It can read the slide structure, move an element, change text, add a new slide, or remove something that should not be there.

There's a lot more that can be improved. But for version 1, I'd say that this is a huge success.

You can try it out today at https://theopenpresenter.com

Comments (0)

Login to post a comment.

Michael Salim
Michael Salim

Founder & Engineer of TheOpenPresenter

I build https://theopenpresenter.com

Subscribe to Michael Salim's Newsletter

Trending on ZyVOP

watermarks-remover: Architecture Review & Getting-Started Guide

An architecture-focused review of watermarks-remover, examining its three-layer design, skill/service split, detection pipeline, file-format handling, security posture, optional research backends, and the important distinction between verifiable removal and best-effort rewriting.

Tomson Alex
Tomson Alex·
9 minSep 4

My Pull Request Failed — Because GitHub Actions Was Protecting the Repository

Sometimes the most useful security lessons don't start with a security audit. They start with a failed CI job. Recently, while contributing to an open-source...

Ismail ZAHIR
Ismail ZAHIR·
9 minSep 4

FinderGit 0.29.0 — open a commit like a folder

There’s a moment, reading a commit list, where you want to know one small thing: which files did that one touch?

Giovambattista Fazioli
Giovambattista Fazioli·
3 minSep 4

Refactoring Amplitude Integration in Next.js: From Build-Time to Runtime Configuration

How we solved environment variable issues in a production Next.js application using Amplitude's...

Giovambattista Fazioli
Giovambattista Fazioli·
9 minSep 4

Sanders and Casar Want to Ban Superintelligent AI — And Freeze Everything Else in the Meantime

Sanders and Casar have introduced a bill to permanently ban superintelligent AI and pause advanced development until a new federal agency sets safety rules — with penalties up to 20 years in prison. It's already drawing pushback from industry and AI safety circles alike.

Pradeep Kumar
Pradeep Kumar·
4 minSep 4