Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
gpt-tokenizer
Advanced tools
A pure JavaScript implementation of a BPE tokenizer (Encoder/Decoder) for GPT-2 / GPT-3 / GPT-4 and other OpenAI models
gpt-tokenizer
is a Token Byte Pair Encoder/Decoder supporting all OpenAI's models (including GPT-3.5, GPT-4, GPT-4o, and o1).
It's the fastest, smallest and lowest footprint GPT tokenizer available for all JavaScript environments. It's written in TypeScript.
This library has been trusted by:
Please consider 🩷 sponsoring the project if you find it useful.
As of 2023, it is the most feature-complete, open-source GPT tokenizer on NPM. This package is a port of OpenAI's tiktoken, with some additional, unique features sprinkled on top:
encodeChat
functionr50k_base
, p50k_base
, p50k_edit
, cl100k_base
and o200k_base
)decodeAsyncGenerator
and decodeGenerator
with any iterable input)isWithinTokenLimit
function to assess token limit without encoding the entire text/chatnpm install gpt-tokenizer
<script src="https://unpkg.com/gpt-tokenizer"></script>
<script>
// the package is now available as a global:
const { encode, decode } = GPTTokenizer_cl100k_base
</script>
If you wish to use a custom encoding, fetch the relevant script.
gpt-4o
and o1
)gpt-4-*
and gpt-3.5-turbo
)The global name is a concatenation: GPTTokenizer_${encoding}
.
Refer to supported models and their encodings section for more information.
The playground is published under a memorable URL: https://gpt-tokenizer.dev/
You can play with the package in the browser using the CodeSandbox Playground.
The playground mimics the official OpenAI Tokenizer.
The library provides various functions to transform text into (and from) a sequence of integers (tokens) that can be fed into an LLM model. The transformation is done using a Byte Pair Encoding (BPE) algorithm used by OpenAI.
import {
encode,
encodeChat,
decode,
isWithinTokenLimit,
encodeGenerator,
decodeGenerator,
decodeAsyncGenerator,
} from 'gpt-tokenizer'
// note: depending on the model, import from the respective file, e.g.:
// import {...} from 'gpt-tokenizer/model/gpt-4o'
const text = 'Hello, world!'
const tokenLimit = 10
// Encode text into tokens
const tokens = encode(text)
// Decode tokens back into text
const decodedText = decode(tokens)
// Check if text is within the token limit
// returns false if the limit is exceeded, otherwise returns the actual number of tokens (truthy value)
const withinTokenLimit = isWithinTokenLimit(text, tokenLimit)
// Example chat:
const chat = [
{ role: 'system', content: 'You are a helpful assistant.' },
{ role: 'assistant', content: 'gpt-tokenizer is awesome.' },
] as const
// Encode chat into tokens
const chatTokens = encodeChat(chat)
// Check if chat is within the token limit
const chatWithinTokenLimit = isWithinTokenLimit(chat, tokenLimit)
// Encode text using generator
for (const tokenChunk of encodeGenerator(text)) {
console.log(tokenChunk)
}
// Decode tokens using generator
for (const textChunk of decodeGenerator(tokens)) {
console.log(textChunk)
}
// Decode tokens using async generator
// (assuming `asyncTokens` is an AsyncIterableIterator<number>)
for await (const textChunk of decodeAsyncGenerator(asyncTokens)) {
console.log(textChunk)
}
By default, importing from gpt-tokenizer
uses cl100k_base
encoding, used by gpt-3.5-turbo
and gpt-4
.
To get a tokenizer for a different model, import it directly, for example:
import {
encode,
decode,
isWithinTokenLimit,
// etc...
} from 'gpt-tokenizer/model/gpt-3.5-turbo'
If you're dealing with a resolver that doesn't support package.json exports
resolution, you might need to import from the respective cjs
or esm
directory, e.g.:
import {
encode,
decode,
isWithinTokenLimit,
// etc...
} from 'gpt-tokenizer/cjs/model/gpt-3.5-turbo'
If you don't mind loading the tokenizer asynchronously, you can use a dynamic import inside your function, like so:
const {
encode,
decode,
isWithinTokenLimit,
// etc...
} = await import('gpt-tokenizer/model/gpt-3.5-turbo')
If your model isn't supported by the package, but you know which BPE encoding it uses, you can load the encoding directly, e.g.:
import {
encode,
decode,
isWithinTokenLimit,
// etc...
} from 'gpt-tokenizer/encoding/cl100k_base'
o1-*
(o200k_base
)gpt-4o
(o200k_base
)gpt-4-*
(cl100k_base
)gpt-3.5-turbo
(cl100k_base
)text-davinci-003
(p50k_base
)text-davinci-002
(p50k_base
)text-davinci-001
(r50k_base
)Note: if you're using gpt-3.5-*
or gpt-4-*
and don't see the model you're looking for, use the cl100k_base
encoding directly.
encode(text: string, encodeOptions?: EncodeOptions): number[]
Encodes the given text into a sequence of tokens. Use this method when you need to transform a piece of text into the token format that the GPT models can process.
The optional encodeOptions
parameter allows you to specify special token handling (see special tokens).
Example:
import { encode } from 'gpt-tokenizer'
const text = 'Hello, world!'
const tokens = encode(text)
decode(tokens: number[]): string
Decodes a sequence of tokens back into text. Use this method when you want to convert the output tokens from GPT models back into human-readable text.
Example:
import { decode } from 'gpt-tokenizer'
const tokens = [18435, 198, 23132, 328]
const text = decode(tokens)
isWithinTokenLimit(text: string, tokenLimit: number): false | number
Checks if the text is within the token limit. Returns false
if the limit is exceeded, otherwise returns the number of tokens. Use this method to quickly check if a given text is within the token limit imposed by GPT models, without encoding the entire text.
Example:
import { isWithinTokenLimit } from 'gpt-tokenizer'
const text = 'Hello, world!'
const tokenLimit = 10
const withinTokenLimit = isWithinTokenLimit(text, tokenLimit)
countTokens(text: string | Iterable<ChatMessage>, encodeOptions?: EncodeOptions): number
Counts the number of tokens in the input text or chat. Use this method when you need to determine the number of tokens without checking against a limit.
The optional encodeOptions
parameter allows you to specify custom sets of allowed or disallowed special tokens.
Example:
import { countTokens } from 'gpt-tokenizer'
const text = 'Hello, world!'
const tokenCount = countTokens(text)
encodeChat(chat: ChatMessage[], model?: ModelName): number[]
Encodes the given chat into a sequence of tokens.
If you didn't import the model version directly, or if model
wasn't provided during initialization, it must be provided here to correctly tokenize the chat for a given model. Use this method when you need to transform a chat into the token format that the GPT models can process.
Example:
import { encodeChat } from 'gpt-tokenizer'
const chat = [
{ role: 'system', content: 'You are a helpful assistant.' },
{ role: 'assistant', content: 'gpt-tokenizer is awesome.' },
]
const tokens = encodeChat(chat)
Note that if you encode an empty chat, it will still contain the minimum number of special tokens.
encodeGenerator(text: string): Generator<number[], void, undefined>
Encodes the given text using a generator, yielding chunks of tokens. Use this method when you want to encode text in chunks, which can be useful for processing large texts or streaming data.
Example:
import { encodeGenerator } from 'gpt-tokenizer'
const text = 'Hello, world!'
const tokens = []
for (const tokenChunk of encodeGenerator(text)) {
tokens.push(...tokenChunk)
}
encodeChatGenerator(chat: Iterator<ChatMessage>, model?: ModelName): Generator<number[], void, undefined>
Same as encodeChat
, but uses a generator as output, and may use any iterator as the input chat
.
decodeGenerator(tokens: Iterable<number>): Generator<string, void, undefined>
Decodes a sequence of tokens using a generator, yielding chunks of decoded text. Use this method when you want to decode tokens in chunks, which can be useful for processing large outputs or streaming data.
Example:
import { decodeGenerator } from 'gpt-tokenizer'
const tokens = [18435, 198, 23132, 328]
let decodedText = ''
for (const textChunk of decodeGenerator(tokens)) {
decodedText += textChunk
}
decodeAsyncGenerator(tokens: AsyncIterable<number>): AsyncGenerator<string, void, undefined>
Decodes a sequence of tokens asynchronously using a generator, yielding chunks of decoded text. Use this method when you want to decode tokens in chunks asynchronously, which can be useful for processing large outputs or streaming data in an asynchronous context.
Example:
import { decodeAsyncGenerator } from 'gpt-tokenizer'
async function processTokens(asyncTokensIterator) {
let decodedText = ''
for await (const textChunk of decodeAsyncGenerator(asyncTokensIterator)) {
decodedText += textChunk
}
}
There are a few special tokens that are used by the GPT models. Note that not all models support all of these tokens.
By default, all special tokens are disallowed.
The encode
, encodeGenerator
and countTokens
functions accept an EncodeOptions
parameter to customize special token handling:
gpt-tokenizer
allows you to specify custom sets of allowed special tokens when encoding text. To do this, pass a
Set
containing the allowed special tokens as a parameter to the encode
function:
import {
EndOfPrompt,
EndOfText,
FimMiddle,
FimPrefix,
FimSuffix,
ImStart,
ImEnd,
ImSep,
encode,
} from 'gpt-tokenizer'
const inputText = `Some Text ${EndOfPrompt}`
const allowedSpecialTokens = new Set([EndOfPrompt])
const encoded = encode(inputText, { allowedSpecialTokens })
const expectedEncoded = [8538, 2991, 220, 100276]
expect(encoded).toBe(expectedEncoded)
You may also use a special shorthand for either disallowing or allowing all special tokens, by passing in the string 'all'
, e.g. { allowedSpecial: 'all' }
.
Similarly, you can specify custom sets of disallowed special tokens when encoding text. Pass a Set
containing the disallowed special tokens as a parameter to the encode
function:
import { encode, EndOfText } from 'gpt-tokenizer'
const inputText = `Some Text ${EndOfText}`
const disallowedSpecial = new Set([EndOfText])
// throws an error:
const encoded = encode(inputText, { disallowedSpecial })
In this example, an Error is thrown, because the input text contains a disallowed special token.
If both allowedSpecialTokens
and disallowedSpecial
are provided, disallowedSpecial
takes precedence.
The tokenizer uses an LRU (Least Recently Used) cache to improve encoding performance for similar strings. By default, it stores up to 100,000 merged token pairs. You can adjust this value to optimize for your specific use case:
You can modify the cache size using the setMergeCacheSize
function:
import { setMergeCacheSize } from 'gpt-tokenizer'
// Set to 5000 entries
setMergeCacheSize(5000)
// Disable caching completely
setMergeCacheSize(0)
The cache is persisted between encoding calls. To explicitly clear the cache (e.g. to free up memory), use the clearMergeCache
function:
import { clearMergeCache } from 'gpt-tokenizer'
clearMergeCache()
gpt-tokenizer
includes a set of test cases in the TestPlans.txt file to ensure its compatibility with OpenAI's Python tiktoken
library. These test cases validate the functionality and behavior of gpt-tokenizer
, providing a reliable reference for developers.
Running the unit tests and verifying the test cases helps maintain consistency between the library and the original Python implementation.
gpt-tokenizer
provides comprehensive data about all OpenAI models through the models
export from gpt-tokenizer/models
. This includes detailed information about context windows, costs, training data cutoffs, and deprecation status.
The data is regularly maintained to match OpenAI's official documentation. Contributions to keep this data up-to-date are welcome - if you notice any discrepancies or have updates, please feel free to open a PR.
Since version 2.4.0, gpt-tokenizer
is the fastest tokenizer implementation available on NPM. It's even faster than the available WASM/node binding implementations.
It has the fastest encoding, decoding time and a tiny memory footprint. It also initializes faster than all other implementations.
The encodings themselves are also the smallest in size, due to the compact format they are stored in.
MIT
Contributions are welcome! Please open a pull request or an issue to discuss your bug reports, or use the discussions feature for ideas or any other inquiries.
Thanks to @dmitry-brazhenko's SharpToken, whose code was served as a reference for the port.
Hope you find the gpt-tokenizer
useful in your projects!
FAQs
A pure JavaScript implementation of a BPE tokenizer (Encoder/Decoder) for GPT-2 / GPT-3 / GPT-4 and other OpenAI models
The npm package gpt-tokenizer receives a total of 129,138 weekly downloads. As such, gpt-tokenizer popularity was classified as popular.
We found that gpt-tokenizer demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.