Help us fix this page
If you found a broken link, missing page, or incorrect redirect, please let us know. Your report helps us improve the website for everyone.

A typical day in VS Code is full of small text tasks. You need Base64 for an HTTP header. You convert a constant from camelCase to SCREAMING_SNAKE_CASE. You clean messy text from an email. You generate a GUID. You sort lines. You fix a URL or an HTML entity.
Each job is trivial on its own, but the context switching is not. You hop to online tools, paste sensitive data into random websites, copy results back, and repeat this many times per day.
Dev Toolbox is a free Visual Studio Code extension that gives you an integrated toolbox for these everyday operations. You select text, run a command, and move on. No browser. No extra app. Just fast, predictable text utilities inside your editor.
Ctrl+Shift+P / Cmd+Shift+P) or right-click context menu on selected text.Math.random()-suitable for general use but not cryptographically secure. Avoid for security-critical applications.Most developer workflows suffer from three recurring issues around text:
You leave VS Code for a browser tab to do Base64, URL encoding, slug generation, or GUIDs. Every switch breaks focus and invites distractions.
You manually change case, add underscores, or reorder lines. This leads to typos in identifiers, inconsistent naming, and bugs in configs or translations.
You maintain a collection of bookmarks to different tools: one for slugs, one for GUIDs, one for HTML entities, another for Unicode escapes. You repeat the same copy-paste dance all day.
Dev Toolbox fixes all three. You keep every operation inside the editor. You rely on commands instead of manual edits. You use a consistent interface for all the tiny tasks that usually cost you several minutes each.
Dev Toolbox is a lightweight VS Code extension that bundles many everyday text tools into one package. It focuses on practical tasks that developers use multiple times per day:
Because Dev Toolbox lives inside VS Code, it works on any file type you open: source code in JavaScript, TypeScript, C#, Java, Python, etc.; configuration files like JSON, YAML, TOML, XML, INI; documentation in Markdown, HTML, plain text; and translation files and resource bundles.
Refactors and naming changes are some of the most common places where text tools save time and prevent bugs.
Dev Toolbox converts selected text between many programming case styles:
| Style | Example | Use Case |
|---|---|---|
| camelCase | myVariableName | JavaScript variables, Java fields |
| PascalCase | MyClassName | C# classes, TypeScript interfaces |
| snake_case | my_variable_name | Python variables, JSON field names |
| SCREAMING_SNAKE_CASE | MY_CONSTANT_NAME | Environment variables, constants |
| kebab-case | my-variable-name | CSS classes, URLs |
| train-case | MY-VARIABLE-NAME | Some configuration formats |
| flatcase | myvariablename | Compact identifiers |
| UPPERCASE | MYVARIABLENAME | All caps without separators |
Example scenarios:
userId to USER_ID in an environment file.hero-section to heroSection while porting to a JS object style.snake_case in JSON but camelCase in code.Instead of hand-editing every occurrence, you select the text and run the appropriate Dev Toolbox command.
Case conversion is not the same in every language. Some characters have special rules that simple toUpperCase and toLowerCase do not handle correctly.
Dev Toolbox uses locale-aware case conversion via toLocaleLowerCase and toLocaleUpperCase. You can pass optional locale parameters, and the extension falls back safely when a specific locale is not available.
This matters when you work on internationalized websites or applications; you maintain content in languages with special casing rules; or you generate URLs or labels that must respect local language rules.
Dev Toolbox includes a slugify command that turns arbitrary text into a URL-safe, file-safe slug. It:
Typical uses:
For example, you select “Refactor: Clean up user onboarding flow” and run the slugify command. Dev Toolbox produces a clean slug like refactor-clean-up-user-onboarding-flow that you can paste into routes, markdown IDs, or filenames.
GUIDs and UUIDs appear in many places: database primary keys and seed data; configuration entries; application IDs and client IDs; and attributes in .NET or COM code.
Dev Toolbox generates GUIDs in several convenient formats:
| Format | Example | Use Case |
|---|---|---|
| Raw | a1b2c3d4-e5f6-7890-9abc-c1d2e3f4a5b6 | Default UUID format |
| Registry | {a1b2c3d4-e5f6-7890-9abc-c1d2e3f4a5b6} | Windows Registry keys |
| Square brackets | [Guid("a1b2c3d4-e5f6-7890-9abc-c1d2e3f4a5b6")] | C# attributes |
| Angle brackets | <Guid("a1b2c3d4-e5f6-7890-9abc-c1d2e3f4a5b6")> | Some code generation scenarios |
You can insert a new GUID at the cursor or replace a selection.
Note: GUID generation uses Math.random() which is suitable for general purposes but not cryptographically secure. While collision risk is minimal, avoid using it for security-critical applications.
Sorting and cleanup are boring but important. Doing them manually is slow and inconsistent. Dev Toolbox provides commands that handle real-world text structures and Unicode correctly.
Simple ASCII sorting is not enough when you deal with names, localized strings, or keys that include diacritics. Dev Toolbox offers advanced, Unicode-aware line sorting that:
"10" comes after "2" instead of before it"a" comes before "á"This is useful for sorting lists of person names from different countries; organizing translation keys alphabetically; reordering log lines by message or field; and maintaining sorted dictionaries or configuration lists.
Sometimes alphabetical order is not what you want. You may prefer to sort by line length:
Dev Toolbox can sort lines by character count: shortest to longest; longest to shortest; with stable sorting and optional alphabetical tie-breaking when lengths match.
Messy text sneaks into projects from many sources: copy-paste from emails or office documents; logs pasted into issues; and snippets copied from PDFs or forums.
Dev Toolbox includes cleanup helpers to:
You can run these commands on a selection or the whole file.
Encoding and escaping are classic reasons developers open a browser. Doing this for sensitive data is risky, and it slows you down.
Dev Toolbox turns VS Code into a local toolbox for common encodings and conversions.
Dev Toolbox can:
Use cases: preparing Authorization headers or test payloads for HTTP clients; inspecting encoded tokens or cookies; and debugging issues with URL parameters that contain special characters.
When you embed text into HTML templates, content strings, or inline scripts, you often need entity conversions:
é to é)é to é)é to é)This helps when you maintain static HTML snippets or email templates; embed symbols or non-ASCII characters in environments with limited encoding support; or debug issues where some characters do not render as expected.
Different layers in a web stack use different escape formats. Dev Toolbox supports a broad range of them:
| Escape Format | Example | Use Case |
|---|---|---|
| JavaScript UTF-16 | \u00E9 | JS string literals |
| CSS Unicode | \00E9 | CSS content properties |
| Unicode code point notation | U+00E9 | Documentation and debugging |
| Unicode code point escape | \u{00E9} | Modern JS (ES6+) |
| PCRE Unicode hex | \x{00E9} | PCRE-compatible regex |
| Hex code points | 0x00E9 | Low-level contexts |
Practical applications: preparing safe strings for JavaScript source code or JSON that pass through multiple parsers; writing CSS content values that include special symbols; building regex patterns that target specific Unicode ranges; and documenting character codes in technical docs or specs.
Modern codebases often serve users in many languages. That means translation files in multiple locales, content editors who do not work in English, and developers who prefer tools with localized interfaces.
Dev Toolbox addresses this in two ways.
As mentioned earlier, case conversion and sorting functions use locale-aware logic when possible. This matters for correct ordering of names and words with accents; proper casing in languages with special rules; and avoiding subtle bugs in string handling.
Dev Toolbox is localized into 17 languages:
Team members can access commands and messages in their preferred language while still sharing the same toolset and workflows.
The GUID generation uses Math.random() which is suitable for general purposes but not cryptographically secure. While collision risk is minimal, avoid using it for security-critical applications.
Text processing operations occur in memory. Very large documents may experience performance impacts. Consider processing selections for optimal performance.
Ctrl+Shift+X / Cmd+Shift+X)Alternatively, install directly from the Visual Studio Marketplace.
Access Dev Toolbox commands via:
Ctrl+Shift+P / Cmd+Shift+P)-search for the command you needSelect text, run the relevant Dev Toolbox command, and see the result in place.
camelCase to SCREAMING_SNAKE_CASE, Dev Toolbox covers the formats developers use daily.Small text tasks add up. Case conversions, slugs, GUIDs, line sorting, cleanup, and encoding all steal time from real development work when you rely on external tools and manual edits.
By adding a focused set of text utilities in VS Code, you turn these chores into quick, reliable commands that fit into your existing workflow. Dev Toolbox does exactly that. It replaces a whole collection of separate browser tools with one integrated toolbox inside your editor.
Install Dev Toolbox from the Visual Studio Marketplace, try it on your next refactor or content cleanup, and keep your hands on the keyboard and your focus in the code.
Need help with your development workflow? Playful Sparkle has been engineering digital products since 2004, offering Web Development, App Development, and UI/UX & Web Design services. Contact us to discuss how we can help you build better tools and streamline your development process.