If you're in a team with this kind of semi-automated semi-manual regression testing workflow for changes, where there's human-in-loop engineering effort to review regression tests that indicate 'there's some difference between actual output and expected output' and decide if the new output is "OK" or not, the cost of a beyond compare license likely pays for itself in less than a month in terms of freeing up hours of engineering effort.
That said, you can often do better than this by investing engineering effort to build a custom domain-specific file normalizer / differ tool, to e.g. deserialize values, normalize them to eliminate irrelevant details, compare them for equivalence in a domain specific way, show actionable diffs when they differ, which might give a much better result than a high quality general-purpose tool beyond compare.
e.g. in the CLI you might do something like `git diff commit_a commit_b -- some/path/in/repo` to show the diff from commit_a to commit_b limited to some path
Refer to the "configuration" sections for
https://git-scm.com/docs/git-difftool
https://git-scm.com/docs/git-mergetool
these git documentation pages mention meld (along with many other diff tools).