A sharp reminder that technical bloat is the enemy of efficiency, exposing how legacy formats act as a hidden tax on AI reasoning. It’s a pragmatic lesson in digital hygiene for anyone serious about optimizing token economy.
Deep Dive
Prerequisite Knowledge
- No data available.
Where to go next
- No data available.
Deep Dive
Stop Wasting TokensAdded:
People often upload spreadsheets to their favorite large language models and ask the AI to analyze things.
You know, give me the key insights from this file and tell me what I should do about it.
And this seems like a reasonable request on the surface.
But when you understand what's going on underneath, you realize that spreadsheets are actually really bad for large language models.
In practice, this means you're paying way more for tokens and significantly increasing opportunity for hallucination and error.
So, let me explain what's going on really with spreadsheets and large language models.
You've probably used thousands of Excel files, but never even thought about what's going on inside that Excel file.
Well, what if I told you that that Excel file isn't a file at all, but a whole directory of files?
See here, I'm going to show you how to crack open an XLSX file and show you what's inside.
Then I'll explain why Excel behaves the way it does and why that makes it fundamentally the wrong tool for serious analytics work with large language models.
So here, I've grabbed an Excel file from a project that I'm working on.
I'm going to rename the file extension from XLSX to zip.
So far, so good. Nothing's changed.
But now I can unzip this file and show you something interesting.
To do this, I'm going to jump into the terminal because that's where I feel more comfortable and I'll run an unzip command over that file.
So there you go. So what you see now is a folder structure with XML files, relationship files, shared strings, styles, and then the actual sheet data.
Microsoft introduced this format in 2007, which if you're old enough to remember, was when XLS became XLSX.
It's called Office Open Office XML and it's now an international standard.
So your Excel file is actually a whole bunch of files with different use cases.
The relationship files are like a map that tells Excel how to piece the content together.
The worksheets folder is where your actual data lives.
Each sheet is its own XML file. So sheet one XML, sheet two XML, and so on.
So your one Excel file is actually a whole bunch of files with different uses.
The relationship files are like a map that tells Excel how all the pieces connect.
The worksheets folder is where your actual data lives. And each sheet is its own XML file.
The shared strings file is the quirky part. Because Excel doesn't actually short store text directly in the cell, it stores an index number pointing to this shared script strings file.
So if you type revenue in 500 cells, it only stores the word revenue once.
But this is also why it Excel can behave unexpectedly when you manipulate files programmatically.
And then you've got the styles file, which includes every bit of formatting, the fonts, the colors, the borders, etc. So why does all this matter?
Well, Excel is really convenient for humans, but it's terrible for AI.
Because the AI needs to do a lot of work to get the key insights.
When you look inside that XLSS, which is actually a zip, you can see that the data and presentation are completely tangled together. Numbers, fonts, column widths are all baked in the same file, referencing each other through a web of XML relationships.
And that's fine for a human when it's opening it in Excel, but it's a nightmare for machine trying to read it and do analytical work.
It's like cracking open a coconut so you can extract the coconut milk. There's layers of husk and shell that you need to get through.
And to do that, you're going to be burning through tokens. And of course, the more tokens you burn, the far more likely is you'll get hallucinations.
So if you want to be kind to the AI and save yourself a bunch of tokens, upload a CSV file with just the data instead.
Of course, the deeper issue is that Excel was never designed to be ingested by AI.
It was designed to be used by a human sitting at a desk looking at a screen using Excel, and the format reflects that.
The file structure is optimized for the application and for the experience of using the spreadsheet, not for making the data inside it really easily available.
So as tokens get more and more expensive, you don't want to be wasting them by making the AI do hard work by ripping open the hard shell.
Now of course, the big AI companies don't mind doing this work for you, of course.
And right now, people are already complaining about token costs.
And the thing is, we're not even yet paying full price for tokens, which will allow the investors who poured billions into AI to get a reasonable return on their investment.
We're still in the drug dealer phase where they're giving out this stuff for less than cost price to get you addicted.
But of course, as tokens become more expensive, you're going to be need to be thinking about how to make the most of your tokens.
This is just one of the key insights behind the AI solution I've developed called Kira.
I worked out a long time ago that large language models are very much like humans. If you make a task easy for someone, there's a much greater chance of them getting it right.
Throwing a horrible, messy file format like Excel at a large language model and expecting it to sort things out is a recipe for disaster.
My solution addresses that problem in a scalable and secure way.
And in doing that, our token consumption is tiny, which means we get far more value from every prompt than simply uploading a spreadsheet and hoping for the best.
If you enjoyed this video, please consider liking and subscribing. And as always, I love reading your comments and the feedback. And even if you don't agree, I try to respond to everyone.
I've also recently activated memberships for those who'd like to learn a little bit more about what we do inside Kira.
[music] So thank you and I'll see you in the next one.
Related Videos
Agentforce NOW AMA: Build with React and Salesforce Multi-Framework
SalesforceDevs
490 views•2026-05-28
How agent o11y differs from traditional o11y — Phil Hetzel, Braintrust
aiDotEngineer
450 views•2026-05-28
WEB TECHNOLOGIES UNIT-2 | Degree 4th sem BCOM Computers web technologies unit-2 full explanation💯✅
LearnwithSahera
1K views•2026-05-29
More tests are always better? How to use AI to identify tests that bring little value
Alliance4Qualification
335 views•2026-05-29
Search Algorithms Explained in 60 Seconds! 🤖💨
samarthtuliofficial
218 views•2026-06-01
People of Game of Thrones using JavaScript DOM
AltCampus
296 views•2026-05-30
Introduction to Problem Solving Part - 1 | Lecture 1 | Intermediate DSA
ascensionix
107 views•2026-05-29
🚀 BCS613C Compiler Design | Module 1 to 5 Schema Evaluation 🔥 | VTU 6th Sem 💯 #VTU #bcs613c #exam
Pranavaa-y4y
104 views•2026-06-02











