We stand with Ukraine and our team members from Ukraine.

The Community Of Over 578,000

Home ›› Accessibility ›› UI copy: Remove vs Delete

UI copy: Remove vs Delete

by Alex Zlatkus
4 min read
Share this post on


The difference between “remove” and “delete,” and how to ensure your user understands.

I noticed something interesting while cleaning up my Google Docs this past weekend — and it’s related to UI copy.

I was trying to get rid of a doc and saw a Remove optionyet it was accompanied by a trash can icon. The first thing that came to my mind was that trash cans were for deleting…but I am also new to this area, so what did I know?


Remove option with the trash can icon.

So I selected Remove, but then I was hit with a toast notification saying the doc was moved to the trash.

Moved to Trash

I do like the UNDO functionality at least

This started to feel more and more like a delete action than a remove action. I decided to investigate Google Contacts’ copy. Surprisingly, I saw they used the option of Delete with the same trash can.

Moved to Trash

Now we have Delete option with a trash can.

By this point, I realized that (at the very least) Google’s tools are a little confusing, but they might also be downright inconsistent.

Before I could confirm the latter claim I needed to do a little more research on what Delete and Remove really mean in the context of software — as I am not a developer.

Unfortunately, Medium did not provide much help (which is why I am writing this article).

Moved to Trash

Medium came up empty on all three of these searches.

I turned to my colleague — and UX Unicorn — Masha S. She was able to successfully differentiate the two.

Delete means something gets erased from the system completely. Remove means that it still exists in the system, just not visible in the UI. So I guess I would describe deleting as erasing from backend and removing as hiding from frontend.

She went on to explain some more, in context to the software we work on.

For example, we have different types of widgets that are always available to the user, but it’s up to them if they want to see them or not. If they remove a widget, nothing will change on the backend. But if they delete something (element/user/etc.), the information will be gone forever.

This made all the sense in the world, but then why was google being liberal with these words?

I dug a little deeper and realized Docs and Contacts could both be restored. Furthermore, deleting an email can be restored and removing a Google Sheet could be restored. Everything in Google’s suite can be restored. So why are they using different action names? Maybe they know the inconsistency and it’s not worth changing it. Or maybe their Style Guide does not call it out and no one has put the time in to set up some clear rules.

In this scenario, don’t be Google. Make it clear to users what you will be doing with their objects/items. Educate them what the difference is. The below info can be your guide to achieving this.

Fragmented approaches



Definitions of ‘Delete’ and ‘Remove’, with examples.

Moved to Trash

Examples should apply to the majority of apps but you should always ensure they apply to your tool.

What about ‘Create’ and ‘Add’?

In most cases, Create can be paired with Delete, and Add can be paired with Remove.

Moved to Trash

Again, the examples may not apply to your software so confirm by reading the definition.

Where should I be using this copy?

Everywhere! This knowledge should not just be implemented on buttons or dropdown options. Create a consistent experience and add it to all components of your application, like buttons, toast notifications, dropdowns, alerts, headers, dialogs, etc.

Moved to Trash

There must be more examples, but this was all I could come up with

‘Create’ and ‘Add’ Can’t be used for everything, right?

Correct. Here is a list of items that do not have to follow the norm.

Moved to Trash

There must be more examples, but this was all I could come up with

So how do I educate my users?

In the descriptions of alerts you can subtly describe what Remove Delete / Add Create mean.

Moved to Trash

This description showcase the bond between Remove and Add.

Moved to Trash

An example of telling you what Delete means.

There are potential learning opportunities in micro-copy and empty state copy as well!

In review

It can be frustrating trying to be consistent with Delete/Remove, and Create/Add, but I promise the extra effort is worth it for your users. I hope one day the differences between these actions will be common knowledge to users and designers alike.

post authorAlex Zlatkus

Alex Zlatkus,

Alex is a product designer from Boston, MA. With a history in customer support and quality assurance, he focuses on creating empathetic solutions, that work for all use cases.

Alex has extensive experience bringing UX best practices to startups and relish's every opportunity to advocate for design. Alex works at LogicManager, designing SaaS solutions in the risk management industry, and works part time at Connective, a social app for creatives. 


Related Articles

Transition towards customer-centricity and make your UX/CX agile by following 5 steps

How To Make CX/UX Agile In 5 Steps
  • Debbie Levitt suggests her 5 steps to transform however you’re doing Agile towards Customer-Centric Agile:
    1. Hire fully qualified CX and UX pros to do CX and UX work
    2. Hire CX/UX at a nearly 1:1 ratio with engineering
    3. Kill most meetings, five UX decision-making autonomy
    4. Estimate time and plan
    5. Tri-Track Customer-Centric Agile
Share:How To Make CX/UX Agile In 5 Steps
7 min read
How to make CX/UX agile

The project was to design a platform that educates and supports the wishes of those passing, as well as those who are left to mourn by using the design thinking process model.

YOU GOT THIS: An App Designed to Connect, Educate and Empower People Through Their Loss
  • The author designed a platform to educate and support the wishes of those passing, as well as those who are left to mourn.
  • The challenge was to understand the sensitive process of EOL (End of Life) Care and what individuals need.
  • The author’s idea was to create an app that would:
    • Perform daily check-ins
    • Provide resources
    • Provide tips
    • Connect people
  • The author’s approach to this challenge was based on the design thinking process model.
  • The author of this article unpacks the research process:
    • Qualitative analysis
    • Competitive analysis & industry standards
    • User interviews
    • Ideation
    • Prototyping
  • Key takeaways: 
    • Make MVP a key to staying focused
    • Keep iterating
Share:YOU GOT THIS: An App Designed to Connect, Educate and Empower People Through Their Loss
8 min read
YOU GOT THIS: An App Designed to Connect, Educate and Empower People Through Their Loss

An ultimate guide to conversational UX (CUX). Conversational UX principles.

Conversational Design
  • The author defines “conversational UX as a user experience that combines chat, voice or any other natural language-based technology to mimic a human conversation.”
  • The author looks at the following conversational UX Principles:
    •  Affordances
    • Signifiers
    • Feedback
  • Conversational user interface & principles:
    • Cooperative Principle (discover hidden intentions)
    • Turn-Taking (give users a space to interact)
    • Context-aware (in context / out of context)
  • While designing virtual assistants, the author suggests taking two things into consideration:
    1. How to set user expectations and educate users about what their assistants can do
    2. How to help these users
Share:Conversational Design
8 min read
Conversational Design

This website uses cookies to ensure you get the best experience on our website. Check our privacy policy and