A one-row export can still be corrupted by convenient assumptions. This example contains the headers sku, price and active separated by semicolons, followed by 00123, 12.50 and false. All three values resemble data that another converter might coerce, so the tuple makes CSVBridge's string-only policy directly visible and executable.
Select semicolon before conversion
Load the leading-zero preset or paste sku;price;active, then a line containing 00123;12.50;false. Choosing semicolon is part of the input contract, not a suggestion derived from punctuation frequency. With comma selected, the same text would form one header and one value; CSVBridge does not silently change the user's selected dialect.
Compare the exact pretty JSON
The output is an array with one object whose keys remain sku, price and active. Their values are exactly "00123", "12.50" and "false". Pretty mode uses two spaces and LF between JSON lines; compact mode removes insignificant whitespace but represents the same three strings. Copy and download always use the currently visible mode.
Apply types only with a reviewed schema
If the destination truly requires price as a decimal or active as a boolean, perform that conversion where a schema names the column, accepted literals, range, nullability and error policy. The generic CSV spelling is not enough evidence. Keeping source tokens as strings makes the first transformation reversible in meaning and prevents a leading-zero identifier from being shortened accidentally.