How do I get a GitHub personal access token?

Visit github.com/settings/tokens, click 'Generate new token', select 'repo' scope for private repositories, and copy the generated token. The token is stored securely and never exposed to the client.

GitHub Repository Tree Viewer

Visualize GitHub repository structure and generate markdown tree for README documentation.

Repository URL

GitHub Token (optional for public repos)

Required for private repositories. Get your token at github.com/settings/tokens

How to Use

Paste your GitHub repository URL (e.g., https://github.com/username/repo)
For private repos, add your GitHub personal access token
Click 'Fetch Repository Tree' to visualize the structure
Copy the generated markdown and paste it into your README.md

What is GitHub Repository Tree Viewer?

GitHub Repository Tree Viewer is a free online tool that helps you visualize the directory structure of any GitHub repository and generate beautiful markdown tree format to add to your project's README.md file.

The tool supports both public repositories (no token needed) and private repositories (requires GitHub personal access token). All processing is done securely on the server to protect your credentials.

Why Use GitHub Repository Tree Viewer?

✓
Free & No Installation: Use directly in your browser without downloading or installing any tools
✓
Interactive Visualization: View tree structure with visual icons, expandable/collapsible folders
✓
Auto-Generate Markdown: Creates standard ASCII tree format, ready to copy and paste into README.md
✓
Private Repo Support: Works with both public and private repositories using GitHub token
✓
100% Secure: Tokens are processed securely on the server, never exposed to the client
✓
Dark Mode: Beautiful interface supporting both light and dark themes

How to Use GitHub Repository Tree Viewer:

Step 1: Enter Repository URL

Paste the URL of the GitHub repository you want to view. Example: https://github.com/username/repo-name

Step 2: Add GitHub Token (If Needed)

For public repositories, you can skip this step. For private repositories, you need a GitHub personal access token:

Visit github.com/settings/tokens
Click "Generate new token" (classic)
Select "repo" scope to access private repositories
Copy the token and paste it into the "GitHub Token" field

Step 3: Fetch Repository Tree

Click the "Fetch Repository Tree" button and wait for the tool to fetch information from GitHub API

Step 4: View and Copy

View the structure in visual tree format (expandable/collapsible) or markdown preview. Click "Copy Markdown" to copy and paste into your README.md.

Common Use Cases:

→
Project Documentation: Add directory structure to README for users to understand code organization
→
Code Review: Quickly get an overview of project structure before reviewing
→
Learning: Study the structure of popular open source projects
→
Reports: Create structure diagrams for technical reports
→
Onboarding: Help new developers understand project structure quickly

Frequently Asked Questions (FAQ)

Do I need a GitHub token for public repositories?

No, tokens are only required for private repositories. Public repositories can be viewed without authentication.

Is my GitHub token safe?

Yes, your token is sent securely via HTTPS and used only to authenticate with GitHub API. It's never stored or logged. All API calls are made server-side to protect your credentials.

Does the markdown tree display correctly on GitHub?

Yes, the tool generates a standard tree structure using ASCII characters (├──, └──, │) that displays correctly in GitHub README files and most markdown viewers.

Is there a repository size limit?

GitHub API has limits for large directory trees. If the repository is too large, results may be truncated. The tool will display a warning in this case.

Does the tool filter files/folders?

Yes, the tool automatically filters common directories and files like .git, node_modules, .next, dist, build, .vscode for clearer structure display.

💡 Tips for Effective Use:

• Use visual tree to explore structure interactively before copying markdown
• Tokens can be reused for multiple repositories, no need to create new ones each time
• For large repositories, check truncated warnings and may need additional filtering
• Copy markdown and add to the top of README for easy code navigation
• Use Dark Mode when working at night to protect your eyes