# Centralized

#### You Don’t Really Own Your NFT

There’s actually some merit to this – as mentioned previously, when you buy an NFT, you generally aren’t purchasing a digital good or piece of art. &#x20;

The art that represents most NFTs is simply too large to be hosted on a blockchain, and storing even a modest picture could cost thousands of dollars.  As such, the assets themselves need to be stored on a separate server, and the NFT itself is little more than a link that points to the address of this database.

&#x20;    **Metadata of an actual NFT that includes the name, description and a URL to where its stored**

<figure><img src="/files/T7BRs85qKjExekmfnjje" alt=""><figcaption></figcaption></figure>

This scares some people – and rightfully so.  If your image is stored on a third-party, centralized server, who is to say that they can’t replace the image?&#x20;

Fortunately, many projects are shifting to decentralized storage services such as Filecoin’s IFPS and Arweave.  These services use blockchain technology to encrypt and store data across several different devices, offering the same advantages as a standard database, with the added benefits that no one entity controls your asset. &#x20;

In addition, many newer NFTs – such as Chainrunners – are opting for simpler formats that allow them to store all of their data “on-chain”.&#x20;


---

# Agent Instructions: 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://www.digitalnations.xyz/web3-overview/the-web3-ecosystem/nfts/criticisms-of-nfts/weak-arguments-against-nfts/centralized.md?ask=<question>
```

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.
