<blockquote>
<pre><code>27GB as of 2020-06-14 
</code></pre>
</blockquote>

<p>You yourself can check this via going to <code>.bitcoin/blocks/index</code> folder. Where .bitcoin folder is usually hidden folder on home when using linux. </p>

<p>It depends if you have pruned than the index folder might appear less in size. As of today my index folder is <code>105.4 MB</code> since I've <code>prune=1000</code> and it would remain the same in future as well.</p>

<p>Our question is answered <a href="https://bitcoin.stackexchange.com/questions/48481/how-much-extra-disk-space-does-txindex-1-require">here</a> as well. Please check comment by <a href="https://bitcoin.stackexchange.com/users/24925/anonymous">@anonymous</a></p>

CC BY-SA 4.0
2020-06-17T01:48:45.537Z
`-txindex` and `-prune` are exclusive, only one of the two may be active at the same time. `-txindex` is inactive by default, and your folder size is smaller because you don't have a complete transaction index.
Murch
CC BY-SA 4.0
2020-06-17T06:56:51.713Z
@Murch so if I have pruned=1000 doesn't it effect the size of transaction index? I think it will reduce the size.
Haseeb Saeed
CC BY-SA 4.0
2020-06-17T16:37:02.820Z
What I meant was that `txindex` builds a complete transaction index which is 27 GB. This is incompatible with running a pruned node. Your node is running in pruned mode, so it cannot be running with a txindex at the same time. I'm not sure whether the index folder of a pruned node would be smaller than that of an archival node that doesn't build a transaction index.
Murch
CC BY-SA 4.0
2020-06-17T17:24:50.123Z
@Murch yes it is smaller I have tested
Haseeb Saeed
CC BY-SA 4.0
2020-06-15T15:18:42.903Z
2020-06-15T15:18:42.903Z
Haseeb Saeed
<p>Due to reputation limitations, I cannot ask for an update on this question:</p>
<p><a href="https://bitcoin.stackexchange.com/questions/48481/how-much-extra-disk-space-does-txindex-1-require/">How much extra disk space does txindex=1 require?</a></p>
<p>What is the current size of the txindex folder when txindex=1 is set in the bitcoin.conf file on a fully synced full node?
As pointed out in the referenced post, the size should now be around 28GB?</p>
<p>Thanks!</p>

<full-node><pruning><storage><txindex>
What is the current size of txindex folder when txindex=1 set?
Johannes Rottenkolber
# What is the current size of txindex folder when txindex=1 set?

(Asked by: username_0 on 2020-06-14)

Due to reputation limitations, I cannot ask for an update on this question:

[How much extra disk space does txindex=1 require?](https://bitcoin.stackexchange.com/questions/48481/how-much-extra-disk-space-does-txindex-1-require/)

What is the current size of the txindex folder when txindex=1 is set in the bitcoin.conf file on a fully synced full node?
As pointed out in the referenced post, the size should now be around 28GB?

Thanks!

**Tags:** full-node, pruning, storage, txindex


---

## 1 answers

### Answer by username_1 on 2020-06-15. Score: 3 | Accepted answer

> ```
> 27GB as of 2020-06-14 
>
> ```

You yourself can check this via going to `.bitcoin/blocks/index` folder. Where .bitcoin folder is usually hidden folder on home when using linux.

It depends if you have pruned than the index folder might appear less in size. As of today my index folder is `105.4 MB` since I've `prune=1000` and it would remain the same in future as well.

Our question is answered [here](https://bitcoin.stackexchange.com/questions/48481/how-much-extra-disk-space-does-txindex-1-require) as well. Please check comment by [@anonymous](https://bitcoin.stackexchange.com/users/24925/anonymous)

> **Comments:**
> **username_2**: `-txindex` and `-prune` are exclusive, only one of the two may be active at the same time. `-txindex` is inactive by default, and your folder size is smaller because you don't have a complete transaction index.  
> **username_1**: @username_2 so if I have pruned=1000 doesn't it effect the size of transaction index? I think it will reduce the size.  
> **username_2**: What I meant was that `txindex` builds a complete transaction index which is 27 GB. This is incompatible with running a pruned node. Your node is running in pruned mode, so it cannot be running with a txindex at the same time. I'm not sure whether the index folder of a pruned node would be smaller than that of an archival node that doesn't build a transaction index.  
> **username_1**: @username_2 yes it is smaller I have tested  

---

