Scroll Top

FTP Clients: Which to Use, and Why You Should Use SFTP

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

An FTP client is a program for moving files between your computer and a web server. The honest starting point is that plain FTP is obsolete and insecure — it sends credentials in clear text — and almost everyone searching for an FTP client actually needs SFTP or FTPS, which the same programs support. This page covers which clients are worth using, what the protocol differences actually mean, and when file transfer is the wrong tool entirely.

The short answerThree things settle this quickly. First, do not use plain FTP: it transmits your username and password unencrypted, and every mainstream client supports SFTP instead at no extra cost or difficulty. Second, pick a client on the platform you actually use — FileZilla and WinSCP on Windows, Cyberduck and Transmit on macOS, and the built-in tools if you are comfortable at a command line. Third, and most important: if you are transferring website files by hand on a regular basis, the transfer method is not your problem. Deployment is, and that is a different and better-solved thing.

Client capabilities described here reflect each product’s own published documentation as of August 2026 and the free or paid tiers stated on their own sites. Pricing and features change; confirm against the vendor before purchasing. Progression Agency has no affiliate relationship with any product named and receives nothing from these recommendations.

Progression Agency runs Web Development and Website Maintenance as separate divisions, and this page reflects what the second one spends most of its time undoing: sites edited directly on the server with no version history. We are a New York City firm working across the United States. We have no affiliate relationship with any product named here.

The protocols, and which to use
The last row is the one worth acting on. If you are moving website files manually more than occasionally, choosing a better transfer client optimizes a process that should not be manual in the first place.

What is an FTP client?

An FTP client is a program that moves files between your computer and a remote server. The name has stuck even though the protocol it refers to should no longer be used: modern clients primarily connect over SFTP or FTPS, which are encrypted, and support plain FTP mainly for compatibility with old servers.

This matters more than a naming quibble. Plain FTP transmits your username, your password and everything you transfer without encryption, so anybody positioned between you and the server can read all of it. It was designed before that was a realistic concern and it has not changed.

FTP, FTPS, SFTP and SCP, briefly

FTP is the original unencrypted protocol. FTPS is FTP wrapped in TLS, which encrypts it. SFTP is a different protocol entirely, running file transfer over an SSH connection, and is what most hosts and most people should use. SCP is an older SSH-based copy mechanism, still fine inside scripts.

The practical rule

Use SFTP. It is supported by every client on this page, by essentially every modern host, and it requires no extra cost or meaningful additional effort. If a host offers only plain FTP, that is worth treating as information about the host.

Transfer methods by suitability and risk
The two deployment options sit alone in the strong corner. Everything on the left of the chart is a way of moving files; deployment is a way of changing a site, and they are not the same activity even when they move the same bytes.
Plain FTP on port 21 — Avoid. Credentials sent in clear text..
Passwords in a text file — Avoid. The most common credential leak..
Editing live files directly — Avoid. No history, no review, real risk..
Clicking past host key warnings — Avoid. It removes the protection..
Full-site uploads for one change — Avoid. Slow and error-prone..
Bundled software in installers — Avoid. Read every installer screen..

Which FTP client should you use?

FileZilla if you want free and cross-platform, WinSCP if you are on Windows and want the best scripting, Cyberduck if you want something simple, Transmit if you are on macOS and will pay for polish, and the command line if you are comfortable there.

FileZilla — Free, cross-platform. The common default; watch the installer..
WinSCP — Free, Windows only. Excellent scripting and sync..
Cyberduck — Free, Mac and Windows. Simple; connects to cloud storage too..
Transmit — Paid, macOS only. Polished; strong sync features..
Command line — Free, everywhere. sftp and rsync; best for scripts..
Host file manager — Free, in the panel. Fine for one small edit..
FTP and SFTP clients compared
Platform coverage is the column that usually decides. WinSCP is Windows only and Transmit is macOS only, which removes them from consideration for a lot of people before any feature comparison happens.
FTP and SFTP clients compared on what actually differs
ClientPlatformsCostStrongest atWorth knowing
FileZillaWindows, macOS, LinuxFreeBeing available everywhereRead the installer screens carefully
WinSCPWindows onlyFreeScripting and directory syncNo macOS or Linux version
CyberduckmacOS, WindowsFree, donation promptedSimplicityAlso connects to cloud storage
TransmitmacOS onlyPaidInterface polish and syncmacOS users only
Command line sftpEverywhereFreeAutomation and scriptsNo interface to learn or misuse
Rsync over SSHEverywhereFreeTransferring only what changedThe right tool for large syncs
Host control panel managerIn the browserIncludedOne quick editPoor for anything repeated

The ‘worth knowing’ column carries the practical differences. FileZilla’s installer has historically offered additional bundled software on some platforms, which is worth reading rather than clicking through; and rsync is the correct answer to ‘this transfer takes too long’ far more often than a different client is.

Free is not the deciding factor here

Most of these are free and the free ones are genuinely good. The paid option earns its price on interface quality rather than capability, which is a legitimate reason to buy it and not a functional necessity.

The command line deserves more consideration than it gets

The built-in sftp command and rsync are available everywhere, need no installation, and are the only options that script cleanly. For anybody doing the same transfer repeatedly, learning two commands removes the client entirely.

How do you connect securely?

Ask your host for SFTP credentials, connect on port 22 rather than 21, use key-based authentication if offered, verify the host key fingerprint on first connection, and store credentials in the client’s encrypted store.

How to set up a connection securely
Step four is the one people skip. Verifying the host key fingerprint the first time is what makes every subsequent connection trustworthy, and clicking through it removes the protection the protocol was providing.
Use SFTP, not FTP — Do. Same clients, no extra cost..
Verify the host key — Do. Once, properly, first connection..
Use key authentication — Do. Stronger and easier daily..
Store credentials encrypted — Do. In the client, not a file..
Keep a local copy — Do. Before overwriting anything..
Move to deployment — Do. If transfer is routine..

Verify the host key once, properly

The first time you connect, the client shows a fingerprint and asks whether you trust it. That is the moment the connection becomes trustworthy for every subsequent session, and clicking past it without checking removes the protection SSH was providing. Ask your host for the fingerprint and compare it.

Key authentication is easier as well as safer

A key pair removes the password from the process entirely: nothing to type, nothing to leak, nothing to rotate when someone leaves. Most hosts support it and the setup is a one-off task of a few minutes.

Never store credentials in a plain text file

Server credentials pasted into a text file or a shared document are among the most common sources of compromise for small websites. Every client on this page has an encrypted credential store, and a password manager is the right home for anything shared across a team.

Transfer decisions worth making
The ninth row causes the most damage in practice. Editing a live file directly over a connection means no version history, no review, and a broken site if the connection drops mid-save.

Why should you probably not be transferring website files by hand at all?

Because manual transfer has no version history, no review step, no rollback and no record of who changed what. If you are doing it regularly for a website, the transfer client is not the problem — the absence of a deployment process is.

Git-based deployment — Instead. Version history and rollback..
A staging environment — Instead. Break things safely..
Automated pipeline — Instead. Consistent, repeatable, logged..
Rsync for large syncs — Instead. Transfers only what changed..
Key-based SSH access — Instead. No passwords to leak..
Backups before any change — Instead. The cheapest insurance available..

This is the most useful thing on this page and it is not what people arrive looking for. Choosing a better client makes a manual process slightly more pleasant; moving to deployment removes an entire category of website outage caused by a half-uploaded file or an overwritten change nobody can recover.

What deployment gives you that transfer does not

  • A record of every change, who made it and when.
  • The ability to roll back to any previous state in seconds.
  • A review step before anything reaches a live site.
  • Consistency: the same process every time, not whatever was dragged where.
  • A staging environment where breaking something costs nothing.
  • Automatic transfer of only what actually changed.
  • No half-finished uploads leaving a site in a broken state.

None of that is available from any FTP client at any price, because it is a different problem. The transfer is the easy part; knowing what changed and being able to undo it is the part that matters when something goes wrong at an inconvenient time.

Moving from manual transfer to deployment
The first row costs nothing and can be done today. Everything after it is a genuine project, and the first row is worth doing immediately regardless of whether the rest ever happens.

The migration timeline puts the free win first deliberately. Switching from FTP to SFTP takes one connection setting and can happen today; the rest is a genuine project worth doing and worth planning, and the first step should not wait for it.

When is manual file transfer the right answer?

For genuinely one-off tasks: retrieving a log file, uploading a single image, pulling a database backup, or inspecting something on a server you do not otherwise control. Those are legitimate and a client is the right tool.

Transfer method by task
TaskBest methodWhy
Retrieving a log fileSFTP client or command lineOne-off read, no risk
Uploading a single imageSFTP clientFine; nothing to version
Downloading a database backupSFTP or command lineWatch file size and integrity
Deploying website code changesGit-based deploymentHistory, review and rollback
Syncing a large media directoryRsync over SSHTransfers only what changed
Editing a live configuration fileDeployment, or with a backup firstDirect editing is where outages start
Migrating a whole siteScripted transfer plus a checklistManual dragging loses files silently

The last row is where most website migrations go wrong. Dragging a site folder from one server to another silently omits hidden files, permissions and anything the transfer interrupted, and the omissions are discovered afterwards by users rather than by the person migrating.

Search demand around file transfer
The fourth bar matters more than its size suggests: people searching for an SFTP client already know which protocol they need, while the larger FTP terms include many people who do not.

What about the host’s built-in file manager?

Fine for one small edit, poor for anything repeated. It is convenient because it requires no setup, and it shares every weakness of manual transfer plus a browser session that can time out mid-save.

Do you need an FTP client for WordPress?

Occasionally, and less than most guides suggest. Plugins, themes and updates are handled inside the admin, and the times a file connection is genuinely needed are usually recovery situations — a plugin that has broken the site, or a file that needs removing when the admin is unreachable.

That recovery use is a good reason to have a working SFTP connection set up before you need it. Configuring one during an outage, without the credentials to hand, is considerably less pleasant than doing it on a quiet afternoon.

What file permissions should you set?

Follow your host’s documented recommendation rather than a number from a forum. Permissions that are too open are a genuine security problem and permissions copied from an unrelated setup are a common cause of a site that suddenly stops working.

Why is a transfer slow?

Usually many small files rather than total size, because each file carries connection overhead. Rsync solves this by transferring only differences, and archiving a directory before transferring it solves the small-file problem directly.

Is FTP being removed?

It has been progressively removed from places it used to be supported — browsers dropped built-in FTP support some years ago — and dedicated clients continue to support it for legacy servers. The direction of travel is clear and it argues for moving to SFTP now rather than when something forces it.

What should a team standardize on?

One protocol (SFTP), key-based authentication, a shared password manager rather than shared credentials in a document, and deployment for anything touching a live website. The client each person prefers matters far less than those four.

Common mistakes

Seven, and the first two are the ones that cause actual damage.

File transfer mistakes and what to do instead
MistakeConsequenceInstead
Using plain FTPCredentials sent in clear textSFTP; same client, no extra cost
Editing live files directlyNo history, no rollback, real outagesDeployment with a review step
Clicking past host key warningsThe protection is removedVerify the fingerprint once, properly
Credentials in a text fileA common source of compromiseEncrypted store or password manager
Uploading a whole site for one changeSlow, and it can leave a broken stateTransfer only what changed
Dragging a site folder to migrateHidden files and permissions lost silentlyScripted transfer plus a checklist
Copying permissions from a forum postA site that stops workingYour host’s documented recommendation

For the wider picture, our website maintenance page covers what a properly maintained site actually needs, and the web development page covers how the deployment side of this is set up in the first place.

A decision table: which client, for which person

Answer first: the client that fits you is decided by platform first, then by whether you script anything, then by whether you will pay for interface quality. The table below runs those three questions in order.

Which file transfer client fits which situation
Your situationUse thisWhyWhat you give up
Windows, occasional transfersWinSCPFree, strong sync, easy to learnNothing on Windows
Windows, also uses Mac or LinuxFileZillaOne tool on every platformLess polished sync
macOS, wants simpleCyberduckFree, clean, connects to cloud storageFewer advanced features
macOS, will pay for polishTransmitBest interface and sync on the platformCost, and macOS only
Comfortable in a terminalBuilt-in sftpNothing to install, scripts cleanlyNo visual file browser
Large media directoriesRsync over SSHTransfers only what changedCommand line only
One quick edit, no setupHost control panelZero configurationPoor for anything repeated

Notice that the last row is the only one where convenience wins, and it comes with the strongest caveat. A control panel file manager is genuinely the fastest way to make one small change and genuinely the worst way to make ten.

What a secure setup actually looks like, end to end

Answer first: SFTP on port 22, key-based authentication, host key verified once, credentials in an encrypted store, and a backup taken before anything is overwritten. Five things, all one-off except the last.

Secure transfer checklist and what each item prevents
SettingWhat it preventsOne-off or ongoing
SFTP rather than FTPCredentials readable in transitOne-off
Port 22, not 21Accidentally using plain FTPOne-off
Key-based authenticationPassword leakage and reuseOne-off
Host key verified on first connectConnecting to the wrong serverOne-off
Credentials in the encrypted storeThe most common small-site compromiseOne-off
Local and remote start directories setUploading to the wrong placeOne-off
Backup before overwritingLosing a file with no copyEvery time

Six of the seven are configured once and then protect you indefinitely, which is an unusually good return for about fifteen minutes of setup. The seventh is the habit, and it is the one that saves you on the day something goes wrong.

Still moving website files by hand?

Tell us how your site is currently updated and we will tell you what a deployment process would look like for it — including when the honest answer is that switching to SFTP and taking a backup before each change is enough for the size of site you are running.

Talk to Progression Agency

Video: servers, deployment and web infrastructure

Three talks covering servers, deployment practice and web infrastructure. Everything relevant to protocols and clients is written out in text above, so nothing here depends on watching them.

Getting found in search

AI, AEO and what is changing

Paid media and lead generation

Websites and design

Choosing and working with an agency

Social, content and brand

By industry and by situation

Frequently asked questions

What is an FTP client?
A program that moves files between your computer and a remote server. The name persists although the original protocol should no longer be used: modern clients connect primarily over SFTP or FTPS, which are encrypted.
Is FTP secure?
No. Plain FTP transmits your username, password and file contents without encryption, so anyone positioned between you and the server can read all of it. Use SFTP instead — every mainstream client supports it at no extra cost.
What is the difference between FTP, FTPS and SFTP?
FTP is the original unencrypted protocol. FTPS is FTP wrapped in TLS, which encrypts it. SFTP is a different protocol running file transfer over SSH and is what most hosts and most people should use.
What is the best free FTP client?
FileZilla if you need cross-platform, WinSCP if you are on Windows and want the best scripting and sync, Cyberduck if you want something simple. All three are free and genuinely capable; platform coverage usually decides.
Is there a good FTP client for Mac?
Cyberduck is free and simple; Transmit is paid and more polished with stronger sync features. FileZilla also runs on macOS. The paid option earns its price on interface quality rather than capability.
What is the best FTP client for Windows?
WinSCP for most Windows users: free, with excellent scripting and directory synchronisation. FileZilla is the cross-platform alternative if you also work on macOS or Linux and want one tool everywhere.
Which port does SFTP use?
Port 22, the same as SSH. Plain FTP uses port 21. If your client is set to port 21 you are using unencrypted FTP regardless of what the connection is labeled.
Should I use key-based authentication?
Yes where your host supports it. A key pair removes the password from the process entirely — nothing to type, nothing to leak, nothing to rotate when someone leaves — and setup is a one-off task of a few minutes.
Why does the client ask me to verify a host key?
Because that first connection is when trust is established. Verifying the fingerprint against one your host provides is what makes every later session trustworthy; clicking past it removes the protection SSH was providing.
Where should server credentials be stored?
In the client’s encrypted credential store, or a password manager for anything shared across a team. Credentials pasted into a text file or shared document are among the most common sources of compromise for small websites.
Should I be transferring website files manually at all?
Not routinely. Manual transfer has no version history, no review step, no rollback and no record of who changed what. If you are doing it regularly, the absence of a deployment process is the real problem.
What does deployment give me that an FTP client does not?
A record of every change, rollback in seconds, a review step before anything goes live, a consistent repeatable process, a staging environment, transfer of only what changed, and no half-finished uploads leaving a broken site.
When is manual file transfer the right tool?
For genuinely one-off tasks: retrieving a log file, uploading a single image, pulling a database backup, or inspecting something on a server you do not otherwise control. Those are legitimate uses for a client.
Do I need an FTP client for WordPress?
Occasionally, and less than most guides suggest. Plugins, themes and updates happen in the admin. The genuine need is usually recovery — a plugin that broke the site, or a file to remove when the admin is unreachable.
Should I set up SFTP before I need it?
Yes. Configuring a connection during an outage without credentials to hand is considerably less pleasant than doing it on a quiet afternoon, and recovery is exactly when you will want it working.
Why is my file transfer so slow?
Usually many small files rather than total size, because each file carries connection overhead. Rsync transfers only differences, and archiving a directory before transferring removes the small-file problem directly.
What file permissions should I set?
Whatever your host documents. Permissions that are too open are a genuine security problem, and numbers copied from an unrelated forum post are a common cause of a site that suddenly stops working.
Is FTP being phased out?
It has been progressively removed from places that used to support it, including browsers some years ago, while dedicated clients keep it for legacy servers. The direction is clear enough to argue for moving to SFTP now.
What is rsync and when should I use it?
A command-line tool that transfers only what has changed between two locations, over SSH. It is the right answer for large media directories and for any sync that is slow because most of the files are already identical.
Is the host’s file manager good enough?
For one small edit, yes. For anything repeated, no. It shares every weakness of manual transfer and adds a browser session that can time out part-way through saving a file.
What should a team standardize on?
SFTP as the only protocol, key-based authentication, a shared password manager rather than credentials in a document, and deployment for anything touching a live site. Which client each person prefers matters much less.
What is the most damaging file transfer habit?
Editing files directly on a live server. There is no history, no review and no way back, and a connection dropping mid-save leaves the site broken with no record of what it looked like beforehand.

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.

Our website uses cookies from third party services to improve your browsing experience. Read more about this and how you can control cookies by clicking "Privacy Preferences".
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.
Privacy Policy
You have read and agreed to our privacy policy
Required