Published by SOPIDOTECH LTD · · 3 min read

Compare a saved configuration with a revised version before deploying it. A difference view helps separate the lines that changed from the lines that stayed the same.

Open the Text Diff Checker to follow the workflow. Processing runs in your browser; the tool does not upload the input for conversion.

A practical workflow

  1. Paste both versions. Place the earlier text in Original / before and the revised text in Updated / after.
  2. Select lines, words or characters. Use lines for files; switch to words or characters for smaller changes.
  3. Compare and inspect highlights. Run Compare inputs. Green marks additions and red marks removals.
  4. Save the difference. Copy the readable summary or download text-difference.txt.

Try a concrete example

The following demonstration input is also available in the workspace. Replace it with your own data after checking the expected behaviour.

const price = 100;
const status = "draft";

Compare it with this updated version:

const price = 120;
const status = "ready";

With the default settings, the result is:

- const price = 100;
const status = "draft";+ const price = 120;
const status = "ready";

Choose the comparison that fits the document

Line mode is a useful starting point for code, configuration files and lists. Word mode makes changes inside paragraphs easier to follow. Character mode is more precise for a short identifier or a compact expression, but can be noisy on a large file.

Preserve meaningful whitespace

Leading spaces can carry meaning in languages such as Python or YAML. Keep the whitespace option off when indentation is part of the data. When it is on, the tool trims leading and trailing whitespace on each line before comparing, so the result describes those normalised versions.

Review the change in context

A highlighted addition is not automatically a correct change. Read the neighbouring lines and check that removed settings are no longer required. The downloadable difference is a readable text summary; it is not a guaranteed patch file that can be applied automatically.

If the result needs attention

Ignoring whitespace changes what is compared. Keep it off when indentation or spaces are meaningful.

Read the exact error before changing the input. Keep a copy of the original, reduce the sample when investigating a large file, and use the destination application to verify that the result has the meaning you intended. The tool processes the supplied data; it cannot infer an unstated application schema or project requirement.

Use the Text Diff Checker to compare a saved result with the original. Keep transformation and application testing as separate steps so presentation changes are not mistaken for verified behaviour.

Sources and further reading

Turn the next step into a project

Need help with a brand identity, business website or launch assets? Explore SOPIDOTECH services and client projects, or discuss your brief.

Keep learning