A LINE Official Account profile page returns 79 words to a plain HTTP client from a Japanese exit, 80 from Thailand and 112 from the United States, and exactly the same counts when rendered. The exit country rewrites the language of the page chrome, not the account. Plain HTTP costs 91,422 bytes; rendering costs 1,833,420 for the same words. We measured it on 28 September 2026. The setting for LINE proxies is one line: residential exit pinned to the account's market, plain HTTP, no browser.
The keyword belongs to a vendor called Proxyline and to card games
Search "line proxies" from the United States and the first page is not about LINE. Four of ten results are a per-IP vendor whose brand happens to be Proxyline, plus its Firefox extension and its review page; one is an r/EDH thread about where to draw the line on Magic card proxies; the AI Overview hedges between the two. Only two results are about the messenger, both vendor listicles ranking providers, and the suggest box confirms the confusion: proxies for linewize, proxyline alternative, can china use line app, line proxies mtg.
What none of them does is fetch a page.line.me URL. LINE runs the messenger of Japan, Thailand and Taiwan, and every business on it has an Official Account with a public profile page: name, description, hours, a LocalBusiness block, sometimes a feed of posts. Those pages are what a brand-monitoring, market-research or local-business-data job actually reads. So we picked one, a ramen shop in Japan listed in LINE's own sitemap, and measured it.
The exit country rewrites the page language, not the account
We audited page.line.me/kfc5694s with and without JavaScript from three residential exits within four minutes.
| Exit | No-JS words | Rendered words | Title suffix served | Description language | Audit time (both passes) |
|---|---|---|---|---|---|
| Japan | 79 | 79 | LINE 公式アカウント | Japanese | 6.6 s |
| Thailand | 80 | 80 | บัญชีทางการ LINE | Thai | 5.7 s |
| United States | 112 | 112 | LINE Official Account | English | 8.7 s |
Three things are stable across the three rows: the H1 is the account name in every country, the canonical is present without JavaScript, and the audit diff is empty everywhere, no title change between passes, no H1 that exists only in the render, no content that lives only in the script. The account's own text is the same 519 Markdown words from Japan whether or not a browser runs. What moves is LINE's chrome around it: the title suffix, the meta description ("Add them as a friend for the latest news" in English, the same sentence in Japanese and Thai), the button labels. The extra 33 words the US exit returns are English UI strings, not more data about the shop.
That has one practical consequence. If you collect Official Account pages across markets, the page language is a function of your exit, not of the account. Fetch a Bangkok restaurant from a Japanese exit and its chrome is Japanese; the description the business wrote stays in Thai. Pin the exit to the market you are reading and parsers stop breaking on a suffix that changed language overnight. On TikTok the exit selects a different backend; on LINE it selects a translation of the frame.
Rendering multiplies the bytes by 20 and adds nothing
On 28 September 2026 the plain fetch of the page from Japan was 91,422 bytes in 2.0 seconds and produced 519 Markdown words, six headings and one image. The rendered fetch was 1,833,420 bytes in 5.7 seconds and produced 519 Markdown words, six headings and one image. Twenty times the bytes, nothing extra, which is the same shape we measured on Kakao and Zalo in reverse: those two serve nothing without a browser, LINE serves everything without one.
Counting a gigabyte as 10^9 bytes, and using the per-GB prices on our pricing page:
| Fetch | Bytes per page | Pages per GB | Residential Basic $0.80/GB | Residential Premium $2.20/GB | Mobile $2.30/GB |
|---|---|---|---|---|---|
| Plain HTTP (79 words, 519 in Markdown) | 91,422 | 10,938 | $0.000073 | $0.00020 | $0.00021 |
| Rendered (same words) | 1,833,420 | 545 | $0.00147 | $0.00404 | $0.00422 |
Ten thousand Official Account pages over plain HTTP on residential Basic is $0.73. The same ten thousand rendered is $14.70, twenty times more, for the same 519 words each. Nothing in seven fetches from three countries asked about our address, so the Basic line is the right one; the Premium and Mobile columns buy nothing we could measure on a logged-out profile page. Spend the money on the exit country instead, which is a per-request flag on the residential network. For sizing a pool from the page weight, how much proxy data you need does the arithmetic.
robots.txt allows the profile pages and hands you 70 sitemap shards
page.line.me/robots.txt is 382 bytes and disallows four things for every crawler: /*/report, /*/profile/img, /*/signboard and /*/signboard/. The report form, the raw profile image and the signboard widget are out; the profile page itself is in. Then one line that matters more than the four above it:
User-agent: *
Disallow: /*/report
Disallow: /*/profile/img
Disallow: /*/signboard
Disallow: /*/signboard/
Sitemap: https://page.line.me/sitemaps/index.xmlThat index lists 70 account-page shards, each with a lastmod of the next day. We opened the first: 4,805,282 bytes and exactly 50,000 profile URLs, the ramen shop among them. LINE is publishing the list of the pages it wants read from outside, tens of thousands per shard, refreshed daily. For a market-wide collection that is the crawl frontier, free, and the reason nobody needs to guess account ids. The sitemap is served from a CDN with a five-minute cache and, unlike the pages, is the same from every exit.
The Messaging API is for your own account and needs a channel access token
LINE's developer platform is generous with businesses and silent with everyone else. The Messaging API reference documents how to issue, verify and revoke a channel access token (POST /v2/oauth/accessToken), and behind that token you get GET /v2/bot/insight/followers?date= for the follower count and GET /v2/bot/followers/ids for the list. Every one of those calls is scoped to the channel that issued the token: your own Official Account. There is no unauthenticated read, no oEmbed and no public search endpoint. For anyone else's account, the public profile page is the only surface, and as measured above it is a complete one.
The LY Corporation Common Terms of Use, section 15, draw the line in two items. Item 5 prohibits wrongfully operating the services "by using BOT, cheat tools or other technical means"; item 8 prohibits "wrongfully collecting, accumulating, disclosing or providing information related to third parties such as personal information, registration information and usage history information". Reading a business's public profile page, which LINE lists in a 70-shard sitemap for that purpose, is neither. Running automated accounts, or harvesting users' personal data through the app, is both, and we do not help with either.
The setting that works on LINE
- Network: residential proxies, Basic line, $0.80/GB. Seven fetches from Japan, Thailand and the United States produced seven plain 200s with the full profile; the Premium ($2.20/GB) and Mobile ($2.30/GB) lines returned nothing extra on logged-out reads.
- Fetch mode:
engine: tls, plain HTTP. Without JavaScript the page is 91,422 bytes and 79 audited words (519 in Markdown); rendered it is 1,833,420 bytes for the same words. Never render a page.line.me profile. - Country: pin the exit to the account's market. The same URL served Japanese chrome from Japan (79 words), Thai from Thailand (80) and English from the United States (112); the account text does not change, the frame around it does. A rotating pool without a country hands your parser three languages.
- When the proxy is not enough: there is no LINE collector in our catalogue. Use the web scraping API without rendering, $0.0002 per page, to get the profile as Markdown or JSON with the exit pinned, and feed it the 50,000-URL sitemap shards as the URL list; for the two-view check the SEO audit API fetched this page both ways in 5.7 seconds for $0.0012.
- Free tier: every account gets $2 of free API usage per month, which at $0.000073 per plain page is about 27,000 Official Account pages before you pay anything.
Pin the market, fetch over plain HTTP, crawl from the sitemap, leave the browser and the accounts alone. That is the whole configuration for LINE.