cf-pages/telegraph-image

Image Hosting solution, Flickr/imgur alternative, make it easy for users to share their images. Using Cloudflare Pages and Telegraph.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 31 minutes ago
Added to GitGenius on September 14th, 2026
Created on October 31st, 2022
Open Issues & Pull Requests: 25 (+0)
GitHub issues: Enabled
Number of forks: 8,908
Total Stargazers: 4,682 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.1 days
Mean response time: 125.6 days
90th percentile: 421.3 days
Tracked items: 131

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 630 days
Stale 30+ days: 5
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (3)
  • help wanted (3)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Telegraph-Image is an image hosting solution that provides a free alternative to Flickr and Imgur by leveraging Cloudflare Pages and the Telegram Bot API.

The tool solves the problem of hosting and sharing images without relying on centralized commercial platforms. It works by accepting image uploads through a web interface and storing them in a Telegram channel via a bot, which then generates shareable links. The approach uses Cloudflare's serverless infrastructure to handle the frontend and API logic, while Telegram's storage and API provide the backend image persistence.

Developers should choose this tool if they want a lightweight, cost-free image hosting setup with minimal infrastructure management. It suits personal projects, small communities, or anyone seeking an alternative to commercial image hosts. The project explicitly positions itself as a Flickr and Imgur alternative. Deployment requires only a Cloudflare account and a Telegram bot token, making it accessible to users without advanced DevOps knowledge. Optional features include a dashboard, upload protection, short links, image review, anti-hotlinking, Cloudflare R2 storage integration, site customization, whitelist mode, and custom domain support.

The project maintains active documentation with a quick-start guide covering deployment in three steps and detailed configuration references. Development activity shows responsiveness to infrastructure changes, as evidenced by the migration from the original Telegraph API to Telegram Channel storage when the former became unavailable. The codebase includes comprehensive optional features documentation and a local development setup guide, indicating ongoing refinement of the user experience. An update log is maintained to track changes and improvements over time.