<p>Your scriptSig is too big! It is limited to 200 kbytes, and you've got <em>1400 inputs @ 0.2kbyte</em> (best case scenario): <code>1400x 200 = 280</code>kbyte.</p>

<p>Try using half the inputs (preferably newer inputs) to cut the scriptSig down in size.</p>

CC BY-SA 3.0
2015-04-30T05:08:26.887Z
Why newer inputs? Wouldn't older inputs have a higher priority?
Nick ODell
CC BY-SA 3.0
2015-04-30T05:17:53.553Z
@NickODell Yep, just "picking the better half" so to speak
Wizard Of Ozzie
CC BY-SA 3.0
2015-04-30T06:01:03.627Z
@WizardOfOzzie The older ones are the better ones.
Pieter Wuille
CC BY-SA 3.0
2015-04-30T06:46:32.203Z
@PieterWuille I personally would try sweeping up the *worse (newer) ones* to hopefully comprise a fee-free Tx. I'm not disputing the priority being inversely proportional to age; it's more a difference in opinion of how to handle dust, but tbh, I'll defer to you  here!
Wizard Of Ozzie
CC BY-SA 3.0
2015-04-30T10:19:46.757Z
Priority is proportional to age, not inversely. And every output spent has its own scriptSig in the txin, which is around 105 bytes total per output spent.
Pieter Wuille
CC BY-SA 3.0
2015-04-30T23:21:33.087Z
Thanks for your help. I have been able to send out various smaller sized amounts (0.0004 BTC). I looks like I will have to slowly transfer out the remaining balance in smaller transactions.
bob
CC BY-SA 4.0
2020-08-25T12:19:27.603Z
I had over 1600 Transactions and was getting "Transaction too large" message. I cut down the inputs to 600 transactions and was able to send without issue. Your answer above helped me resolve this.
Raul Jimenez
CC BY-SA 3.0
2015-04-30T05:03:51.510Z
2015-04-30T05:03:51.510Z
Wizard Of Ozzie
<p>I have over 1400 small transactions in my wallet that add up to a little over 0.2 BTC. I am trying to send them, but keep getting a transaction too large error. I have tried to set a custom transaction fee, but am unable to still send. I am using Bitcoin core v0.10 on Windows. I have looked at this thread but am still unable to find a solution. </p>

<p><a href="https://bitcoin.stackexchange.com/questions/5583/how-can-i-combine-all-the-tiny-amounts-ive-received-to-minimise-transaction-fee">How can I combine all the tiny amounts I&#39;ve received to minimise transaction fees, and do I need to?</a></p>

CC BY-SA 3.0
2015-04-30T00:30:50.840Z
Does it say 'Transaction too large' or 'Transaction too large for fee policy?' They're different errors.
Nick ODell
CC BY-SA 3.0
2015-04-30T02:10:49.843Z
It says just says "Transaction too large"
bob
<transactions><bitcoin-core>
Transaction too large error
bob
# Transaction too large error

(Asked by: username_0 on 2015-04-30)

I have over 1400 small transactions in my wallet that add up to a little over 0.2 BTC. I am trying to send them, but keep getting a transaction too large error. I have tried to set a custom transaction fee, but am unable to still send. I am using Bitcoin core v0.10 on Windows. I have looked at this thread but am still unable to find a solution.

[How can I combine all the tiny amounts I've received to minimise transaction fees, and do I need to?](https://bitcoin.stackexchange.com/questions/5583/how-can-i-combine-all-the-tiny-amounts-ive-received-to-minimise-transaction-fee)

**Tags:** transactions, bitcoin-core

> **Comments:**
> **username_1**: Does it say 'Transaction too large' or 'Transaction too large for fee policy?' They're different errors.  
> **username_0**: It says just says "Transaction too large"  

---

## 1 answers

### Answer by username_2 on 2015-04-30. Score: 3

Your scriptSig is too big! It is limited to 200 kbytes, and you've got *1400 inputs @ 0.2kbyte* (best case scenario): `1400x 200 = 280`kbyte.

Try using half the inputs (preferably newer inputs) to cut the scriptSig down in size.

> **Comments:**
> **username_1**: Why newer inputs? Wouldn't older inputs have a higher priority?  
> **username_2**: @username_1 Yep, just "picking the better half" so to speak  
> **username_3**: @username_2 The older ones are the better ones.  
> **username_2**: @username_3 I personally would try sweeping up the *worse (newer) ones* to hopefully comprise a fee-free Tx. I'm not disputing the priority being inversely proportional to age; it's more a difference in opinion of how to handle dust, but tbh, I'll defer to you  here!  
> **username_3**: Priority is proportional to age, not inversely. And every output spent has its own scriptSig in the txin, which is around 105 bytes total per output spent.  
> **username_0**: Thanks for your help. I have been able to send out various smaller sized amounts (0.0004 BTC). I looks like I will have to slowly transfer out the remaining balance in smaller transactions.  
> **username_4**: I had over 1600 Transactions and was getting "Transaction too large" message. I cut down the inputs to 600 transactions and was able to send without issue. Your answer above helped me resolve this.  

---

