Telegraph
Platform · this deep dive is built from the official pages of the platform itself and of the tools that support it.
Overview
Telegraph (telegra.ph) is a publishing service made by the Telegram team. It is built on fundamentally different lines from the other platforms in this guide, and forcing it into the common template would be dishonest. There are no accounts here, no subscribers, no feed, no recommendations, no advertising and no payouts. There is a page with a text field and a "Publish" button.
The service describes itself like this: “Telegra.ph is a minimalist publishing tool that allows you to create richly formatted posts and push them to the web in just a click; Telegraph posts also get beautiful Instant View pages on Telegram”. That last part is the key to why the service exists: it was made so that a link sent into a Telegram chat would open inside the messenger instantly and without advertising.
Open the home page and you will see exactly three elements: the "Telegraph" heading and the "Edit" and "Publish" buttons. There is no sign-in form, no registration and no account area.
The authors explained the idea on launch day: “today we are launching Telegraph — a publishing tool that lets you create richly formatted posts with photos and all sorts of embedded elements… with Telegraph your Telegram channel can put out material as good as the main media”. The same post describes the technology it was all built for: Instant View “allows Telegram users to view articles from across the web in a consistent way and with zero page load time”, and the pages “are cached on Telegram's servers”.
Who's here
Telegraph has no audience in the usual sense: pages have no authors with subscribers, there is no feed and no catalogue.
The only source of readers is the sharing of a link. A page is found because somebody forwarded it, not because the platform showed it. The practical conclusion: Telegraph is not a channel for attracting an audience but a way to lay out a long text nicely for an audience you already have.
The interface language is English. The content of the pages themselves may be in any language: all API requests are made in UTF-8.
Getting started
There is no registration. You open telegra.ph, write a title, an author name and the text, press "Publish" — and get an address of the form telegra.ph/Title-12-15 where, as the documentation explains, “12 is the month and 31 is the day of the article's first publication”.
The ability to come back and edit is tied to the browser, not to an account: behind the button sits an "account" that the service creates automatically. The concept of an account in Telegraph exists only at the level of programmatic access. The documentation describes it like this: “most users only need one account, but this may be useful for channel administrators who would like to keep separate author names and profile links for each channel”.
An account has just three configurable fields, and all of them come with limits: short_name — 1–32 characters, visible only to you above the "Edit/Publish" button; author_name — 0–128 characters, shown under the article title; author_url — 0–512 characters, opened by clicking the author's name and free to lead anywhere, not necessarily into Telegram.
For those who need more, there is a bot. The documentation explains: “to keep the basic interface clean, we launched the @Telegraph bot for those who need advanced features; this bot helps you manage your articles from any number of devices and get view statistics for any Telegraph page”.
What you can publish
The format is tightly constrained, and that is a deliberate decision. A page's content is described by a tree of nodes, and the list of permitted tags is closed: a, aside, b, blockquote, br, code, em, figcaption, figure, h3, h4, hr, i, iframe, img, li, ol, p, pre, s, strong, u, ul, video. Of the attributes only two are allowed — href and src.
Several practical conclusions follow. There are only two heading levels — h3 and h4; there are no tables at all; there are no custom styles, fonts or colours; embedding external material is possible only via iframe and video. Styling a page "to match a brand" is impossible.
Sizes are named directly: a title of 1–256 characters, content of up to 64 KB. 64 kilobytes is a great deal for Latin script and noticeably less for Cyrillic or Chinese characters, because what is counted is bytes, not characters.
The content rules boil down to a report form. At the bottom of every page there is a "Report" button, and its categories show what counts as a violation here: violence, child abuse, copyright infringement, illegal drugs, personal details, other. For rights holders a separate address is given: “send your DMCA takedown request to [email protected]”.
How to grow
You don't — not by the platform's own means. Telegraph has no feed, no subscriptions, no recommendations, no tags, no on-site search and no rankings. The service provides not a single distribution mechanism and nowhere writes about any.
The only thing the platform gives you for assessing results is a view counter, and it is available through the programmatic interface. The getViews method returns the number of page views and can be narrowed down to a year, month, day and hour: year — 2000–2100, month — 1–12, day — 1–31, hour — 0–24. This is proper hourly statistics — a rarity for a free service with no registration — but it is about a single page, not about an audience.
It works without any authorisation whatsoever: the example request from the documentation answers {"ok":true,"result":{"views":40}}. That is, the views of anyone else's Telegraph page are visible to anyone — worth bearing in mind if you consider such data sensitive.
There is no breakdown by traffic source, country or device. There is no ad manager.
The realistic growth scenario looks like this: Telegraph is used as the "long text" for a Telegram channel. The channel supplies the audience, Telegraph supplies a readable page that opens in the messenger instantly.
Path to monetization
Telegraph does not pay authors and offers no way to earn inside it. There is no share of ad revenue, no donations, no paid subscriptions and no paid pages on the platform — the corresponding features appear neither in the interface nor in the list of API methods, which covers only creating, editing and reading pages and viewing statistics.
That is the design of the service: a page has no owner in any legally meaningful sense, no link to payment details, and no concept of an author-as-recipient at all. The only way to earn through Telegraph is to take the reader somewhere else via a link.
The flip side matters too: the service charges authors nothing. Hosting, the address, statistics and the API are free, and no pricing exists.
Tools and automation
Telegraph's programmatic interface is open and detailed, and the platform explicitly invites you to use it: “all developers can use this Telegraph API to create bots like @Telegraph for any other platforms, or even standalone interfaces”.
There are nine methods: createAccount, createPage, editAccountInfo, editPage, getAccountInfo, getPage, getPageList, getViews, revokeAccessToken. Listing an account's pages is limited: getPageList returns a list sorted from the most recently created, with the parameters offset (default 0) and limit (0–200, default 50).
Security deserves a separate note: access to an account rests on a token, and it can be reset — revokeAccessToken revokes the access_token and issues a new one. Without a token, the methods that work with an account do not run: to a request without one the service answers {"ok":false,"error":"ACCESS_TOKEN_INVALID"}. No application for access needs to be filed: an account and a token are created by an ordinary createAccount request.
The documentation explains the content format with a JavaScript code example that turns an article's DOM tree into an array of nodes and sends it to createPage — so writing your own editor is not hard.
Limits and rules
- No accounts in the usual sense. There is no sign-in, no password and no access recovery; an "account" exists only as an API token with the fields
short_name,author_name,author_url. - Sizes. A title of 1–256 characters, content of up to 64 KB.
- Markup. A closed list of 24 tags, only the
hrefandsrcattributes — no tables and no custom styles. - Headings. Only
h3andh4. - API. Nine methods,
getPageListreturns no more than 200 pages per request. - Reports. Six violation categories and a separate address for DMCA requests.
- There is no monetization either for the platform or for the author.
Who it's for
Suits you as an adjunct to a Telegram channel: long texts, instructions and roundups that will not fit in a message open in the messenger instantly and are read without an external browser.
Suits quick one-off posts with no registration: a note, an announcement, a document that simply needs to be put up at a link.
Suits developers: the API is open, the token is issued by a request, and there are hourly view statistics for any page.
Does not suit you as a standalone platform: there is no audience, no feed, no search and no recommendations here, and you bring the readers yourself. Does not suit you if you need branded styling, tables or complex layout. Does not suit earning money: there are no monetization methods whatsoever. And it does not suit projects where retaining access matters: with no account, losing the browser or the token means losing the ability to edit the page.
Verified data
The checked data this deep dive rests on.
About the platform
the platform describes itself as follows: «Telegra.ph is a minimalist publishing tool that allows you to create richly formatted posts and push them to the Web in just a click. Telegraph posts also get beautiful Instant View pages on Telegram.»
Self-description: this is the platform's claim about itself, not an independent assessment
source, checked 2026-07-28
Telegraph was launched together with Instant View; the announcement said: «today we are launching Telegraph — a publishing tool… with Telegraph your Telegram channel can put out material as good as the main media»
A Telegram announcement; the exact date is not stated on the page
source, checked 2026-07-28
Instant View allows Telegram users to view articles from across the web in a consistent way and with zero page load time; the pages are cached on Telegram's servers
It was for this mechanism that Telegraph was created
source, checked 2026-07-28
Account and access
there is no registration, no sign-in and no access recovery; an «account» exists only as an API token with the fields short_name (1-32 characters), author_name (0-128) and author_url (0-512)
Advanced features are moved out into the @Telegraph bot
source, checked 2026-07-28
What you can publish
a closed list of 24 tags: a, aside, b, blockquote, br, code, em, figcaption, figure, h3, h4, hr, i, iframe, img, li, ol, p, pre, s, strong, u, ul, video; of the attributes only href and src are allowed
There are no tables; headings come in only two levels; there are no custom styles
source, checked 2026-07-28
Analytics
view statistics for any page are available without authorisation and are broken down by year (2000-2100), month (1-12), day (1-31) and hour (0-24)
We ran the example from the documentation and got the response {"ok":true,"result":{"views":40}} — this is our own measurement of the API response
source, checked 2026-07-28
Limits and restrictions
a page title of 1-256 characters, content of up to 64 KB
The 64 KB are counted in bytes, so for Cyrillic and Chinese characters the volume of text is smaller
source, checked 2026-07-28
Legal
the report form on a page contains six categories (violence, child abuse, copyright, illegal drugs, personal details, other); DMCA requests are sent to [email protected]
We found no separate terms of use on telegra.ph
source, checked 2026-07-28
API access
Ways to earn. nine methods: createAccount, createPage, editAccountInfo, editPage, getAccountInfo, getPage, getPageList, getViews, revokeAccessToken; requests over HTTPS to api.telegra.ph/%method%, GET and POST, a JSON response
getPageList: offset defaults to 0, limit 0-200 (default 50)
source, checked 2026-07-28
methods that work with an account do not run without a token: the service answers {"ok":false,"error":"ACCESS_TOKEN_INVALID"}
Our own measurement of the API response on the check date
source, checked 2026-07-28
Catalogue section: all similar See also: catalogue index · region: Middle East · scheduler comparison · find by situation · platform restrictions