Telephone URI
RFC3966 phone number converter
Create an RFC3966 telephone URI and copyable, HTML-escaped anchor snippet from one global number.
- One global number at a time
- RFC3966 URI output
- Copyable escaped HTML snippet
Try it now
Create an RFC3966 telephone URI
Enter one global number with a leading +. This is a URI formatter, not a dialing test.
Enter a global number to begin.
Quick answer
A focused telephone URI formatter
The output is a URI representation, not a dialing or reachability test.
URI
Uses the RFC3966 tel form.
Snippet
Escapes both attribute and text.
Boundary
Does not test devices.
Practical workflow
Create a telephone URI
Provide one global number, inspect the URI, then copy the safe HTML snippet.
- 1
Enter
Paste one global number.
- 2
Create
Generate the URI locally.
- 3
Copy
Use the escaped snippet where appropriate.
What an RFC3966 URI means
A formatted URI does not establish assignment, carrier, owner, reachability, deliverability, or device acceptance.
What the tel URI is for
An RFC3966 tel URI is a standardized text representation for a telephone reference. It can be useful in markup, documents, and interfaces that expect a telephone link, but it is not a command to contact a carrier or device.
This tool accepts one global number because an unambiguous global representation is the right input for this focused formatter. It does not infer a country or repair an unclear local number.
Why the HTML snippet is escaped
The copied anchor snippet escapes the URI in both the href attribute and visible text. Escaping prevents characters in the produced URI from being interpreted as HTML markup when the snippet is placed into an HTML context.
The snippet is a convenience for a reviewed global input. Check the surrounding site’s accessibility, link-label, and publishing requirements before adding any generated markup to a public page.
Review before copying
If the formatter returns Review, no URI or anchor snippet is offered. That boundary prevents a misleading link from being created from an input that did not produce the required global result.
A successful clipboard notice only confirms that the browser accepted the copy action. It does not confirm that a content system saved the snippet or that a telephone application will accept the resulting link.
Practice resource
RFC3966 global URI subset
Uses packaged libphonenumber-js@1.13.9/max metadata, not live carrier, assignment, or reachability data.
| Input | URI | Support |
|---|---|---|
| +1 202 555 0125 | tel:+12025550125 | Global number |
| +1 202 555 0125 ext 42 | tel:+12025550125;ext=42 | Global extension |
| Local phone-context form | Review | Not supported subset |
Result
The tool returns an RFC3966 URI and safe anchor snippet.
| Input | Result | Meaning |
|---|---|---|
+1 202 555 0125 | tel:+12025550125 | Global URI. |
+1 202 555 0125 ext 42 | tel:+12025550125;ext=42 | Extension URI. |
020 7946 0018 | Review | No local phone-context support. |
RFC3966 questions
Does this place a call?
No. It only formats a telephone URI.
Does copied mean a device can dial it?
No. Copy success is only a browser clipboard outcome.
Why is there no URI for Review?
The tool avoids producing a telephone link when it cannot make the requested global result.
Policies and references
Related phone converters and workflows
Continue with the next workflow or browse the full directory.