Skip to content
Docs navigationBrowse tools →

Tool docs

URL Parser & Query Editor

Parse URLs, inspect their components, edit query parameters, and rebuild encoded results locally in the browser. This guide explains how the parser behaves, where query editing helps most, and which URL details still need careful review.

Tool

Overview

01

URL Parser & Query Editor

The URL tool helps you break a URL into protocol, host, path, query, and hash, then rebuild it after editing query parameters. It is useful for debugging callback URLs, API requests, tracking parameters, and encoding problems.

Guide

Common usage patterns

01

Parsing and query editing workflow

  • Paste a full URL and inspect the parsed components before making changes.
  • Edit query parameters as rows when copy-pasting raw search strings has become error-prone.
  • Use the rebuilt URL output as the new canonical value once you have sorted, removed, or changed keys.
  • Reach for the encode/decode helper when you need to inspect an individual path, query, or fragment value.

Guide

Edge cases & common pitfalls

01

Protocols, duplicates, and encoding semantics

  • If a protocol is missing, the tool applies a default one, which can change how the URL is interpreted.
  • Duplicate query keys are sometimes meaningful and should not always be collapsed.
  • Sorting keys or removing empty rows changes the exact output, which can matter for signatures and cache keys.
  • Encoding and decoding reserved characters can alter URL semantics if you are not clear about which component you are editing.

Internals

How it works internally

01

Browser URL parsing with explicit rebuild rules

Birdor uses browser URL parsing where possible, stores query rows explicitly in local state, and rebuilds the output from the parsed base plus your current edits. The tool stays local and favors explicit transformations.