Protecting Photoshop files alone wasn’t enough — introducing REFLO’s cross-format support

So far I’ve introduced REFLO’s timeline and comparison modes. Today I want to talk about why those two features couldn’t stay locked to a single file format, and how REFLO came to cover several formats.

A moment almost everyone has had

A designer’s work doesn’t end with one Photoshop file. The draft is a PSD, but the project brief is written in Word, the deck for the client is built in PowerPoint, and the schedule or asset list is kept in Excel. Having files of completely different kinds mixed together inside one project is the normal picture, not the exception.

How well those files are protected, though, is all over the place. You might carefully keep versions of the design file, while the brief and the deck next to it still sit somewhere in a folder under names like “final_really_final.” And what you actually send the client at the end is often the PowerPoint deck — so the file that matters most at the most important moment is the one with the thinnest safety net.

Each program has a little of its own history. Word has Track Changes; some cloud office tools have their own version history. But those live in different places, in different ways. Every time the file format changes, you have to relearn “how do I undo this one again?”

That mismatch is why we built cross-format support

After we’d built a safety net with the timeline and made change visible with comparison modes, actually using REFLO made something odd stand out. PSD files were being protected this well — and the brief and the deck in the folder next door were still sitting there the old way.

Looked at as a whole project, protecting only the design file was no better than protecting half of it.

> Why should how protected you are depend on the file format?

That’s the question where cross-format support started. Users shouldn’t have to think differently every time — “this file was made in that program, so I have to take care of it this way.” Whatever the format, it should be equally safe.

What cross-format support is after

The goal is clear. Regardless of which program made the file, every piece of work inside one project should be protected the same way. PSD, docx, xlsx, pptx — inside REFLO they should all be recorded automatically the same way, and you should be able to leave milestones the same way. Comparison splits by format. Design and image files get visual comparison; documents like Word, Excel, and PowerPoint get text comparison.

What cross-format support looks like

1. A timeline that works the same regardless of format

Whether it’s a PSD or a Word document, the timeline stacks the same way inside REFLO. Every save is recorded automatically, work is grouped into sessions as the flow goes, and you can leave a milestone whenever you want. You don’t have to learn a new workflow just because the file format is different.

2. Comparison modes that apply smartly to the format

What you compare, though, inevitably differs by format. For design and image files (PSD and the like), showing changed areas visually is the right call, and that’s where Split, Overlay, Heatmap, and Blink (Flicker in the app) from the last post belong. Split is available for free right away; the other three modes are available in Pro. For documents like Word, Excel, and PowerPoint, instead of those four visual modes, text comparison points out changes in the writing on the document, sheet, or slides. You still pick two points on the timeline the same way; the comparison screen splits to fit the format.

3. One place, without hopping between programs

You don’t have to bounce between Photoshop, Word, PowerPoint, and Excel to check each program’s version history on its own. Open REFLO once, and you can see and go back through every format of work in the project from a single place.

What’s next

The timeline records files in a protected folder broadly, and the center of gravity for deep comparison work is currently PSD and Office (docx, xlsx, pptx). That isn’t the end. We’ll keep watching which formats designers and other creative workers use most — and miss most painfully — and we’ll keep widening support.

Per-format comparison accuracy is something we’ll keep refining too. Especially with structurally complex files like PowerPoint or Excel, we want to keep improving how precisely we can tell what actually changed.

And when collaboration lands, we’re preparing so that files of several formats can be shared and managed together inside one project as a natural continuation of this experience. We’ll invite a small number of teams to validate that first, then launch it properly.

Closing

Cross-format support may not be a flashy, eye-catching feature. But I think it’s essential if we’re going to answer the question “is my work as a whole actually safe?” Not a tool that protects only the design file, but a tool that protects the whole project. That’s what cross-format support is trying to do.

In the next post I’ll continue introducing more of REFLO’s features. Thank you for reading.