⇄ FieldConvert
Support for a utility product that stays focused

Need help with FieldConvert?

This page covers the practical basics: what FieldConvert is meant to do, what to check first if something feels off, and what information is useful when reporting a problem.

  • FieldConvert is built around unit conversion, not account-heavy workflows.
  • The product is intended to remain useful for core conversion tasks even in limited-connectivity situations.
  • Measurement system defaults may differ depending on whether you use Metric, US, or Imperial preference mode.
If a result looks unexpected, first verify the selected category, from and to units, rounding mode, and active unit-system preference. Those settings explain most incorrect conversion reports.

Common support topics

Conversion result seems off

Confirm that you chose the correct unit category and the intended from and to pair. Similar symbols across systems can cause accidental pair mismatches.

Product opened with different defaults

Check the selected unit-system preference in settings. FieldConvert supports Metric, US, and Imperial handling, and the chosen preference affects defaults and suggestions.

Saved items are missing

Favorites, history, presets, and preferences are part of the product’s practical on-device workflow. If they disappear, note your device details, product version, and what happened immediately before the issue.

What to include in a support request

Device details

Include your device model and software version if available.

Exact conversion context

Share the category, input value, source unit, target unit, and selected precision or rounding mode.

What you expected

Describe the expected result and why it seemed incorrect, incomplete, or confusing.

Contact

Best way to report

Include the exact steps, conversion pair, expected result, and device details so the issue can be reproduced clearly.

Frequently asked questions

Does FieldConvert need sign-in?

The current product direction is utility-first and does not revolve around account-heavy interaction. Support materials here are written for that lightweight usage model.

Does the product work offline?

FieldConvert is designed so key conversion flows remain useful even without a stable network connection.

Which languages are supported?

Public-facing documentation is maintained in English for consistency.

What if Imperial and US behavior feels similar?

In some categories, the currently bundled unit catalog may not fully diverge between all non-metric datasets. FieldConvert keeps the preference explicit while using available accurate defaults.