blast-studio 0.0.0-stage → 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (255) hide show
  1. package/LICENSE +202 -0
  2. package/README.md +138 -2
  3. package/bin/bstudio.mjs +13 -0
  4. package/dist/agent-env.js +152 -0
  5. package/dist/brief.js +53 -0
  6. package/dist/budget/ledger.js +153 -0
  7. package/dist/campaign-zip.js +93 -0
  8. package/dist/cli.js +118 -0
  9. package/dist/commands/accept.js +64 -0
  10. package/dist/commands/auth.js +77 -0
  11. package/dist/commands/brief.js +117 -0
  12. package/dist/commands/budget.js +22 -0
  13. package/dist/commands/dashboard.js +9 -0
  14. package/dist/commands/doctor.js +57 -0
  15. package/dist/commands/export.js +42 -0
  16. package/dist/commands/init.js +24 -0
  17. package/dist/commands/install-skills.js +52 -0
  18. package/dist/commands/library.js +12 -0
  19. package/dist/commands/make.js +71 -0
  20. package/dist/commands/mark.js +44 -0
  21. package/dist/commands/new.js +25 -0
  22. package/dist/commands/plan.js +57 -0
  23. package/dist/commands/render-preview.js +43 -0
  24. package/dist/commands/render.js +243 -0
  25. package/dist/commands/review.js +119 -0
  26. package/dist/commands/revise.js +73 -0
  27. package/dist/commands/sources.js +33 -0
  28. package/dist/commands/status.js +34 -0
  29. package/dist/config.js +141 -0
  30. package/dist/dashboard/server.js +171 -0
  31. package/dist/dashboard/static/app.css +1 -0
  32. package/dist/dashboard/static/app.js +52 -0
  33. package/dist/dashboard/static/index.html +8 -0
  34. package/dist/env.js +47 -0
  35. package/dist/export.js +110 -0
  36. package/dist/fetch-text.js +64 -0
  37. package/dist/io.js +1 -0
  38. package/dist/keychain.js +41 -0
  39. package/dist/library.js +49 -0
  40. package/dist/packs.js +91 -0
  41. package/dist/plan.js +75 -0
  42. package/dist/posts.js +40 -0
  43. package/dist/providers/images.js +116 -0
  44. package/dist/providers/voice.js +55 -0
  45. package/dist/render/ffmpeg.js +96 -0
  46. package/dist/render/metrics.js +109 -0
  47. package/dist/render/stills.js +172 -0
  48. package/dist/render/template.js +20 -0
  49. package/dist/render/video.js +173 -0
  50. package/dist/review/gates.js +201 -0
  51. package/dist/review/reviewer.js +79 -0
  52. package/dist/review/score.js +21 -0
  53. package/dist/review/slop.js +17 -0
  54. package/dist/review-hash.js +21 -0
  55. package/dist/types.js +29 -0
  56. package/dist/updater/check.js +140 -0
  57. package/dist/updater/propose.js +144 -0
  58. package/dist/workspace.js +142 -0
  59. package/package.json +45 -4
  60. package/platforms/bluesky/guide.md +94 -0
  61. package/platforms/bluesky/pack.yml +150 -0
  62. package/platforms/dailydev/guide.md +82 -0
  63. package/platforms/dailydev/pack.yml +152 -0
  64. package/platforms/devto/guide.md +93 -0
  65. package/platforms/devto/pack.yml +119 -0
  66. package/platforms/gist/guide.md +92 -0
  67. package/platforms/gist/pack.yml +119 -0
  68. package/platforms/github-discussion/guide.md +92 -0
  69. package/platforms/github-discussion/pack.yml +122 -0
  70. package/platforms/hashnode/guide.md +93 -0
  71. package/platforms/hashnode/pack.yml +124 -0
  72. package/platforms/hn/guide.md +48 -0
  73. package/platforms/hn/pack.yml +59 -0
  74. package/platforms/instagram/guide.md +95 -0
  75. package/platforms/instagram/pack.yml +136 -0
  76. package/platforms/lemmy/guide.md +88 -0
  77. package/platforms/lemmy/pack.yml +141 -0
  78. package/platforms/linkedin/guide.md +93 -0
  79. package/platforms/linkedin/pack.yml +145 -0
  80. package/platforms/mastodon/guide.md +92 -0
  81. package/platforms/mastodon/pack.yml +138 -0
  82. package/platforms/medium/guide.md +92 -0
  83. package/platforms/medium/pack.yml +119 -0
  84. package/platforms/newsletter/guide.md +94 -0
  85. package/platforms/newsletter/pack.yml +144 -0
  86. package/platforms/producthunt/guide.md +92 -0
  87. package/platforms/producthunt/pack.yml +166 -0
  88. package/platforms/reddit/guide.md +92 -0
  89. package/platforms/reddit/pack.yml +151 -0
  90. package/platforms/snapshots/.gitkeep +0 -0
  91. package/platforms/snapshots/bluesky-10.sha256 +1 -0
  92. package/platforms/snapshots/bluesky-10.txt +1 -0
  93. package/platforms/snapshots/bluesky-11.sha256 +1 -0
  94. package/platforms/snapshots/bluesky-11.txt +1 -0
  95. package/platforms/snapshots/bluesky-12.sha256 +1 -0
  96. package/platforms/snapshots/bluesky-12.txt +1 -0
  97. package/platforms/snapshots/bluesky-13.sha256 +1 -0
  98. package/platforms/snapshots/bluesky-13.txt +1 -0
  99. package/platforms/snapshots/bluesky-14.sha256 +1 -0
  100. package/platforms/snapshots/bluesky-14.txt +1 -0
  101. package/platforms/snapshots/cross-platform-63.sha256 +1 -0
  102. package/platforms/snapshots/cross-platform-63.txt +1 -0
  103. package/platforms/snapshots/cross-platform-64.sha256 +1 -0
  104. package/platforms/snapshots/cross-platform-64.txt +1 -0
  105. package/platforms/snapshots/dailydev-55.sha256 +1 -0
  106. package/platforms/snapshots/dailydev-55.txt +1 -0
  107. package/platforms/snapshots/dailydev-56.sha256 +1 -0
  108. package/platforms/snapshots/dailydev-56.txt +1 -0
  109. package/platforms/snapshots/dailydev-57.sha256 +1 -0
  110. package/platforms/snapshots/dailydev-57.txt +1 -0
  111. package/platforms/snapshots/devto-26.sha256 +1 -0
  112. package/platforms/snapshots/devto-26.txt +1 -0
  113. package/platforms/snapshots/devto-27.sha256 +1 -0
  114. package/platforms/snapshots/devto-27.txt +1 -0
  115. package/platforms/snapshots/devto-28.sha256 +1 -0
  116. package/platforms/snapshots/devto-28.txt +1 -0
  117. package/platforms/snapshots/devto-29.sha256 +1 -0
  118. package/platforms/snapshots/devto-29.txt +1 -0
  119. package/platforms/snapshots/gist-52.sha256 +1 -0
  120. package/platforms/snapshots/gist-52.txt +1 -0
  121. package/platforms/snapshots/gist-53.sha256 +1 -0
  122. package/platforms/snapshots/gist-53.txt +1 -0
  123. package/platforms/snapshots/gist-54.sha256 +1 -0
  124. package/platforms/snapshots/gist-54.txt +1 -0
  125. package/platforms/snapshots/github-discussion-policy.sha256 +1 -0
  126. package/platforms/snapshots/github-discussion-policy.txt +1 -0
  127. package/platforms/snapshots/hashnode-30.sha256 +1 -0
  128. package/platforms/snapshots/hashnode-30.txt +1 -0
  129. package/platforms/snapshots/hashnode-31.sha256 +1 -0
  130. package/platforms/snapshots/hashnode-31.txt +1 -0
  131. package/platforms/snapshots/hashnode-32.sha256 +1 -0
  132. package/platforms/snapshots/hashnode-32.txt +1 -0
  133. package/platforms/snapshots/hn-23.sha256 +1 -0
  134. package/platforms/snapshots/hn-23.txt +1 -0
  135. package/platforms/snapshots/hn-24.sha256 +1 -0
  136. package/platforms/snapshots/hn-24.txt +1 -0
  137. package/platforms/snapshots/hn-25.sha256 +1 -0
  138. package/platforms/snapshots/hn-25.txt +1 -0
  139. package/platforms/snapshots/hyperframes-releases.sha256 +1 -0
  140. package/platforms/snapshots/hyperframes-releases.txt +1 -0
  141. package/platforms/snapshots/instagram-43.sha256 +1 -0
  142. package/platforms/snapshots/instagram-43.txt +1 -0
  143. package/platforms/snapshots/instagram-47.sha256 +1 -0
  144. package/platforms/snapshots/instagram-47.txt +1 -0
  145. package/platforms/snapshots/lemmy-policy.sha256 +1 -0
  146. package/platforms/snapshots/lemmy-policy.txt +1 -0
  147. package/platforms/snapshots/linkedin-1.sha256 +1 -0
  148. package/platforms/snapshots/linkedin-1.txt +1 -0
  149. package/platforms/snapshots/linkedin-2.sha256 +1 -0
  150. package/platforms/snapshots/linkedin-2.txt +1 -0
  151. package/platforms/snapshots/linkedin-3.sha256 +1 -0
  152. package/platforms/snapshots/linkedin-3.txt +1 -0
  153. package/platforms/snapshots/linkedin-4.sha256 +1 -0
  154. package/platforms/snapshots/linkedin-4.txt +1 -0
  155. package/platforms/snapshots/mastodon-15.sha256 +1 -0
  156. package/platforms/snapshots/mastodon-15.txt +1 -0
  157. package/platforms/snapshots/mastodon-16.sha256 +1 -0
  158. package/platforms/snapshots/mastodon-16.txt +1 -0
  159. package/platforms/snapshots/mastodon-17.sha256 +1 -0
  160. package/platforms/snapshots/mastodon-17.txt +1 -0
  161. package/platforms/snapshots/medium-34.sha256 +1 -0
  162. package/platforms/snapshots/medium-34.txt +1 -0
  163. package/platforms/snapshots/medium-35.sha256 +1 -0
  164. package/platforms/snapshots/medium-35.txt +1 -0
  165. package/platforms/snapshots/medium-36.sha256 +1 -0
  166. package/platforms/snapshots/medium-36.txt +1 -0
  167. package/platforms/snapshots/newsletter-58.sha256 +1 -0
  168. package/platforms/snapshots/newsletter-58.txt +1 -0
  169. package/platforms/snapshots/newsletter-59.sha256 +1 -0
  170. package/platforms/snapshots/newsletter-59.txt +1 -0
  171. package/platforms/snapshots/newsletter-60.sha256 +1 -0
  172. package/platforms/snapshots/newsletter-60.txt +1 -0
  173. package/platforms/snapshots/newsletter-61.sha256 +1 -0
  174. package/platforms/snapshots/newsletter-61.txt +1 -0
  175. package/platforms/snapshots/newsletter-62.sha256 +1 -0
  176. package/platforms/snapshots/newsletter-62.txt +1 -0
  177. package/platforms/snapshots/openai-image-pricing.sha256 +1 -0
  178. package/platforms/snapshots/openai-image-pricing.txt +1 -0
  179. package/platforms/snapshots/playwright-releases.sha256 +1 -0
  180. package/platforms/snapshots/playwright-releases.txt +1 -0
  181. package/platforms/snapshots/producthunt-37.sha256 +1 -0
  182. package/platforms/snapshots/producthunt-37.txt +1 -0
  183. package/platforms/snapshots/producthunt-38.sha256 +1 -0
  184. package/platforms/snapshots/producthunt-38.txt +1 -0
  185. package/platforms/snapshots/producthunt-39.sha256 +1 -0
  186. package/platforms/snapshots/producthunt-39.txt +1 -0
  187. package/platforms/snapshots/reddit-20.sha256 +1 -0
  188. package/platforms/snapshots/reddit-20.txt +1 -0
  189. package/platforms/snapshots/reddit-21.sha256 +1 -0
  190. package/platforms/snapshots/reddit-21.txt +1 -0
  191. package/platforms/snapshots/reddit-22.sha256 +1 -0
  192. package/platforms/snapshots/reddit-22.txt +1 -0
  193. package/platforms/snapshots/substack-policy.sha256 +1 -0
  194. package/platforms/snapshots/substack-policy.txt +1 -0
  195. package/platforms/snapshots/threads-18.sha256 +1 -0
  196. package/platforms/snapshots/threads-18.txt +1 -0
  197. package/platforms/snapshots/threads-19.sha256 +1 -0
  198. package/platforms/snapshots/threads-19.txt +1 -0
  199. package/platforms/snapshots/tiktok-50.sha256 +1 -0
  200. package/platforms/snapshots/tiktok-50.txt +1 -0
  201. package/platforms/snapshots/tiktok-51.sha256 +1 -0
  202. package/platforms/snapshots/tiktok-51.txt +1 -0
  203. package/platforms/snapshots/x-5.sha256 +1 -0
  204. package/platforms/snapshots/x-5.txt +1 -0
  205. package/platforms/snapshots/x-6.sha256 +1 -0
  206. package/platforms/snapshots/x-6.txt +1 -0
  207. package/platforms/snapshots/x-7.sha256 +1 -0
  208. package/platforms/snapshots/x-7.txt +1 -0
  209. package/platforms/snapshots/x-8.sha256 +1 -0
  210. package/platforms/snapshots/x-8.txt +1 -0
  211. package/platforms/snapshots/x-9.sha256 +1 -0
  212. package/platforms/snapshots/x-9.txt +1 -0
  213. package/platforms/snapshots/youtube-shorts-40.sha256 +1 -0
  214. package/platforms/snapshots/youtube-shorts-40.txt +1 -0
  215. package/platforms/snapshots/youtube-shorts-41.sha256 +1 -0
  216. package/platforms/snapshots/youtube-shorts-41.txt +1 -0
  217. package/platforms/snapshots/youtube-shorts-42.sha256 +1 -0
  218. package/platforms/snapshots/youtube-shorts-42.txt +1 -0
  219. package/platforms/sources.yml +947 -0
  220. package/platforms/substack/guide.md +94 -0
  221. package/platforms/substack/pack.yml +116 -0
  222. package/platforms/threads/guide.md +93 -0
  223. package/platforms/threads/pack.yml +148 -0
  224. package/platforms/tiktok/guide.md +92 -0
  225. package/platforms/tiktok/pack.yml +129 -0
  226. package/platforms/x/guide.md +94 -0
  227. package/platforms/x/pack.yml +130 -0
  228. package/platforms/youtube-shorts/guide.md +92 -0
  229. package/platforms/youtube-shorts/pack.yml +138 -0
  230. package/providers/prices.yml +31 -0
  231. package/schemas/campaign.v2.json +26 -0
  232. package/schemas/manifest.v1.json +37 -0
  233. package/schemas/pack.schema.json +601 -0
  234. package/schemas/review.schema.json +31 -0
  235. package/skills/studio-reviewer/SKILL.md +13 -0
  236. package/skills/studio-updater/SKILL.md +8 -0
  237. package/skills/studio-video/SKILL.md +20 -0
  238. package/skills/studio-visual/SKILL.md +12 -0
  239. package/skills/studio-writer/SKILL.md +14 -0
  240. package/templates/README.md +7 -0
  241. package/templates/card.html +1 -0
  242. package/templates/carousel-closing.html +1 -0
  243. package/templates/carousel-content.html +1 -0
  244. package/templates/carousel-title.html +1 -0
  245. package/templates/code.html +1 -0
  246. package/templates/fonts/IBM-Plex-OFL.txt +93 -0
  247. package/templates/fonts/IBMPlexMono.woff2 +0 -0
  248. package/templates/fonts/IBMPlexSans.woff2 +0 -0
  249. package/templates/fonts/Space-Grotesk-OFL.txt +93 -0
  250. package/templates/fonts/SpaceGrotesk.woff2 +0 -0
  251. package/templates/poster.html +1 -0
  252. package/templates/quote.html +1 -0
  253. package/templates/thumbnail.html +1 -0
  254. package/test/fixtures/reviews/calibration.json +22 -0
  255. package/test/fixtures/reviews/grounding/cases.json +17 -0
@@ -0,0 +1 @@
1
+ Email sender guidelines The guidelines in this article can help you successfully send and deliver email to personal Gmail accounts. Starting in 2024, email senders must meet the requirements described here to send email to Gmail personal accounts. A personal Gmail account is an account that ends in @gmail.com or @googlemail.com. For the latest updates about sender requirements, visit the Email sender guidelines FAQ . Google Workspace senders: If you use Google Workspace to send large volumes of email, review the Spam and abuse policy in Gmail . The policy is part of the Google Workspace Acceptable Use Policy . Sender requirements updates This table lists our updates to the sender guidelines and requirements: Sender requirement Date added Use a TLS connection for transmitting email Dec. 2023 Sender requirements and guidelines Follow these guidelines to help ensure messages are delivered to Gmail accounts as expected, and to help prevent Gmail from limiting sending rates, blocking messages, or marking messages as spam. Requirements for all senders Starting February 1, 2024, all email senders who send email to Gmail accounts must meet the requirements in this section. Important: If you send more than 5,000 messages per day to Gmail accounts, follow the Requirements for sending 5,000 or more messages per day . Set up SPF or DKIM email authentication for your sending domains. Ensure that sending domains or IPs have valid forward and reverse DNS records, also referred to as PTR records. Learn more Use a TLS connection for transmitting email. For steps to set up TLS in Google Workspace, visit Require a secure connection for email . Keep spam rates reported in Postmaster Tools below 0.3%. Learn more about spam rates Format messages according to the Internet Message Format standard, RFC 5322 . Don’t impersonate Gmail From: headers. Gmail will begin using a DMARC quarantine enforcement policy , and impersonating Gmail From: headers might impact your email delivery. Requirements for sending 5,000 or more messages per day Starting February 1, 2024, email senders who send more than 5,000 messages per day to Gmail accounts must meet the requirements in this section. Set up SPF and DKIM email authentication for your domain. Set up DMARC email authentication for your sending domain. Your DMARC enforcement policy can be set to none. Learn more Ensure that sending domains or IPs have valid forward and reverse DNS records, also referred to as PTR records. Learn more Use a TLS connection for transmitting email. For steps to set up TLS in Google Workspace, visit Require a secure connection for email . Keep spam rates reported in Postmaster Tools below 0.30%. Learn more about spam rates Format messages according to the Internet Message Format standard, RFC 5322 . Don’t impersonate Gmail From: headers. Gmail will begin using a DMARC quarantine enforcement policy , and impersonating Gmail From: headers might impact your email delivery. For direct email, the domain in the sender's From: header must be aligned with either the SPF domain or the DKIM domain. This is required to pass DMARC alignment . Marketing messages and subscribed messages must support one-click unsubscribe, and include a clearly visible unsubscribe link in the message body. Learn more If you send more than 5,000 emails per day before February 1, 2024, follow the guidelines in this article as soon as possible. Meeting the sender requirements before the deadline may improve your email delivery. If you don’t meet the requirements described in this article, your email might not be delivered as expected, or might be marked as spam. To get help with email delivery issues, go to Troubleshooting . Email authentication requirements & guidelines We require that you set up these email authentication methods for your domain: All senders: SPF or DKIM Bulk senders: SPF, DKIM, and DMARC Authenticated messages: Help protect recipients from malicious messages, such as spoofing and phishing messages. Help protect you and your organization from being impersonated. Are less likely to be rejected or marked as spam by Gmail. Set up email authentication for each of your sending domains at your domain provider. You can use instructions Google provides and our domain provider's email authentication support information. To verify messages are authenticated, Google performs checks on messages sent to Gmail accounts. To improve email delivery, we recommend that you always set up SPF, DKIM, and DMARC for your domains. Make sure you're meeting the minimum authentication requirements described on this page. Messages that aren’t authenticated with these methods might be marked as spam or rejected with a 5.7.26 error . If you use an email service provider, verify that they authenticate your domain’s email with SPF and DKIM. If you regularly forward email or manage a forwarding service, help ensure forwarded messages are authenticated by following our Best practices for forwarding email to Gmail . We recommend you always set up email authentication for the domain that hosts your public website SPF SPF prevents spammers from sending unauthorized messages that appear to be from your domain. Set up SPF by publishing an SPF record at your domain. The SPF record for your domain should include all email senders for your domain. If your third-party senders aren't included in your SPF record, messages from these senders are more likely to be marked as spam. Learn how to define your SPF record and add it to your domain . DKIM Turn on DKIM for the domain that sends your email. Receiving servers use DKIM to verify that the domain owner actually sent the message. If you use Google Workspace to send email, learn how to turn on DKIM for your domain . If you don’t use Google Workspace to send email, you can use one of many available internet tools to create your DKIM keys, or check with your domain provider for help. Important: Sending to personal Gmail accounts requires a DKIM key of 1024 bits or longer. For security reasons, we recommend using a 2048-bit key if your domain provider supports this. Learn more about DKIM key length . DMARC DMARC tells receiving servers what to do with your messages that don’t pass SPF or DKIM. Set up DMARC by publishing a DMARC record for your domain. To pass DMARC authentication, messages must be authenticated by SPF or DKIM, or both. The authenticating domain must be the same domain that appears in the message From: header. Learn how to set up DMARC . We recommend you set up DMARC reports so you can monitor email sent from your domain, or appears to have been sent from your domain. DMARC reports help you identify senders that may be impersonating your domain. Learn more about DMARC reports . Infrastructure configuration requirements and guidelines IP addresses Important: The sending IP address must match the IP address of the hostname specified in the Pointer (PTR) record. The public IP address of a sending SMTP server must have a corresponding PTR record that resolves to a hostname. This is called a reverse DNS lookup . The same hostname must also have an A (for IPv4) or AAAA (for IPv6) record that resolves to the same public IP address used by the sending server. This is called a forward DNS lookup . Set up valid reverse DNS records of your sending server IP addresses that point to your domain. Check for a PTR record with the Google Admin Toolbox Dig tool. Important: The sending IP address must match the IP address of the hostname specified in the Pointer (PTR) record. Shared IP addresses A shared IP address is an IP address used by more than one email sender. The activity of any senders using a shared IP address affects the reputation of all senders for that shared IP address. A negative reputation can impact your delivery rate. If you use a shared IP address for sending email: Make sure the shared IP address isn’t on any internet blocklist. Messages sent from IP addresses on a blocklist are more likely to be marked as spam. If you use an email service provider for your shared IP, use Postmaster Tools to check the reputation of the shared IP address. Subscription requirements and guidelines If you manage mailing lists or other email subscriptions, you should send email only to people who want to get messages from you. These recipients are less likely to report your messages as spam. If messages from your domain are frequently reported as spam, future messages from you are more likely to be marked as spam. Over time, user spam reports can lower your domain’s reputation. Check your spam rate and your domain and IP address reputation with Postmaster Tools . Make it easy to subscribe To help ensure recipients are engaged: Make sure recipients opt in to get messages from you. Confirm each recipient's email address before subscribing them. Periodically send messages to confirm that recipients want to stay subscribed. Consider unsubscribing recipients who don’t open or read your messages. Make it easy to unsubscribe Always give recipients an easy way to unsubscribe from your messages. Letting people opt out of your messages can improve open rates, click-through rates, and sending efficiency. Important: If you send more than 5,000 message per day, your marketing and subscribed messages must support one-click unsubscribe . To set up one-click unsubscribe for Gmail messages, include both of these headers in outgoing messages: List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: <https://solarmora.com/unsubscribe/example> When a recipient unsubscribes using one-click, you receive this POST request: "POST /unsubscribe/example HTTP/1.1 Host: solarmora.com Content-Type: application/x-www-form-urlencoded Content-Length: 26 List-Unsubscribe=One-Click" Learn more about List-Unsubscribe: headers in RFC 2369 and RFC 8058 . These unsubscribe options can also be used but they should not replace one-click unsubscribe: Let recipients review the individual mailing lists they’re subscribed to. Let them unsubscribe from lists individually, or all lists at once. Automatically unsubscribe recipients who have multiple bounced messages. Message formatting requirements and guidelines Follow these message formatting guidelines to help ensure messages are delivered as expected: If your messages are in HTML, format them according to HTML standards . Follow these message header guidelines: From: headers should include only one email address. For example: From: notifications@solarmora.com Avoid excessively large message headers. To learn more, visit Gmail message header limits . Format messages according to the Internet Format Standard ( RFC 5322 ). Make sure every message includes a valid Message-ID. Make sure single-instance message headers are included only once in a message. Examples of single-instance headers include From:, To:, Subject:, and Date:. Message headers and message content should be accurate, and not misleading or deceptive. Email message subject, headers, display names, and other message elements should accurately represent the sender identity and message content, and shouldn’t be misleading. For example, don’t send messages with subject lines starting with Re: or Fwd: unless the messages are actual replies or forwards, and include only actual senders and recipients in From: and To: headers. Don't use emojis or other non-standard characters to imitate graphic elements in messages, with the intent to deceive or influence recipients. For example, don’t use emojis or images next to display names or brand names to imply the name has been verified in some way. Don’t use HTML and CSS to hide content in your messages. Hiding content might cause messages to be marked as spam. Web links in the message body should be visible and easy to understand. Recipients should know what to expect when they click a link. Sender information should be clear and visible. Format the following international domains according to Section 5.2 of Unicode Technical Standard #39 . An international domain is also called an ; internationalized domain name (IDN ), and is a URL that is specific to a region or country. Authenticating domain Envelope from domain Payload domain Reply-to domain Sender domain Guidelines for email display names Misuse of display names can impact email deliverability when sending to personal Gmail accounts. When you send commercial or bulk email, it’s important to follow the Email sender guidelines and to respect recipients’ inboxes. Follow the display name guidelines here to help ensure your messages are delivered as expected. Display name guidelines Sender display names should be used exclusively to identify the sender. Display names should reflect a consistent, clear, and accurate statement of the sender's identity, name and/or organization. Don’t include subject or message content in display names. Display names should never be used to attempt to deceive the recipient of the email. Avoid misleading or deceptive display names by following these guidelines: Identify the sender first and don’t include subject or message content in this display name. For example, don’t use display names like these: Important Update ---------- From [Company Name] TIME IS RUNNING OUT (SALE) [Product/News] Alert URGENT REQUEST Last Chance The display name should not include the recipient’s name and should not imply a message reply or threaded conversation. For example, don’t use display names like these: [recipient’s first name] <info@organization.com> User (2) The display name should clearly identify the sender and shouldn't include emojis or other non-standard characters to imitate graphic elements. For example, don’t use display names like these: LATEST UPDATE MAIL, ME [1] New Message Spoofing and display names Avoid these types of spoofing, which are deceptive display name practices: Using an @gmail.com domain as the display name for bulk email Using characters that imply the mail is part of threaded conversation, for example: User (2) Using the name of the recipient in the display name To manage an effective email campaign, your messages should connect you and your recipients in a meaningful way. Be sure to follow all Email sender guidelines to improve your email delivery and effectiveness. Senders who fail to follow best practices may not be considered for deliverability mitigations. Sending practices requirements and guidelines To reduce the chances that messages from your domain are sent to spam or blocked by Gmail, follow the best practices in this section. Authenticate email with SPF and DKIM that are aligned with each other at the organizational level. If you use an email provider, verify that your provider supports this. Ideally, send all messages from the same IP address. If you must send from multiple IP addresses, use a different IP address for each message type. For example, use one IP address for sending account notifications and a different IP address for sending promotional messages. Messages of the same category should have the same From: email address. For example, messages from a domain called example.com might have From: addresses like: Sales receipt messages: sales@example.com Promotional messages: deals@example.com Account notification messages: alert@example.com Messages sent from an address in the recipient’s contacts are less likely to be marked as spam. Sending practices to avoid Don't mix different types of content in the same message. For example, don't include promotions in sales receipt messages. Don't impersonate other domains or senders without permission. This practice is called spoofing , and Gmail might mark these messages as spam. Don't mark internal messages as spam. This can negatively affect your domain's reputation, and future messages might be marked as spam. Don't purchase email addresses from other companies. Don't send messages to people who didn't sign up to get messages from you. These recipients might mark your messages as spam, and future messages to these recipients will be marked as spam. Avoid opt-in forms that are checked by default and that automatically subscribe users. Some countries and regions restrict automatic opt-in. Before you opt-in users automatically, check the regulations in your region. Some legitimate messages may be marked as spam. Recipients can mark valid messages as not spam, so future messages from the sender should be delivered to their inbox. Increase sending volume slowly to avoid delivery problems These factors affect how quickly you can increase sending volume: Amount of email sent : The more email that you send, the more slowly you should increase sending volume. Frequency of sending email : You can increase the sending volume more quickly when you send daily instead of weekly. Recipient feedback about your messages : Make sure you send only to people who subscribe to your emails, and give recipients an option to unsubscribe. When you increase your sending volume: To protect users from spam, there are limits on the number of messages you can deliver within a certain timeframe. Gmail tracks volume, feedback, and limits per domain and IP address: DKIM and SPF quotas are specific to your domain. If you hit the limit, other domains that send from the same IP may not be affected. The IP address quota is shared for all senders that use that IP address. When the IP address hits its quota, all domains that send from that IP address stop sending emails. As you gradually increase your sending email volume, you should monitor your email delivery with Postmaster Tools . For Google Workspace work and school accounts, sending limits apply even when recipients are in different Google Workspace domains. For example, you might send email to users with email addresses that have the domains your-company.net and example.com . Although the domains are different, if both domains have google.com as their MX record, messages sent to these domains count toward your limit. If you use Google Workspace or Gmail : When you reach the sending limit, the sending rate is limited for the sending IP address. If you send large amounts of email, we recommend you: Send email at a consistent rate. Avoid sending email in bursts. Start with a low sending volume to engaged users, and slowly increase the volume over time. As you increase the sending volume, regularly monitor server responses, spam rate, and the sending domain's reputation. Regular monitoring will allow you to quickly adapt if your sending is rate limited, if the spam rate is increased, or when the sending domain's reputation drops. Avoid introducing sudden volume spikes if you do not have a history of sending large volumes. For example, immediately doubling previously sent volumes suddenly could result in rate limiting or reputation drops. If you change the format of your bulk emails, gradually increase the sending volume of messages with the new format. After making any significant changes to your sending infrastructure or email header structure, increase the modified segment of traffic separately. If messages start bouncing or start being deferred, reduce the sending volume until the SMTP error rate decreases. Then, increase slowly again. If bounces and deferrals continue at a low volume, review individual messages to identify problems. For example, you can try sending a blank test message and see if it experiences issues. Stay within the IP limits for sending: Be aware of email sending limits when sending from domains that have a Google.com MX host. Limit sending email from a single IP address based on the MX record domain, not the domain in the recipient email address. Monitor responses so you can change sending rates as needed to stay within these limits. Pay attention to the SMTP errors you receive. When you exceed your quota, Gmail typically rejects messages with SMTP error code 4.7.28. If you get this error: Do not send email for at least 10 minutes. Identify the cause. If the error message does not specify if you exceeded your DKIM, SPF, or IP quota, assume that all three are affected. After 10 minutes, send emails from a single connection. If the single connection fails, wait another 10 minutes. If successful, increase the number of connections one at a time until your desired number of connections are established. Additional guidelines Guidelines for using email service providers Google and Gmail don’t accept allowlist requests from email providers. We can't guarantee messages sent by email providers will pass Gmail’s spam filters. If you use a third-party email provider to send email for your domain: Verify that the provider follows the guidelines on this page. Large providers, such as Google, AOL, and Yahoo, typically follow these guidelines. Make sure the SPF record for your domain includes all email senders for your domain. If third-party senders aren't included in your SPF record, messages sent from these providers are more likely to be marked as spam. Learn how to set up your SPF record . If you use a domain provider but you manage your own email, we recommend you: Review and follow the requirements and guidelines on this page. Use Postmaster Tools to monitor information about messages sent from your domain to Gmail accounts. Guidelines for email service providers When clients use your service to send email, you’re responsible for their sending practices. We recommend taking these steps to help manage your clients’ sending activity: Offer an email address for reporting email abuse, for example: abuse@email-provider.com . Make sure your contact information in your WHOIS record and on abuse.net is current. Immediately remove any client who uses your service to send spam. Affiliate marketing Affiliate marketing programs offer rewards to companies or individuals that send visitors to your website. However, spammers can abuse these programs. If your brand is associated with marketing spam, other messages sent by you might be marked as spam. We recommend you regularly monitor affiliates, and remove any affiliates that send spam. Phishing exercises Don’t send test phishing messages or test campaigns from your domain. Your domain’s reputation might be negatively affected, and your domain could be added to internet blocklists. Monitoring and troubleshooting Postmaster Tools Use Postmaster Tools to get information about the email you send to Gmail users, for example: When recipients mark your messages as spam Why messages might not be delivered as expected If messages are authenticated Your domain or IP reputation and the impact on message delivery rates Spam rate Regularly monitor your domain's spam rate in Postmaster Tools . Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher. Learn more Maintaining a low spam rate helps senders be more resilient to occasional spikes in user feedback. Maintaining a high spam rate leads to increased spam classification. It can take time for improvements in spam rate to reflect positively on spam classification. Open rate Google doesn't track open rates. Google can't verify the accuracy of open rates reported by third parties. Low open rates aren't necessarily an accurate indicator of deliverability or spam classification issues. Troubleshooting email delivery If messages aren't being delivered as expected: Check regularly that your domain isn’t listed as unsafe with Google Safe Browsing . To check your domain status, enter your domain in the Safe Browsing site status page . Regularly check the status of any domains that are linked to yours. Sending with email service providers If you’re having delivery issues with email sent by a service provider, verify the provider follows the requirements and guidelines on this page. Use the Google Admin Toolbox to review domain settings Use the Google Admin Toolbox to check and fix settings for your domain. Fix the source of rejected email If your messages are rejected, you might get an error message. Learn more about the error so you can fix the problem. Common error messages are: 421, "4.7.0": Messages are rejected because the sending server’s IP address is not on the allowed list for the recipient’s domain. 550, "5.7.1": Messages are rejected because the sending server’s IP address is on an IP suspended list. You might get this error if you’re sending email using a shared IP with a poor reputation. Learn more about email and SMTP error messages: SMTP error reference Fix bounced or rejected emails Fix IPv6 authorization errors An IPv6 authorization error could mean that the PTR record for the sending server isn’t using IPv6. If you use an email service provider, confirm they’re using an IPv6 PTR record. Here's an example of an IPv6 authorization error: 550-5.7.1: Message does not meet IPv6 sending guidelines regarding PTR records and authentication. Use the troubleshooting tool If you’re still having email delivery problems after following the guidelines in this article, try Troubleshooting for senders with email delivery issues . Related topics Email sender guidelines FAQ Fixed bounced emails Fix messages rejected by Google Groups Translations of our policies are provided for your convenience. If there is a conflict between the text of this policy in language other than English and the text of the English language version of the policy, the text of the English language version of the policy takes precedence.
@@ -0,0 +1 @@
1
+ 0efd1643974635247ac96b0370ae46ae23aa02a60d5625a65995e9cded83343a
@@ -0,0 +1 @@
1
+ Submit your link to us Have you got something you think our readers should see? Whether it's a fresh tutorial, great video, a new tool, or opinion piece we want to know about it. Just fill in the form below and your link will be sent across to our editorial team for review. Note: We receive a lot of submissions every week, so whilst we will look over each one, we make no guarantee of inclusion — this is just a quick way for you to put something on our radar . Last updated: September 2020
@@ -0,0 +1 @@
1
+ f833f859001b16677b82918756798080ba6ece2cdcb8da92d84d321c21018668
@@ -0,0 +1 @@
1
+ Want something featured in Changelog News ? Please sign in / up to submit news. Your profile is used for attribution and notification. Submitting other people's work is encouraged. Submitting your own work is also encouraged. Here's a short list of things that we aren't interested in 🙅‍♂️ 🚫 How-to's and tutorials. e.g. - "Configure Nginx on Ubuntu Linux 18.04" 🚫 Commercial products/services. Sponsorship is your path. 🚫 Reader-hostile websites. We consider the entire reading experience . 🚫 Podcast episode suggestions. Use this form instead. The golden rule: if your fellow devs will find it interesting, submit it. That being said... we get a lot of submissions. Do your best to convince us why something is newsworthy. You'll be notified via email if and when your submission gets published. Keep it positive. Keep it hacker. 💚 URL * Title * What's interesting about it? Markdown supported
@@ -0,0 +1 @@
1
+ fe089d8d1b3d2c3b996560a1cada8f939ebda4e02c306a96bc8627f295af2b8d
@@ -0,0 +1 @@
1
+ OpenAI Pricing See pricing for our business and enterprise plans. Start creating with OpenAI’s powerful models. Get started (opens in a new window) Contact sales Get OpenAI for Business updates Product updates, practical guides, upcoming events, and more. Email address * By subscribing, you agree to receive emails from OpenAI. You can unsubscribe at any time. Read our Privacy Policy ⁠ . Subscribe
@@ -0,0 +1 @@
1
+ 048e03da7fbe6467050cd5513bad4177588c4b8c16c2274e7729d4df0aaea80e
@@ -0,0 +1 @@
1
+ 049226728d2da8054db18b04782a9848b755855e
@@ -0,0 +1 @@
1
+ 46d5db587c91dd4e1616bf0b641e7d053a8bad153d505c9d4990cb6c23d12751
@@ -0,0 +1 @@
1
+ Product Hunt Help Center Search for articles... What are points? Upvotes to points Written by Jake Crump October 1, 2025 Every launch on Product Hunt is assigned points, which determine its ranking on the homepage. These points are calculated based on genuine engagement, including upvotes and other signals, such as comments. The points system also encourages more meaningful interactions by considering diverse engagement signals, providing a holistic representation of a product&#x27;s impact. Points on Product Hunt are not solely determined by upvotes. Instead, the system considers various forms of engagement, including interactions and participation by community members. This ensures that the points more accurately represent meaningful activity and traction beyond raw counts. Previously, we only displayed the upvote count, but this often caused confusion when rankings didn’t align exactly with the number of upvotes. This is because not all upvotes carry the same weight – our system considers various factors to ensure rankings reflect authentic community engagement. Using points instead of raw upvote counts provides a more accurate and fair representation of a launch’s overall traction. Additionally, discrepancies between displayed points and upvote counts occur because points are calculated using additional criteria. This helps provide a more equitable and accurate metric for tracking success on the platform. These changes aim to reward authentic community participation and minimize inconsistencies, ensuring a fairer ranking system overall. Related Topics Upvoting Guidelines on Product Hunt Improving Product Engagement for Better Points Understanding the Product Hunt Community Dynamics Did this answer your question? Disappointed Reaction 😞 Neutral Reaction 😐 Smiley Reaction 😃
@@ -0,0 +1 @@
1
+ f33beb71a9ed331d313d1cbc0ee24b5a88fe6778291f878bde78932fd2b6a5c4
@@ -0,0 +1 @@
1
+ Product Hunt Help Center Search for articles... 8. Launch FAQ and myths Quick answers to the questions makers ask most, plus the launch myths worth ignoring. Written by Juan Francisco Secchi Updated over 3 weeks ago Quick answers to the questions we hear most from makers. Each one links to the article in the Launch Guide that covers it in depth. Frequently asked questions Is Product Hunt free? Yes. Submitting a launch, commenting, and reaching Product of the Day are all free. Never pay for upvotes. See "How Product Hunt works" . Do I need a hunter? No. You can, and should, hunt your own product. Hunting just means posting. There&#x27;s no advantage to having someone else post it for you. Can I launch from a company account? No. Product Hunt is a community of people, so launches and comments must come from personal accounts. Your co-makers should use their own accounts too. What do I need to submit a launch? A personal account with a verified email address, your product URL, a name, a tagline, a description, at least one launch tag, a logo, at least one gallery image and your role (maker or hunter). See "Build your product page" . When does my launch go live? At 12:01 AM Pacific Time on the date you schedule. You can schedule from tomorrow up to 30 days ahead. See "Set your goals and pick your launch date" . What&#x27;s the best day to launch? The day you&#x27;re most prepared for and can be fully present. There&#x27;s no day that guarantees a top spot. See "Set your goals and pick your launch date" . Why wasn&#x27;t my launch featured? Featuring is an editorial decision. Our team curates the homepage, and the Featuring Guidelines explain what we look for, but meeting them doesn&#x27;t guarantee a spot. A launch that isn&#x27;t featured is still live and can be found through your link and the "See all of today&#x27;s products" button on the homepage. See "What kind of products get featured" . How do I promote my launch? Share your link wherever your audience is, and ask people to try it and leave feedback. Never ask for upvotes. See "How to promote your launch" . Why is a launch with fewer upvotes ranked above mine? The leaderboard uses upvotes, comments, time since launch, and other signals, not upvotes alone. See " What to do during and after your launch ". Someone else already posted my product. What now? You can ride the wave and relaunch later with a major update, or email us at hello@producthunt.com and we&#x27;ll help. See "Set your goals and pick your launch date" . How often can I launch? Every time you ship a major update. If your last launch was less than two months ago, you&#x27;ll need to submit a relaunch request. See "Relaunch your product" . Why was my account marked as spam? Accounts are flagged when their activity breaks our Community Guidelines , for example by asking for upvotes, using multiple accounts, or posting from a company account. If you think it&#x27;s a mistake, email us at hello@producthunt.com . Launch myths Myth: Every upvote counts the same. False. Upvotes from established, active community members earn your launch far more points than upvotes from brand-new or low-quality accounts. That&#x27;s why a wave of upvotes from people who just signed up barely moves a launch, and real engagement from the community does. Myth: A launch is only worth it if you finish #1. False. Many launches hit their goals without topping the leaderboard. Feedback, users, and connections count too. Myth: You need a famous hunter. False. Anyone can hunt, and we encourage makers to post their own product. Who posts it doesn&#x27;t affect ranking. Myth: Linking directly to your product gets you penalized. False. We encourage you to link straight to your product. Glossary Maker: Anyone who helped build the product. Hunter: The person who submits a product. Usually the maker. Launch page: The page for a single launch, where people upvote and comment. Product Page: The permanent home for a product, with all its launches, reviews, and awards. Featured: A launch our team has selected to appear on the homepage leaderboard. Product of the Day: The top-ranked featured launch of the day. There are also Week and Month awards. Maker comment: The first comment on a launch, written by the maker. Launch tags: The tags you choose so people browsing a topic can find your launch. Shoutouts: Short public reviews thanking the tools you used to build your product. Still have questions? Email us at hello@producthunt.com . Did this answer your question? Disappointed Reaction 😞 Neutral Reaction 😐 Smiley Reaction 😃
@@ -0,0 +1 @@
1
+ 6949ada9a0c2a116cc9c4462363cda27b45de11373e8e14c083da53b156887e4
@@ -0,0 +1 @@
1
+ Product Hunt Help Center Search for articles... 4. Build your product page Every field in the submission form, what&#x27;s required, and how to write a Maker comment that starts the conversation. Written by Juan Francisco Secchi Updated over 3 weeks ago For a lot of people, your launch page is the first time they&#x27;ll ever meet your product. Treat it like a landing page that gets one shot to make the introduction count. This article walks through the submission flow step by step, then covers how to write your Maker comment. Your work saves as a draft as you go, so you don&#x27;t need everything ready at once. Step 1: Click Submit Sign in with your personal account and click Submit in the top-right corner of any page. Step 2: Add your product link Paste the link to your product and click Get started . Use a direct link to where people can use or download it: your homepage, an app store page, or a GitHub repo. Skip link shorteners. Product Hunt uses the link to check if your product is already on the site: Launching again? If you&#x27;ve launched before, you&#x27;ll see a Launching again? box. Choose your product from the list so the new launch is added to your existing Product Page. First launch? If there&#x27;s no match, a new Product Page is created for your product. If the same link launched in the last two months, you&#x27;ll be asked to request a relaunch. Step 3: Introduce the product Next, add the three basics. You can change them any time before you launch. Name (up to 40 characters). Just the product&#x27;s name. No taglines or emoji. Tagline (up to 60 characters). Say exactly what the product does. Skip hype like "the best" or "#1". This is what people read on the leaderboard before deciding to click, so make it clear before you make it clever. Description (up to 500 characters). Lead with the value, then the features that deliver it. What problem does your product solve, and for who? Tagline test: if someone reads only your name and tagline, do they know what the product does? "Meeting notes that write themselves" works. "The future of productivity" doesn&#x27;t. Step 4: Build your page in the editor Now you&#x27;re in the launch editor. It shows your launch page the way people will see it, and you fill it in right on the page. Your name, tagline, and description are already at the top. Logo and links Logo (required). Click the Logo box next to your name to upload it. It&#x27;s the square image people see next to your launch on the leaderboard. Animated GIFs work, but they only play on hover, so make sure the first frame looks good on its own. Recommended size: 240x240px. JPG, PNG, or GIF, up to 2MB. Add links (optional). Use the Add links button on the right to add other places people should know about, like your social accounts, app store pages, or alternative links. Launch media The launch media box is where you show the product in action. Drop image files in, or add videos and demos by link. Add images (at least 1 required). Show the product in use, not just your logo. Screenshots of the core flow, a before-and-after, or a short GIF of the key moment all work well. Recommended size: 1270x760px. Add video (optional but recommended). A quick demo of the product doing its thing. It doesn&#x27;t need to be polished. A simple screen recording with your voice can do more than a big-budget trailer. Add demo (optional but recommended). A clickable walkthrough so people can try the interface without signing up. This launch by Loom shows how a strong, compelling product gallery looks. Pricing, launch tags, and promo code These three buttons sit under the media box. They help people understand your product at a glance. Add pricing (recommended). Tell people if your product is Free , Paid , or has Free options (it requires payment but offers a free trial or free version). Add launch tags (required, up to 3). Pick the tags that fit your product best. They help people browsing a topic find your launch. Add promo code (optional). Give the Product Hunt community a discount or free trial. You&#x27;ll add a short offer text (up to 25 characters) and the code itself (up to 15 characters), plus an optional end date. Launch team First, tell us your role: I made this: you&#x27;re the hunter and one of the makers. I&#x27;m hunting it: you&#x27;re posting someone else&#x27;s product, so you&#x27;re the hunter only. Then click Add makers to add everyone who built the product. You can add as many as you want. Ask them to create their Product Hunt accounts well before launch day, so they&#x27;re credited and can reply to comments. If you chose I made this , you&#x27;ll also see Add a shoutout . Shoutouts are a way to thank the tools that helped you build your product. Each one is a short public review on that tool&#x27;s Product Page, with a note between 20 and 2,000 characters, and you can shout out each product once. Write something specific: "We built our whole onboarding on X, and it saved us weeks" is far more useful than "Great tool!" First comment This is where you write your Maker comment. It&#x27;s posted and pinned at the top of the discussion when you launch, so it&#x27;s one of the most-read parts of your page. You have up to 5,000 characters, and you can use bold, lists, links, quotes, and @mentions to tag your co-makers. The prompt in the box is a good starting point: why did you build this, and what feedback would help most? See the Maker comment section below for what else to include. Before you launch checklist The Before you launch checklist on the right side of the editor tracks your progress. It has two parts: Required: launch name, tagline, description, logo, gallery image, launch tags, and your role (maker or hunter). You can&#x27;t schedule until these are done. Make it stand out: 3 or more images, other makers, first comment, video or demo, pricing, and shoutouts. These are optional, but launches that complete them make a much stronger first impression. At the bottom, Company info (optional) lets you share more about the team behind the product: your X handle, whether it&#x27;s open source (you&#x27;ll need to link the repository), if you&#x27;re backed by Y Combinator, and more. Step 5: Save a draft or schedule your launch When all the required items are done, the checklist shows Your page is ready to schedule . At the top of the sidebar you have two buttons: Create draft: saves your Product Page with the launch in draft mode. Nothing goes live, and our team doesn&#x27;t review drafts. You can come back and keep working as long as you need. Schedule launch: picks the day your launch goes live. If your launch isn&#x27;t 100% finished, click Create draft, not Schedule launch. Scheduled launches are reviewed before they go live, and incomplete ones can be removed. Schedule only when everything is ready. When you schedule, pick a date up to 30 days ahead. Your launch is visible starting at midnight Pacific Time and runs for the entire day. You&#x27;re not locked in: you can change the date whenever you like. For help choosing, see this article. Write your Maker comment The Maker comment is the first comment on your launch, written by you. It&#x27;s pinned at the top of the comments, so it&#x27;s one of the most-read parts of the page. You write it in the First comment box in the editor, and it goes live with your launch. A good Maker comment includes: Who you are. A line about you and your team. Why you built it. The problem you ran into and the story behind the build. What it does. The two or three things that matter most, in plain words. Who it&#x27;s for. Name the people you built it for. You can&#x27;t be everything to everybody. What makes it different. Your edge over what already exists. What you want to hear. Ask a specific question to invite feedback. Any offer. If you have a Product Hunt promo, mention it here. Write like a person, not a press release. Humble and helpful beats hype every time. Images and GIFs are welcome, and a few emojis can work as bullets, but don&#x27;t overdo it. Ask for feedback, never for upvotes. "What would make this useful for your team?" starts a conversation. "Please upvote!" breaks our rules. Your co-makers can join in once the launch is live by replying to comments. Before you schedule Product works in production, signup included Name and tagline are clear on their own Gallery shows the product in use Co-makers are added and have accounts Maker comment is written Promo code works, if you have one Need help with the form? Email us at hello@producthunt.com . Next up Your page is ready. Now, tell people it&#x27;s coming. Did this answer your question? Disappointed Reaction 😞 Neutral Reaction 😐 Smiley Reaction 😃
@@ -0,0 +1 @@
1
+ 7c0e80d3907150ca66106f0372883af85d34424cda68148dc22b0bbf35e022eb
@@ -0,0 +1 @@
1
+ What are home feed recommendations? Updated October 05, 2026 21:41 Home feed recommendations are recommendations for posts that use machine learning (ML). They’re part of an effort to improve the Best sort on home feeds by personalizing and ranking the content to create the best feed for users. When you’ll see home feed recommendations When sorting by Best you will see these recommendations. On Reddit, the Best sort is a personalized sorting option that’s continuously being improved. To suggest content, it takes some elements of your Reddit activity into account such as whether you tend to like new communities or not, how old or new your account is, and what types of posts you’ve upvoted or commented on in the past. What home feed recommendations look like Along with personalization, home feed recommendations have a different design than other recommendations on Reddit. Home feed recommendations highlight the post itself (not the community), and provide you with context for why we think you may be interested in that particular piece of content. How to enable or disable home feed recommendations If you’d like to turn off home feed recommendations on reddit.com, visit your preferences and turn off the toggle next to Show recommendations in home feed. If you're on iOS or Android, go to your account settings and scroll down to Privacy. From there, you'll see the option to turn off the toggle to Show recommendations in home feed. If you have more questions that aren’t covered in these FAQs, check out r/help . Someone may have had the same question, or you can ask a new one and a Reddit administrator or another member of the community will help you out. Get in touch Still have questions? If you didn't find what you need, contact us or visit r/modsupport or r/help for more help. Submit a request Still need help as a user? Come check out r/help and see if other Reddit users can help you out. Although this isn't an official Reddit community, you'll find admins here as well. Still need help as a moderator? Come check out r/modsupport! Here you can post mod tool-related questions for Reddit admins.
@@ -0,0 +1 @@
1
+ 85ccaef4d24d02b66ceb3a89f06a5f8c99c0c969652a72f89fa1ffdfc7eec658
@@ -0,0 +1 @@
1
+ How do I post and comment on Reddit? Updated October 05, 2026 23:21 Posting Posting on Reddit is a great way to share your thoughts, opinions, and interesting content with a large and diverse community. To make a post, you’ll need to find a community that’s relevant to your interests and don’t forget to check the community’s rules. Some communities have guidelines around how to format your post or what should or shouldn’t be included, so make sure you’re not accidentally missing something. You can find the community’s rules on the right-hand sidebar if you’re on reddit.com or if you’re using the mobile app, by tapping See more and then navigating to the About tab. On reddit.com Click Create at the top right-hand corner of the screen. From a Community page, you can find the Create a post button to the far right of the community name. If you decide to create a post from the home page, you’ll need to select a community to post into from the dropdown menu. If you’re already in a particular community, this will be selected automatically when you select Create . Add a title and description for your post. Make sure the title is descriptive and accurately summarizes your content. You’ll have options in your rich text editor to include the following: - Link - Image - Video - AMA Note: Not all communities allow all options, so you may see some combination of the above options depending on the community you’re trying to post in. Tip: On a desktop browser using the rich text editor, you can quickly search for and insert emojis by typing a colon (:) followed by a descriptive word (e.g., :smile) to bring up a predictive emoji menu. The picker currently only supports English shortcode matching. You can also mark your post as NSFW (Not Safe for Work) if you’re sharing mature content that’s only for people over 18 or add a spoiler tag if you're sharing content that may ruin a surprise. Once you're happy with your content, click Post . Once your post is live, you can interact with other users by replying to their comments. If you’d like to edit your post, click the overflow menu ( ) in the top right corner of your post. Note: You can only edit a post’s content and not its title. Also, once you edit something, an asterisk * will appear next to it to tell other users that it’s been changed. On iOS and Android Tap the Create icon ( ) at the bottom of the screen (Android), top right-hand corner (iOS), or within a community. Add a title and description for your post. Make sure the title is descriptive and accurately summarizes your content. You’ll have options in your rich text editor to include the following: - Link - Image - Video - Poll - AMA Note: Not all communities allow all options, so you may see some combination of the above options depending on the community you’re trying to post in. You can add any tags or flair if necessary, to complete the rest of your post. Tip: If you need help formatting your post check out this article . You can also mark your post as NSFW (Not Safe for Work) if you’re sharing mature content that’s only for people over 18 or add a spoiler tag if you're sharing content that may ruin a surprise. To find those tags, tap on the overflow menu ( ). Once you're happy with your content, tap Post . Once your post is live, you can interact with other users by replying to their comments. If you’d like to edit your post, tap the overflow menu ( ) in the top right corner of your post and select Edit post. Note: You can only edit a post’s content and not its title. Also, once you edit something, an asterisk * will appear next to it to tell other users that it’s been changed. On old Reddit From the right-hand sidebar, select submit a new link or submit a new text post depending on the type of post you’d like to make. Add your title and complete the rest of your post. Last, click submit. Commenting Commenting on Reddit is a great way to engage in discussions with other users. Find the post or comment you want to respond to. Click or tap the comment icon ( ) below a post or Reply below a comment. Type your response in the text box that appears. If you’re on mobile, this box will be located at the bottom of the screen. If you’d like, you can also format your response . Tip: On a desktop browser using the rich text editor, you can quickly search for and insert emojis by typing a colon (:) followed by a descriptive word (e.g., :heart) to bring up a predictive emoji menu. The picker currently only supports English shortcode matching. Click Comment on reddit.com, tap the send icon ( ) in the app . You can save a comment draft and come back later to finish it as well. When you start typing in the comment composer, your copy excluding media will be automatically saved to drafts in case you accidentally exit or would like to come back and finish later. Up to 20 drafts can be saved for a maximum of 14 days. As you exit the post detail page, you can also choose to delete the draft. You can access your comment drafts by visiting the Drafts menu in your profile drawer on the mobile app and reddit.com, or by tapping the Comment or Reply button to a post or comment that you were previously responding to. That's it! Your comment will appear below the post or comment. To edit a comment you’ve made, click or tap the overflow menu ( ) and then select Edit. FAQ Why am I being told "You're doing that too much..."? To prevent spammers, there’s a limit to how often users can post and comment in a community. If you’re brand new to Reddit and don’t have a lot of karma yet, you may be hitting this spam filter. If you’re brand new to a community that’s especially sensitive to spammers, you may also be hitting this filter. Even earning a small amount of karma by commenting on another post within a community, can help you get past the filter. Also, keep in mind that becoming a Reddit Premium member won’t affect the spam filter and isn’t a quick fix to get around earning karma. If you have more questions that aren’t covered in these FAQs, check out r/help . Someone may have had the same question, or you can ask a new one and a Reddit administrator or another member of the community will help you out. Get in touch Still have questions? If you didn't find what you need, contact us or visit r/modsupport or r/help for more help. Submit a request Still need help as a user? Come check out r/help and see if other Reddit users can help you out. Although this isn't an official Reddit community, you'll find admins here as well. Still need help as a moderator? Come check out r/modsupport! Here you can post mod tool-related questions for Reddit admins.
@@ -0,0 +1 @@
1
+ ea10b4b8e9cc6599f432ed8048910b503c1559b82c982838d5b119a31548e694
@@ -0,0 +1 @@
1
+ Spam Updated October 30, 2026 21:19 Do not use Reddit for repeated or unsolicited mass engagement. Spam – defined as repeated or unsolicited actions (whether automated or manual) that negatively affect users, communities, and/or Reddit itself – is never allowed. Spammers compromise everyone's use of Reddit by artificially inflating exposure to unwanted or irrelevant content. What are some things that may violate this policy? Mass-posting repetitive content for the purpose of exposure or financial gain. Mass-tagging other users or sending large amounts of unsolicited chat or private messages. Repeatedly posting or sharing old content for the purpose of rapidly gaining karma . Using tools (e.g., bots, generative AI tools) that may break Reddit or facilitate the proliferation of spam. Link-masking or redirecting to harmful domains. Leveraging multiple accounts to artificially inflate the subscriber count of a subreddit. Some examples of policy violations Programming a bot that continuously promotes specific products or services within a community or across many communities. Sending large amounts of unsolicited private messages to expose others to harmful links, such as malware, phishing, deceptive pop-ups, etc. Repeatedly posting unrelated/off-topic/link-farmed content that disrupts conversations within a community. Repeatedly sharing "not-safe for-work" content in "safe-for-work" spaces. Automating the creation of multiple Reddit accounts or communities. How do I avoid being labeled as a spammer? Post authentic content into communities where you have a personal interest. If your contributions to Reddit consist primarily of links to a business that you run, own, or otherwise benefit from, please be thoughtful about the frequency of posting, or consider advertising opportunities using our self-serve platform . If you’re unsure if your content is considered spam, check to see if the community you want to engage with has specific rules in addition to the guidelines above. (Note that community moderators adjudicate what constitutes unwanted/spammy content in their communities and may take action accordingly.) You may also contact the moderators of the community if you need additional clarifications. How can I report potential spam/spammers? To report potential spam, please use the report button next to the content you’d like to report in the app or on reddit.com . For more information, please visit Reddit's enforcement philosophy . You can also learn about our policy enforcement data in the latest Reddit Transparency Report . &#x2715; Was this article helpful? Yes No We're sorry the article wasn't helpful. Please let us know why! Inaccurate: information doesn't match what I'm seeing Confusing: information is unclear or translation is wrong Missing information: it's not comprehensive enough Other: suggestions to improve content Thanks for your feedback! Get in touch Still have questions? If you didn't find what you need, contact us or visit r/modsupport or r/help for more help. Submit a request Still need help as a user? Come check out r/help and see if other Reddit users can help you out. Although this isn't an official Reddit community, you'll find admins here as well. Still need help as a moderator? Come check out r/modsupport! Here you can post mod tool-related questions for Reddit admins.
@@ -0,0 +1 @@
1
+ 147ba7cc3e6fe609d8960a1f26aac1679bd6f291e5e9d082d84cd3727f26ca07
@@ -0,0 +1 @@
1
+ Resources Creators Explore Start publishing Sign in Explore Substack App Discover Featured Substacks around the world Creators Switch to Substack Go paid Grow your audience For live video For video For podcasts For bloggers For finance writers For authors For food writers For local news For media founders Resources How to start a Substack Going paid guide Resource center Community & programs Brand partnerships Help center Brand assets Documents Terms of Use Privacy Policy Publisher Agreement Content Guidelines Copyright Dispute Policy Copyright Repeat Infringer Policy CCPA Policy Support Chatbot Terms Content Guidelines Last Updated: September 29, 2026 Substack is a place for independent writers, podcasters, and creators. We host and celebrate a diverse range of thought and discussion. The following guidelines outline what is and is not acceptable on Substack. We have the exclusive right to interpret and enforce these guidelines, although we may consult outside experts, research, and industry best practices in doing so. If you encounter content that may be in breach of these guidelines or have any questions about them, you can email us at tos@substackinc.com . If we determine that any content is in breach of these guidelines, we may remove it, hide it from public view, or impose other restrictions. This is an evolving document: we reserve the right to update these Content Guidelines at our discretion and without notice. Legal Please respect people’s intellectual property and don’t infringe on their privacy or any other legal rights. Don’t publish anything that violates laws or regulations. You and you alone are responsible for the content you publish on Substack, and liable for any harm caused by the content you publish. In General We want Substack to be a safe place for discussion and expression. At the same time, we believe that critique and discussion of controversial issues are part of robust discourse, so we work to find a reasonable balance between these two priorities. In all cases, Substack does not allow credible threats of physical harm. Hate Substack cannot be used to publish content or fund initiatives that incite violence based on protected classes. Offending behavior includes credible threats of physical harm to people based on their race, ethnicity, national origin, religion, sex, gender identity, sexual orientation, age, disability or medical condition. Private information Using private information to intimidate, harass, or threaten others is strictly prohibited on our platform. You must not publish private information, or threaten to expose private information, or incentivize others to do so, for these purposes. To be clear: we will presume in most cases that the publication of a private home address or phone number is a violation of this policy. Plagiarism Do not publish any material that was written or created by someone else and claim it as your own. Impersonation We don’t allow impersonation, which includes posing as another person, brand, or organization. This applies to Substack itself: don’t use Substack’s name, logo, or trademark in any way that misrepresents the company or misleads others. People restricted from making money on Substack Substack’s payments are processed through Stripe, which excludes certain types of businesses from using their service. Please refer to the Stripe Service Agreement ( see the US agreement here ) and Stripe’s restricted businesses for more information about restricted business categories and practices. Harmful and illegal activities We don’t allow content that promotes harmful or illegal activities, including material that advocates, threatens, or shows you causing harm to yourself, other people, or animals. We don’t allow child sexual abuse material, including AI-generated or otherwise synthetic depictions of a minor in a sexual manner, or the use of Substack for child sexual exploitation or abuse. We also do not allow non-consensual intimate images, including synthetic or AI-generated ones — sharing, or threatening to share, sexual images of a person without their consent. Additional restrictions for users in Australia On top of the rules above, users in Australia must not post the following types of content. These restrictions reflect our obligations under the Australian Online Safety Act 2021: – pro-terror material (Class 1A); – crime and violence material (Class 1A and Class 1B); – drug-related material (Class 1B); and – content that depicts shocking, gratuitous, or exploitative real violence against people or animals, or gore, including images presented as if they are real (“high-impact violence material”). These rules apply to content accessible to people in Australia. Additional restrictions for users in the UK On top of the rules above, users in the UK must not post the following types of content. These restrictions reflect our obligations under the UK Online Safety Act 2023 (OSA) in respect of priority illegal content (Schedule 7 to the OSA) and priority harmful content (Schedules 4 and 5 to the OSA): – terrorism content — material that encourages or supports terrorist acts, glorifies terrorism, or helps people carry out attacks; – content that encourages or assists serious violence, including material that provides practical assistance for committing serious violent offenses; – content that promotes, facilitates, or assists fraud or financial crime, including scams targeting other users; – content that facilitates human trafficking or modern slavery; and – content that encourages, promotes, or provides instructions for suicide or self-harm. These rules apply to content accessible to people in the UK. Spam and phishing We are vehemently anti-spam and anti-phishing. If you are importing a mailing list from another platform, you are required to ensure it’s made up of people who explicitly opted-in to receive emails from your specific publication. We don’t allow imports of email addresses that were purchased, scraped, or harvested from third party websites. Don’t add people to your mailing list without their consent, and don’t import your contacts list or social graphs. Similarly, you may not create publications for spamming or phishing purposes. Don’t post spam when interacting with others on Substack, such as in comments, discussion threads, or email replies. Marketing and Promotion Substack is intended for high quality editorial content, not conventional email marketing. We don’t permit publications whose primary purpose is to advertise external products or services, drive traffic to third party sites, distribute offers and promotions, enhance search engine optimization, or similar activities. Brands and commercial organizations publishing on Substack may be subject to additional verification. Nudity, porn, erotica We don’t allow porn or sexually exploitative content on Substack, including any visual depictions of sexual acts for the sole purpose of sexual gratification. We strictly prohibit sexualized portrayals of minors, or of any subject that appears to us to be a minor, regardless of whether the content is synthetic or includes age disclaimers, where the apparent purpose of the content is sexual arousal or gratification. We do allow depictions of nudity for artistic, journalistic, or related purposes, as well as erotic literature, however, we have a strict no nudity policy for profile images. We may hide or remove explicit content from Substack’s discovery features, including search and on Substack.com . Comments, Notes & Community Surfaces These guidelines also apply to Substack comments, notes, and other community surfaces. We believe that writers are responsible for moderating their own communities as they see fit and readers for curating their own experiences on the platform. Don’t create accounts for the sole purpose of circumventing boundaries like blocks and bans imposed by other users. We may intervene to remove accounts engaged in artificial or inauthentic activity on community surfaces. Digital Services Act (DSA) – Single point of contact (Arts 11 & 12): Coimisiún na Meán, an EU Member State authority, the European Commission or the European Board for Digital Services can contact us regarding matters pertaining to the DSA (such as our content moderation practices): by email at dsa@substackinc.com . Please ensure that any communications sent to us are submitted in English or accompanied by an English translation. Digital Services Act (DSA) – Legal Representative (Art 13): Substack has appointed Lionheart Squared (Europe) Limited (”Lionheart”) as its legal representative. You can contact Lionheart, regarding matters pertaining to the DSA: by email at Substack-DSA@LionheartSquared.eu ; by writing to Lionheart Squared (Europe) Ltd, FAO Substack, 2 Pembroke House, Upper Pembroke St. 28-32, Dublin, D02 EK84, Republic of Ireland; or by phone at +353 (0) 1234 2458. Please ensure that any communications sent to Lionheart are submitted in English or accompanied by an English translation. You may also contact us directly at dsa@substackinc.com . **Reports and Complaints** Reports submitted through our reporting tools must be made in good faith and relate to content or conduct that you genuinely believe violates these Guidelines. We reserve the right to close reports that are frivolous, vexatious, or manifestly unfounded without taking action. Repeated misuse of our reporting system, including submitting reports intended to harass, suppress, or disadvantage other users, may result in restrictions on your ability to submit further reports or on your account more broadly. Discover Explore Get the app Substack Reader Top podcasts Top in culture Top in food & drink Top in finance Top in sports Top in politics Top in technology Top in faith Top in business Topics Creators Switch to Substack Get started Go paid Sponsorships For video For podcasts For bloggers For finance writers For authors For food writers For local news For media founders Company About Help Jobs Blog Vulnerability Policy Taxes Contact Sitemap Resources Resource center Guide to going paid Help center Community and programs Brand assets Features Brand Partnerships How to start a podcast Best podcast hosting Comparison Substack vs. Patreon Substack vs. beehiiv Substack vs. YouTube Substack vs. Spotify for Creators Substack vs. Buzzsprout Substack vs. Podbean Substack vs. Acast Substack vs. Supercast Substack vs. Supporting Cast Substack vs. Captivate.fm Substack vs. Transistor.fm Substack vs. Libsyn Substack vs. RSS.com Substack vs. Riverside Substack vs. Spreaker Substack is the home for writing, podcasting, and media founders. © Substack Inc. Privacy Terms Accessibility Collection notice This site requires JavaScript to run correctly. Please turn on JavaScript or unblock scripts
@@ -0,0 +1 @@
1
+ 94811244c47b4998014896bd08d839f9427b06c7de4cba974af918022b3a414f
@@ -0,0 +1 @@
1
+ Back to Newsroom Threads Find Your Community With New Threads Educational Insights October 21, 2024 June 26, 2025 Listen to Article 10 Pause 10 0.25× 0.5× 1× 1.25× 1.5× 2× Takeaways We’re introducing new Threads educational resources to help you learn how to drive conversations and get discovered by more people on Threads. Resources will include best practices, data-backed tips and content examples from successful Threads creators to help you create compelling content and improve your post performance. We created Threads because we think everyone has something worth saying, and we want you to be able to create a community around your best ideas and most interesting thoughts. That’s why today, we’re introducing new educational resources to help you learn how to drive conversations on Threads and get discovered by more people. These educational resources will include best practices, data-backed tips and content examples from successful Threads creators to help you create compelling content and improve your post performance. Here are just a few insights that are already helping people build their audiences on Threads: We’ve found that replies account for almost half of the views on Threads, so try joining a conversation to reach more people. Higher post frequency is linked to higher impressions per post, so we recommend posting at least 2-5 times per week if you’re looking to build your audience. Funny content receives a higher number of views on Threads, so don’t be afraid to add a little humor. Video, photo and carousel posts that include text average more views than those without text, so try giving your followers some context. Posting more frequently on the weekends can help drive higher engagement, so consider logging in on Saturday and Sunday. Combining text and video in a single post can help you get more views, so don’t limit yourself to just one media format. Posts that drive conversations are more likely to get recommended, so think of new ways to invite feedback from your community. Creators who saw the most replies posted text about TV & Movies, Photography, Books & Literature, Fashion & Style, Fitness & Workouts, Sports, Music, Food & Drink, Beauty, Technology and Travel & Leisure, so consider branching out into one of these topics if you haven’t already. Top performing creators post original content specifically for Threads, so try sharing something new. Head to the Threads website to find even more tips that can help you create engaging, discoverable content. In the coming months, we’ll keep working to get you more stories from successful creators, and even more best practices to help you make the most of Threads. Categories : Product News Threads Tags: Creators DOWNLOAD ALL IMAGES Share this article Recent News Advancing Science Together: Highlights From the Open Source AI For Science Summit Introducing Direct: An App Just for Messaging Meta’s New Agreements Bring Clean Manufacturing to Data Center Supply Chains Expanding Teen Account Protections to Teens Around the World Related News Threads Threads Expands Podcast Toolkit for Creators and Listeners September 16, 2026 September 16, 2026 Threads New Parental Supervision Tools Coming To Threads July 21, 2026 September 15, 2026
@@ -0,0 +1 @@
1
+ 97ded72d7f5087b119edc7fbb604234978659d28df06845c9dc88d297f803a77
@@ -0,0 +1 @@
1
+ # Threads posts You can use the Threads API to publish image, video, text, or carousel posts. This document covers: * [Single thread posts](#single-thread-posts) * [Carousel posts](#carousel-posts) * [Label AI-generated content](#label-ai-generated-content) * [Topic tags, links, and GIFs](#topic-tags--links--and-gifs) * [Media specifications](#media-specifications) ## Permissions Publishing posts requires the following permissions: * `threads_basic` — Required for making any calls to all Threads API endpoints. * `threads_content_publish` — Required for Threads publishing endpoints only. If your app has not been approved for advanced access for the `threads_content_publish` permission, you can only post on behalf of [Threads testers](https://developers.facebook.com/documentation/threads/get-started#threads-testers) on your app. After your app is published and approved, you can post on behalf of any Threads user who grants your app the permission. ## Single thread posts Publishing a single image, video, or text post is a two-step process: 1. Create a media container with text only or with an image or video hosted on your public server with optional text using the `POST /{threads-user-id}/threads` endpoint. 2. Publish the media container using the `POST /{threads-user-id}/threads_publish` endpoint. ### Limitations * Text posts are limited to 500 characters. * Emojis are counted as the [number of UTF-8 bytes](https://www.npmjs.com/package/grapheme-splitter). ### Step 1: Create a Threads media container Use the `POST /{threads-user-id}/threads` endpoint to create a Threads media container. #### Parameters | Name | Description | | --- | --- | | `is_carousel_item`<br><br>Boolean | **Required.** <br>Indicates that images, videos, or both appear in a carousel.<br><br>**Values:** `true`, `false` *(default for single thread posts)* | | `media_type`<br><br>string | **Required.** <br>Indicates the current media type.<br><br>**Values:** `TEXT`, `IMAGE`, `VIDEO`<br><br>**Note:** `CAROUSEL` is not available for single thread posts. | | `image_url`<br><br>URL string | **Optional.** <br>The URL path to the image. Required if `media_type=IMAGE`.<br><br>**Note:** Threads will retrieve your image from the URL provided, so it must be on a public server. | | `video_url`<br><br>URL string | **Optional.** <br>The URL path to the video. Required if `media_type=VIDEO`.<br><br>**Note:** Threads will retrieve your video from the URL provided, so it must be on a public server. | | `text`<br><br>string | **Optional.** <br>The text associated with the post. Required if `media_type=TEXT`. If any URLs are included, the first URL in the `text` field is used as the link preview for the post.<br><br>**Note:** For the post character limit, emojis are counted as the [number of UTF-8 bytes](https://www.npmjs.com/package/grapheme-splitter). | Refer to the [`POST /{threads-user-id}/threads` endpoint reference](https://developers.facebook.com/documentation/threads/reference/publishing#post-threads-user-idthreads) for additional supported parameters. #### Example request ```bash curl -i -X POST \ -d "media_type=IMAGE" \ --data-urlencode "image_url=<IMAGE_URL>" \ --data-urlencode "text=<TEXT>" \ -d "access_token=<ACCESS_TOKEN>" \ "https://graph.threads.com/v1.0/<THREADS_USER_ID>/threads" ``` #### Example response ```json { "id": "<THREADS_MEDIA_CONTAINER_ID>" } ``` ### Step 2: Publish the Threads media container Use the `POST /{threads-user-id}/threads_publish` endpoint to publish the media container ID returned in the previous step. Wait about 30 seconds before publishing a Threads media container to give Threads enough time to fully process the upload. See the [media container status endpoint](https://developers.facebook.com/documentation/threads/troubleshooting#publishing-does-not-return-a-media-id) for more details. #### Parameters | Name | Description | | --- | --- | | `creation_id`<br><br>numeric string | **Required.** <br>The Threads media container ID. | #### Example request ```bash curl -i -X POST \ -d "creation_id=<MEDIA_CONTAINER_ID>" \ -d "access_token=<ACCESS_TOKEN>" \ "https://graph.threads.com/v1.0/<THREADS_USER_ID>/threads_publish" ``` #### Example response ```json { "id": "<THREADS_MEDIA_ID>" } ``` ## Carousel posts You can publish up to 20 images, videos, or a mix of the two in a carousel post. Publishing carousels is a three-step process: 1. Create the individual media containers for each image and video that should appear in the carousel using the `POST /{threads-user-id}/threads` endpoint. 2. Create a single carousel container to contain the media containers using the `POST /{threads-user-id}/threads` endpoint. 3. Publish the carousel container using the `POST /{threads-user-id}/threads_publish` endpoint. **Note:** Carousel posts count as a single post against a profile's [rate limit](https://developers.facebook.com/documentation/threads/overview#rate-limiting). ### Limitations * Carousels are limited to 20 images, videos, or a mix of the two. * Carousels require a minimum of two children. ### Step 1: Create a media container Use the `POST /{threads-user-id}/threads` endpoint to create a media container for each image or video that appears in the carousel. #### Parameters | Name | Description | | --- | --- | | `is_carousel_item`<br><br>Boolean | **Required.** <br>Indicates that images, videos, or both appear in a carousel when set to `true`.<br><br>**Values:** `true`, `false` | | `media_type`<br><br>string | **Required.** <br>Indicates the current media type.<br><br>**Values:** `IMAGE`, `VIDEO`<br><br>**Note:** `CAROUSEL` is not available for single thread posts. | | `image_url`<br><br>URL string | **Optional.** <br>The URL path to the image. Required if `media_type=IMAGE`.<br><br>**Note:** Threads will retrieve your image from the URL provided, so it must be on a public server. | | `video_url`<br><br>URL string | **Optional.** <br>The URL path to the video. Required if `media_type=VIDEO`.<br><br>**Note:** Threads will retrieve your video from the URL provided, so it must be on a public server. | | `text`<br><br>string | **Optional.** <br>The text associated with the post. If any URLs are included, the first URL in the `text` field is used as the link preview for the post.<br><br>**Note:** For the post character limit, emojis are counted as the [number of UTF-8 bytes](https://www.npmjs.com/package/grapheme-splitter). | Refer to the [`POST /{threads-user-id}/threads` endpoint reference](https://developers.facebook.com/documentation/threads/reference/publishing#post-threads-user-idthreads) for additional supported parameters. #### Example request ```bash curl -i -X POST \ -d "media_type=IMAGE" \ --data-urlencode "image_url=<IMAGE_URL>" \ -d "is_carousel_item=true" \ -d "access_token=<ACCESS_TOKEN>" \ "https://graph.threads.com/v1.0/<THREADS_USER_ID>/threads" ``` #### Example response ```json { "id": "<THREADS_MEDIA_CONTAINER_ID>" } ``` If the operation is successful, the API returns a media container ID, which can be used when creating the carousel container. Repeat this process for each image or video that appears in the carousel. ### Step 2: Create a carousel container Use the `POST /{threads-user-id}/threads` endpoint to create a carousel container. #### Parameters | Name | Description | | --- | --- | | `media_type`<br><br>string | **Required.** <br>Indicates the current media type.<br><br>**Value:** `CAROUSEL` | | `children`<br><br>list of numeric strings | **Required.** <br>A comma-separated list of the media container IDs of the images, videos, or both that should appear in the published carousel.<br><br>**Note:** Carousels must have at least 2 and no more than 20 total images, videos, or a mix of the two. | | `text`<br><br>string | **Optional.** <br>The text associated with the post. | Refer to the [`POST /{threads-user-id}/threads` endpoint reference](https://developers.facebook.com/documentation/threads/reference/publishing#post-threads-user-idthreads) for additional supported parameters. #### Example request ```bash curl -i -X POST \ -d "media_type=CAROUSEL" \ -d "children=<MEDIA_ID_1>,<MEDIA_ID_2>,<MEDIA_ID_3>,..." \ -d "access_token=<ACCESS_TOKEN>" \ "https://graph.threads.com/v1.0/<THREADS_USER_ID>/threads" ``` #### Example response ```json { "id": "<THREADS_CAROUSEL_CONTAINER_ID>" } ``` ### Step 3: Publish the carousel container Use the `POST /{threads-user-id}/threads_publish` endpoint to publish a carousel post. **Note:** Profiles are limited to 250 published posts within a rolling 24-hour period. Publishing a carousel counts as a single post. #### Parameters | Name | Description | | --- | --- | | `creation_id`<br><br>numeric string | **Required.** <br>The Threads carousel container ID. | #### Example request ```bash curl -i -X POST \ -d "creation_id=<MEDIA_CONTAINER_ID>" \ -d "access_token=<ACCESS_TOKEN>" \ "https://graph.threads.com/v1.0/<THREADS_USER_ID>/threads_publish" ``` #### Example response ```json { "id": "<THREADS_MEDIA_ID>" } ``` If the operation is successful, the API returns the carousel album's Threads media ID. ## Label AI-generated content To disclose that a post contains AI-generated content, set `is_made_with_ai=true` when creating the media container with `POST /{threads-user-id}/threads`. The published post displays the AI info label, as it does when you select the AI-label option in the Threads composer. This parameter supports text, image, video, and carousel posts. It defaults to `false`. Omitting it or setting it to `false` does not add an AI self-disclosure and does not prevent automatic AI labeling. ### Example request Create a text post container with the AI self-disclosure: ```bash curl -i -X POST \ -d "media_type=TEXT" \ --data-urlencode "text=<TEXT>" \ -d "is_made_with_ai=true" \ -d "access_token=<ACCESS_TOKEN>" \ "https://graph.threads.com/v1.0/<THREADS_USER_ID>/threads" ``` The response contains the container `id`. Publish that container using the existing publishing flow: ```bash curl -i -X POST \ -d "creation_id=<THREADS_MEDIA_CONTAINER_ID>" \ -d "access_token=<ACCESS_TOKEN>" \ "https://graph.threads.com/v1.0/<THREADS_USER_ID>/threads_publish" ``` Set `is_made_with_ai` on the creation request, not on `POST /{threads-user-id}/threads_publish`. ### Carousel posts For a carousel, set `is_made_with_ai=true` when creating the parent container with `media_type=CAROUSEL`. The label applies to the whole post. Do not set it to `true` on individual items created with `is_carousel_item=true`; those requests return an error. ## Topic tags, links, and GIFs {#topic-tags--links--and-gifs} Topics and links appear in posts in such a way as to encourage engagement. ### Topic tags Topics make posts more social by allowing central topics of discussion. You can include a topic in a post either by using the `topic_tag` parameter or by including a tag within the text of a post. #### Using the `topic_tag` parameter **Note:** Topic tags must be at least 1 character and no more than 50 characters long. The following characters are not allowed: * Periods (.) * Ampersands (&) ##### Example request ```bash curl -i -X POST \ -d "media_type=TEXT" \ --data-urlencode "text=<Text>" \ -d "access_token=<ACCESS_TOKEN>" \ --data-urlencode "topic_tag=<TAG>" \ "https://graph.threads.com/v1.0/<THREADS_USER_ID>/threads" ``` #### Using an in-text topic tag **Warning:** This method is not preferred but is kept for backward compatibility. A topic can also be attached to a post by including it in-line within the text of the post. Only one topic tag is allowed per post, so the first valid tag included in a post of any type (text-only, image, video, carousel) through the API is treated as the tag for that post. Information to keep in mind when adding a topic to a post using an in-text tag: * Valid tags start with a hash sign (#). * The text is also configured in the app without the hash sign. * Topic must be at least 1 character and no more than 50 characters long. * Whole numbers that are preceded by a hash sign (for example, #1) are not converted into a tag. This is because it is assumed that # is signifying a number sign in this scenario. * The following characters are not allowed when using in-text tags with the Threads API, so any in-text tag that starts with a hash sign ends just before these characters: * Spaces, tabs, and newline characters * Periods (.) * Ampersands (&) * At signs (@) * Exclamation marks (!) * Question marks (?) * Commas (,) * Semicolons (;) * Colons (:) ### Links To attach a link to your post, use the `link_attachment` parameter when creating a media container. If no `link_attachment` parameter is provided, then the first link made in a text-only post through the API is configured as the link attachment, which displays as a preview card, to make it easier to engage with and click on. #### Limitations * This feature is only available for text-only posts. It does not work with image, video, or carousel posts. * The number of links is restricted to 5 or fewer. **Warning:** Since December 22, 2025, Threads posts containing more than 5 links fail to post during the media creation step (`POST /{threads-user-id}/threads`) with the error code: `THREADS_API__LINK_LIMIT_EXCEEDED`. How links are counted: * All unique URLs found in the text field are counted as links. * If the `link_attachment` field contains a URL that is different from all URLs in the text field, it is counted as an additional link. * If the `link_attachment` URL is the same as any URL in the text field, it is only counted once, rather than twice. Examples: * If the `text` field contains only www.facebook.com, and the `link_attachment` is also www.facebook.com, this counts as 1 link. * If the `text` field contains www.instagram.com and www.threads.com, and the `link_attachment` is www.facebook.com, this counts as 3 links. * If the `text` field contains www.example.com, www.example.com, and www.test.com, and the `link_attachment` is www.test.com, this counts as 2 links (www.example.com and www.test.com are each counted once). If you receive this error, reduce the number of unique links in your post to 5 or fewer. #### Publishing Links can be attached when making an API call to the `POST /{threads-user-id}/threads` endpoint to [create a media container](https://developers.facebook.com/documentation/threads/posts#step-1-create-a-threads-media-container). | Name | Description | | --- | --- | | `link_attachment`<br><br>URL string | **Optional.** <br>The URL that should be attached to a Threads post and displayed as a link preview. This must be a valid, publicly accessible URL.<br><br>**Note:** Can only be used for `media_type=TEXT` posts. | ##### Example request ```bash curl -i -X POST \ -d "media_type=TEXT" \ --data-urlencode "text=<TEXT>" \ -d "access_token=<ACCESS_TOKEN>" \ --data-urlencode "link_attachment=<URL>" \ "https://graph.threads.com/v1.0/<THREADS_USER_ID>/threads" ``` ##### Example response ```json { "id": "<THREADS_MEDIA_CONTAINER_ID>" } ``` The request above creates a Threads media container that, once [published](https://developers.facebook.com/documentation/threads/posts#step-2-publish-the-threads-media-container), attaches a link preview to your media. #### Media retrieval The value for the `link_attachment` URL can be retrieved by making a request to the `GET /threads` or `GET /{threads-media-id}` endpoint to [retrieve media object(s)](https://developers.facebook.com/documentation/threads/retrieve-and-discover-posts/retrieve-posts). | Name | Description | | --- | --- | | `link_attachment_url`<br><br>URL string | The URL attached to a Threads post. | ##### Example request ```bash curl -s -X GET \ "https://graph.threads.com/v1.0/<THREADS_MEDIA_ID>?fields=id,link_attachment_url&access_token=<ACCESS_TOKEN>" ``` ##### Example response ```json { "id": "<THREADS_MEDIA_ID>", "link_attachment_url": "<LINK_ATTACHMENT_URL>" } ``` ### GIFs GIFs make posts more engaging by allowing users to express reactions, emotions, or ideas visually. #### Limitations * This feature is only available for text-only posts. It does not work on image, video, or carousel posts. * [GIPHY](https://developers.giphy.com/docs/api) is currently the only available GIF provider. #### Publishing GIFs can be attached when making an API call to the `POST /{threads-user-id}/threads` endpoint to [create a media container](https://developers.facebook.com/documentation/threads/posts#step-1-create-a-threads-media-container). | Name | Description | | --- | --- | | `gif_attachment`<br><br>object | **Optional.** <br>The ID and GIF provider for the GIF to attach to the post.<br><br>**Fields:** `gif_id`, `provider` | ##### Example request ```bash curl -i -X POST \ -d "media_type=TEXT" \ --data-urlencode "text=<TEXT>" \ -d "access_token=<ACCESS_TOKEN>" \ -d 'gif_attachment={"gif_id":"<GIF_ID>","provider":"GIPHY"}' \ "https://graph.threads.com/v1.0/<THREADS_USER_ID>/threads" ``` **Note:** The value of the `id` field you receive from the GIF provider's API response should be used as the `<GIF_ID>` in the API call. ##### Example response ```json { "id": "<THREADS_MEDIA_ID>" } ``` The request above creates a Threads media container that, once [published](https://developers.facebook.com/documentation/threads/posts#step-2-publish-the-threads-media-container), attaches a GIF to your media. ## Media specifications ### Image Specifications * **Format:** JPEG and PNG image types are the officially supported formats for image posts. * **File Size:** 8 MB maximum. * **Aspect Ratio Limit:** 10:1 * **Minimum Width:** 320 (will be scaled up to the minimum if necessary) * **Maximum Dimensions:** Images larger than 4096 x 4096 pixels are scaled down to fit. Images with an aspect ratio of 2:1 or wider are scaled down to about 16.8 megapixels. * **Height:** Varies (depending on width and aspect ratio) * **Color Space:** sRGB. Images using other color spaces will have their color spaces converted to sRGB. ### Video Specifications * **Container:** MOV or MP4 (MPEG-4 Part 14), no edit lists, moov atom at the front of the file. * **Audio Codec:** AAC, 48khz sample rate maximum, 1 or 2 channels (mono or stereo). * **Video Codec:** HEVC or H264, progressive scan, closed GOP, 4:2:0 chroma subsampling. * **Frame Rate:** 23-60 FPS * **Picture Size:** * Maximum Columns (horizontal pixels): 1920 * Required aspect ratio is between 0.01:1 and 10:1 but we recommend 9:16 to avoid cropping or blank space. * **Video Bitrate:** VBR, 100 Mbps maximum. * **Audio Bitrate:** 128 kbps. * **Duration:** 300 seconds (5 minutes) maximum, minimum longer than 0 seconds. * **File Size:** 1 GB maximum. ## Learn more * [Reposts](https://developers.facebook.com/documentation/threads/posts/reposts) * [Quote posts](https://developers.facebook.com/documentation/threads/posts/quote-posts) * [Polls](https://developers.facebook.com/documentation/threads/create-posts/polls) * [Spoilers](https://developers.facebook.com/documentation/threads/create-posts/spoilers) * [Text attachments](https://developers.facebook.com/documentation/threads/create-posts/text-attachments) --- Full documentation index for this product: https://developers.facebook.com/documentation/threads/llms.txt
@@ -0,0 +1 @@
1
+ ea45577f68dba53eb17b8e97eb1c9eea9b5ae2dbf64fe95cf60a6f6721fff9ad
@@ -0,0 +1 @@
1
+ Last updated August 4, 2026 File upload Work with chunks Chunk restrictions Media transfer HTTP schema Examples Response Pull from URL Prerequisites Ownership verification rules Domain URL Prefix Cancel ongoing pull from URL tasks Request Response Video restrictions Image restrictions On this page Media Transfer Guide New: Content Posting API now supports posting photos ! This guide explains the process of transferring media files to TikTok servers when using the Content Posting API. # File upload Using this method, you can transfer your media to TikTok using HTTP. Upon initializing your video upload with source=FILE_UPLOAD , an upload_url will be returned. You must send the media binary to this URL. To learn how to send videos to TikTok servers and for details on the HTTP request (endpoint, request and response schema, and headers), see the API reference for the Upload Video endpoint or the Direct Post endpoint . # Work with chunks # Chunk restrictions The value of total_chunk_count should be equal to video_size divided by chunk_size , rounded down to the nearest integer. Each chunk must be at least 5 MB but no greater than 64 MB, except for the final chunk, which can be greater than chunk_size (up to 128 MB) to accommodate any trailing bytes. Videos with a total size less than 5 MB must be uploaded as a whole, with chunk_size equal to the entire video&#x27;s byte size. Videos with a total size greater than 64 MB must be uploaded in multiple chunks. There must be a minimum of 1 chunk and a maximum of 1000 chunks. File chunks must be uploaded sequentially. # Media transfer HTTP schema PUT {UPLOAD_URL} HTTP /1.1 Content-Type: {MIME_TYPE} Content-Length: {BYTE_SIZE_OF_THIS_CHUNK} Content-Range: bytes {FIRST_BYTE}-{LAST_BYTE}/{TOTAL_BYTE_LENGTH} BINARY_FILE_DATA # Examples Chunk upload In this example, there is a file with a size of 50,000,123 bytes. The chunk size is specified to be 10,000,000 bytes. The trailing 123 bytes is merged into the 10,000,000-byte chunk to meet the restriction that each chunk must be greater than 5 MB. Example UPLOAD_URL= https://upload.us.tiktokapis.com/video/?upload_id=67890&upload_token=chunkexample will be shared across all chunks. Variable 1st Request 2nd Request 3rd Request 4th Request 5th Request MIME_TYPE video/mp4 video/mp4 video/mp4 video/mp4 video/mp4 TOTAL_BYTE_LENGTH 50,000,123 50,000,123 50,000,123 50,000,123 50,000,123 BYTE_SIZE_OF_THIS_CHUNK 10,000,000 10,000,000 10,000,000 10,000,000 10,000,123 FIRST_BYTE 0 10,000,000 20,000,000 30,000,000 40,000,000 LAST_BYTE 9,999,999 19,999,999 29,999,999 39,999,999 50,000,122 BINARY_FILE_DATA BINARY1 BINARY2 BINARY3 BINARY4 BINARY5 response HTTP status 206 206 206 206 201 The following is the corresponding source_info for initializing video upload . "source_info": { "source": "FILE_UPLOAD", "video_size": 50000123 "chunk_size": 10000000 "total_chunk_count": 5 } Whole upload In this example, the media file is 4 MB, which must be uploaded as a whole in one request. Variable Single Request UPLOAD_URL https://open-upload.tiktokapis.com/video/?upload_id=123&upload_token=wholeexample MIME_TYPE video/mp4 TOTAL_BYTE_LENGTH 4,194,304 BYTE_SIZE_OF_THIS_CHUNK 4,194,304 FIRST_BYTE 0 LAST_BYTE 4,194,303 BINARY_FILE_DATA BINARY1 response status code 201 The following is the corresponding source_info for initializing video upload . "source_info": { "source": "FILE_UPLOAD", "video_size": 4194304 "chunk_size": 4194304 "total_chunk_count": 1 } # Response HTTP Code Status Description 201 Created All parts are uploaded. TikTok will start the posting process. 206 PartialContent The current chunk has been successfully processed. There are additional chunks yet to be uploaded. 400 BadRequest Malformated request headers, or BYTE_SIZE_OF_THIS_CHUNK does not reflect the true byte size of the binary in the request body. 403 Forbidden The upload_url has expired. 404 NotFound TikTok cannot find a valid upload task given the upload_url . 416 RequestedRangeNotSatisfiable Content-Range does not reflect the actual upload progress. 5xx InternalServerError Gateway connection error or TikTok Internal error. You should retry submitting this chunk. The response header includes the following key-value pair indicating the number of bytes uploaded: Content-Range:bytes 0-{UPLOADED_BYTES}/{TOTAL_BYTE_LENGTH} . # Pull from URL By initializing your content post using /init endpoints with source=PULL_FROM_URL , the TikTok server starts to download the media resource using the URL you provide. Learn more about getting post status. TikTok server&#x27;s ingress bandwidth for file downloads can reach 100 Mbps. # Prerequisites Ensure that the media URL you provided belongs to a path that you own. To confirm ownership, log into the TikTok for Developers website and add your Domain or URL Prefix property to your application in the URL properties widget as shown below. You must have manage or write access to the property. The media URL must use "https" and should not redirect to another URL. The URL must remain accessible for the entire duration of the download process, which times out one hour after the download task is initiated. Note: To conveniently test the Pull from URL feature, you can try this URL without any verification. # Ownership verification rules # Domain Definition A domain can be a base domain (for example, example.com) or a subdomain (for example, subdomain.example.com). Verification To verify domain ownership, it is recommended that you add a signature string to the domain&#x27;s DNS records. Once the ownership of a domain is verified, all paths under that domain or its subdomains are considered owned by the developer application. For example, if you have verified the domain static.example.com , then URLs like https://video.static.example.com/tiktok/example.mp4 are considered verified, while URLs like https://example.com/videos/example.mp4 are still considered unverified. # URL Prefix Definition A URL prefix consists of: https:// + host + path + /. The host must be a domain and should not be an IP address. Redirections are not followed. URLs that return HTTP 3xx are considered invalid. Verification Once a URL prefix&#x27;s ownership is verified, all URLs with the exact prefix are considered owned by the developer application. For example, if you have already verified the domain https://example.com/videos/user/ , then URLs like https://example.com/videos/user/123/example.mp4 are considered verified, while URLs like https://example.com/videos/2023/user/123/example.mp4 are still considered unverified. # Cancel ongoing pull from URL tasks The API can cancel downloads for both Direct Post and Content Upload endpoints on a best-effort basis. While it is possible to cancel ongoing slow downloads, it is not feasible to cancel downloads that are nearing completion or already in the file processing state. # Request POST /v2/post/publish/cancel/ HTTP /1.1 Host: open.tiktokapis.com Authorization: Bearer {{AccessToken}} Content-Type: application/json; charset=UTF-8 { "publish_id": {PUBLISH_ID} } # Response 200 OK { "error": { "code": "ok", "message": "", "log_id": "202210112248442CB9319E1FB30C1073F3" } } response.error.code specification HTTP Status error.code Description 200 ok The request was successful 400 invalid_publish_id The publish_id does not exist token_not_authorized_for_specified_publish_id The access_token does not have authorization to cancel the publish publish_not_cancellable The task associated with this publish_id is already in a final state and can&#x27;t be cancelled 403 url_ownership_unverified To use PULL_FROM_URL as the media transfer method, developer must verify the ownership of the URL prefix or domain 401 access_token_invalid The access_token is invalid or has expired scope_not_authorized The access_token does not bear user&#x27;s grant on video.upload or video.publish 429 rate_limit_exceeded Your request is blocked due to exceeding the API rate limit 5xx internal_error TikTok server or network error. Try again later. # Video restrictions Supported media formats MP4 (recommended) WebM MOV Supported codecs H.264 (recommended) H.265 VP8 VP9 Framerate restrictions Minimum of 23 FPS Maximum of 60 FPS Picture size restrictions Minimum of 360 pixels for both height and width Maximum of 4096 pixels for both height and width Duration restrictions All TikTok creators can post 3-minute videos, while some have access to post 5-minute or 10-minute videos. The longest video a developer can send via the initialize Upload Video endpoint is 10 minutes. TikTok users may trim developer-sent videos inside the TikTok app to fit their accounts&#x27; actual maximum publish durations. Size restrictions Maximum of 4GB # Image restrictions Supported media formats WebP JPEG Picture size restrictions Maximum 1080p Size restrictions Maximum of 20MB for each image On this page File upload Work with chunks Chunk restrictions Media transfer HTTP schema Examples Response Pull from URL Prerequisites Ownership verification rules Domain URL Prefix Cancel ongoing pull from URL tasks Request Response Video restrictions Image restrictions File upload
@@ -0,0 +1 @@
1
+ 462fca6406599e06fb9bf66b1160af24a4e980cd97bdf66fb280ce920a1e3522
@@ -0,0 +1 @@
1
+ Community Guidelines Integrity and Authenticity Released August 25, 2026 Effective September 24, 2026 Previous Versions: Here TikTok is all about having authentic experiences—from the accounts you follow, to the content you see. We want you to feel confident that what you’re watching is reliable, original, and shared by real people. This trust is what helps build strong communities both on and off-platform. Misinformation In a global community, people will have different opinions—but we aim to ground those conversations in facts. That&#x27;s why we don&#x27;t allow misinformation that could cause significant harm to individuals or society, no matter the intent of the person posting it. This includes hoaxes, misleading AIGC, harmful conspiracy theories, and other false information related to public safety, crises, or major civic events—when such content may lead to violence or cause public panic. We work with independent fact-checkers and experts to assess the accuracy of content, and we factor their assessments into our moderation decisions. Content is ineligible for the FYF if it contains misinformation that may cause moderate harm to individuals or society. To be cautious, unverified information about crises, major civic events, or content temporarily under review by fact-checkers is also ineligible for the FYF. We may also apply warning labels or prompt users to pause before sharing unconfirmed content. More information Civic and Election Integrity Elections are important events that often spark lively conversations and debate. We aim to respect these discussions while ensuring TikTok remains a space that brings people together. We welcome informed civic conversations, but draw the line at content that could mislead voters or cause real-world harm. That includes misinformation that could prevent people from voting, interfere with elections, or encourage the unlawful disruption of results. We classify eligible political TikTok accounts as Government, Politician, and Political Party Accounts and apply a set of policies that prevent the use of certain features. These accounts aren&#x27;t allowed to participate in incentive programs or creator monetization features. We also don&#x27;t allow paid political advertising . This includes creators being compensated for making branded political content , and the use of other promotional tools on the platform, such as Promote . We prohibit advertising of any kind by political figures and entities, and suspected paid political advertising is ineligible for the For You feed. However, eligible government entities may advertise in specific, approved categories—such as public health and safety information, tourism, and culture—after completing a certification process. Additionally, official electoral management bodies may run informational ads about election processes. To help you manage your TikTok experience, we may add warning labels to content that our fact-checking partners cannot verify. Learn more about our election integrity work. More information Edited Media and AI-Generated Content (AIGC) We welcome creativity, including when it comes from new digital tools like generative artificial intelligence (AI). But generative AI and editing can blur the line between fact and fiction. To help keep content on TikTok trustworthy and provide people with important context about what they are viewing, we require creators to label AI-generated or significantly edited content that shows realistic-looking scenes or people . Unlabeled content may be removed, restricted, or labeled by our team, depending on the harm it could cause. Even with labels, some edited or AI-generated content can still be harmful. We don’t allow content that’s misleading about matters of public importance or harmful to individuals . More information Unoriginal Content and Intellectual Property Rights The creativity on TikTok is what makes our community special. We want to protect that. You should only post content you created or have the right to share. We don&#x27;t allow content that violates someone else&#x27;s intellectual property (IP) rights. If we become aware of content that breaks these rules, we will remove it. Learn more about our IP policies . Content is also ineligible for the FYF if it includes unoriginal or reused material without anything new. If you think your copyright or trademark rights have been violated, you can submit a copyright or trademark report through our in-app tools. More information Deceptive Behaviors and Fake Engagement We want TikTok to be a trustworthy space where people around the world can create, connect, and learn. Authentic engagement is core to that experience—it helps power the recommendations you see. That’s why we don’t allow accounts that mislead or try to manipulate our platform , or the trade of services that artificially boost engagement or trick the recommendation system . This includes behaviors like covert influence operations, impersonation, spam, fake reviews, and sharing hacked materials in harmful ways. You can have multiple accounts—for example, for fan content or creative expression—but not to deceive others or break the rules. If we find deceptive account behavior, we may: Ban your account Ban additional or new accounts you create Restrict your account, which could include limiting your ability to post new content, appear in top search results, or in the FYF We strictly prohibit automation tools, scripts, or other tricks designed to bypass our systems. These can result in content removal, account bans, or other enforcement. If your account is restricted or banned, you may not create or use another account to get around it. If we detect accounts or content with inauthentic metrics, we’ll remove fake likes, followers, or other inflated signals. Content that tries to manipulate people into giving gifts or inflating likes or follows isn’t eligible for the FYF. More information
@@ -0,0 +1 @@
1
+ c519e1771448fb65e43045eb06c90706959d9e55ed72d88b87bc8bd5a461d2b3
@@ -0,0 +1 @@
1
+ 269340ce2eb8ca785bafa4f2c17a2e8b752bccd3
@@ -0,0 +1 @@
1
+ 6e9798f6957343b9acec4b718e1891d39ab6df1785577d6f878b8fa2f9cbcd42
@@ -0,0 +1 @@
1
+ How to Post Follow step-by-step instructions for composing and sharing posts on >x< from your iOS, Android, or web browser. Table of contents A post may contain photos, GIFs, videos, links, and text. Looking for information on how to post at someone? Check out our article about how to post replies and mentions on >x< . How to Post iOS Android Desktop iOS Select the post compose icon You can include up to 4 types of photos, a GIF , or a video (and up to 4 total media items, e.g. 2 photos, 1 GIF, and 1 video) in your post. Compose your message (up to 280 characters) and select Post. Android Select the post compose icon You can include up to 4 types of photos, a GIF , or a video (and up to 4 total media items, e.g. 2 photos, 1 GIF, and 1 video) in your post. Enter your message (up to 280 characters), and then select Post . A notification will appear in the status bar on your device and will go away once the post successfully sends. Desktop Type your post (up to 280 characters) into the compose box at the top of your Home timeline, or select the Post button in the navigation bar. You can include up to 4 photos, a GIF , or a video in your post. Select the Post button to post the Post to your profile. To save a draft of your post, select the >x< icon in the top left corner of the compose box, then select Save . To schedule your post to be sent at a later date/time, select the calendar icon at the bottom of the compose box and make your schedule selections, then select Confirm . To access your drafts and scheduled posts, select Unsent posts from the post compose box. How to create a longer post iOS Android Desktop iOS Longer posts are a feature of X Premium and the Plus, Premium, Super, and Ultra plans on The X Subscription, and can be created the same way a regular post would be Select the post compose icon You can include photos, a GIF , or a video (and up to 4 total media items, e.g. 2 photos, 1 GIF, and 1 video) in your post. Compose your message. When you reach 280 characters, the word count will switch from tracking your progress around the perimeter of the circle icon to filling it Once you’ve finished writing (up to 4,000 characters), select post. You can learn more about >x< Premium here . Android Longer posts are a feature of X Premium and the Plus, Premium, Super, and Ultra plans on The X Subscription, and can be created the same way a regular post would be Select the post compose icon You can include photos, a GIF , or a video (and up to 4 total media items, e.g. 2 photos, 1 GIF, and 1 video) in your post Compose your message. When you reach 280 characters, the word count will switch from tracking your progress around the perimeter of the circle icon to filling it Once you’ve finished writing (up to 4,000 characters), select post A notification will appear in the status bar on your device and will go away once the post successfully sends You can learn more about >x< Premium here . Desktop Longer posts are a feature of X Premium and the Plus, Premium, Super, and Ultra plans on The X Subscription, and can be created the same way a regular post would be Type your post (up to 25,000 characters) into the compose box at the top of your Home timeline, or select the Post button in the navigation bar When you reach 280 characters, the word count will switch from tracking your progress around the perimeter of the circle icon to filling it You can include up to 4 photos, a GIF, or a video in your post Select the Post button to post the post to your profile You can learn more about >x< Premium here . Post source labels help you better understand how a post was posted. This additional information provides context about the post and its author. If you don’t recognize the source, you may want to learn more to determine how much you trust the content. Click on a post to go to the post details page. At the bottom of the post, you’ll see the label for the source of the account’s post. For example, >x< for iPhone , >x< for Android , or >x< for Web . posts containing the >x< for Advertisers label indicate they are created through the >x< Ads Composer and not whether they are paid content or not. Paid content contains a Promoted badge across all ad formats. In some cases you may see a third-party client name, which indicates the post came from a non- >x< application. Authors sometimes use third-party client applications to manage their posts, manage marketing campaigns, measure advertising performance, provide customer support, and to target certain groups of people to advertise to. Third-party clients are software tools used by authors and therefore are not affiliated with, nor do they reflect the views of, the post content. Posts and campaigns can be directly created by humans or, in some circumstances, automated by an application. Visit our partners page for a list of common third-party sources . Deleting posts Read about how to delete a post . Note that you can only delete your own posts. You cannot delete posts which were posted by other accounts. Instead, you can unfollow , block or mute accounts whose posts you do not want to receive. Read about how to delete or undo a repost . Keyboard shortcuts The following are a list of keyboard shortcuts to use on x.com. Actions n = new post l = like r = reply t = repost m = Direct Message u = mute account b = block account enter = open post details o = expand photo / = search cmd-enter | ctrl-enter = send post Navigation ? = full keyboard menu j = next post k = previous post space = page down . = load new posts Timelines g and h = Home timeline g and o = Moments g and n = Notifications tab g and r = Mentions g and p = profile g and l = likes tab g and i = lists tab g and m = Direct Messages g and s = Settings and privacy g and u = go to someone’s profile Share this Article
@@ -0,0 +1 @@
1
+ 3879c51543fdb83ef44c53bb2c77f0b4fc3c972ad9fcc1022e539c04c0e8862f
@@ -0,0 +1 @@
1
+ About longer videos for >x< Premium subscribers With >x< Premium, you can upload videos up to 4 hours long, compared to the standard 140-second limit available to all users. Table of contents Note >x< Premium is now part of The X Subscription, one plan for >x< , Grok, and Cursor. Every paid plan includes >x< Premium benefits on the >x< account you connect. If you already subscribe to >x< Premium, your plan, price, and features stay the same until you choose to switch, and the details on this page still apply to you. Learn more about The X Subscription Subscribe Share more content with your followers with >x< Premium. Subscribers can upload videos up to 4 hours long (1080p) on x.com and >x< for iOS. Subscribers can upload videos up to 10 minutes long on Android. If you aren’t a Premium subscriber, you can still upload videos up to 140 seconds long on any platform. All videos must comply with the >x< Rules . See details on all of our video upload options here . Longer videos FAQ As a Premium subscriber, how do I upload longer videos? On x.com, use the compose box, or click the post button. Click the gallery button. Choose a video file stored on your device and click Open. You’ll be prompted if the video isn’t in a supported format. Videos shorter than 4 hours (1080p) should not exceed 16GB file size. Videos above 2 hours and under 4 hours must be at 720p and should not exceed 16GB file size. Complete your message and click post to share your post and video. Is there a limit to the number of videos I can upload? There is no limit to the number of videos you can upload, even if all videos are the maximum length. Will video quality be affected when uploading longer videos? We strive to maintain the highest possible video quality for all videos uploaded to our platform. However, we may modify or adapt your original video for distribution, syndication, publication, or broadcast by us and our partners and/or make changes in order to adapt it to different media, including modifying the resolution and bitrate of the original video while streaming based on the speed and stability of the viewer’s internet connection. How do I troubleshoot issues with uploading longer videos? If you are experiencing issues with uploading longer videos, we recommend trying the following troubleshooting steps: Check your internet connection and ensure that it is stable and fast enough to support the upload process. Make sure that you are using a supported web browser and device. Check the file size and format of your video to ensure that it meets the requirements for uploading to our platform. If you are still experiencing issues after trying these steps, please don&#x27;t hesitate to contact us for further assistance. What file formats are supported for video uploads? Longer video uploads will adhere to all video file formats currently supported by >x< . You can learn more here . Share this Article
@@ -0,0 +1 @@
1
+ 85ff9a327ace3f723edab24e3e9a1ac7daa569d7f66ae1bda8ede7264ba61a46
@@ -0,0 +1 @@
1
+ Authenticity To maintain a trustworthy platform, >x< requires accounts to be authentic. This article explains our authenticity policy and what constitutes inauthentic behavior like account manipulation, impersonation, and misuse. Table of contents April 2025 You may not engage in inauthentic activity that undermines the integrity of >x< . We want >x< to be a place where people have authentic experiences. To make that possible, we do not allow any activity that attempts to manipulate our platform or disrupt our services through inauthentic accounts, behaviors or content . Inauthentic Accounts Accounts on >x< must be authentic. Under this policy, you may not create, operate, or mass-register accounts that are not legitimate, genuine and transparent as to their source, identity, and popularity. This includes: Unauthorized automation: Automated or scripted accounts that do not comply with our Developer Policy . Please note that as a user you are ultimately responsible for third-party applications you may authorize to access or use your account. Fake personas: You may not use manufactured identities to engage in disruptive or deceptive behavior. This may include using stock, stolen or AI-generated profile photos, copied or stolen profile bios, and/or misleading profile information for the purpose of deceiving others. Impersonation: You may not impersonate other identities of individuals, groups, or organizations to deceive others. Although you are not required to display your real identity on your profile, your account should not use false profile information to impersonate others. We allow compliant Parody, Commentary, and Fan (PCF) accounts on >x< only if the purpose is to discuss, satirize or share information. If you believe an account is posing as you or your brand, you can file a report here . Accounts may depict another entity as long as they clearly indicate that they are unaffiliated. If your account is a Parody, Commentary, or Fan account (PCF), you must meet ALL of the following requirements to clarify its purpose and avoid misleading others about its affiliation: Include a PCF label; do not use an identical avatar as the entity; include terms such as "parody," "fake," "fan," or "commentary at the beginning of your account name; and include terms such as "parody," "fake," "fan," or "commentary in your bio or profile description. Learn more about how to add a PCF label here . Multiple Accounts and Coordination: We prohibit coordinated inauthentic activity that artificially influences conversations or disrupts >x< . Not Allowed Operating multiple accounts that interact with the same or substantially similar content or in order to inflate or manipulate the prominence of content and/or accounts by, for example, creating multiple accounts to: “boost” trending topics or hashtags; engage with the same posts, accounts, or polls; misuse the mention/reply feature; and amplify one of your own accounts by misusing engagement features. Operating multiple accounts that post substantially similar or identical content to one another by, for example, cross-posting: content across multiple accounts (content that is cross-posted but localized into another language is permitted); and similar or duplicate content to the same trending topics or hashtags. Employing workarounds to exceed the technical limits of account creation (e.g., account phone number limits ). >x< allows users to create and/or operate up to ten (10) accounts for different, non-duplicative purposes. Allowed Operating multiple accounts with distinct identities, purposes, or use cases that comply with our technical limits of account creation (e.g. account phone number limits ), such as: accounts tracking when objects in space travel over a specific location on Earth, e.g. New York, Hong Kong; accounts sharing news about different professional teams in the same sport or league, e.g. NFL, NBA, Premier League; accounts for personal projects, hobbies/interests, or for your business(es); accounts for branded entities specific to unique locations or languages, e.g. brand accounts in English, Spanish and French; control multiple accounts on behalf of a third-party (e.g. “Social Media Managers”), provided that no violations of >x< Rules (including this policy) occurs; organizations with related but separate chapters or branches, such as a business with multiple locations; and operating a personal account in addition to pseudonymous accounts or accounts associated with your hobbies or initiatives. Authentically coordinating with others to express ideas, viewpoints, support, or opposition towards a cause in a non-violative manner. Ban Evasion: You may not circumvent >x< enforcement actions. Not Allowed Attempting to evade >x< enforcement actions by, for example: creating new accounts; imitating a suspended account to replace it; repurposing an already-existing account; and having someone else operate an account on your behalf. If an account has been suspended for violations of the >x< Rules, >x< reserves the right to also suspend any other account we believe the same account holder or entity may be operating in violation of our earlier suspension, regardless of when the other account was created. Account Compromise: The unauthorized access or modification of someone’s >x< account is strictly prohibited. Account compromise may occur when: your login data (such as credentials, passwords, tokens, keys, cookies) are shared with a potential malicious third-party application or website; you use a weak or reused password; viruses or malware were installed on your computer to collect passwords; or you logged in to your >x< account on a compromised network. If unauthorized updates appear in your account, it could signify a potential compromise of your account security. Learn more about how to keep your account secure . If you suspect that your account has been compromised, you can find a guide on how to troubleshoot the issue here . In the event that the troubleshooting doesn&#x27;t work, please submit a report here . Inauthentic Behaviors You may not engage in behaviors that manipulate >x< or artificially impact how content is discovered and amplified. This includes: Content Spam: You may not share or post content in a bulk, duplicative, irrelevant or unsolicited manner that disrupts people&#x27;s experience. Not Allowed Sending bulk, aggressive, high-volume unsolicited replies, mentions, or direct messages; using trending or popular hashtags with an intent to subvert or manipulate a conversation or to drive traffic or attention to accounts, websites, products, services, or initiatives; posting with excessive, unrelated hashtags in a single post or across multiple posts; repeatedly posting or sending direct messages consisting of links shared without commentary, so that this comprises the bulk of your post/direct message activity; promoting content by replying with content that is irrelevant to the topic of the original post; posting and deleting the same content repeatedly; repeatedly posting identical or nearly identical posts in a duplicative manner popularly known as “Copypasta”, or sending identical direct messages; deceptively editing to artificially amplify content or deceive people, by, for example, using a post&#x27;s existing engagement to amplify substantially different content (e.g. editing a post from “What’s better? Pancakes or waffles?” to “Thousands of people trust my service. Like my post and subscribe to my channel to get tips on investing”); and editing links (URLs) so that the final destination page has significantly changed, either in content or location (e.g. domain, URL path). Engagement Spam: We prohibit inauthentic use of >x< engagement features to artificially impact traffic or disrupt people’s experience. Not Allowed Trading, buying, selling (either through monetary or virtual compensation) or soliciting access of >x< accounts, including the temporary or permanent transfer or sales of accounts, username or >x< (e.g. “pay for affiliation” schemes) products; coordinating to exchange engagement in any >x< features, such as Likes, Polls, Replies, Reposts, Lists, Views, or Follows; coordinating with and/or compensating others to conduct account metric inflation in any >x< features, including Likes, Polls, Replies, Reposts, Lists, Views, or Follows; engaging in “follow churn” – following and then unfollowing large numbers of accounts in an effort to inflate one’s own follower count; engaging in indiscriminate following – following and/or unfollowing a large number of unrelated accounts in a short time period, particularly by automated means; engaging with posts aggressively or through the use of automation to drive traffic or attention to accounts, websites, products, services, or initiatives; engaging in aggressively adding users to Lists or Moments; duplicating another account’s followers, particularly using automation; using or promoting third-party services to perform any of the transactions described in this policy; engaging with >x< report features or forms, whether manually or through the use of automation, in order to submit duplicate or false reports in large numbers, including repeatedly reporting the same post(s) or accounts; and coordinating and/or encouraging others to misuse >x< reporting features to harass others under false pretenses or hope to cause their account(s) or post(s) to be restricted or removed. Allowed Obtaining prior consent from >x< if you are a Law Enforcement Organizations (“LEO”) or Non-Governmental Organizations (“NGO”) to use automation to submit reports, provided you identify as such organizations, either by submitting reports through their official email domain or in the application through a verified account representing their affiliated entity. manually submitting reports in good faith that you believe may violate our policies; and encouraging others to engage in good faith with >x< reporting features for customer support queries. Scams: You may not use >x< to engage in scam tactics to obtain money, property, or private information. Not Allowed Some examples of deceptive tactics that are prohibited under this policy include: social engineering, including relationship/trust-building schemes; money-flipping schemes; fraudulent discounts; and phishing scams. Allowed >x< does not intervene in financial disputes between individuals who use >x< , such as: claims relating to the sale of goods on >x< ; disputed refunds from individuals or brands; and complaints of poor quality goods received. Inauthentic Content You may not share inauthentic content on >x< that may deceive people or lead to harm. This includes: Synthetic and Manipulated Media: You may not share inauthentic media, including, manipulated, or out-of-context media that may result in widespread confusion on public issues, impact public safety, or cause serious harm (“misleading media”). We may use our own technology or receive reports through partnerships with third parties in order to determine if media have been manipulated or presented out of context. In situations where we are unable to reliably determine if it is misleading media, we may not take action. Not Allowed Manipulated: Media that is shared as authentic but is significantly and deceptively altered, manipulated, or fabricated in a way that fundamentally changes its meaning and can result in widespread confusion on public issues, impact public safety, or cause serious harm, such as: media that have been substantially edited or post-processed in a manner that fundamentally alters their composition, sequence, timing, or framing and distorts their meaning; media with visual or auditory information (such as new video frames, overdubbed audio, or modified subtitles) that has been added, edited, or removed that fundamentally changes the understanding, meaning, or context of the media; media created, edited, or post-processed with enhancements or use of filters that fundamentally changes the understanding, meaning, or context of the content; and media depicting a real person that has been fabricated or simulated, especially through use of algorithms or broader artificial intelligence. Out-of-context: Media that is not manipulated, but is shared in a deceptive manner or out-of-context or with intent to deceive people about the nature or origin of the content and can result in widespread confusion on public issues, impact public safety, or cause serious harm, such as: media presented with false or misleading context surrounding the source, location, time, or authenticity of the media; media presented with false or misleading context surrounding the identity of the individuals or entities visually depicted in the media; and media presented with misstatements or misquotations of what is being said or presented with fabricated claims of fact of what is being depicted. Allowed Sharing manipulated or out-of-context media in non-deceptive ways. Malicious URLs: You may not post malicious, harmful, or deceptive links on >x< that may cause harm. This includes posting links that may damage or disrupt another person’s browser (malware), compromise a person’s privacy (phishing), and deceptive links that redirect people to unexpected destinations or mislead people about the website’s content. How we enforce The consequences for violating this policy depend on the severity of the violation as well as any previous history of violations. The following is a list of potential enforcement options for content that violates this policy: Anti-spam challenges: When we detect suspicious levels of activity, accounts may be locked and prompted to provide additional information (e.g., a phone number) or to solve a puzzle. Denylisting URLs: We denylist or provide warnings about URLs we believe to be unsafe. Read more about unsafe links , including how to appeal if we’ve falsely identified your URL as unsafe. Restricting Reach: This may include excluding posts from search results, trends, and recommended notifications, removing posts from the For You and Following timelines, restricting a post&#x27;s discoverability to the author’s profile, restricting likes, replies, reposts, quote posts, bookmarks, share, pin to profile, or edit post, and downranking the post in replies. Temporary loss of access to >x< features or products: We may temporarily limit or restrict access to >x< features or products, including (but not limited to) posts, Edit post, Direct Messages, Spaces, Communities, or Live. Profile Modifications: If your account is potentially confusing in terms of its affiliation, including as a non-compliant parody, commentary or fan account, we may require you to edit the content on your profile. If you violate this policy again after your first warning, your account may be suspended. Suspension: For severe violations, accounts will be permanently suspended at first detection. If the offense is an isolated incident or first offense, we may take a number of actions ranging from requiring deletion of one or more posts to temporarily locking account(s). In the case of a violation centering around the use of multiple accounts, you may be asked to choose one account to keep. The remaining accounts will be suspended. How to report You can report inauthentic accounts, behaviors and content using our dedicated in-app reporting flow. Appeals If you believe we made a mistake, you can submit an appeal . Share this Article
@@ -0,0 +1 @@
1
+ 75251aa872b60babec9a3cfca3c941785b7ff7afa8546c0b4da76fcc515f016f
@@ -0,0 +1 @@
1
+ Paid Partnerships Policy Paid partnerships are when brands compensate creators or users to promote their products or services. Table of contents What are Paid Partnerships? >x< defines paid partnerships as the involvement of a third-party brand providing compensation or incentives to a user, such as an influencer or content creator, to promote their product or service. This includes mentions or endorsements of products or services under the following conditions: The products or services are gifted by or on behalf of a brand. You receive compensation for promoting these products or services, either through monetary payments or in-kind contributions. These products or services generate a commission for you from sales, for instance, through affiliate links or discount codes. You have a commercial agreement involving these products or services, such as your role as a brand ambassador. Our policies for Paid Partnerships are distinct from our Advertising policies. Content prohibited under paid partnerships may be permissible in >x< Ads. If you are interested in promoting >x< Ads, please refer to our >x< Advertising Policies. Rules for Paid Partnerships All content on >x< must comply with the >x< Rules . Posts that are part of a Paid Partnership published as an organic Post must have the “Paid Partnership” disclosure on. You can access this in the Content Disclosure settings when creating your post. Once the toggle is on and you indicate that the post is on behalf of a third party, your content will be automatically labeled to show that it is Paid Partnership content. You are responsible for ensuring that any Paid Partnership that you post complies with all applicable laws and regulations including all advertising laws and, where applicable, FTC regulations including the FTC’s Guides Concerning the Use of Endorsements and Testimonials in Advertising. You must ensure that the product, service or call-to-action (CTA) are clearly promoted without requiring users to click on any additional links. Prohibited Industries The following content categories are not eligible for Paid Partnership promotion: Adult and sexual products and services (including adult merchandise, entertainment-related, or content that is adult in nature) Alcoholic beverages and related accessories Contraceptives Dating & Marriage Services Drugs and drug-related products or services (including recreational and prescription drugs, paraphernalia, and CBD supplements) Geo-political, political, social issues or crises for commercial purposes Health and wellness supplements (including health, dietary, food, nutrition, muscle enhancement substances and supplements Pharmaceutical and medicine-related products or services (including medical institutions, over-the-counter medicines, prescription drugs) Tobacco and tobacco-related products or services (including shisha, vaporizers or vape devices) Weapons and weapons-related products or services (including ammunition and weapons training/certification) Weight loss products and services and content focused on weight loss (including fat burning pills, appetite suppressants, fasting and detox teas) Upon a request, >x< may consider exceptions to this policy on a case-by-case basis, subject to restrictions that might be applicable. For more information, please contact your internal Sales Representative. Country Specific Policies Australia Prohibited Industries The following content categories are not eligible for Paid Partnership promotion: Financial products, services, or opportunities (including loans, investment services, crypto, buy now pay later services and other financial-related content) Gambling products and services (including lotteries, social casinos, sports betting and other gambling related content) Brazil Prohibited Industries The following content categories are not eligible for Paid Partnership promotion: Gambling products and services (including lotteries, social casinos, sports betting and other gambling related content) You can report any suspected violations to the above through this form . European Union Prohibited Industries The following content categories are not eligible for Paid Partnership promotion: Financial products, services, or opportunities (including loans, investment services, crypto, buy now pay later services and other financial-related content) Gambling products and services (including lotteries, social casinos, sports betting and other gambling related content) United Kingdom Creators should include all applicable disclosures that are required to indicate the commercial nature of their content. Remember that all posts with commercial intent, including own-brand posts created by a user who has a commercial interest in the relevant brand (for example, as a director) will require a disclosure. Failure to include an appropriate disclosure, as mentioned in the global section above, in a clear and prominent way could result in enforcement actions. Creators may also check the Influencers&#x27; Guide to Making Clear that Ads are Ads as provided by Committee of Advertising Practice (CAP) and the Competition & Markets Authority (CMA). Users who believe they have viewed a Paid Partnership which does not include an appropriate disclosure, may report their concerns directly to the relevant brand or to an appropriate regulatory authority, such as the Advertising Standards Authority (ASA) . Prohibited Industries The following content categories are not eligible for Paid Partnership promotion: Financial products, services, or opportunities (including loans, investment services, crypto, buy now pay later services and other financial-related content) Gambling products and services (including lotteries, social casinos, sports betting and other gambling related content) How to Report Anyone can report violations of this policy via the >x< paid partnerships reporting form . An >x< account is not needed to report potential violations. What happens if you violate this policy? When determining the penalty for violating this policy, we consider a number of factors including, but not limited to the severity of the violation and an individual’s previous record of rule violations. The following is a list of potential enforcement options for content that violates this policy: Requiring post removal. For example, we may ask someone to remove the violating content and serve a period of time in read-only mode before they can post again. Subsequent violations may lead to account suspension. Suspending accounts whose sole purpose is to violate our Paid Partnerships policy. Taking action against the official brand or sponsor for repeated violations. To learn more, please see our range of enforcement options , and if someone believes their account was enforced against in error, they can submit an appeal . Share this Article
@@ -0,0 +1 @@
1
+ ecd8b3ed8604619a3fde81709bcdee8104b987145f5053dc5a3b0d60417cbb91
@@ -0,0 +1 @@
1
+ Search & discovery tips On YouTube, viewers are matched to the Shorts they are most likely to watch and enjoy. YouTube’s search and discovery system caters to each viewer and their varying interests. The goal is to connect each viewer with Shorts they want to watch so that they come back to YouTube regularly. YouTube Search & Discovery: 'The Algorithm' and Performance FAQs Subscribe to the YouTube Creators channel for the latest news, updates, and tips. What kind of videos does the YouTube system favor? Our system has no opinion about what type of Shorts you make. It also doesn’t favor any particular format. Shorts are ranked based on performance and viewer personalization. Shorts may be catered to viewers based on their watch and search history. How does YouTube personalize recommendations? YouTube takes many cues from the viewer and recommends Shorts by understanding which: Shorts or channels the viewer has enjoyed in the past. That way, the system can surface Shorts the viewer is most likely to enjoy. Topics or themes a viewer watches. That way, the system can identify what content to recommend to viewers. Trending songs or sampled audio they might have engaged with. That way, the system can suggest other Shorts based on the trend to viewers who are more likely to enjoy watching that trend. How does the YouTube system look at video performance? Our systems look at how a Short performs when it’s recommended to viewers. For example, when a Short is recommended to a viewer– do they choose to watch it, ignore it, or click “not interested”? Then, we look at whether or not viewers stick around. Our systems use the signals for % of viewers who chose to view, avg. view duration and avg. % viewed to inform ranking. Lastly, we look at whether or not viewers enjoyed the Short using likes and post-watch survey results. What external factors influence how many people see your videos? There are three major factors that explain where your audience is coming from: Topic interest Topic Interest is how many people worldwide are interested in and watching Shorts about a given topic. Some topics have more broad appeal than others, and that appeal can change over time. Competition YouTube’s systems rank videos from all channels that a viewer might watch. Even if you have good metrics on your Short, you may get fewer impressions if Shorts from other channels are performing even better. Seasonality YouTube traffic can vary at different times of year. Think about your audience, such as which country or region they live in or what’s going on in their lives. Expect fluctuations in viewership during major holidays. What factors influence how videos are recommended? A viewer’s watch history, a video’s performance & engagement metrics, and external factors that ultimately try to help viewers reach you influence YouTube systems. How does the audience find your Shorts? Shorts tab: Shorts are ranked based on their performance and relevancy to that individual viewer. Home tab: Displays Shorts that we believe have the best chances to be enjoyed by a specific viewer. Subs tab: Displays most recently uploaded Shorts by the channels that a viewer is subscribed to. Search: Content is ranked based on various factors. These factors include how well the metadata matches the viewers’ search and whether or not the viewers click and watch the content. Sounds & hashtags: Creators leaning into trends that feature popular sounds can increase their chances of appearing on sounds pages by using sounds from the Audio Library. Trends Page: Shorts ranked by popularity on the platform are featured in the Trends page to provide inspiration for what to create next. Its sad but true🥲#totheleft #shorts #comedyshorts #zayaanvids #zayaan South African creator ZayaanFour uses popular songs like Nicki Minaj’s “Do We Have A Problem?” to act out relatable skits that use the lyrics as a punch line, garnering over 100 million views. Things to keep in mind There is no minimum posting cadence required for your videos to perform well. We suggest you identify what works best for your audience and well-being to focus on creating great content. Shorts performance doesn’t negatively impact long form Video recommendations. Shorts can help with audience discovery but can’t hurt your Video performance. We recommend Focus on what your audience likes. If you do that and people watch, recommendations will follow. Ask yourself, which Shorts does your audience enjoy most? How often do they like to watch my channel? To help with these questions, be sure to get to know your audience . Next: check out watchtime drop tips Was this helpful? How can we improve it? Yes No Submit Shorts Video More
@@ -0,0 +1 @@
1
+ c100dc399553ee23395c570f96e84bc0298258b468ae0a918ff2aea2f71bc831
@@ -0,0 +1 @@
1
+ Understand three-minute YouTube Shorts You can now create YouTube Shorts up to three minutes in length. This gives you more time to tell your stories, showcase your creativity, and captivate your audience. Eligibility for three-minute Shorts Standard YouTube channels Videos uploaded after October 15, 2024: Any videos uploaded on or after this date with a square or vertical aspect ratio up to three minutes in length will be categorized as Shorts on YouTube. These videos can be monetized in the Shorts revenue sharing model from the Shorts Feed. Learn more about Shorts monetization . Videos uploaded before October 15, 2024: Any videos uploaded before this date will remain the same, as a long-form video on YouTube. These videos can continue to be monetized in the long-form revenue sharing mode on the Watch Page. Learn about YouTube monetization policies . Official Artist Channels Videos uploaded after December 8, 2025: Any videos uploaded on or after this date with a square or vertical aspect ratio up to three minutes in length will be categorized as Shorts on YouTube. These videos can be monetized in accordance with your monetization agreement with YouTube. Learn more about Shorts monetization . Videos uploaded before December 8, 2025: Any videos uploaded before this date will remain the same, as a long-form video on YouTube. These videos can continue to be monetized in accordance with your monetization agreement with YouTube. Learn about YouTube monetization policies . Upload three-minute Shorts UPDATE: Create 3 Minute Shorts 📲🙌 You can upload Shorts that are up to three minutes through the YouTube app and YouTube Studio. Learn how to upload YouTube Shorts . Third-party claimed content for Short that is over one minute Any Short that is over one minute in duration with an active copyright claim of any type, including manual claims, will be blocked globally on YouTube. The video will not be playable or recommended on YouTube, and will not be eligible for monetization. There are no penalties to your channel. You may remove the claimed content from your videos . If you believe the claim was made in error, you can file a dispute . Once the claim is resolved, your Short will be viewable and eligible for monetization. There are no changes in limitations for Shorts that are less than one minute in length. Learn more about music eligibility for YouTube Shorts . Frequently asked questions What music can I use? Standard YouTube channels You can use any song available in the Shorts Audio Library. You can use most songs for up to 90 seconds in a 3 minute Short. However, some tracks may be limited to 60 or 30 seconds. You may also use royalty-free music from the YouTube Audio Library. The royalty-free music won’t receive a Content ID claim. You can access YouTube Audio Library by going to YouTube Studio Audio Library where you can browse, preview, and download songs that you can use for your Shorts at no charge. Learn more about music eligibility for YouTube Shorts . Official Artist Channels Videos uploaded before December 8, 2025 that are square or taller in aspect ratio and are over one minute in length for Official Artists Channels or channels linked to a music Content Owner will continue to be treated as long-form videos. Videos with the same parameters uploaded on or after December 8, 2025 will be classified as Shorts. What happened to my blocked Short? Shorts longer than one minute that have an active Content ID claim, regardless of the policy, will be blocked on YouTube. If your Short has been blocked, you will get a notification of the blocked content. Once the claim is resolved, your Short will be viewable and eligible for monetization. Learn how to remove claimed content from your videos and more about music eligibility for YouTube Shorts . If you are an artist channel linked to a music content owner, your Shorts may get blocked as a result of a “first-party claim." Those Content ID claims can be automatically created by your music label if you uploaded a 1-3 minute Short with the label’s music synced offline. To get your Short unblocked, contact your label to release the first-party claim. Is my Short eligible for monetization? Shorts that show up in the Shorts Feed are eligible for monetization and are subject to the YouTube Shorts monetization policies. Shorts that are blocked globally on YouTube will not be eligible for monetization. Learn more about the YouTube Shorts monetization policies . How can I view my Shorts Analytics? You can view your Shorts analytics to better understand your video performance. Get started with YouTube Analytics . YouTube app Open the YouTube app . Tap your profile picture View channel . From the middle menu, tap Analytics . Can I prevent my video from being turned into a Short? If you don’t want your content to be classified as Shorts, use a wider aspect ratio such as 16:9 for long-form videos. Learn how to upload your long-form videos . Was this helpful? How can we improve it? Yes No Submit
@@ -0,0 +1 @@
1
+ dbe3c6d41af2929b5ba1d574a3173c075239a13e86079d98f26a3f35415f1b89
@@ -0,0 +1 @@
1
+ Disclosing use of GenAI content We encourage creators’ innovative and responsible use of content editing or generation tools. At the same time, we recognize that viewers want to know if what they’re watching or listening to is real. We require creators to disclose AI-generated or altered content that seems realistic. Creators can make this disclosure during the upload process. Creators must disclose GenAI content that: Makes a real person appear to say or do something they didn’t do. Alters footage of a real event or place. Generates a realistic scene that didn’t actually occur. Creates music that’s the main focus of the video. This could include content that is fully or partially altered or created using AI tools. AI disclosure requirements and examples To disclose content that is AI-generated or meaningfully AI-altered, the ‘AI use’ setting is available to creators using YouTube Studio on a computer or mobile device. After a creator selects this field and uploads content, the content will be labeled as AI generated or altered for viewers. Examples of GenAI content The following list includes examples of AI content. AI content can include content that is fully or partially altered or created using any AI audio, video, image creation or editing tools. Realistic AI content and meaningful changes require disclosure, while non-realistic or minor edits don’t. Keep in mind, this isn’t a complete list. Examples of content creators don’t have to disclose Creators don’t need to disclose non-realistic content that’s made with AI, or edits to realistic content that are minor. Minor edits are ones that are primarily aesthetic, and don't alter the content in a way that could mislead the viewer about what actually happened. Examples of content, edits, or video assistance that creators don’t need to disclose: Not realistic Someone riding a unicorn through a fantastical world Green screen used to depict someone floating in space Using an AI-generated or altered animation of a missile in a fully animated video Minor Applying beauty filters Color adjustment or lighting filters Special effects filters, like adding background blur or vintage effects Production assistance, like using generative AI tools to create or improve a video outline, script, thumbnail, title, or infographic Caption creation Video sharpening, upscaling or repair and voice or audio repair Idea generation Cloning one’s own voice to create voice overs or dubs Gameplay footage from video games AI generating or extending a backdrop to simulate a moving car Using effects to enhance previously recorded audio Keep in mind, the above list is not exhaustive. Examples of content creators need to disclose To help keep viewers informed about the content they're viewing, we require creators to disclose content that is generated or meaningfully altered with AI when it appears realistic. Examples of content, edits, or video assistance that creators need to disclose: AI generated music AI generated extra footage of a real place, like a video of a surfer in Maui for a promotional travel video AI generated realistic videos of a match between two real professional tennis players Making it appear as if someone gave advice that they did not actually give Showing a realistic depiction of a tornado or other weather events moving toward a real city that didn’t actually happen Making it appear as if hospital workers turned away sick or wounded patients Depicting a public figure stealing something they did not steal, or admitting to stealing something when they did not make that admission Making it look like a real person has been arrested or imprisoned Keep in mind, the above list is not exhaustive. How to disclose GenAI content We require creators to disclose AI-generated or altered content that seems realistic. Creators can make this disclosure during the upload process. Music artists can read the following article to learn how to Disclose Gen AI usage for music content . Go to YouTube Studio . Follow the steps to upload content. In the Attributes section, under “AI use,” tap Yes if your content meets the disclosure requirements or No if not. Continue to select other video details. Labels for AI content If creators select “Yes” to indicate that their content is realistic and generated by AI or meaningfully altered with AI, we’ll add a label to their video. Label on the video player for music or photorealistic AI content For AI-generated music or content that is photorealistic, a label in the video player may also appear. Label in the expanded description field Labels may appear in the expanded description for non-music AI-generated audio or AI content that is non-photorealistic or animated. Note: Disclosing AI content alone won’t limit a video’s audience or impact its eligibility to earn money. Automatic detection of AI content YouTube may automatically apply an AI label on the video player or in the expanded description for: Content made using YouTube's GenAI tools Content that contains C2PA metadata Content that our internal systems detect is Al generated or altered You will receive a notification in YouTube Studio if an AI label has been automatically applied on or below the video player. If our systems make an error, creators will have the ability to change AI disclosure in most cases by selecting No in the AI disclosure survey under “Attributes” in YouTube Studio. The notification in YouTube Studio will remain until the creator updates their disclosure survey. However, content made with YouTube’s AI tools, content containing C2PA metadata, or content labeled after manual review can not be adjusted. Risks of not disclosing Creators who consistently choose not to disclose this information may be subject to manual application of a label, or penalties from YouTube, including removal of content or suspension from the YouTube Partner Program. Remember, we apply our Community Guidelines to all content on YouTube, including content that is AI generated or altered using AI. Was this helpful? How can we improve it? Yes No Submit Android phone & tablet Computer iPhone & iPad More