null Skip to main content

GF 238 MotorMark Armor - 12 mil Gloss UV Lam, Clear Permanent Adhesive

Item#Item NameRegular PriceSale PriceQty
GF 238 MotoMark

GF 238 MotoMark® “ARMOR” 12.0 mil is a flexible gloss clear laminate that offers UV protection and is designed for use as a protective overlaminating film when used in combination with GF 235 MotoMark® “GRIP” vinyl. MotoMark® is recommended for a variety of applications including Quads, Snowmobiles, Motocross, Powersport Vehicles, Helmets and Carts. The adhesive system is formulated to adhere to most common solvent, eco-solvent, latex, thermal, UV, offset and screen inks.

APPLICATIONS

  • General Signage
  • Vehicle Graphics

Ink Compatibility

Not Applicable

 

This is a very thick film, can my cutter cut through MotoMark®?

Most cutters, printer/cutters and cutting software have specific instructions on how to achieve this. General Formulations has a set of general guidelines on this topic. Please see our website and under technical tips see “Cutting Thicker Materials”.
 

Will GF 238 adhere to all ink types?

The adhesive system is formulated to adhere to most common solvent, eco-solvent, latex, thermal, UV, offset and screen inks. However, specific formulations must be tested before use. Some ink may contain excessive flow additives that could reduce adhesion of this product. Testing is always suggested before production.
Free Local Delivery
Next Day Delivery
Order By 5PM CST
Save 2% On Pickup
Low Rate Financing
Flat Rate Shipping
Join Our Mailing List

Sign up to receive updates, special offers, and discounts!

// 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