Skip to main content

Semver Increment — Bump A Version Number

Bump a version the npm way and see major, minor, patch and every pre-release result at once, all in the browser

  • Runs locally
  • Category Developer & DevOps
  • Best for Formatting, validating, shrinking, or inspecting code-adjacent text.
Bump results
  • majorBreaking change
    2.0.0
  • minorNew feature, backward compatible
    1.3.0
  • patchBug fix, backward compatible
    1.2.4
  • premajorPre-release of the next major
    2.0.0-beta.0
  • preminorPre-release of the next minor
    1.3.0-beta.0
  • prepatchPre-release of the next patch
    1.2.4-beta.0
  • prereleaseBump the pre-release counter
    1.2.4-beta.0

What this tool does

A semantic version incrementer that follows the same rules as npm's semver inc command, built on the semver.org core grammar. Type one current version and the tool shows every bump at the same time: major (1.2.3 to 2.0.0), minor (1.2.3 to 1.3.0), patch (1.2.3 to 1.2.4) and the four pre-release flavours premajor, preminor, prepatch and prerelease. Set an optional pre-release identifier such as beta, alpha or rc and the pre-release rows seed with it, so 1.2.3 premajor becomes 2.0.0-beta.0 and a fresh prerelease becomes 1.2.4-beta.0. Already on a pre-release? It bumps the counter the npm way, so 1.2.3-beta.1 prerelease becomes 1.2.3-beta.2, and a stable bump resolves it down, so 1.2.4-0 patch becomes 1.2.4. It accepts a leading v, drops build metadata, validates as you type, and copies any result with one click. Everything runs client-side and the version plus identifier live in the URL so one link reopens the same bump. 100% in your browser, nothing uploaded.

Tool details

Input
Text + Numbers
The page exposes text boxes, numeric controls, file pickers, or structured inputs depending on the tool.
Output
Live result + Copy
The result area focuses on usable output, with copy, download, or preview actions when supported.
Privacy
Browser-side processing
The main tool logic does not call an external API, so inputs normally stay in the current tab.
Save / share
Shareable URL state
Key settings are encoded in the URL so another person can reopen the same setup.
Performance budget
Initial JS <= 9 KB
No WASM budget is declared, keeping the tool quick to open on mobile.
Best fit
Developer & DevOps · Developer
Category and role tags drive related tools, internal links, and quick fit checks.

How to use

  1. 1. Input

    Paste or drop your content into the tool panel.

  2. 2. Process

    Click the button. All processing is local in your browser.

  3. 3. Copy / Download

    Copy the result or download to disk in one click.

How Semver Increment fits into your work

Use it in the small gaps between coding, reviewing, debugging, and shipping.

Developer jobs

  • Formatting, validating, shrinking, or inspecting code-adjacent text.
  • Preparing snippets for documentation, tickets, commits, or handoff.
  • Checking a small payload quickly without switching tools.

Developer checks

  • Run irreversible transforms like minify or obfuscate on a copy.
  • Keep secrets out of pasted snippets unless the tool explicitly stays local.
  • Use your normal tests or linter before shipping transformed code.

Good next steps

These links move the current task into a more complete workflow.

  1. 1 JSON Formatter & Validator Format, validate, and minify JSON instantly — right in your browser. Open
  2. 2 Semver Compare Tell which semantic version is newer, sort a whole list, and check ^ ~ >= ranges, all in the browser Open
  3. 3 Semantic Version Normalizer Normalize, sort, and prepare semantic versions from pasted text or uploaded local files. Open

Real-world use cases

  • Pick the right version for a release commit

    You finished a change and the release script asks for the next version. Paste the current 1.4.2, read the three stable rows, and if the change adds a feature you take the minor row (1.5.0); if it only fixes a bug you take the patch row (1.4.3). No mental arithmetic, no accidentally shipping 1.4.10 as 1.4.3, and the verdict is in front of you before you tag.

  • Cut a release candidate before the real release

    The next big version is nearly ready and you want a beta out for testers first. Enter 1.4.2, set the identifier to rc, and read the premajor row to get 2.0.0-rc.0. Ship that, gather feedback, then come back and bump the prerelease row to 2.0.0-rc.1 for the next round until you finally take the plain major row at 2.0.0.

  • Keep a pre-release counter moving correctly

    You are publishing nightly betas and need each one numbered one above the last. Drop in 1.2.3-beta.7, read the prerelease row, and get 1.2.3-beta.8 every time, with the numeric tail incremented as a number so beta.9 rolls to beta.10 rather than beta.91. Copy it straight into your publish command.

  • Teach or check semver inc behaviour without installing node

    Explaining to a teammate why a stable patch on 1.2.4-0 lands on 1.2.4 rather than 1.2.5, or why prerelease on a clean 1.2.3 jumps to 1.2.4-0? Open the tool, type the version, and point at the rows. It mirrors npm semver inc, so it settles the argument without anyone spinning up a node REPL.

Common pitfalls

  • Treating version segments as text instead of numbers. A patch bump on 1.2.9 is 1.2.10, never 1.2.91. Each segment is an integer, so the count carries over the way a number should. The tool always increments numerically.

  • Bumping the wrong field for the change. Adding a feature but taking the patch row, or fixing a bug but jumping the major, breaks the contract that consumers rely on. Match the row to the change so breaking goes major, feature goes minor, and fix goes patch.

  • Expecting a stable bump to keep the pre-release tag. A patch on 1.2.4-0 resolves down to 1.2.4, and a minor on 1.3.0-rc.1 resolves to 1.3.0. The pre-release was already leading up to that release, so the stable bump lands on it rather than skipping ahead.

Privacy

Parsing the version and computing every bump are plain JavaScript that runs in your browser tab. No version string is uploaded and nothing is logged. The one thing to know: the current version and the pre-release identifier are stored in the page URL so a share link reopens the same bump, which means a link pasted into chat records those two strings in the recipient server access log. For an unreleased internal version, copy the result text instead of sharing the URL.

FAQ

Tool combos

Folks in your role tend to reach for these alongside this tool.

Browse all tools for this role
Made by Toolora · 100% client-side · Updated 2026-06-13