Choose a Client

By editor

VS Code

Two options, depending on your needs:

VS Code REST Client

IDE Extension

The originator of the .http file format (circa 2017). VS Code extension with ~6K GitHub stars. Supports HTTP requests, variables, environments, and response viewing with rich editor integration.

VS Code TypeScript

Docs Source

httpyac

IDE Extension

The most interoperable implementation. CLI tool and VS Code extension that supports both JetBrains and REST Client syntax while adding its own extensions. Bridges the gap between ecosystems.

VS Code, CLI TypeScript/Node.js

Docs Source

VS Code REST Client is the originator of the format — straightforward, stable, well-documented. httpyac offers broader compatibility (supports both REST Client and JetBrains syntax) and adds scripting, assertions, and protocol extensions.

JetBrains IDEs

JetBrains HTTP Client

IDE Extension

Built into all JetBrains IDEs. The most feature-rich IDE implementation, with the only semi-formal spec attempt. Also available as a standalone CLI (ijhttp).

IntelliJ IDEA, WebStorm, GoLand, PyCharm, Rider Kotlin/Java

Docs Source CLI

Built into IntelliJ IDEA, WebStorm, GoLand, PyCharm, Rider, and all other JetBrains IDEs. No extension to install.

Visual Studio

Visual Studio 2022

IDE Extension

Built-in since v17.6, significantly enhanced in v17.8+. Adopted JetBrains env format with Microsoft extensions including Azure Key Vault secrets providers.

Visual Studio 2022 C#

Docs

Built into Visual Studio 2022 since v17.6. Supports the JetBrains environment format with Microsoft extensions.

Neovim

kulala.nvim

Neovim Plugin

Neovim plugin targeting 100% IntelliJ compatibility. Includes kulala-fmt formatter, kulala-ls language server, and a CLI with GitHub Action support.

Neovim Lua

Docs Source

rest.nvim

Neovim Plugin

Neovim plugin using tree-sitter for parsing. Revived after being archived.

Neovim Lua

Docs Source

kulala.nvim targets full JetBrains compatibility and includes a formatter, language server, and CLI. rest.nvim uses tree-sitter parsing.

By use case

CI/CD pipelines

Run .http files headlessly with any of the CLI tools — JetBrains' ijhttp, the httpyac CLI, and several others.

Building tools that parse .http files

Start from one of the parser libraries rather than writing a grammar from scratch.

Compatibility at a glance

If you want maximum portability, stick to the universal core syntax and use http-client.env.json for environments. See Writing Portable Files for specific recommendations.

If you want maximum features, httpyac supports the broadest feature set: both JetBrains and REST Client syntax, plus its own scripting, assertions, and protocol extensions.

If you want the tightest IDE integration, use the built-in client for your IDE — JetBrains HTTP Client, Visual Studio 2022, or VS Code REST Client.