返回生态系统
Urlescent app icon

Urlescent

URL 编码、解码与解析工具

关于

Urlescent 是一款快速、私密的工具,可直接在 iPhone 和 iPad 上完成 URL 的编码、解码与解析。

输入或粘贴任意内容,即可立即看到结果。轻点即可切换编码模式,复制输出内容,继续下一步操作。没有繁琐的菜单,无需等待。

Urlescent 的独特之处

  • 即时编码与解码。对单个部分或整个 URL 进行百分号编码,支持 Base64 与 URL 安全的 Base64——输入的同时即时呈现。
  • 解析任意 URL。将 URL 拆分为协议、主机、端口、路径、查询和片段,每个查询参数都已自动解码。
  • 为速度而生。输入时即时显示结果,支持一键复制、粘贴、分享和清空,并在本地保存最近的转换记录。
  • 设计之初即注重隐私。一切都在设备本地完成——无需账户、无需注册、不联网、不追踪。

定价

Urlescent 完全免费,无需账号,也没有订阅。所有功能均在设备本地运行,没有需要解锁的内容。

反馈

由一个小型独立团队制作。如有反馈、问题报告或功能建议,欢迎发邮件至 obeliskclubclub@gmail.com

专为开发者、测试人员,以及所有需要处理链接、查询字符串和 API 的人打造。

服务条款(EULA):https://obelisk.club/urlencoder/terms

核心能力

输入的同时即可编码和解码 URL

对单个部分或整个 URL 进行百分号编码

在同一处支持 Base64 与 URL 安全的 Base64

常见问题

What does URL encoding (percent encoding) actually do?
URLs can only contain a limited character set, so reserved or unsafe characters are written as a percent sign plus their hex code — a space becomes %20, an ampersand becomes %26 — which keeps them from being mistaken for URL structure. Urlescent encodes and decodes live as you type, and can percent-encode either a single component or a whole URL with its structure preserved.
Why does my URL break when a query parameter contains & or = ?
In a query string, & separates parameters and = separates keys from values, so an unencoded & or = inside a value gets parsed as structure and splits your parameter apart. The fix is to percent-encode the value itself; Urlescent has a dedicated mode for encoding a single component like a query value, so only the characters inside the value are escaped.
Is it safe to decode tokens or URLs with sensitive data in an online tool?
URLs and Base64 tokens often carry session IDs, API keys, or personal data, and a web-based encoder sends all of it to a third-party server. Urlescent does everything on your device — no accounts, no network, no tracking — so the text you encode or decode never leaves your iPhone or iPad.
What is URL-safe Base64 and how is it different from regular Base64?
Standard Base64 uses + and /, which have special meanings in URLs, so the URL-safe variant swaps them for - and _ — that's why a JWT segment won't always decode as plain Base64. Urlescent handles both Base64 and URL-safe Base64 in the same place, and can decode any Base64 or percent-encoded string back to readable text.
How can I see all the query parameters in a long URL?
Urlescent's inspector breaks any URL into its scheme, host, port, path, query, and fragment, and lists every query parameter with its value already decoded, so you don't have to eyeball a wall of %-escapes. Tap any part to copy just that piece, and recent conversions are saved locally for reuse.

界面展示

Urlescent screenshot 1

高保真界面

Urlescent screenshot 2

高保真界面

Urlescent screenshot 3

高保真界面

隐私政策服务条款支持账号删除© 2026 Urlescent. 保留所有权利。