Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenCompare an original and a modified text and see exactly which lines were added or removed.
Put the before version in the left box.
Put the after version in the right box.
Unified diff or side by side, then click Compare.
Read the marked lines and the addition and removal counts.
Staging works and production does not, and the two nginx configs are 'basically the same'. Scrolling both files in separate editor tabs misses the one changed directive. Diff Checker lines them up and marks every line that differs.
Paste the original into the left box and the modified version into the right, then click Compare. The tool runs a line-based longest-common-subsequence diff, the same idea behind most version-control diffs, and shows the result as a unified view with + and - markers or as two columns side by side. Below the result you get a count of additions and removals. Switching views re-renders without pasting again.
An edited line appears as one removal plus one addition, since the comparison works on whole lines rather than words. Trailing spaces and different line endings count as changes too, so normalise those if the diff is full of lines that look identical. Very large inputs, several thousand lines on each side, can make the tab pause because every pair of lines is compared. For structured data, compare by meaning instead: JSON Compare sorts keys before comparing, and the YAML diff tool suits config files where indentation matters.
Both texts are compared in browser memory and dropped when you close the tab. Nothing is saved to a server.
Related: URL Compare
Keyboard shortcut
Spot unintended edits between staging and production snippets.
Sanity-check two versions when you lack a full IDE diff.
Highlight wording changes between draft and final text.
Answers for this tool. For site-wide help, open the FAQ hub.
The diff compares whole lines. When any character on a line changes, the old line counts as removed and the new one as added, which is how unified diffs from git present it too.
No. Every character counts, including trailing spaces, tabs versus spaces and Windows line endings. If the diff shows lines that look identical, the difference is almost always invisible whitespace.
The comparison builds a table with one cell per pair of lines, so a few thousand lines per side is fine, while tens of thousands can freeze the tab for a while. Split very large files or run git diff locally.