Scroll Top

BigCommerce vs Shopify

Updated September 2026 · Written and maintained by the Progression Agency strategy team

BigCommerce and Shopify solve the same problem well enough that a feature comparison mostly produces a tie. What actually separates them for a given business is narrower: how much your catalog’s complexity is native rather than bolted on, how transaction fees interact with your payment provider, and how much of your future work you expect to happen through apps versus through the platform itself. This page works through those three, states where each genuinely wins, and is explicit about what changes fast enough that any comparison ages.

The short answerThree questions decide it. First, does your catalog need complex variants, B2B pricing tiers or many SKUs with option combinations — because BigCommerce handles more of that natively while Shopify handles it through apps. Second, will you use Shopify Payments, since Shopify’s transaction fee on external gateways is a real cost that BigCommerce does not charge, and it inverts the pricing comparison for anyone tied to a specific processor. Third, how much do you value ecosystem depth against fewer moving parts — Shopify’s app and agency ecosystem is substantially larger, which is an advantage until it becomes a stack of eleven subscriptions nobody can debug.

Progression Agency builds ecommerce sites and is platform-agnostic; we have no reseller, affiliate or partner-revenue relationship with either platform and receive nothing if you choose one. Pricing, plan names, transaction fees and feature availability in this category change frequently. Everything here reflects each vendor’s published information as of August 2026 and must be verified against their current pricing pages before you decide.

The three things that actually decide it
The fourth row covers most of what feature comparisons discuss. Both platforms are fast, both have adequate themes, and both are usable — those axes do not separate them.

What actually separates BigCommerce and Shopify?

Three things: how much catalog complexity each handles natively, how transaction fees interact with your payment processor, and how large an ecosystem you want against how many moving parts you are willing to maintain.

Almost everything else in a typical comparison — themes, page speed, ease of use, uptime, basic SEO capability — is adequate on both, and listing them produces a tie with extra steps. The three above are structural rather than featural, which is why they persist while feature gaps close.

Both platforms close each other’s gaps continually

Any comparison declaring a decisive feature win is describing a snapshot. Both vendors ship continuously and have spent a decade converging, so a page that tells you one platform ‘wins on X’ is worth checking against the current documentation before you act on it, including this one.

We have no relationship with either platform

No reseller arrangement, no affiliate links, no partner revenue. This is worth stating because a substantial share of published comparisons in this category carry commission that is disclosed obscurely or not at all, and the ordering correlates with payout more reliably than with fit.

Requirements by how much they differentiate the platforms
The bottom-right is where comparison articles spend their words: common requirements that do not differentiate. The top-left is where the decision actually gets made.

How much does catalog complexity actually matter?

It is the single most differentiating requirement. BigCommerce handles more complex product structures natively; Shopify reaches the same outcome through apps, which works and adds dependencies.

If your products are simple — a handful of variants, standard options — this axis does not separate them and you should decide on ecosystem. If your catalog involves large numbers of option combinations, configurable products, or pricing that varies by customer group, it becomes the decision.

Catalog requirements and how each platform meets them
RequirementBigCommerceShopifyPractical consequence
Simple variantsNativeNativeNo difference
Large numbers of option combinationsNative, historically more generousNative with limits; apps beyondCheck current limits against your real catalog
Configurable or made-to-order productsNative option rulesUsually an appOne dependency versus none
B2B customer groups and pricing tiersNativeApp or a B2B planA recurring cost and a moving part
Bundles and kitsApp or native depending on complexityUsually an appBoth commonly need help here
Faceted product filteringNativeUsually an appMatters at catalog scale
Large catalogsHandles wellHandles wellNeither is the constraint

The pattern across the table is consistent: BigCommerce does more of this natively and Shopify does it through the ecosystem. Neither is wrong, and the honest framing is that you are choosing between fewer dependencies and a larger set of available solutions.

Verify current limits against your actual catalog

Option and variant limits are specific numbers that both vendors publish and both have changed. If your catalog is genuinely complex, this is a ten-minute check against the current documentation rather than something to take from any comparison article.

Complex variants natively — BigCommerce leans. Fewer apps to achieve it..
B2B customer groups — BigCommerce leans. Native pricing tiers..
No fee on external gateways — BigCommerce leans. A real cost difference..
Fewer moving parts — BigCommerce leans. Less to debug..
Faceted search natively — BigCommerce leans. Useful at catalog scale..
API limits at scale — BigCommerce leans. Historically generous..
App ecosystem size — Shopify leans. More solutions exist..
Agency and developer supply — Shopify leans. Easier and cheaper to hire for..
Point of sale — Shopify leans. Mature physical retail support..
Third-party integrations — Shopify leans. More things connect out of the box..
Published solutions — Shopify leans. Almost every problem has been solved publicly..
Checkout maturity — Shopify leans. Heavily optimized over years..

How do transaction fees change the cost comparison?

Materially, and in one direction. Shopify charges an additional transaction fee when you use a payment gateway other than Shopify Payments; BigCommerce does not charge a platform transaction fee.

How the comparison changed
The convergence is why hard feature verdicts date so quickly. Anything a comparison declares a decisive win is a candidate for being closed within a year, which is why this page emphasises the structural differences instead.

For a merchant happy to use Shopify Payments, this is not a cost at all. For one committed to a specific processor — because of an existing merchant agreement, a rate they negotiated, an unsupported region or an industry restriction — it is a percentage of every order, indefinitely, and it can exceed the entire platform fee.

Work the arithmetic on your own volume

A percentage fee on revenue behaves very differently from a fixed monthly cost as you grow. Multiplying your expected annual revenue by the applicable rate and comparing that against the plan difference takes two minutes and occasionally reverses the decision entirely.

Check whether your processor is even supported

Shopify Payments is not available in every country and does not serve every industry. Where it is unavailable to you, the external-gateway fee is not optional and should be treated as part of the platform’s price rather than as an edge case.

What is the real monthly cost of each?

Platform fee plus apps plus payment processing plus theme and development. The platform fee is frequently the smallest of the four.

Search demand around this decision
The brand volume gap is roughly thirteen to one, which is itself a fact about the ecosystem: more developers, more apps, more agencies and more published solutions exist for the larger platform.
What actually appears on the monthly bill
Cost componentTypical rangeNotes
Platform subscription$29-$400+/mo standard tiersBoth have comparable entry and mid tiers
Enterprise tiers$2,000+/moNegotiated; volume-based on both
Apps$0-$500+/moThe variable that actually differs; count them
Payment processing2-3% plus fixed fee, typicallySet by your processor, not the platform
Platform transaction fee0% BigCommerce; a % on Shopify with external gatewaysThe structural difference
Theme$0-$500 once, or customBoth have free and paid options
Development and maintenanceVaries enormouslyUsually the largest line for a serious store

The third row is where the comparison is genuinely decided for most merchants, and it is the one almost never included in a published comparison. A Shopify store needing six apps to match what BigCommerce does natively is not cheaper because its plan costs the same.

Count the apps for your specific requirements, not in general

The exercise is concrete: list what your store must do, check which of those each platform does natively, and price the apps required to close the gap on either side. That number, added to the plan fee, is the comparison.

Development cost usually dwarfs the platform difference

For any store beyond a basic theme, the build and ongoing maintenance exceed the platform fee by a wide margin, and developer availability is genuinely easier and cheaper for Shopify. That is a real point in its favor and it belongs in the total rather than in a feature list.

The axes that genuinely differ
Rows three and four are the honest comparison, because in practice nobody runs either platform bare. Adding apps closes the catalog gap on Shopify and costs moving parts; that trade is the actual decision.

How much does the ecosystem difference matter?

More than most comparisons admit. Shopify’s app, agency and developer ecosystem is substantially larger, which means more problems have already been solved publicly and hiring is easier.

The practical effect is that an unusual requirement on Shopify frequently has an existing app, a published solution and three agencies who have done it before. The same requirement on BigCommerce is more likely to need custom work. That is a real, recurring advantage.

And the ecosystem is also the cost

A store running eleven apps has eleven subscriptions, eleven update cycles, eleven potential conflicts and eleven places for something to break that nobody owns. The advantage is genuine and so is the maintenance burden, and merchants underestimate the second consistently.

Developer availability is a real business consideration

When your developer leaves, how easily can you replace them? The larger ecosystem answers that better, and for a business without internal technical capacity it can outweigh a native feature advantage.

When is each the clearer choice?

BigCommerce when the catalog is complex, B2B pricing is required, or you are tied to an external payment processor. Shopify when you want ecosystem depth, need point of sale, or rely heavily on third-party integrations.

Situations, and which platform they point toward
‘Leans favourable’ rather than ‘wins’ is deliberate. Both platforms close each other’s gaps continually, and a comparison stating hard verdicts on features is describing a snapshot as though it were permanent.
How to decide, in order
Step seven is the only step that produces certainty. Both platforms offer trials, and loading your genuinely difficult products into each reveals in an afternoon what weeks of comparison reading will not.
1 — Name your hardest requirement. Catalog, not aesthetics..
2 — Native or via app?. Native is fewer failure points..
3 — Choose the processor first. It changes the cost comparison..
4 — Count required apps. Each is a subscription..
5 — Total the real cost. Platform fee is not the cost..
6 — Build a trial store. Two days beats two weeks of reading..

Physical retail points clearly to Shopify

Point of sale, in-store hardware and unified inventory across online and physical selling are mature on Shopify and are the clearest single-feature case in the comparison. A retailer with shops should probably stop reading here.

B2B with pricing tiers points toward BigCommerce

Customer groups with distinct pricing, quote workflows and account-based purchasing are closer to native on BigCommerce. Shopify addresses this too, and the route is generally through a higher plan tier or apps, which returns you to the moving-parts question.

What about migrating between them?

Products, customers and orders migrate reasonably well. URLs, apps, custom functionality and anything built into a theme do not, and the migration cost is usually underestimated.

What migrates easily and what does not
ItemMigratesNotes
Products and variantsUsually wellComplex option structures need mapping
CustomersUsually wellPasswords do not transfer; customers must reset
Order historyUsually wellAs records; not as live, editable orders
URLs and redirectsManuallyThe commonest cause of traffic loss after migration
Apps and their dataNoEach must be replaced and reconfigured
Theme and custom codeNoA rebuild, not a transfer
ReviewsDepends on the appFrequently lost; check before migrating
Search rankingsAt riskRedirect mapping is what protects them

The fourth row causes more damage than anything else on the list. A migration that does not map every existing URL to its new equivalent loses accumulated search visibility, and recovering takes months. It is entirely preventable and routinely skipped under deadline pressure.

Do not migrate to escape a problem you have not diagnosed

Stores frequently replatform because performance is poor or the site is hard to manage, and the cause is usually the build rather than the platform. A migration that carries the same decisions to a new platform reproduces the same problems at considerable cost.

What should you actually do before deciding?

Build a trial store on each with your ten hardest products. Two days of that answers more than any amount of comparison reading.

  1. List your genuinely difficult requirements — catalog structure, pricing rules, integrations
  2. Check each against both platforms’ current documentation rather than any article
  3. Decide your payment processor, since it changes the cost comparison materially
  4. Price the apps each option would need to meet your requirements
  5. Total plan fee, apps and transaction fees on your expected volume
  6. Open a trial on both and load your ten hardest products, not your ten easiest
  7. Attempt your two hardest workflows on each, end to end
  8. Ask a developer you would actually hire which they would rather maintain

Step six is where merchants mislead themselves. Loading simple products proves nothing, because both platforms handle those. The value of the trial is entirely in the products and workflows you were worried about.

Ask the developer who will maintain it

The person supporting the store for the next three years has a view worth more than any comparison. Developer availability, familiarity and preference are real inputs, and asking is free.

What does not decide this, despite appearing in every comparison?

Theme quality, page speed, ease of use, uptime, and basic SEO capability. All are adequate on both, and none separates them.

Theme quality — Does not decide it. Both are adequate..
Page speed — Does not decide it. Both are fast when built well..
'Ease of use' — Does not decide it. Both are usable..
Uptime claims — Does not decide it. Both are reliable..
SEO capability — Does not decide it. Both are competent..
Which one an article prefers — Does not decide it. Check for affiliate links..

Page speed in particular is worth dismissing explicitly. Both platforms are fast; store speed is determined by the theme, the images, the apps loading scripts and the build quality, and a slow store on either platform is a build problem rather than a platform one.

SEO capability is comparable

Both handle titles, metadata, structured data, canonicals, sitemaps and redirects competently, with minor differences in URL structure flexibility. Neither has a meaningful advantage, and comparisons claiming otherwise are usually describing a limitation that has since been addressed.

Both platforms run partner programs that pay for referred merchants. That does not make a recommendation wrong and it does explain why the ordering in published comparisons is more consistent than the underlying products are.

How does the bigcommerce vs shopify decision change by business stage?

Early stores should optimize for speed of launch and reversibility; established stores should optimize for the constraint they have actually hit.

What the decision looks like at each stage
StageWhat matters mostWhich way it leansWhat to ignore
Pre-launch, simple catalogSpeed to launch, low commitmentEither; Shopify is marginally faster to stand upFeature depth you will not use
Early, growing catalogWhether complexity is arrivingBigCommerce if variants are multiplyingEnterprise features
Established, hit an app-count problemFewer moving partsBigCommerce leans favourableSunk cost in the current build
Established, hit a hiring problemDeveloper availabilityShopifyNative feature comparisons
Adding physical retailPoint of sale maturityShopifyEverything else
Adding B2B alongside retailCustomer groups and pricing tiersBigCommerce leans favourableApp workarounds you will maintain
Going internationalCurrency, tax, fulfillment specificsEither; check current capabilityGeneral claims either way

The third and fourth rows are the two genuine reasons established stores replatform, and they point in opposite directions. A store drowning in app subscriptions and one that cannot find a developer have different problems, and moving to solve one can create the other.

Shopify alternatives are a broader question than this comparison

People searching shopify alternatives are frequently not choosing between these two at all — they may be considering open-source platforms, headless commerce, or a marketplace-only approach. BigCommerce is the closest direct substitute, and it is not the only option and should not be assumed to be the answer.

Reversibility matters more early than late

A store with fifty products and no custom development can move platforms in a fortnight. The same store three years later, with apps, integrations and accumulated search visibility, cannot. Early decisions should weight that asymmetry rather than trying to predict requirements you do not have yet.

Want a build that works properly on whichever you choose?

We build ecommerce sites on both, with no partner revenue from either, and we will tell you plainly which one your specific catalog and payment situation points toward — including when the honest answer is that your current platform is fine and the build is the problem.

Talk to Progression Agency

Video: ecommerce, platforms and measurement

A general library on marketing and ecommerce practice. The platform comparison is written out in full above.

Websites and design

Frequently asked questions

What is the real bigcommerce cost once you add everything?
Plan fee plus apps plus payment processing, and the plan tier is volume-gated. The headline bigcommerce cost starts low, but plans upgrade automatically once annual sales cross a threshold, which catches growing merchants by surprise. Budget for the tier above the one you sign on.
How does shopify vs bigcommerce pricing compare at the same sales volume?
Closer than the sticker prices suggest, once transaction fees are included. Shopify vs bigcommerce pricing differs most in how each handles payments: BigCommerce charges no additional transaction fee on any gateway, while Shopify adds one unless you use Shopify Payments. At high volume on a non-native gateway, that single difference can outweigh the plan fee gap.
Should I choose shopify or bigcommerce for a catalog-heavy store?
BigCommerce, generally, for complex product data. Choosing shopify or bigcommerce comes down to where your complexity sits: BigCommerce handles large variant counts and B2B price lists natively, while Shopify’s app ecosystem and checkout conversion are stronger. Neither is better in the abstract.
How does shopify plus vs bigcommerce enterprise compare for a large merchant?
Checkout control versus native B2B features. Shopify plus vs bigcommerce enterprise is largely a trade between Shopify Plus’s checkout customization and ecosystem depth and BigCommerce Enterprise’s built-in B2B, multi-storefront and no-transaction-fee model. Migration cost usually decides it more than feature lists do.
What actually separates BigCommerce and Shopify?
Three things: how much catalog complexity each handles natively, how transaction fees interact with your payment processor, and ecosystem size against how many moving parts you want to maintain.
Which is better overall?
Neither. They solve the same problem well enough that a feature comparison produces a tie. The right answer depends on your catalog, your payment processor and your appetite for apps.
Which handles complex products better?
BigCommerce does more of it natively — option rules, customer groups, faceted filtering. Shopify reaches the same outcomes through apps, which works and adds dependencies.
What is Shopify’s transaction fee?
Shopify charges an additional platform transaction fee when you use a payment gateway other than Shopify Payments. BigCommerce does not charge a platform transaction fee. Verify current rates on each vendor’s pricing page.
Does the transaction fee matter if I use Shopify Payments?
No. If you are happy using Shopify Payments it is not a cost at all. It matters when you are tied to a specific processor by an existing agreement, a negotiated rate, your region or your industry.
How should I compare the real monthly cost?
Platform fee plus apps plus payment processing plus any platform transaction fee, on your expected volume. The plan fee alone is frequently the smallest of the four components.
Why do apps matter so much to the cost comparison?
Because a Shopify store needing six apps to match what BigCommerce does natively is not cheaper for having the same plan price. Count the apps your specific requirements need on each side.
Which has the bigger ecosystem?
Shopify, substantially. More apps, more agencies, more developers, and more problems already solved publicly. Brand search volume differs by roughly thirteen to one, which reflects the same thing.
Is a bigger ecosystem always better?
No. A store running eleven apps has eleven subscriptions, eleven update cycles and eleven places for something to break that nobody owns. The advantage is real and so is the maintenance burden.
Which is better for B2B?
BigCommerce leans favourable — customer groups with distinct pricing and account-based purchasing are closer to native. Shopify addresses it through a higher tier or apps, which returns you to the moving-parts question.
Which is better for physical retail?
Shopify, clearly. Point of sale, in-store hardware and unified inventory across online and physical selling are mature there, and it is the clearest single-feature case in the comparison.
Is one faster than the other?
No meaningful difference. Store speed is determined by the theme, images, apps loading scripts and build quality. A slow store on either platform is a build problem, not a platform problem.
Is one better for SEO?
They are comparable. Both handle titles, metadata, structured data, canonicals, sitemaps and redirects competently, with minor differences in URL structure flexibility.
Which is easier to use?
Both are usable, and this axis does not separate them. It appears in every comparison because it is easy to write about, not because it decides anything.
How hard is it to migrate between them?
Products, customers and order history migrate reasonably well. URLs, apps, custom functionality and anything built into a theme do not, and the cost is usually underestimated.
What causes the most damage during a migration?
Unmapped URLs. A migration that does not redirect every existing URL to its new equivalent loses accumulated search visibility, and recovery takes months. It is entirely preventable.
Do customer passwords transfer?
No. Customers have to reset them, which is worth planning a communication around rather than discovering on launch day.
Should I replatform because my site is slow or hard to manage?
Diagnose first. Those problems are usually caused by the build rather than the platform, and a migration that carries the same decisions across reproduces them at considerable cost.
What is the single most useful thing I can do before deciding?
Open a trial on both and load your ten hardest products — not your ten easiest — then attempt your two hardest workflows end to end. Two days answers more than weeks of comparison reading.
Should I ask my developer which they prefer?
Yes. The person maintaining the store for three years has a view worth more than any comparison, and developer availability and familiarity are genuine business inputs.
Why do published comparisons agree with each other so consistently?
Both platforms run partner programs that pay for referred merchants. That does not make a recommendation wrong, and it explains why the ordering is more consistent than the underlying products are.
How current is this comparison?
It reflects each vendor’s published information as of August 2026. Both ship continuously and have converged for a decade, so verify anything decisive against their current documentation before acting on it.

Sources and further reading

  1. Google Search Essentials — SEO starter guide
  2. Google: creating helpful, reliable, people-first content
  3. Google: intro to structured data
  4. Google: LocalBusiness structured data
  5. Google: FAQPage structured data
  6. Google: Article structured data
  7. Google: Product structured data
  8. Google: title links in search results
  9. Google: control your snippets
  10. Google: robots.txt introduction
  11. Google: sitemaps overview
  12. Google: consolidate duplicate URLs
  13. Google: redirects and Search
  14. Google: JavaScript SEO basics
  15. Google: multi-regional and multilingual sites
  16. Google Search Central Blog
  17. Google: get started with Search Console
  18. Google: how local search results are determined
  19. Google Business Profile: prohibited and restricted content
  20. Google Business Profile: address and service area guidelines
  21. Google Business Profile: review policy
  22. Google Business Profile: add or edit categories
  23. Google Ads: location targeting settings
  24. Google Ads: about negative keywords
  25. Google Ads: about Quality Score
  26. Google Ads: importing offline conversions
  27. Google Ads: about Smart Bidding
  28. Google Ads: about Performance Max
  29. Google Local Services Ads: eligibility and screening
  30. Google Ads: keyword match types
  31. Google Analytics 4: about conversions
  32. Google Analytics 4: attribution models
  33. US Census Bureau QuickFacts: New Jersey
  34. US Census Bureau: American Community Survey
  35. US Census: Statistics of US Businesses
  36. Bureau of Labor Statistics: New Jersey data
  37. BLS: Occupational Employment and Wage Statistics
  38. NJ Department of Labor: labor market information
  39. New Jersey Business Action Center
  40. US Small Business Administration: New Jersey district
  41. USA.gov: business resources
  42. web.dev: Core Web Vitals explained
  43. web.dev: Largest Contentful Paint
  44. web.dev: Cumulative Layout Shift
  45. web.dev: Interaction to Next Paint
  46. Google PageSpeed Insights
  47. Google Rich Results Test
  48. Google Search Console
  49. W3C Markup Validation Service
  50. Schema.org: LocalBusiness type
  51. Schema.org: Service type
  52. Schema.org: FAQPage type
  53. Schema.org: HowTo type
  54. W3C: WCAG 2.2 quick reference
  55. FTC: CAN-SPAM Act compliance guide
  56. FCC: telemarketing and robocall rules (TCPA)
  57. FTC endorsement guides — reviews and testimonials
  58. FTC: rule on consumer reviews and testimonials
  59. HHS: HIPAA guidance on online tracking technologies
  60. New Jersey Courts: attorney advertising guidelines
  61. New Jersey DCA: construction codes and permits
  62. New Jersey Home Improvement Contractor registration
  63. New Jersey Division of Consumer Affairs
  64. TikTok for Business
  65. TikTok Creative Center
  66. TikTok Ads Help Center
  67. TikTok Community Guidelines
  68. TikTok Terms of Service
  69. TikTok Privacy Policy
  70. TikTok Safety Center
  71. TikTok Transparency Center
  72. TikTok Creator Portal
  73. TikTok Newsroom
  74. TikTok for Developers
  75. TikTok advertising solutions
  76. TikTok Creator Marketplace
  77. TikTok Business Center
  78. TikTok for Business blog
  79. TikTok Creative Center: top ads
  80. TikTok Branded Content policy
  81. TikTok Shop for sellers
  82. Instagram for Business
  83. Instagram for Creators
  84. Instagram Help Center
  85. About Instagram
  86. Meta Business Suite
  87. Meta Business Help Center
  88. Meta Transparency Center
  89. About Meta
  90. Meta: Instagram platform docs
  91. YouTube Creators
  92. YouTube Official Blog
  93. YouTube Shorts help
  94. How YouTube Works
  95. YouTube Studio
  96. LinkedIn Marketing Solutions
  97. LinkedIn Help
  98. Pinterest Business
  99. Pinterest Business Help
  100. Snapchat for Business
  101. X for Business
  102. Reddit communities
  103. Reddit for Business Help
  104. ASCAP
  105. BMI
  106. SESAC
  107. Global Music Rights
  108. PRS for Music (UK)
  109. PPL (UK)
  110. SOCAN (Canada)
  111. APRA AMCOS (Australia)
  112. GEMA (Germany)
  113. SACEM (France)
  114. SIAE (Italy)
  115. JASRAC (Japan)
  116. IFPI
  117. RIAA
  118. National Music Publishers Association
  119. Harry Fox Agency
  120. SoundExchange
  121. Music Reports
  122. Epidemic Sound
  123. Artlist
  124. Soundstripe
  125. PremiumBeat
  126. AudioJungle
  127. Free Music Archive
  128. Creative Commons
  129. Incompetech
  130. FTC: advertising and marketing
  131. FTC: disclosures 101
  132. FTC: endorsement guides
  133. FTC: consumer reviews rule
  134. FTC: advertising FAQs
  135. US Copyright Office
  136. US Copyright Office: DMCA
  137. US Copyright Office: music FAQ
  138. US Copyright Office: fair use FAQ
  139. USPTO: trademarks
  140. UK Advertising Standards Authority
  141. ACCC (Australia)
  142. Competition Bureau Canada
  143. GDPR overview
  144. California Consumer Privacy Act
  145. COPPA
  146. FTC: children’s privacy
  147. W3C Web Accessibility Initiative
  148. W3C: WCAG
  149. W3C: captions
  150. W3C: making audio and video accessible
  151. ADA.gov
  152. WebAIM
  153. Epilepsy Foundation
  154. Pew Research: internet and technology
  155. DataReportal
  156. US Census Bureau
  157. US Bureau of Labor Statistics
  158. Interactive Advertising Bureau
  159. Think with Google
  160. Google Trends
  161. Nielsen insights
  162. Schema.org: VideoObject
  163. Schema.org: SocialMediaPosting
  164. Schema.org: MusicRecording
  165. Schema.org: HowTo
  166. Schema.org: FAQPage
  167. Schema.org: Organization
  168. Google: video best practices
  169. Google: video structured data
  170. CapCut
  171. Adobe Premiere Rush
  172. DaVinci Resolve
  173. Canva
  174. Descript
  175. VEED
  176. Kapwing
  177. Otter.ai
  178. Later
  179. Buffer
  180. Hootsuite
  181. Sprout Social
  182. Google Analytics
  183. Google Search Console
  184. Google Analytics developer docs
  185. GA4: events and conversions
  186. Matomo
  187. Plausible Analytics
  188. Similarweb
  189. UK Information Commissioner’s Office
  190. Office of the Privacy Commissioner of Canada
  191. Australian OAIC
  192. European Data Protection Board
  193. EU data protection
  194. EU Digital Services Act
  195. Ofcom
  196. FCC
  197. AIGA
  198. Nielsen Norman Group
  199. Smashing Magazine
  200. web.dev
  201. MDN: web media
  202. MDN: the video element
  203. ISO 21001 (reference)
  204. Buma/Stemra (Netherlands)
  205. STIM (Sweden)
  206. Teosto (Finland)
  207. Koda (Denmark)
  208. TONO (Norway)
  209. IMRO (Ireland)
  210. SGAE (Spain)
  211. ZAiKS (Poland)
  212. KOMCA (South Korea)
  213. MCSC (China)
  214. CISAC
  215. World Intellectual Property Organization
  216. TikTok: creating videos
  217. TikTok: exploring videos
  218. TikTok: privacy settings
  219. TikTok: growing your audience
  220. TikTok Creator Academy
  221. TikTok Effect House
  222. TikTok for small business
  223. Instagram: Reels help
  224. YouTube: Shorts best practice
  225. How YouTube recommends
  226. Pinterest Predicts
  227. Snapchat for Business
  228. Hootsuite blog
  229. Social Media Examiner
  230. Marketing Week
  231. Adweek

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.