Bricklink<->LEGO Color Translation Table

[Giantorange]

15 hours ago, koalayummies said:

Bricklink should just get their nonsense together already and finally use the official Lego color names. Bluish? What are they, ages 4-7?

There are only 117,000 types of item listed on Bricklink, shouldn't take long for the 10,000 sellers to get all their stock relabelled.

[Aanchir]

9 hours ago, zux said:

I think it would be better to be done the other way around, where TLG adopt Bricklink's (or better name it call it community) colour naming standard, as it is much more clear. TLG has quite vague names to be honest. Do you know what "light reddish violet" [TLG] colour is? Pink!

Light Reddish Violet is a pretty common-sense name as I see it, following more or less the same naming rules as many other colors in the LEGO palette. It's two shades lighter than Bright Reddish Violet, just as Light Yellowish Orange is two shades lighter than Bright Yellowish Orange or Light Bluish Green is two shades lighter than Bright Bluish Green. Easy-peasy!

Additionally, a lot of color names that are common sense in English might not be in Danish or vice-versa.

In general, I prefer LEGO color names by virtue of them not referring to totally different colors by the same name. Copper's the most egregious here. BrickLink's "Copper" refers to the official colors 139 Copper, 176 Red Flip/Flop, 189 Reddish Gold, 300 Copper, Drum Lacquered, and 346 Copper Metallic, all of which are easy to tell apart with the naked eye. 300 Copper, Drum Lacquered isn't even a "pearl" color like the others.

[koalayummies]

11 hours ago, Giantorange said:

There are only 117,000 types of item listed on Bricklink, shouldn't take long for the 10,000 sellers to get all their stock relabelled.

That's grossly misleading, that total is from the entire bricklink 'catalog' which includes: sets (14,615), minifigures (10,360), books (4,088), gear (10,917) and Lego catalogs (3,883) which don't require color naming specific parts. ~50,000 parts and no they shouldn't take long the parts should be in bins; these sellers aren't individually pre-bagging and labeling every piece into single serving sizes.

In any case not changing to the official names because it'd be inconvenient for third party sellers who were using unofficial names is not a strong argument. A truly savvy seller should already be dual-labeling having noticed the regularly reoccurring Lego official color name discussions. A number of bricklink sellers clearly use B&P (or abuse depending on viewpoint) so they're familiar with many of the official names already.

14 hours ago, zux said:

I think it would be better to be done the other way around, where TLG adopt Bricklink's (or better name it call it community) colour naming standard, as it is much more clear. TLG has quite vague names to be honest. Do you know what "light reddish violet" [TLG] colour is? Pink!

 

4 hours ago, Aanchir said:

Easy-peasy!

Additionally, a lot of color names that are common sense in English might not be in Danish or vice-versa.

Agreed.

Many in the Lego community understand why TLG doesn't like English speakers adding an 's' onto their company and product name in plurality yet even those who understand that still attempt to force the English language domination of dictating what works best in their subjective opinion. If the names that the Danish company Lego has chosen work best for Lego and translating then that is what is best, not what some English-speaking average consumer would prefer simply because they've been using a third party's arbitrary naming convention and are thus resistant to change.

Edited June 20, 2018 by koalayummies

[Giantorange]

16 hours ago, koalayummies said:

That's grossly misleading, that total is from the entire bricklink 'catalog' which includes: sets (14,615), minifigures (10,360), books (4,088), gear (10,917) and Lego catalogs (3,883) which don't require color naming specific parts. ~50,000 parts and no they shouldn't take long the parts should be in bins; these sellers aren't individually pre-bagging and labeling every piece into single serving sizes.

In any case not changing to the official names because it'd be inconvenient for third party sellers who were using unofficial names is not a strong argument. A truly savvy seller should already be dual-labeling having noticed the regularly reoccurring Lego official color name discussions. A number of bricklink sellers clearly use B&P (or abuse depending on viewpoint) so they're familiar with many of the official names already.

 

Not really at all.  I have  a small store, but I still have 5,000 different lots.  If I start to get orders through saying 'brick yellow' I'm clearly going to have to re-reference all my storage for 'tan'.  This isn't because everything is pre-bagged, it's because a Bricklink order will tell me which tray/box/drawer to look in for the part.  If this gets messed up, even at 30 sec. per lot to change the description that's a couple of days of non stop work.

Saying 'truly savvy sellers should also be doing x' is also not going to bite, as the colours have been referenced as they are right back to the days when Peeron was the prime source for information.  I would be fairly confident that the 'newer' dark gray is referred to as 'DBG' on this site far more often than it is as  'Dark Stone Gray'.

I would say rather that truly savvy sellers will be selling on both Brickowl and Bricklink, and therefore will be able to cope with either naming convention.

It's a bit like metric and imperial,  we really should have just one standard, but most people can cope with either, but changing from one to the other is not trivial.

 

 

[koalayummies]

4 hours ago, Giantorange said:

It's a bit like metric and imperial,  we really should have just one standard, but most people can cope with either, but changing from one to the other is not trivial.

Yes, the US should switch to metric and its Dark Stone Grey.

[Giantorange]

14 hours ago, koalayummies said:

Yes, the US should switch to metric and its Dark Stone Grey.

You lot need to learn to spell 'tyre' correctly.  Makes is much harder for me to list items when the descriptions aren't in proper English :P

 

[hsousa]

Regarding on-topic, I use this table, helps me immensely:

 

https://www.ldraw.org/article/547

[Aanchir]

Since this topic has been revived, I'll mention that this is the best, most thorough table I'm currently aware of! And the colored cells link to example photos of the colors on Rylie's Flickr.

https://ryliehowerter.net/colors.php

[JesseNight]

I have to agree with what's been said before, it bugs the hell outta me that BL doesn't use official Lego color names... as well as official part numbers for some parts (especialy printed ones). That's honestly even worse bc the common colors at least stick once you figured it out, I can't say the same about part numbers...

And to comment on Giantorange's message from 6 years ago, no the sellers won't have to change anything bc listed parts go by an ID number in the database. All they gotta do is change the color name that goes with the ID number. Or at least take it upon themselves to publish a conversion chart.

[MAB]

12 hours ago, JesseNight said:

I have to agree with what's been said before, it bugs the hell outta me that BL doesn't use official Lego color names... as well as official part numbers for some parts (especialy printed ones). That's honestly even worse bc the common colors at least stick once you figured it out, I can't say the same about part numbers...

And to comment on Giantorange's message from 6 years ago, no the sellers won't have to change anything bc listed parts go by an ID number in the database. All they gotta do is change the color name that goes with the ID number. Or at least take it upon themselves to publish a conversion chart.

Bricklink evolved independent of LEGO, and internal LEGO code names were not public knowledge. Bricklink's language therefore evolved independently. I have used BL for many years and so I tend to use BL's colour names as they are the ones I am used to. To me, they make more sense than LEGO's names but that might be because that I was I have used for so long. There is also the issue that BL recognises some colour variations that LEGO does not, and I think there are some cases the other way around.

Most (new) printed parts do have the official part numbers, so you can search for those, even if the base part number is made to fit in with the regular BL numbering scheme.

[JesseNight]

Oh it doesn't even matter to me which are used... The problem lies in the fact that there's different standards (color names and part IDs) for the same things and it's confusing when wanting to find parts on both BL and PAB, or wanting to find a part from irl instruction sheet in BL's Studio. It causes a lot of unnecessary confusion. Even more if you see Brickowl's part IDs are yet different ones from either BL and TLG.

I myself am more used to BL's color names too, but the fact is that TLG won't ever change their database as the official owner of these parts. Just would be great if it were the same all across the board.

I might think of making a colors sheet but I'd be surprised if someone hasn't already.

On 2/27/2024 at 10:46 AM, MAB said:

Most (new) printed parts do have the official part numbers, so you can search for those, even if the base part number is made to fit in with the regular BL numbering scheme.

The basic part numbers match yes, but the print suffixes do not.
For example 3068 tile 2x2 with the new modern classic space logo print, released with the new 2024 space sets: 3068bpr0699 at TLG, 3068bpb2339 at BL.

Edited February 28, 2024 by JesseNight

[MAB]

11 hours ago, JesseNight said:

The basic part numbers match yes, but the print suffixes do not.
For example 3068 tile 2x2 with the new modern classic space logo print, released with the new 2024 space sets: 3068bpr0699 at TLG, 3068pb2339 at BL.

At bricklink, do you mean 3068bpb2339? Where does the other number come from, as LEGO call this part  "FLAT TILE 2X2, NO. 699" with part number 6465626. That part number from the LEGO parts database is used on BL.

[JesseNight]

Oops, yeah I meant that BL number (corrected it).
I see I mixed up even more numbers, 3068bpr0699 being the LDraw number.
I suppose this only amplifies my point, having 4 or possibly even more numbers for a single part gets confusing! I'm not pointing fingers at anyone bc it's great having all these websites and programs around, just wish they all used the same standard (or correct it after TLG makes it public).

[edit]
LEGO part number 6465626
Design number 105854 (came across this on Brickset)
LDraw 3068bpr0699
Bricklink 3068bpb2339
Brickowl 726374
(so that's 5 already...)

Edited February 28, 2024 by JesseNight

[MAB]

19 hours ago, JesseNight said:

Oops, yeah I meant that BL number (corrected it).
I see I mixed up even more numbers, 3068bpr0699 being the LDraw number.
I suppose this only amplifies my point, having 4 or possibly even more numbers for a single part gets confusing! I'm not pointing fingers at anyone bc it's great having all these websites and programs around, just wish they all used the same standard (or correct it after TLG makes it public).

 

LEGO's part numbering scheme is rather useless, as it doesn't allow users to identify base parts. BL (and LDraw) use the base part then use their own numbering scheme. That cataloguing is their property. When Brickowl first started, BL objected to Brickowl using the same catalogue numbers as that was BL property. Similarly, LEGO doesn't really care about naming of parts, and BL names are much more user friendly for searching for parts. This has the downside that the description they use is their property, so cannot be used by others unless they have permission.