How To Find And Change A User's UID On Linux

A user’s UID (User ID) is a unique numerical identifier in Linux. You’ll need to check or modify UIDs when migrating systems, fixing permission issues, or managing user accounts across multiple machines.

Finding a user’s UID

To check a user’s UID, use the id command:

id -u username

This returns just the numeric UID. For more complete user information including UID, GID, and groups:

id username

Example output:

uid=1000(alice) gid=1000(alice) groups=1000(alice),27(sudo),997(docker)

You can also check the /etc/passwd file directly:

grep ^username /etc/passwd

The output format is username:x:uid:gid:..., so the third field is the UID:

alice:x:1000:1000:Alice User:/home/alice:/bin/bash

Changing a user’s UID

Use usermod to change a user’s UID:

sudo usermod -u 2000 username

Replace 2000 with your desired UID and username with the actual username.

Important considerations before changing a UID

Stop user processes first. The user must not have any running processes. Kill existing sessions:

sudo killall -u username

Or log them out if they’re connected via SSH or another session.

Update file ownership. Changing a UID doesn’t automatically update ownership of existing files. Find and update all files owned by the old UID:

find / -uid 1000 -exec chown 2000 {} \;

This is critical—without it, the user will lose access to their home directory and other files.

A safer approach using find with -exec:

sudo find /home -user username -exec chown 2000 {} +

Check for hardcoded UIDs. Some applications store UIDs in configuration files or databases. Search your system:

grep -r "1000" /etc/ /opt/ /home/

Avoid conflicts. Ensure the new UID isn’t already in use:

getent passwd 2000

If it returns nothing, the UID is available.

Complete example: Migrating a user to a new UID

# Check current UID
id -u alice

# Kill any running processes
sudo killall -u alice

# Change the UID
sudo usermod -u 2000 alice

# Update file ownership in home directory
sudo find /home/alice -exec chown 2000 {} +

# Update file ownership system-wide if needed
sudo find / -uid 1000 2>/dev/null -exec chown 2000 {} +

# Verify the change
id alice

Reverting a UID change

If something goes wrong, you can revert using the same process:

sudo usermod -u 1000 alice
sudo find /home/alice -exec chown 1000 {} +

Notes on system UIDs

Linux reserves UIDs below 1000 for system accounts (root is 0, then daemons like bin, daemon, etc.). Regular user UIDs typically start at 1000. When assigning new UIDs, stay within the user range to avoid conflicts.

2026 Best Practices and Advanced Techniques

For How to Find and Change a User’s UID on Linux, understanding both the fundamentals and modern practices ensures you can work efficiently and avoid common pitfalls. This guide extends the core article with practical advice for 2026 workflows.

Troubleshooting and Debugging

When issues arise, a systematic approach saves time. Start by checking logs for error messages or warnings. Test individual components in isolation before integrating them. Use verbose modes and debug flags to gather more information when standard output is not enough to diagnose the problem.

Performance Optimization

Monitor system resources to identify bottlenecks
Use caching strategies to reduce redundant computation
Keep software updated for security patches and performance improvements
Profile code before applying optimizations
Use connection pooling and keep-alive for network operations

Security Considerations

Security should be built into workflows from the start. Use strong authentication methods, encrypt sensitive data in transit, and follow the principle of least privilege for access controls. Regular security audits and penetration testing help maintain system integrity.

Related Tools and Commands

These complementary tools expand your capabilities:

Monitoring: top, htop, iotop, vmstat for system resources
Networking: ping, traceroute, ss, tcpdump for connectivity
Files: find, locate, fd for searching; rsync for syncing
Logs: journalctl, dmesg, tail -f for real-time monitoring
Testing: curl for HTTP requests, nc for ports, openssl for crypto

Integration with Modern Workflows

Consider automation and containerization for consistency across environments. Infrastructure as code tools enable reproducible deployments. CI/CD pipelines automate testing and deployment, reducing human error and speeding up delivery cycles.

Quick Reference

This extended guide covers the topic beyond the original article scope. For specialized needs, refer to official documentation or community resources. Practice in test environments before production deployment.