The client says nothing changed and the package is forty megabytes bigger. Or you edited one slide and the whole course was rebuilt. Drop in both versions and see which files actually differ, byte for byte, rather than trusting the publish date.
Free · No account · Your files never upload
Both are read on your computer. Neither is uploaded.
The one you want to compare against.
Takes two published packages and compares them file by file, reporting what was added, removed, changed, and left alone, with the size of each.
Either the client insists nothing changed and the package is forty megabytes bigger, or you edited a single slide and want to know why everything was rebuilt. Both are answered by comparing contents rather than by looking at the publish date, which tells you only when somebody pressed the button.
Authoring tools regenerate identifiers and timestamps on every publish, so most files differ even when the content did not. When nearly everything has changed, that is what happened, and the tool says so rather than letting you conclude the course was rewritten. It is the difference between a useful comparison and a misleading one.
It compares bytes. It cannot tell you what a learner would notice, because a one-character change to a script and a complete rewrite of a slide both show as one changed file. For that, look at which files changed and go and open them.