BITFIELD to treat a string as an array of packed integers and run several operations on it in a single atomic call.
Every operation names an encoding and a bit offset. The encoding is u<bits> for unsigned integers (up to 63 bits) or i<bits> for signed integers (up to 64 bits). The offset is counted in bits from the start of the value or, when prefixed with #, in units of the encoding width, so #2 with u8 addresses the third 8-bit field. The string grows automatically with zero bits when an operation addresses an offset past its current end.
GET reads a field, SET writes one and returns its previous value, and INCRBY adds a possibly negative increment and returns the new value. OVERFLOW sets how the SET and INCRBY operations that follow it behave when a value does not fit the encoding: WRAP wraps around like modular arithmetic and is the default, SAT saturates at the minimum or maximum of the encoding, and FAIL leaves the field unchanged and returns null for that operation. The reply is an array with one entry per operation, in the order the operations were given.
Packing many small counters into a single key this way saves memory and keeps the whole update atomic, which makes it a good fit for rate limiters and compact per-user counters.
Syntax
Arguments
Response
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples
TCP examples use the TLSREDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.
Redis CLI
Redis CLI
@upstash/redis
@upstash/redis
upstash_redis
upstash_redis
ioredis
ioredis
node-redis
node-redis
redis-py
redis-py
go-redis
go-redis
jedis
jedis
redis-rs
redis-rs