--- title: Code opinion: why I prefer avoiding the Async suffix in... description: An opinion piece arguing against the common C# convention of suffixing asynchronous method names with 'Async'. The author contends the suffix adds mental... canonical: https://daily.dev/posts/code-opinion-why-i-prefer-avoiding-the-async-suffix-in-c-asynchronous-methods-e1xd1zgn4 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Code opinion: why I prefer avoiding the Async suffix in C# asynchronous methods | daily.dev og:description: An opinion piece arguing against the common C# convention of suffixing asynchronous method names with 'Async'. The author contends the suffix adds mental... og:url: https://daily.dev/posts/code-opinion-why-i-prefer-avoiding-the-async-suffix-in-c-asynchronous-methods-e1xd1zgn4 og:image: https://api.daily.dev/og/posts/E1Xd1ZGN4.png og:image:alt: Code opinion: why I prefer avoiding the Async suffix in C# asynchronous methods og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Code opinion: why I prefer avoiding the Async suffix in C# asynchronous methods **[Code4IT](https://daily.dev/sources/code4it)** · 9 min read · 0 upvotes · 0 comments ## Summary An opinion piece arguing against the common C# convention of suffixing asynchronous method names with 'Async'. The author contends the suffix adds mental clutter and violates the principle that a method name should express what it does rather than how it's implemented internally. Points covered include readability of call chains already signaled by 'await', the problem of a single interface having both sync and async implementations, and objections such as Microsoft's own use of the suffix and fire-and-forget methods. The author concedes the suffix is justified only when a public library must expose both sync and async versions of the same method to avoid breaking changes. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Should I add the Async suffix to all my asynchronous C# method names? Not necessarily. A method name should express what it does, not how it is implemented, so adding Async just because a method awaits something adds mental overhead without real benefit. The presence of await keywords and a Task return type already signal asynchrony to callers and IDEs. The suffix remains useful mainly when a public library must expose both a synchronous and asynchronous version of the same method to avoid breaking changes for existing consumers. _Developers debating naming conventions in C# compare real-world opinions and tradeoffs on daily.dev._ ### Why does Microsoft use the Async suffix on methods like HttpClient's SendAsync? Microsoft uses the Async suffix because its libraries often need to maintain both synchronous and asynchronous versions of the same method for backward compatibility, so the suffix distinguishes the two explicitly and avoids breaking changes for consumers depending on the original synchronous signature. Once that pattern was established, it was carried forward for newer APIs even where no synchronous counterpart exists. _Teams weighing framework conventions versus their own style can track these discussions on daily.dev._ ## Similar posts on daily.dev - [The quiet problem with unnecessary async](https://daily.dev/posts/the-quiet-problem-with-unnecessary-async-6fhremtom) · Matt Smith · 49 upvotes · 9 comments - [Demystifying async/await in C\#: The Hidden State Machine](https://daily.dev/posts/demystifying-async-await-in-c-the-hidden-state-machine-ej0npqym4) · C\# Corner · 0 upvotes · 0 comments - [Async or Swim: The Complete Guide to Asynchronous .NET](https://daily.dev/posts/async-or-swim-the-complete-guide-to-asynchronous-net-n2fszfnf6) · ITNEXT · 9 upvotes · 1 comments --- Tags: [#.net](https://daily.dev/tags/.net), [#c#](https://daily.dev/tags/c#) [View this post on daily.dev](https://daily.dev/posts/code-opinion-why-i-prefer-avoiding-the-async-suffix-in-c-asynchronous-methods-e1xd1zgn4) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Code opinion: why I prefer avoiding the Async suffix in C# asynchronous methods","url":"https://daily.dev/posts/code-opinion-why-i-prefer-avoiding-the-async-suffix-in-c-asynchronous-methods-e1xd1zgn4","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/code-opinion-why-i-prefer-avoiding-the-async-suffix-in-c-asynchronous-methods-e1xd1zgn4"},"datePublished":"2026-10-04T13:07:33.237Z","dateModified":"2026-10-04T13:19:10.730Z","description":"An opinion piece arguing against the common C# convention of suffixing asynchronous method names with 'Async'. The author contends the suffix adds mental...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f9ff94bb33d7af5b5e2de8e578f5639a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f9ff94bb33d7af5b5e2de8e578f5639a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Code4IT","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Code4IT","logo":"https://media.daily.dev/image/upload/s--OaaG4G10--/f_auto,q_auto/v1791119049/logos/code4it?_a=BAMAMicg0","url":"https://daily.dev/sources/code4it"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/code-opinion-why-i-prefer-avoiding-the-async-suffix-in-c-asynchronous-methods-e1xd1zgn4","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":".net,c#","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Code4IT","item":"https://daily.dev/sources/code4it"},{"@type":"ListItem","position":3,"name":"Code opinion: why I prefer avoiding the Async suffix in C# asynchronous methods"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/code-opinion-why-i-prefer-avoiding-the-async-suffix-in-c-asynchronous-methods-e1xd1zgn4#faq","mainEntity":[{"@type":"Question","name":"Should I add the Async suffix to all my asynchronous C# method names?","acceptedAnswer":{"@type":"Answer","text":"Not necessarily. A method name should express what it does, not how it is implemented, so adding Async just because a method awaits something adds mental overhead without real benefit. The presence of await keywords and a Task return type already signal asynchrony to callers and IDEs. The suffix remains useful mainly when a public library must expose both a synchronous and asynchronous version of the same method to avoid breaking changes for existing consumers. Developers debating naming conventions in C# compare real-world opinions and tradeoffs on daily.dev."}},{"@type":"Question","name":"Why does Microsoft use the Async suffix on methods like HttpClient's SendAsync?","acceptedAnswer":{"@type":"Answer","text":"Microsoft uses the Async suffix because its libraries often need to maintain both synchronous and asynchronous versions of the same method for backward compatibility, so the suffix distinguishes the two explicitly and avoids breaking changes for consumers depending on the original synchronous signature. Once that pattern was established, it was carried forward for newer APIs even where no synchronous counterpart exists. Teams weighing framework conventions versus their own style can track these discussions on daily.dev."}}]} ```