> For the complete documentation index, see [llms.txt](https://1spatial.gitbook.io/fme-form-beginner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://1spatial.gitbook.io/fme-form-beginner/transformer-usage/managing-attributes/removing-attributes.md).
# Removing Attributes
Removing attributes is perhaps seen as a less important task in FME. That's because - for a manual attribute schema - only attributes defined in the writer are written to the output; extra attributes that are not required are just ignored.
However, removing attributes does carry useful benefits:
* Removing attributes that aren’t required tidies up a workspace and makes it easier to understand
* A workspace is a complex network of objects and schemas. Removing attributes simplifies this network and makes the Workbench interface more responsive
* All data processing incurs costs of time and memory. Removing attributes means less data is being processed and so the FME engine performs faster
{% hint style="info" %}
**TIP**
*A reader feature type has parameters to hide attributes from the schema. This helps tidy a workspace, but does not help improve the translation performance. However, some formats (mostly databases) also have a setting for "Attributes to Read" and using this will help performance.*
{% endhint %}
Transformers that can remove attributes are:
* AttributeKeeper
* AttributeManager
* AttributeRemover
* BulkAttributeRemover
## Removing Attributes
The AttributeManager and AttributeRemover have the same technique; select an attribute to be removed:
Attributes can be removed in the AttributeManager by selecting it and clicking the - button. Alternatively, you can change the action field from Do Nothing to Remove.
Notice in the above that three attributes have been removed. The output attribute (when selected) shows no output name, to demonstrate it being absent from the output schema.
## Keeping Attributes
The AttributeKeeper transformer carries out the same function but approaches it from the opposite direction. It lets the user specify which attributes are not to be removed; in other words, this transformer lets the user specify which ones to keep.
So, the AttributeManager should be used where one or two attributes are to be removed, but the majority of them kept. The AttributeKeeper should be used when the majority of attributes are to be removed, and only one or two of them retained.
## Bulk Attribute Removal
The BulkAttributeRemover - like the BulkAttributeRenamer - lets the user carry out a process on multiple attributes. In this case, instead of being able to select all attributes, the user enters a string-matching expression to define which attributes to remove:
Here the user is removing all attribute whose name ends in the word "Count."
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://1spatial.gitbook.io/fme-form-beginner/transformer-usage/managing-attributes/removing-attributes.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.