null Skip to main content

GF 110 EraseMark Pro - 2 Mil Gloss Clear, Clear Permanent Adhesive

Item#Item NameRegular PriceSale PriceQty

EraseMark Pro™ 110 is a 2-mil clear polyester laminate with a high performance hard coated engineered surface. The scratch and abrasion resistant polyester film is coated with a permanent solvent acrylic pressure sensitive adhesive on a smooth paper liner. This film works well with quality dry erase markers and its anti-graffiti properties allows for easy removal of permeant markers and crayons. EraseMark Pro™ 110 has a 5 year interior durability with proper care and cleaning.

APPLICATIONS

  • General Signage
  • POP & Indoor Signage
  • Windows
  • Walls

INK COMPATIBILITY

Not Applicable

 

What types of applications is GF 110 good for?

GF 110 was formulated for high-use dry erase applications such as hospital boards, conference rooms, menu boards, restaurants and schools. It works well for applications where the written information needs to change frequently. The hard-coated engineered surface will stand up to repeated use and cleaning.

Do I need to do any surface prep on the GF 110 Dry Erase film surface before using?

In most cases the dry erase film should be ready for use right out of the box, but we do recommend a quick wipe down of the surface after the application is complete. This will help with maximum marker bond to the surface and eliminate streaking.

// Uses React's native (unpatched) value setter + a real dispatched event, // so the app's own onChange / validation / append logic fires correctly. // build the visible field the user will actually type into // copy the real field's classes + computed styles so it looks identical // preload with existing value (formatted) if the real field already has one // hide the real field visually but keep it in the DOM and functional, // so your app's own validation / append event still works as before // place the visible field right where the real one used to be // send only the plain digits to the real field — this matches what // the numeric field type expects, so no "invalid phone number" error // keep focus/blur events flowing to the real field too, in case your // app's validation triggers specifically on those