Connection Formats¶
DbClone supports multiple connection string formats. You can import any of these through the Connection Manager (Import from Clipboard or the Import button).
URI Format¶
The standard PostgreSQL connection URI:
Special Characters in Passwords¶
DbClone handles special characters in passwords automatically — you can paste a URI with an unencoded password and it will be parsed correctly.
The typical workflow: copy the URI template from your provider's dashboard (which usually contains a [YOUR-PASSWORD] placeholder), replace the placeholder with your real password, and paste the result. Your password goes in raw — no percent-encoding needed:
The parser uses a tolerant approach: it scores every possible @ split (preferring a real-looking host — dotted name, port, database path — over a bare word) and picks the best reading, so the password is identified correctly even when it contains @, #, &, ?, :, /, or spaces. Special characters in query-parameter values are tolerated too:
Pre-encoded URIs (as produced by most cloud dashboards) also work:
Both forms import to the same result — password field shows p@ss#word.
Common percent-encoding reference:
| Character | Encoded |
|---|---|
@ |
%40 |
# |
%23 |
% |
%25 |
/ |
%2F |
: |
%3A |
& |
%26 |
? |
%3F |
| space | %20 |
Tip
If you fill in the individual fields instead of pasting a URI, DbClone handles encoding automatically on export.
Note
If both your password and a query-parameter value contain @ and the host has no port, path, or dots, parsing is inherently ambiguous — percent-encode the password (%40) to remove any doubt.
Key-Value Format¶
The standard Npgsql/ADO.NET connection string format:
No encoding needed — semicolons delimit fields, and the password is taken as-is.
Platform-Specific URIs¶
DbClone recognizes connection strings from popular managed platforms:
Supabase¶
Neon¶
Aiven¶
AWS RDS¶
All of these are parsed as standard PostgreSQL URIs — no special handling needed.