Skip to main content
The Redis Key Browser provides a visual interface for managing Redis keys. Browse keys in a tree structure, view and edit values, and perform bulk operations across your Redis databases.

​
Key Concepts

Key

A unique identifier that stores data. Keys can hold different data types like strings, lists, or hashes.

TTL

Time-To-Live in seconds. Keys can expire automatically after a set duration.

Namespace

Keys are often organized using colons (e.g., user:123:profile). The browser displays these as folders.

Pattern

Wildcard expressions to match multiple keys (e.g., cache:* matches all cache keys).

​
Required Permissions

ActionPermission
View keysiam:project:infrastructure:redis:read
Create keysiam:project:infrastructure:redis:write
Update keysiam:project:infrastructure:redis:write
Delete keysiam:project:infrastructure:redis:delete

​
Supported Key Types

TypeDescriptionUse Case
StringSimple key-value pairCaching, counters, flags
ListOrdered sequence of stringsQueues, recent items, feeds
SetUnordered collection of unique stringsTags, unique visitors
Sorted SetSet with score-based orderingLeaderboards, priority queues
HashField-value mapObjects, user profiles
StreamAppend-only logEvent sourcing, messaging

​
How to Browse Keys

1

Select Connection

Choose a Redis connection from the dropdown.
2

Select Database

Choose the database number (0-15 by default).
3

Navigate Tree

Click folders to expand namespaces. Keys with colons are grouped into folders.
4

Select Key

Click on a key to view its details in the right panel.
Your connection and database selections are saved. The browser will restore your last view on next visit.

​
How to Create a Key

1

Click Add Key

Click the Add Key button in the header.
2

Choose Creation Method

Select a method:
  • Templates: Pre-configured key templates for common patterns
  • Manual: Build the key from scratch
  • Import: Paste JSON data to create a key
3

Enter Key Name

Provide a unique key name. Use colons for namespacing (e.g., cache:user:123).
4

Select Data Type

Choose the appropriate type: String, List, Set, Sorted Set, or Hash.
5

Enter Value

Add the value based on the selected type.
6

Set TTL (Optional)

Choose an expiration time or leave as “No Expiry”.
7

Create

Click Create Key to save the new key.

​
Key Name Rules

RuleDescription
Length1-512 characters
SpacesNot allowed in key names
Special CharactersMost characters allowed, use colons for namespacing
Use consistent naming patterns like {entity}:{id}:{attribute} for easier organization. Example: user:123:sessions.

​
How to View Key Details

1

Select a Key

Click on any key in the tree or list view.
2

View Details

The right panel shows key information including type, TTL, encoding, and size.
3

View Value

The value is displayed with appropriate formatting for the key type.

​
How to Edit a String Key

1

Select the Key

Click on a string key to view its details.
2

Edit Value

Modify the value in the editor.
3

Save

Click Save to update the value.

​
How to Edit a Hash Key

1

Select the Hash

Click on a hash key to view its fields.
2

Edit Field

Click on a field to edit its value inline.
3

Add Field

Click Add Field to add a new field-value pair.
4

Delete Field

Click the delete icon to remove a specific field.

​
How to Edit a List Key

1

Select the List

Click on a list key to view its items.
2

Push Item

Use Push Left or Push Right to add items to the list.
3

Edit Item

Click on an item to edit its value at that index.
4

Remove Item

Click the delete icon to remove an item by value.

​
How to Edit a Set Key

1

Select the Set

Click on a set key to view its members.
2

Add Member

Click Add Member and enter a value.
3

Remove Member

Click the delete icon next to a member to remove it.

​
How to Edit a Sorted Set Key

1

Select the Sorted Set

Click on a sorted set key to view members with their scores.
2

Add Member

Click Add Member, enter a value and score.
3

Remove Member

Click the delete icon next to a member to remove it.

​
How to Rename a Key

1

Select the Key

Click on the key to open its details.
2

Click Rename

Click the Rename button in the toolbar.
3

Enter New Name

Provide the new key name.
4

Confirm

Click Rename to apply the change.
Renaming a key will overwrite any existing key with the new name.

​
How to Set TTL

1

Select the Key

Click on the key to open its details.
2

Click Set TTL

Click the TTL button in the toolbar.
3

Choose Duration

Select a preset duration or enter a custom value in seconds.
4

Apply

Click Update TTL to set the expiration.

​
TTL Options

OptionDuration
No ExpiryKey never expires
1 minute60 seconds
5 minutes300 seconds
1 hour3600 seconds
1 day86400 seconds
1 week604800 seconds
CustomEnter seconds manually
Set TTL to -1 to remove expiration from a key.

​
How to Delete a Key

1

Select the Key

Click on the key to open its details.
2

Click Delete

Click the Delete button.
3

Confirm

Confirm the deletion. This action cannot be undone.

​
How to Bulk Delete Keys

Bulk delete allows you to remove multiple keys matching a pattern.
1

Click Bulk Delete

Click the Bulk Delete button in the header.
2

Choose Method

Select a method:
  • Quick Actions: Pre-defined cleanup patterns
  • Pattern: Enter a custom wildcard pattern
3

Enter Pattern

Use wildcard patterns to match keys:
  • cache:* matches all keys starting with cache:
  • *:temp matches all keys ending with :temp
  • session:*:data matches keys with this pattern
4

Preview Matches

Review the list of keys that will be deleted.
5

Select Keys

Check or uncheck keys to include/exclude from deletion.
6

Type Confirmation

Type “DELETE” to confirm the operation.
7

Execute

Click Confirm Delete to proceed.
Bulk delete is permanent. Always preview matched keys before confirming deletion.

​
Pattern Syntax

PatternMatches
*All keys (use with caution)
cache:*Keys starting with cache:
*:tempKeys ending with :temp
user:*:sessionKeys matching the pattern
?Single character wildcard

​
How to Delete Selected Keys from Tree

1

Select Multiple Keys

Use checkboxes in the key tree to select multiple keys.
2

Click Delete Selected

Click the delete button that appears when keys are selected.
3

Confirm

Confirm the deletion of selected keys.

​
Key Templates

When creating keys, templates provide pre-configured structures:
TemplateTypeUse Case
Cache EntryStringGeneral caching
Session DataHashUser sessions
Task QueueListBackground jobs
Rate LimiterStringAPI rate limiting
Feature FlagStringFeature toggles
LeaderboardSorted SetRankings

​
Troubleshooting

  • Click the refresh button to reload the key list
  • Verify you’re viewing the correct database
  • Check if the key has a very short TTL and expired
  • You need write permission
  • The key type may not support the operation
  • Check if another process is modifying the key
  • Redis keys have a fixed type once created
  • To change type, delete and recreate the key
  • Verify you’re looking at the correct key
  • Always preview matches before deleting
  • Use more specific patterns
  • Use the checkbox selection to exclude keys
  • You need delete permission
  • The key may have been deleted by another process
  • Check for connection issues
  • Very large values may be truncated in the UI
  • Use Redis CLI for viewing complete large values
  • Lists and sets are paginated

​
FAQ

Redis allows key names up to 512 MB, but shorter keys are recommended for performance. Keep key names under 1 KB and use meaningful but concise naming.
String values can be up to 512 MB. Lists, sets, and hashes can contain over 4 billion elements. Practical limits depend on available memory.
Redis does not support value-based search natively. Keys are found by name pattern only. Consider using a search index or naming convention for lookups.
Redis automatically deletes the key when TTL reaches zero. Active expiration occurs during access; passive expiration runs periodically.
Not directly in the UI. Use Redis CLI with COPY command (Redis 6.2+) or DUMP/RESTORE for cross-database key copying.
Redis uses different internal encodings for efficiency (e.g., ziplist, quicklist, hashtable). Encoding changes automatically based on data size.
Keys are split by colon (:) separator to create a folder hierarchy. user:123:profile appears under user > 123 > profile.
Push left (LPUSH) adds to the beginning; push right (RPUSH) adds to the end. Use left for stack behavior, right for queue behavior.

​
Best Practices

​
Naming Conventions

Use consistent, hierarchical naming: 
{entity}:{id}:{attribute}

Examples:
user:123:profile
cache:api:endpoint
session:abc123:data
rate:192.168.1.1:minute

​
TTL Management

  • Always set TTL on cache keys to prevent unbounded growth
  • Use appropriate durations: sessions (hours), cache (minutes to days)
  • Monitor keys without TTL to prevent memory issues

​
Key Organization

  • Keep namespaces shallow (2-3 levels)
  • Use consistent separators (colon recommended)
  • Avoid spaces and special characters in key names
  • Consider key length impact on memory

​
Bulk Operations

  • Always preview before bulk delete
  • Use specific patterns to avoid accidental deletions
  • Test patterns on non-production databases first
  • Consider impact on running applications